The answer-first rewrite: a 50-word pattern that wins snippets

Open a page that ranks well and wins nothing, and look for the answer to its target question. If you can find it — three paragraphs down, split across two sections, sitting under a preamble that establishes context first — the page has the substance and lacks the shape.

That distinction decides what to do next. Substance present but buried means restructure, which is cheap and low risk. Substance absent, wrong or aimed at a different intent means rewrite, which is expensive and risks the ranking you already have. Teams routinely commission the second when they needed the first.

The reason this happens is that good writing and extractable writing pull in different directions. A well-constructed article builds toward its conclusion. An extractable passage leads with it. Both are legitimate; only one gets selected.

Use the question as the heading, phrased the way people actually search it rather than compressed into keyword form. Then answer it immediately in roughly forty to sixty words — long enough to be complete, short enough to be lifted whole. Then continue with the caveats, the detail and the reasoning that a reader who wants more will keep reading for.

The answer paragraph must stand alone. No pronouns referring to earlier sections, no phrases like "as mentioned above", no dependency on a definition established two headings up. Name the subject explicitly even where it feels repetitive, because the passage will be read without anything around it.

Repeat the pattern per section rather than once per page. Each heading is a separate selection opportunity, and pages structured this way routinely accumulate a dozen People Also Ask entries alongside whatever snippet they win.

It is not a magic number, and nothing enforces it. It is the range where an answer is usually complete enough to satisfy a query and short enough that an engine can display it without truncation. Shorter tends to be incomplete; longer tends to get cut mid-thought, which reads badly to whoever sees it.

The discipline matters more than the exact count. Forcing an answer into that range surfaces whether you actually know it. Answers that cannot be stated in sixty words are frequently answers the writer has not resolved, and the padding was hiding that.

For regulated content there is a further reason to care. If a model summarises your page and drops a caveat that sat three paragraphs below the answer, the summary can be materially misleading. Keeping the caution inside the extractable passage is a safety measure, not just a retrieval tactic.

Restructuring rarely harms existing rankings, because the substance and internal links stay intact. That is the main argument for doing it before considering a rewrite: the downside is small and the upside is a surface you were not competing on at all.

Movement typically shows within two to six weeks after recrawl, faster than most content work because you are not asking engines to reassess relevance, only offering them something extractable that was not there before.

It will not rescue a page that does not rank. Selection happens among pages already ranking well, so a page on the third result page gains nothing from being restructured. That is a content depth or authority problem, and the honest answer is to say so rather than sell a restructuring engagement.