Skip to content
pageinspection

Writing a direct answer block an engine can lift verbatim

A page can answer a question thoroughly and still contain no passage anyone can quote. The answer is spread over four paragraphs, each depending on the last, and lifting any one of them produces something that does not stand up. This check is about the passage, not the page.

The short answer

A direct answer block is a passage of roughly 40 to 60 words that answers the page question completely, placed near the top, and readable with nothing around it. The three ways they fail are opening with a caveat, referring to something above them, and running long enough to be truncated in the middle of the useful part.

ImportantAudit check · Direct answer sections

What a direct answer block is

One continuous passage, generally forty to sixty words, that answers the question completely and refers to nothing outside itself. It sits immediately under a heading that states the question. Removed from the page and pasted anywhere else, it still reads as a complete reply.

That last property is the entire specification, and it is stricter than it sounds. Most prose that looks like an answer fails it on one word: a "this", an "it", a "the above", a "as we saw". Each of those is a pointer into surrounding text that will not travel with the passage.

What the check looks for

Under each question-shaped heading, whether the passage immediately following it is self-contained: a resolvable subject, a stated conclusion, no unresolved references, and a length that fits the formats engines actually lift.

It reports three outcomes rather than two, which matters. A page with no answer passage at all is different from a page with one that starts with a pronoun, and different again from one whose answer runs to three hundred words. The first is a writing problem, the second is a one-sentence fix, the third is a formatting decision.

Writing one, and the three ways they usually fail

The pattern that works: restate the subject, give the answer, add the one qualifier that stops it being wrong. Then stop, and put the rest underneath.

answer-blocks.md
## How long should a meta description be?

<!-- FAILS: opens with a pronoun. Quoted alone,
     nothing identifies what "they" are. -->
They work best between 70 and 160 characters, though
as mentioned above this varies by device.

<!-- FAILS: promises an answer instead of giving one.
     Nothing here is liftable. -->
There are a few things to consider when deciding how
long a meta description should be, and the answer
depends on several factors we will cover below.

<!-- FAILS: buries the answer in a hedge. The figure
     arrives in the third clause. -->
While there is no official limit and Google has said
it does not use length as a signal, most practitioners
find that somewhere around 150 characters works.

<!-- WORKS: subject named, figure given, one
     qualifier, complete in 44 words. -->
A meta description should run about 70 to 160
characters. Past roughly 160 the tail is truncated on
desktop results, so any call to action at the end will
not be read. Google rewrites the snippet anyway on
pages that rank for many different queries.

The three failures in order of frequency: an unresolved pronoun in the first sentence, a promise of an answer rather than the answer, and a hedge placed before the figure instead of after it. All three are single-sentence repairs, which is what makes this check unusually cheap to act on.

The copy-and-paste test

The test needs no tooling and cannot be automated away: copy the passage under one of your question headings, paste it into a blank document, and read it as though you had never seen the page. Anything that sends you back is the defect.

This one needs the full crawl

Finding a standalone answer means reading the passage under each heading and judging whether it survives being removed from the page, which runs as part of the page-level audit.

The instant search on this site audits a single page, so rather than show you a verdict it cannot support, this guide sends you to the place the check actually runs.

Why the length band exists

Forty to sixty words is not a mystical number, it is the amount of text the surfaces that quote answers tend to have room for. Paragraph snippets get cut somewhere around there, and a voice assistant reading aloud for much longer than that loses the listener.

The practical consequence is that going long is a real cost, not a neutral choice. A hundred-and-eighty-word answer will be truncated by whoever lifts it, and they will cut at their own boundary rather than at yours, which frequently removes the qualifier that made the answer accurate.

If you cannot answer inside sixty words, the answer is probably a list rather than a paragraph.

That is not a defeat. Some questions genuinely have a shape other than prose, and choosing a list or a table is the correct move rather than compressing a comparison into a sentence nobody can parse.

What this does not license

An answer block is not a summary box, and it is not permission to write shallow pages.

The overcorrection is a page consisting of nothing but answer blocks: a stack of forty-word passages with no argument, no evidence and no reason to be trusted. That is a page built for extraction and worthless to a reader who wants to understand something, and it fails on substance while passing on form.

The answer block is the doorway. What is behind it still has to be worth walking into.

Why an opportunity check still earns Important

Because it is an opportunity check rather than a defect check. A page failing it works correctly in every respect: it is crawled, indexed, ranked and read. What it forgoes is being quoted, which is a specific and increasingly valuable outcome rather than a requirement.

It earns Important rather than Refinement on cost-to-benefit. The work is rewriting one sentence per section, and the benefit is eligibility for the surfaces that lift answers. Few checks on the list have that ratio.

Confirming it works

Re-run the copy-and-paste test on the passages you rewrote. The specific improvement to look for is that the first sentence names its own subject, which is the single change that fixes most failures here.

The external confirmation is slower and worth watching for: a snippet or a citation quoting your answer passage rather than a sentence from the middle of the page. That is the outcome the check exists for, and it arrives a recrawl or two after the edit rather than immediately.

Questions this check raises

How long should a direct answer be?
Around 40 to 60 words. Featured snippets truncate near that range and retrieval systems chunk at a similar order of magnitude, so a longer passage is quoted with its ending cut off. Shorter than about 30 words usually means a definition rather than an answer.
Where should the answer block go?
Above the fold, before the first section heading, immediately after the introduction if there is one. The point is that a reader or a machine arriving at the page finds the answer without scrolling and without deciding which of six sections holds it.
How do I know if my answer block works?
Copy it out of the page, paste it somewhere with no surrounding context, and read it. If it opens with however, this, or the above, or if it assumes the heading is visible, it does not survive being quoted, which is the only situation it exists for.