Website content now has three readers at once. A person deciding whether to trust you. Google, deciding where to rank the page. And AI answer engines, deciding which sentence of the page to quote. The good news is that they want almost the same thing. The bad news is that most website copy serves none of them, because it was written to sound impressive rather than to answer anything.
This post covers the page brief, the structure, the voice rules we wrote for rebuilding our own site, and before and after examples.
Why does most website content fail?
Read a typical home page aloud: "We empower forward-thinking teams to unlock growth with innovative solutions." Ask what question that answers. None. It cannot be quoted, it cannot rank for anything a buyer types, and the buyer still does not know what you sell.
The failures are consistent:
- No question. The page has no single thing it answers.
- Answer last. The useful sentence arrives after three paragraphs of warm-up.
- Adjectives instead of facts. "Powerful", "seamless", "best-in-class", with nothing to check.
- Several pages answering the same thing, none of them well. Our own site had eight near-duplicate posts about share of voice before we merged them.
What goes in a page brief?
Before anyone writes, fill in five lines:
- The question. The one question this page answers, in the buyer's words. "How much does Attensira cost?", not "Pricing".
- The answer. In 40 to 60 words, written now, before the page. If you cannot write it, the page is not ready.
- The proof. The specifics that make the answer believable: numbers with their source and date, an example, a screenshot of the real product.
- The objections. The two or three doubts a buyer will have on reading the answer.
- The next step. The one thing you want the reader to do after.
That brief is the page. Everything else is supporting detail.
How should the page be structured?
| Part | What it does |
|---|---|
| Main heading | Names the question or the subject |
| The answer | The 40 to 60 words from the brief, directly under the heading |
| Proof | The specifics, shown rather than claimed |
| Question-shaped sections | One per objection or follow-up, each answering in its first sentence |
| FAQ | Short answers to the remaining questions |
| Next step | One clear action |
| Date | When the facts were last checked, for pages that change |
Every section should make sense if someone reads only that section, because that is how AI engines read it: they lift passages. See answer blocks and AI search chunking for why.
What voice rules work?
When we rebuilt our own site we wrote the voice down as rules, so every page would sound like the same company. The ones that transfer to any business:
- Numbers over adjectives. "Opened 3 pull requests, drafted 5 pitches" instead of "accelerates your growth".
- Every number carries its sample size and date. "Cited in 4 of 14 answers on ChatGPT, 2026-10-02", never a bare figure.
- Say "we don't know" when you don't. "Not measured" and "no change we can prove" are sentences you are allowed to print.
- Promise the work, not the outcome. You can promise what you will do. You cannot promise what Google or a buyer will do.
- Headings are questions a reader would type. "Will it publish without me?" rather than "Control".
- Sentence case, second person, short sentences, plain words.
- Label what is not shipped yet as coming. Never describe a plan as a feature.
Writing those rules down did more for the consistency of our copy than any amount of editing, because every writer, human or agent, worked from the same page.