Answer first content

What this check does

Measures the word count of the first prose paragraph on the page (after the H1, ignoring nav, hero, and image captions). Passes when that paragraph is roughly 30–80 words and reads like a direct answer.

Why it matters

Answer engines — ChatGPT, Perplexity, Google AI Overviews, Claude — quote-mine the first chunk of text they can parse. If the lead is a marketing throat-clear (“In today’s fast-paced world…”) the model picks a different page that gets to the point. Same effect on humans: Nielsen Norman’s eye-tracking shows readers decide whether to keep going in the first 10–20 seconds.

Inverted-pyramid writing — answer first, context after — is older than the web and still wins.

How to fix it

Rewrite the lead so the first 30–80 words contain a complete, standalone answer to the page’s query.

Before (intro fluff):

Welcome to our comprehensive guide on HTTPS. In today’s connected world, security has never been more important. In this article, we’ll explore everything you need to know about modern web security…

After (answer first):

HTTPS encrypts traffic between a browser and your server, so attackers on the same network can’t read passwords, cookies, or page content. Enable it by installing a TLS certificate — Let’s Encrypt issues free ones in under a minute — and forcing all HTTP requests to redirect to the HTTPS version.

The second version is what an LLM will quote. The first is what gets summarized away.

Concrete checklist:

• Open with a one-sentence definition or direct answer to the H1’s question.
• Add one sentence of “how” or “why” right after.
• Move history, anecdotes, and brand context below the first H2.
• Keep the paragraph short — under 80 words. Walls of text get skipped.

For listicles: the first sentence should state how many items follow and why they’re ordered the way they are. (“These 7 React hooks fixed every state-management bug in our codebase — ranked by how often they came up.”)

For documentation: the first paragraph should answer “what is this and when do I use it?” before any code block.

Pair this with content depth and an optimal title length for the full lede.

Frequently asked questions

Does Google penalize fluffy intros directly?

Not as a ranking factor by name. But helpful-content updates demote pages that don’t satisfy the query quickly, and AI Overviews skip past intros to grab the actual answer — so weak leads lose visibility two ways at once.

What if my page genuinely needs a long setup?

Move the setup. Put a 50-word direct answer on top, then a “Background” H2 below it for readers who need context. The summary doesn’t replace the depth — it just sits in front of it.

How does this interact with the <meta description>?

The meta description targets SERP click-through; the on-page lead targets engagement after the click. They should agree but not be identical — the meta is the pitch, the lead is the payoff.