NOTE · 13 OCTOBER 2026
Write the paragraph an answer engine can quote
Why each important page needs one self-contained definition that matches its structured data, and how we write and check it.
Search used to send people to pages. Answer engines increasingly read the pages and write the answer themselves, citing a source when one makes the answer easier to trust. That changes what a page needs. Rankings still matter, but a page also has to contain a passage that can be lifted out and still make sense.
One paragraph that stands alone
We call it the definitional paragraph. It names the subject, says what it is, who it is for and what makes it different, in two to four sentences that do not depend on the layout, a previous section or an image. If you pasted it into an email to someone who had never seen the site, it would still be correct and complete.
Most product pages fail this test without anyone noticing. They open with a slogan, describe features in fragments next to icons and never say in a sentence what the product is. A reader can piece it together; a system choosing a passage to quote has nothing to choose.
The same facts everywhere
The paragraph has to agree with everything else the site says about the subject. The company name spelled one way, the product described with the same category, the same facts in the visible copy, the page metadata and the structured data. We keep those facts in one approved record and generate the markup from it, so the page and its data cannot drift apart.
Structured data never describes something a visitor cannot read on the page. Markup is a summary of the visible content, and claiming more in the markup than the copy says is the fastest way to make a site look unreliable to the systems reading it.
Readable without scripts
None of this helps if the paragraph only exists after a script runs. Not every crawler runs scripts, and Google's own documentation describes rendering as a separate step that can happen after the page is fetched. A page that renders in the browser can arrive almost empty. We check every priority route with a plain request and fix the rendering before writing a word, because a well written paragraph that is never fetched does nothing.
How we write them
We start from the questions buyers actually ask, taken from sales calls, support tickets and search data, and match each to the page that should answer it. The subject owner reviews every paragraph for accuracy; we review it for whether it stands alone. Then the paragraph goes live with its markup and its place in the internal links, so the page sits where the subject belongs in the site's hierarchy.
We cannot promise that an engine will cite a page. Engines choose their sources. What we can do is make sure that when they read the page, the best available answer to the question is sitting there in one paragraph, correct, consistent and easy to quote.
SOURCES
Where the facts come from
- Understand JavaScript SEO basicsGoogle Search Central
Talk it through with us
Send a short description of your system and the question this note raised. We reply with how we would approach it in your setup.