Most pages are written to be read top to bottom. Cited pages are written to be read in fragments. This is the edit list, in the order that produces the biggest change.
1. Write the answer in the second sentence
A section that opens with context forces the model to reconstruct the point. Open with the answer, then justify it.
Before:
Choosing a static site generator involves many considerations. Performance, ecosystem, authoring experience and deployment all play a role. With that in mind, we can look at…
After:
A static site generator with built-in content collections is the fastest way to ship a documentation site. It removes the API layer, so pages are HTML at build time; nothing has to be fetched before the text exists.
The second version can be lifted whole. The first cannot.
2. Make every heading a question someone would ask
Headings are chunk titles. Use the phrasing a user would type, not a chapter label.
| Instead of | Write |
|---|---|
| Overview | What does GEO change about SEO? |
| Configuration | How do I set the site name and languages? |
| Performance | How fast does the page load on a slow connection? |
3. Keep each section self-contained
Engine passages get separated from their neighbours. Restate the subject at least once per section, and avoid pronouns whose antecedent lives two screens up. If a section only makes sense as step three of a sequence, say “step three of X” inside it.
4. Put the specific in the sentence
Numbers, dates, commands, file paths and names are what make a passage worth quoting. They also make it easy to verify, which is what grounding rewards.
Weak: "the config file supports several options"
Citable: "site.config.yaml sets languages: [en, zh] and nav entries; both are read at build time"
5. Add the machine-readable layer
Three things, in order of payoff:
Article/FAQPagestructured data withheadline,datePublished,dateModifiedandauthor. It does not boost a citation on its own; it removes ambiguity about when and by whom the page was written.- A sitemap that lists real, canonical URLs, updated at build time.
llms.txt— a plain-text map of your most useful pages. Treat it as a hint for crawlers and a convenience for people wiring your site into their own tooling, not as a ranking signal.
# llms.txt (keep it short)
# HowGEO
> Practical notes on being quoted by AI search.
## Guides
- /guides/what-is-geo/: what GEO is, in one page
- /guides/make-a-page-citable/: the rewrite checklist
6. Kill the duplicates
Two URLs with the same body, a paginated archive that repeats excerpts, tag pages that mirror posts: each of these is a version of the same passage competing with itself. Canonical tags handle most of it; deleting the thin ones handles the rest.
7. Date it honestly
A visible “updated” date that changes without edits teaches the engine that your dates carry no information. Update the date only when the content changed, and note what changed.
The checklist
- Every section answers its own heading in the first sentence
- Headings phrased as questions where a question exists
- No section depends on the previous one for meaning
- Specific values inline, not in an attachment
- Structured data with real dates and an author
- One canonical URL per idea
- A short
llms.txtlisting the pages worth reading