How to write a page an AI assistant will quote

When an AI assistant answers with web search, it reads several pages and builds its answer from passages it can lift with confidence. A page gets cited when one of its paragraphs answers part of the question cleanly. The way you write each paragraph matters as much as the topic of the page.

Answer in the first two sentences

Put the direct answer at the top. If the page targets "how much does Acme Voice cost?" (Acme Voice is a made-up product for this example), the opening should give the price and what changes it, before any background.

Weak opening:

Voiceovers have come a long way. In this guide we will look at the many factors that can influence what you pay.

Strong opening:

Acme Voice is free for up to 10 minutes of audio a month, with a watermark. The $19 Pro plan removes the watermark, allows commercial use and adds voice cloning.

The second version can be quoted on its own. The first gives an assistant nothing to use.

Make every paragraph stand alone

Assistants often take one paragraph out of your page. Write each one so it makes sense without the rest: open with its point, name the subject instead of saying "it" or "this tool", and avoid "as mentioned above" or "see below".

Keep paragraphs short, roughly under 80 words, and give each one at least one concrete detail: a number, a limit, a comparison or a named example. Vague paragraphs ("our platform offers powerful features for every need") are skipped because they answer nothing.

State facts the way you want them repeated

If your free plan includes three exports a month with no watermark, write exactly that, in one sentence, on the page where buyers look for it. Assistants repeat what they read. When the fact is buried in a pricing table rendered by JavaScript, or phrased differently on three pages, they guess, and the guess is often an outdated number from a third-party article.

Keep one source of truth for prices and limits, and update every page that repeats them when they change.

Use headings people would search

Phrase H2s and H3s as the questions buyers ask: "Is there a free plan?", "How does it compare with Descript?". Headings like "Overview" or "Why us" give the assistant no signal about what the section answers.

Compare honestly

"X vs Y" and "best tools for Z" are among the prompts assistants answer most often, and they lean on pages that compare fairly. A comparison that admits where a competitor is stronger reads as more credible than one where you win every row, to buyers and to models alike. Include prices, limits and dates, and link to sources.

End with an FAQ and mark it up

Close with four to six questions buyers ask, each answered in a short self-contained paragraph. Then add FAQPage structured data so search engines can parse the pairs:

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Is there a free plan?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. The free plan includes three exports a month with no watermark."
        }
      }
    ]
  }
</script>

Google limits when FAQ rich results appear, but the markup still describes your content in a form machines read reliably.

Check that crawlers can read it

None of this helps if the page content is rendered in the browser. Many AI crawlers do not run JavaScript, so make sure your text is in the HTML your server sends. Our post on AI crawlers and JavaScript explains how to check.

FAQ

How long should the page be?

Long enough to answer the question and the follow-ups buyers ask, usually 900 to 1,600 words for a guide or comparison. Length does not earn citations by itself; specific, quotable paragraphs do.

Should I write for AI or for people?

For people, in a structure assistants can use. Answer-first, specific and honest pages convert human readers better too.

Can AI write these pages for me?

It can draft them, as long as it works from your verified facts and you review the result. Promptvane's Content Agent drafts pages in this structure from the prompts you lose and the facts you confirm.