Built to be quoted, not just ranked.
Built to be found by search engines and answer engines alike.
Answer engines cite sources that read like sources.
This work is as much about how a site states a fact — answer first, question-shaped, citable — as about where it ranks. A paragraph that only makes sense after three sections above it never gets quoted.
- Define the organization once, and reference that identity from every page.
- Date everything, visibly and in schema, because undated pages get discounted.
- Write sections that stand alone, so any one of them can be lifted without losing its meaning.
- JSON-LD structured data across every page type
- One canonical organization identity, referenced site-wide
- Entity and @id architecture
- Content shaped to be quoted rather than skimmed
- Self-contained sections that survive being excerpted
- Visible publish and update dates, in the page and in schema
- FAQ schema
- llms.txt
- Citation monitoring across answer engines
- Rich Text Results in Search Results
Is this different from SEO?
It overlaps, but the unit is different. Search ranks pages; answer engines quote passages. That changes how a section has to be written, not just how a page is tagged.
How would we know it worked?
By being cited. At MID49 organic clicks rose 43.0% year over year on 3.7% more impressions — a ranking gain rather than a traffic gain, which is the shape you want.
Do we need to rewrite everything?
No. Structured data and entity identity come first because they are the cheapest to fix. Rewriting is targeted at the pages that are already close to being quoted.
What is llms.txt?
A plain file that tells answer engines what a site is and which pages are worth reading. It is cheap to deploy and it is deployed for MID49.