Fast answer
Open every section with the answer in one sentence, then explain it. Use the question as the heading. Put numbers, dates and limits in plain text. One page, one question, one clear claim.
Answer first, explain second
This is the whole technique. A section that begins “Choosing a host is an important decision that many founders find difficult…” gives an engine nothing to quote. A section that begins “Shared hosting costs $3–10 a month and is enough for a brochure site under 10,000 visits a month” gives it a complete, attributable fact.
Write the quotable sentence first. Then spend three paragraphs justifying it for the human who wants to understand why. Both audiences get what they came for, in the order they need it.
Use the question as the heading
Headings are the map a retrieval system uses to decide which passage answers which query. A heading like “Our approach” tells it nothing. “How much does a launch-ready site cost?” tells it exactly where to look — and it is the phrasing a real person types.
Keep one intent per section. If a heading needs an “and”, split it into two pages or two sections.
Make facts liftable
- Numbers in text, not images. A price inside a graphic is invisible to extraction.
- Dates on claims. “As of October 2026” prevents a stale page from being cited as current.
- Named limits. “We do not handle tax filings” is more quotable than a list of things you do.
- Definitions in one sentence. If you use a term, define it once, plainly, on the page that matters.
- Tables for comparison. Rows and columns survive extraction better than prose comparisons.
Stop doing these five things
- Burying the conclusion at the bottom, school-essay style.
- Writing “we believe”, “we are passionate about”, “world-class”. None of it can be verified or quoted.
- Putting key copy inside a slider, accordion or tab that only renders on interaction.
- Repeating the same paragraph across five pages to fill space. Duplicate passages compete with themselves.
- Leaving pages undated and unrefreshed for two years while the facts inside them decay.
Refresh on a calendar
Set a six-month reminder per page. Update the numbers, keep the URL, change the date. A page that has been quietly maintained reads as more trustworthy to both a human and a retrieval system than a new page published to replace it.
Checklist for this step
- Every section opens with a one-sentence answer
- Headings are phrased as the question a customer asks
- One intent per page, no “and” in the title
- All prices and limits in plain text, not images
- A visible “last updated” date on every guide
- No key content hidden in sliders or tabs
- Six-month refresh reminder set per page
Common mistakes
- Rewriting everything at once. Do one page, wait two weeks, re-test, then continue.
- Writing for the algorithm before writing for a person. Both read the same opening sentence.
- Adding an FAQ block at the bottom while the body stays vague. The block does not rescue the page.
- Changing URLs during the rewrite and forgetting redirects.
R — Rewrite in this order
Home page first, because it defines the entity. Then the one page that answers your most expensive question. Then the About page. Everything else can wait until those three are right.
Keep the order.
Every step assumes the one before it is finished. Skipping ahead is how sites end up rebuilt twice.