A journalist writes the story so that if the editor cuts it anywhere, what remains still makes sense. Headline, then the fact, then the detail, then the background. They call it the inverted pyramid and it exists because column space used to get cut without warning.
An answer engine cuts without warning. It takes one paragraph and discards the other forty. Write like the cut is coming, because it is.
The pattern
For every question your content addresses, the structure is the same three moves:
"How much does customs clearance cost in Port Klang?" beats "Our Approach to Pricing". The heading defines the topical boundary of the passage underneath it.
Complete, specific, and comprehensible with nothing above it. Include the numbers. Include the qualifier. This is the sentence that gets quoted.
This is where you earn trust with the human who clicked through. It is not wasted. It is simply not the part that gets retrieved.
Typical business page. "Pricing. At DNE we understand that every shipment is unique. Our team works closely with each client to understand their requirements and deliver a tailored solution. Contact us for a quotation."
Contains zero retrievable facts. Answers no sub-query. Will never be cited by anything.
Same page, rewritten. "How much does customs clearance cost at Port Klang? Standard import clearance for a single 20ft container at Port Klang typically runs RM450–RM850 in agent fees, excluding duties, taxes and port charges. Cost varies with commodity classification, whether a permit is required, and whether the shipment is FCL or LCL. Below is a breakdown of each component…"
Answers a real sub-query. Contains a number, a range, and the conditions. Survives being lifted out.
Things that quietly make a page unretrievable
- Pronouns and back-references across paragraphs. "This", "the above", "as mentioned". Each one breaks a passage that would otherwise stand alone.
- Answers split across two sections. The question in one place and the number in another means neither passage is complete.
- Vague headings. "Our Services", "Why Choose Us", "Solutions". They define no topical boundary, so the passage underneath belongs to no sub-query.
- Facts trapped in images. A price list rendered as a JPEG is a blank space to a text retriever. Put the numbers in HTML text, use the image as decoration.
- Burying the specific under the general. Three paragraphs of philosophy before the first concrete claim means the retriever scores your philosophy.
The tension with Google's advice, resolved
Google says you do not need to write in a special way for generative AI, and that its systems understand synonyms, semantic meaning and multi-topic pages. TIER A That is true and you should believe it.
What it means practically is that this chapter is not a compliance exercise with a gate at the end. There is no penalty for prose. What there is, is a competition between passages for each sub-query, and clarity wins ties. You are not obeying a rule. You are making it easier for a machine to choose you over an equally good competitor — and simultaneously making the page better for the human who arrives.
That is the correct mental model for almost every content recommendation in this book. Nothing here is a gate. Everything here is a tiebreaker, and in a field where thousands of pages are competing for three citation slots, tiebreakers decide outcomes.
Print your top service page. Take a highlighter and mark every sentence that states a specific, checkable fact — a number, a timeframe, a named process, a condition. If the page has fewer than five highlighted sentences, it is unretrievable regardless of how well it reads.
Turn every vague heading on your site into a question a customer would actually ask, and make the sentence directly beneath it answer that question completely.