The 'What to Look For' Section of a Buyer Guide: Which Specs to Explain, in What Order, and How Long Before the Reader Leaves
Every buyer guide has a section that explains what the specs mean, and in most of them it's the longest, least-read part of the page: a tour of every number on the listing, in listing order, at 150 words each, before the reader has seen a single product.
It's written because the template has a slot for it and because explaining specs feels like expertise. The section that actually earns its place is a third as long, covers only the specs that change the decision, and sits where the reader who needs it will find it and the reader who doesn't can skip it.
This post covers what the section is for and which of a guide's two readers uses it, how to find the three to five specs that decide the purchase (and why lumens isn't one of them), the order that matches how a buyer thinks, the 80-to-120-word rule per spec with a worked example, where the section sits on a guide versus an informational post, the specs to leave out even though the listing leads with them, and the brief line that stops an AI writer explaining everything.
The how we picked post covers the method section, which is a different job: that one says what you did; this one says what the reader should weigh.
The short answer
Three to five specs, chosen because they differ between the picks and because owners complain about them. Ordered by what the reader asks first. Each in 80 to 120 words: what it is, the range on listings, what each end means in use, which pick sits where.
After the picks, before the table. Leave out the headline spec every listing leads with if it doesn't change the choice. Tell the writer which specs, not "explain the key features".
Who reads it
| Reader | What they do with the section | What it needs to be |
|---|---|---|
| Trusts the verdict | Skips it; goes from the pick to the button | Out of the way: after the picks, skippable by heading |
| Doesn't trust the verdict yet | Reads it to understand why the pick is the pick, then returns to the picks | Short enough to finish, specific enough to resolve the doubt |
| Has a different case | Reads it to work out which pick fits them instead | Each spec names which pick sits where, so the section routes them |
| Researching, not buying | Reads it as a lesson; may not click today | Served better by the informational post this section links to |
The second and third rows are the section's reason to exist: a reader who arrived unconvinced and leaves convinced, or arrived as the wrong reader and leaves with the right pick. Neither needs 1,200 words. Both need the section to point back at the products.
Finding the specs that decide
- The comparison table. Look at each column. If every pick has the same value (all USB-C, all IPX4), the spec doesn't decide anything on this page and doesn't need explaining; one sentence in the intro ("all ten are USB-C and weather-sealed") covers it. The columns where the picks spread out are the candidates.
- The one-star reviews. The complaints are the specs buyers wish they'd understood: the mount that doesn't fit an aero bar, the runtime quoted at the lowest setting, the "waterproof" that meant splash-proof. The one-star reviews post covers reading them; here they're the list of what to explain.
- The intersection, usually three to five specs. If it's more than five, the guide may be covering two categories; if it's fewer than three, the products are near-identical and the guide's verdict is mostly about price.
For commuter bike lights the intersection is beam shape (cut-off or round), runtime at a brightness you'd actually ride on, mount type, and charging port. Lumens, which every listing leads with, mostly doesn't make the list: above a few hundred, more lumens on a round beam is glare for oncoming traffic, and the beam shape decides what the lumens do.
The order
By what the reader asks first, which is usually the spec that determines whether a product is in the running at all, then the one that separates the finalists, then the conveniences.
For lights: beam shape (is this a commuter light or a trail light), then runtime (will it last the week), then mount (will it fit my bike), then charging. For a mattress: firmness, then material, then cooling, then trial period. The order is the reader's decision tree, and the section reads as "first decide this, then this".
The 80-to-120-word rule
Each spec gets four things: what it is in a sentence, the range the reader will see on listings, what the ends of the range mean in use, and which picks on this page sit where. For example:
Runtime at a usable brightness. Listings quote runtime at the lowest setting, which is why a "20-hour" light lasts two hours on the beam you'd ride with.
Look for the figure at the mid or high mode, usually in the manual rather than the listing; for a 40-minute commute each way, you want five hours or more at that setting so you charge once a week. The Cygolite and the Lezyne on this page both clear that; the budget pick doesn't, and it's listed as the pick for short rides for that reason.
That's 95 words, and it does the section's whole job: explains, warns about the listing, sets a threshold, and routes the reader back to a pick. The readability post covers the sentence lengths that keep a phone reader moving; a spec at 300 words loses them before the routing sentence.
Where it sits
- On a buyer guide: after the picks, before the comparison table. The reader who wants the answer has it; the reader who wants the reasoning finds it under its own heading; the table that follows is now readable because its columns have been explained.
- On an informational post ("how to choose a bike light"): it's the page, first and long, with the guide linked at the end for the reader who's ready.
- Never before the first product on a guide. A reader who searched "best X" and meets 600 words of criteria before any X goes back to the results.
The specs to leave out
- The headline spec that doesn't decide: lumens, megapixels, watts, thread count. Explain in one line why it matters less than the listing implies, then move on.
- Anything every pick shares. One sentence in the intro.
- Marketing names for ordinary things: a brand's name for its mount or its battery. Translate once if needed; don't give it a paragraph.
- Specs the reader can't act on: internal construction details that don't map to anything they'd notice.
Briefing an AI writer
- Name the specs: "Explain beam shape, runtime at mid mode, mount type and charging port. Don't explain lumens beyond one sentence on why it matters less than it looks." Without this, the writer explains every spec on the listing in listing order.
- Set the length: 80 to 120 words per spec, and the four-part shape.
- Require the routing sentence: each spec ends by naming which picks on the page sit where.
- Place it: after the product sections, before the table.
- Supply the complaints from the review pattern so the "listings quote this at the lowest setting" warnings are real ones.
Doing it with AffSERP
Guides written by AffSERP's X Best Review tool place the buying-criteria section after the picks and before the comparison table, and build it from the specs that actually vary across the selected products rather than from the listing's headline numbers, with each spec routed back to the picks that sit at each end.
The brief's deciding-spec input names which specs to explain and which to dismiss in a line, and the review pattern feeds the warnings about how listings quote them. The Informational Article tool writes the long version, "how to choose", as its own page that links to the guide, so neither page has to be both.
FAQ
What is the 'what to look for' section in a buyer guide?
The part that explains the three to five things a buyer should judge the products on, in plain terms, before or after the picks. It exists for the reader who doesn't yet trust the verdict and wants to understand why it's the verdict; a reader who reads it and then returns to the picks is a reader who clicks. It isn't a specs glossary. Every spec on the listing can be explained; the section explains only the ones that change which product this reader should buy.
Which specs should a buying guide explain?
The ones that separate the picks from each other and that owners actually complain about. Find them in two places: the comparison table (a column where every product has the same value doesn't decide anything, so cut it) and the one-star reviews (the complaints are the specs people wish they'd understood). For bike lights that's beam shape, runtime at a usable brightness, mount type, and charging port; it isn't lumens, which every listing leads with and which decides almost nothing on its own.
Should the buying criteria go before or after the product list?
After, on a buyer guide. The reader who arrives at 'best bike lights for commuting' wants the pick first; a 600-word lesson before the first product sends them back to the results. Put the verdict, then the picks, then 'what to look for' as the section for the reader who wants to understand the choice, then the comparison table and FAQ. On an informational post ('how to choose a bike light') the criteria are the page and go first, and that post links to the guide.
How long should the 'what to look for' section be?
Eighty to a hundred and twenty words per spec, three to five specs, so 300 to 600 words in all. Each spec gets what it is in one sentence, the range the reader will see on listings, what matters at each end of the range, and which pick on this page sits where. More than that is an informational post wearing a guide's heading; less than that is a list of spec names, which the listing already provides.
AffSERP places the buying-criteria section after the picks, explains only the specs that differ across the selected products, and ends each with which pick sits where.
Start with free words