The old content playbook — pick keywords, publish weekly, wait for rankings — died of abundance. When anyone can generate a thousand competent words on any topic in a minute, competent words on a topic are worth what they cost. What still earns attention, in Google's rankings and in the answers AI engines assemble, is the content that could not have been generated: the piece that carries facts, numbers and experience that exist nowhere else. Happily, a real business produces those every single day.

It helps that the two audiences have converged. Google's systems increasingly reward demonstrated experience and first-hand knowledge; answer engines retrieve and quote sources they can verify. Both are, in different ways, asking the same question of every page: does the person who wrote this actually know something? Content strategy in 2026 is mostly the discipline of making your genuine knowledge legible.

Write what only you can write

The test for every piece before you write it: could a competitor — or a model — produce this without running your business? If yes, it will not move anything, however polished. If no, you have something. Your materials and where they come from. What actually goes wrong with the product and how you fix it. What a year of orders taught you about what people in your town really buy. The comparison you are qualified to make because you have used both.

• Answers to the questions your customers literally ask — in their words, not your category's jargon.
• Original numbers, however small: what you measured, counted or learned from your own orders and seasons.
• Honest comparisons that concede a point — the concession is what makes the recommendation citable.
• Process and experience pieces: how the thing is made, chosen, fitted, repaired. Experience is the one input that cannot be generated.
• Local and niche specificity — the narrower the question, the shorter the list of credible answers, and the more likely yours is the one that gets quoted.

Shape it for extraction

Knowing something is half the job; presenting it so a machine can safely lift it is the other half. Answer engines quote sentences, so write sentences that survive being quoted alone: the direct answer in the opening lines, headings phrased as the questions people ask, facts stated plainly rather than implied across three paragraphs. And keep your facts consistent across every page that mentions them — a delivery time stated three different ways on three pages reads, to a cross-checking machine, as a business not to be quoted.

Your inbox is the editorial calendar

The perennial small-business complaint — "I don't know what to write about" — has a mechanical answer: your customers tell you, daily, in their own words. Every question that arrives by web chat, SMS, WhatsApp or email is a search query with a name attached; if one person paid the social cost of asking, dozens typed it into a search box or an assistant. On a Phoxta business those conversations sit in one console, which turns topic research into a reading exercise: the questions your agent answers most often are, verbatim, the pages you should publish. And the loop closes neatly — the page you write becomes knowledge the agent answers from, so the same work serves the customer you have and the one still searching.

Cadence over bursts

The publishing pattern that works is unheroic: one genuinely useful piece a month, sustained, with an afternoon each quarter spent updating what you have already published — refreshing the numbers, correcting what changed, tightening the answer. Engines notice maintenance, and answer engines in particular prefer sources whose facts are current. A burst of ten posts followed by silence produces neither trust nor rankings; it produces an archive with a death date on it.

Search engines rank pages. Answer engines repeat sentences. The whole craft now is writing sentences worth repeating, on pages worth arriving at.

Knowing whether it works

Content moves slowly, so measure it patiently and honestly. Watch which pages earn search impressions for questions rather than just your name; ask the major assistants your customers' questions monthly and note when your pages start informing the answers; and watch the questions arriving in your own inbox — when customers start saying "I read your piece on this", the flywheel has engaged. What you should not measure is volume. Nobody is counting your posts except you.

The stack matters less than the knowledge, but it is not nothing: the content on a Phoxta storefront is data-driven and structured, so publishing and updating never involves a developer, and every piece lives on the same domain as the checkout it ultimately serves. The pricing page shows what is included. The knowledge — the only part that ranks — was always yours.