How to Write the Introduction of a Buyer Guide: The Three Sentences Before the Verdict
The introduction is the part of a buyer guide that most readers skip and most writers spend the longest on, and generated guides make both problems worse: four paragraphs about the history of the category, two "in this article we will", and the actual guide starting somewhere around paragraph five. The reader, on a phone, gave the page ten seconds and left before the verdict.
This post covers what the intro is for (three things, three sentences), what it isn't for, why generated intros run long and the brief that fixes it, eight opener patterns so a batch of guides doesn't start the same way, and a check that takes ten seconds. The verdict box post covers what comes next; the intro is the runway to it, and runways are short.
The short answer
Three sentences: the reader's situation in specific terms, what this guide decides, and one reason to trust it. Then the verdict. No category history, no "in this article", no definition of the product, no "it depends". Vary the opener across a batch with the eight patterns below. If the verdict isn't visible in the first screen on a phone, the intro is too long.
The three sentences
| Sentence | Job | Example | Not |
|---|---|---|---|
| 1. The reader's situation | Tell the searcher they're on the right page | "You commute on lit streets, and your current light either blinds drivers or dies by Thursday." | "Bike lights are an essential accessory for any cyclist." |
| 2. What this guide decides | Set the scope and carry the keyword | "This guide picks the best bike lights for commuting under $60, with one pick for riders who swap bikes." | "In this article we will explore the top options on the market." |
| 3. Why trust it | One line of basis | "The picks come from the specs, the pattern across owner reviews, and two winters on the Metro." | "We tested dozens of products in our lab." (unless you did) |
Fifty to eighty words. The third sentence doubles as the honesty line Google's reviews guidance asks for, and it's where a real experience sentence goes when you have one; it's the one sentence in the intro that only you can supply.
What the intro is not for
- Category history. "Bike lights have come a long way." Nobody searched for that.
- Defining the product. The searcher typed its name; they know what it is.
- "In this article we will." The heading structure says what the article will do; the sentence is dead weight.
- Hedging. "The right choice depends on your needs" is the sentence the reader came to the page to not have to write.
- The pitch for why the category matters. "A good light could save your life." The reader is already buying one.
- A table of contents in prose. The TOC widget does that.
Each of these is a paragraph a generator produces by default, and each is a paragraph between the searcher and the verdict.
Why generated intros run long
A model writing a buyer guide with no instruction about the intro writes the average buyer-guide intro, and the average one is four paragraphs of the list above. The fix is in the brief: "Intro: three sentences, the reader's situation, what this guide decides, one line of basis, then the verdict.
No category history, no 'in this article', no definitions, no 'it depends'." Tools that take a structure setting apply it to every guide; tools that don't need the line in every prompt. The brief post covers the rest of the inputs.
If you're editing after the fact: delete paragraphs from the top until you reach the sentence that names the reader. That's the intro; the rest was warm-up.
Eight openers, so a batch doesn't repeat
Fifty guides that all begin "You commute on lit streets and…" read as a template. The first sentence's job is the same every time; its shape can rotate:
- The situation: "You commute on lit streets and your light dies by Thursday."
- The wrong buy: "Most people buy a 2,000-lumen light for a lit commute and blind every driver they pass."
- The constraint: "Under $60, two lights are worth buying and the rest are the same light with a different sticker."
- The question: "Does a commuter light need more than 400 lumens? No, and the ones that have more cost you battery."
- The spec that matters: "Beam shape decides a commuter light; lumens don't, past 400."
- The one-line verdict first: "The Cygolite Metro Pro is the commuter pick; here's why, and who should buy the Lezyne instead."
- The mistake in the reviews: "The commonest one-star review on commuter lights is the mount cracking in winter, which rules out half the list."
- The trade-off: "Every light under $60 trades either run time or beam shape; this guide picks by which trade suits your ride."
Rotated across a batch, eight shapes make fifty guides read as fifty guides. The scale post covers the other rotations that go with it.
The ten-second check
Open the guide on a phone. Without scrolling, can you see the verdict box? If yes, the intro is the right length. If no, count paragraphs above the verdict; anything past one is cut. Then read the first sentence: does it name the reader or the product? If it names the product ("Bike lights are…"), rewrite it to name the reader.
Doing it with AffSERP
AffSERP's X Best Review tool writes the intro to the three-sentence shape by default and rotates the first sentence across the eight openers above within a batch, so no two guides in a run start the same way and the verdict lands in the first screen.
The third sentence takes your basis line from the site's notes, which is where "two winters on the Metro" comes from when it's true, and reads "from the specs and what owners report" when it isn't.
FAQ
How long should a blog post intro be for a product review?
Three sentences, about 50 to 80 words, and then the verdict. The reader arrived from a search with a decision to make; every sentence before the pick is a sentence they might leave on. The intro's only jobs are to show you understand their situation, say what the guide decides, and give one reason to trust it. Anything else belongs further down or nowhere.
Why are AI-written intros so long?
Because the training data is full of long ones: four paragraphs of category history, 'in today's fast-paced world', and 'in this article we will explore'. A generator reproduces the genre unless told otherwise. Give it the three-sentence formula and a banned-phrase list and the intro comes out at the right length; or cut the first three paragraphs of whatever it wrote, which is usually where the real intro starts.
What should the first sentence of a buyer guide say?
The reader's situation, specifically: 'You commute on lit streets and your current light either blinds drivers or dies by Thursday.' It tells the searcher they're on the right page in the time it takes to read one line, which is all the time they give it. Not 'Bike lights are an essential accessory', which tells them nothing they didn't know.
Should the intro include the keyword?
Naturally, once, where the sentence would carry it anyway: 'the best bike lights for commuting' appears in the sentence that says what the guide decides. Forcing it into all three sentences reads as what it is. The title and the first heading already carry it; the intro's job is the reader, not the crawler.
AffSERP writes the intro to the three-sentence shape and rotates the opener across a batch, so fifty guides start fifty ways and none of them with category history.
Start with free words