How to write pages that AI assistants can quote

Short answer: put a direct, self-contained answer to the page's main question in the first two or three sentences, then use headings that match the follow-up questions people ask, and answer each one in a short paragraph or list that makes sense on its own. Be specific (names, numbers, who it's for), keep the text in the HTML rather than behind scripts, and keep the page accurate and dated.

Why does page structure matter for AI answers?

When an assistant searches the web, it doesn't read your page like a person scrolling from top to bottom. It splits pages into passages, picks the passages that best match the question and writes its answer from those.

So the unit that competes is the passage, not the page. A passage gets used when it:

• answers the question directly, without needing the surrounding text to make sense,
• says something specific enough to be useful in an answer,
• comes from a page the assistant found and could read.

Most marketing pages fail the first test. The answer is spread across a hero banner, three feature tiles and a testimonial carousel, and no single passage says plainly what the product is and who it's for.

The answer-first pattern

Start each page, and each section, with the answer:

Weak: "In today's fast-moving world, teams need tools that keep up. That's why we built…"

Strong: "Acme is time-tracking software for design agencies of 5–50 people. It records time against client projects and turns it into invoices in Xero or QuickBooks."

The strong version can be quoted on its own and still be correct. It names the category, the audience, the size and the integrations. An assistant answering "time-tracking software for small design agencies" has something concrete to work with.

Use headings that are real questions

Write headings the way people ask. Look at the questions buyers put to your sales team, in support tickets and in search ("People also ask" boxes are a good source), and use them nearly word for word:

• "How much does Acme cost?"
• "Does Acme work with Xero?"
• "Is Acme suitable for freelancers?"

Then answer each in the first sentence below it. This helps people skimming the page, it helps search engines match the page to questions, and it gives assistants clean question–answer pairs.

Make each passage self-contained

A passage lifted out of context should still be true and clear. In practice:

• Repeat the subject. "Acme integrates with Xero" rather than "It integrates with Xero".
• Avoid "as mentioned above". The assistant may never see "above".
• Keep units and conditions with the number. "£9 per user per month, billed annually" rather than "£9" in a pricing table header three screens away.
• One idea per paragraph. Short paragraphs map neatly onto passages.

Be specific and honest

Vague claims ("best-in-class", "powerful", "seamless") give an assistant nothing to repeat. Specific claims do:

• Who the product is for, and who it is not for.
• Prices, limits and plans, written out in text.
• Concrete comparisons: "Unlike X, Acme doesn't charge per client."
• Facts that can be checked elsewhere, so the page agrees with review sites and directories.

Saying who you're not for can feel risky, but it makes the rest of the page more believable, and it helps assistants recommend you for the right questions instead of the wrong ones.

Formats that work well

• Short lists for features, steps and criteria.
• Tables for comparisons and pricing, with plain text in the cells.
• Definitions in one sentence: "X is a Y that does Z."
• A short FAQ at the end for the follow-up questions.

A page template you can reuse

# [The question, or the product + category]

[2–3 sentence direct answer: what it is, who it's for, the key fact.]

## [Follow-up question 1]
[Answer in the first sentence. Detail after.]

## [Follow-up question 2]
[...]

## How does [product] compare with [alternative]?
[Honest comparison, ideally a small table.]

## Frequently asked questions
### [Question]
[Self-contained answer.]

Last updated: [date]

Technical basics that still matter

None of the writing helps if the page can't be found and read:

• Text in the HTML. Several AI crawlers don't run JavaScript. Check the page source.
• Crawlable. The right crawlers are allowed in robots.txt and not blocked by your CDN. See which AI crawlers to allow.
• Indexed and ranking. Assistants that search mostly read pages that rank for the queries they run. A perfectly written page on page five of the results rarely gets used.
• Dated. A visible "last updated" date helps readers judge freshness, and keeping it honest helps you remember to review the page.

Frequently asked questions

Should I rewrite all my existing pages for AI?

No. Start with the few questions where buyers ask assistants and you aren't mentioned. Write or extend one page per question. Rewriting good existing copy for its own sake rarely pays off.

How long should a page be?

As long as it takes to answer the main question and its obvious follow-ups well. Length isn't a goal in itself. A clear 600-word page beats a padded 3,000-word one.

Do I need a separate page for every question?

Not always. Closely related questions can share a page with one heading each. Distinct intents ("pricing" vs "alternatives to X") usually deserve their own pages.

Is writing for AI different from writing for people?

Mostly no. The habits that help assistants (answer first, be specific, use clear headings) also help people who skim. That's the point: GEO rewards clarity, not tricks.