Liftable Content
Engines lift passages, not pages. This chapter covers the shape of a quotable passage: the answer in the first sentence, sections that survive extraction, specificity with edges, and the case for publishing your pricing.
Part III starts here, with the work that moves the most numbers for the most businesses: writing pages the engines can quote. Chapter one told you engines lift passages, not pages. This chapter is about building passages worth lifting, and it will change how you write everything on your site.
Answer first, evidence second
The structure that gets lifted is almost boringly consistent: a heading that states or implies the question, a first sentence that answers it completely, then the evidence and nuance underneath. Most business writing does the opposite. It warms up, builds context, tells a story, and delivers the answer in paragraph six, where no machine and few humans ever find it. The web taught us to write like journalists building to a point. Answer engines reward writing like a good expert on the phone: conclusion first, reasoning after, for every section, every time.
Test it on your own site this way. Take any page, read only the headings and the first sentence under each. If that skim answers the question the page exists for, the page is liftable. If it reads like chapter titles and throat-clearing, it isn't, and the engine reading it will move on to a competitor's page that got to the point.
Every section must survive alone
When an engine lifts a passage, it lifts it out of context. A paragraph that begins "as mentioned above" or leans on "this approach" without naming the approach is unusable, because extracted on its own it says nothing. Write each section as if it might be the only thing a reader ever sees, with the subject named, the claim complete, and no pronouns pointing at paragraphs that didn't come along for the ride. This feels repetitive when you write it. It reads fine, and it's the difference between quotable and not.
Specificity is what gets quoted
Engines composing an answer need material with edges: numbers, prices, timeframes, names, steps. "We deliver fast turnarounds at competitive rates" gives an engine nothing to work with, because it's the same sentence every competitor wrote. "Most projects ship in four to six weeks, and pricing starts at $10,000" is liftable, comparable, and quotable. The same law from our own copy guidelines applies to yours: if a sentence could sit on a competitor's website unchanged, it will never be the reason an engine picks you.
Which brings us to the opinion most businesses resist: publish your pricing, at least as ranges. Cost questions are among the most-asked commercial questions in every industry, and in most industries almost nobody answers them. The engines have to build cost answers from whatever exists, so the businesses that publish real numbers get handed those citations nearly uncontested. Yes, competitors will see your prices. They already know them. The buyers asking an assistant what things cost are the ones you're currently invisible to.
One page, one job
Retrieval matches pages to questions, so a page trying to answer ten questions at once matches none of them strongly. Give each meaningful question cluster from your panel its own page with a clear job: the cost page, the how-it-works page, the comparison page, the location page. This is also where the ultimate-guide era earns its correction. A ten-thousand-word guide that ranks but never answers anything in its first sentences is being outlifted daily by focused pages a tenth its length. Long content still works, but only when every section within it follows the rules above: answer-first, self-contained, specific.
What to do this month: take the ten questions from your panel where you're absent and the diagnosis said content gap, and write or rewrite one page for each, in exactly this shape. That's the work. The next chapter makes sure that when your passages get lifted, the engines know precisely whose words they're quoting.