Writing the Meta Description for a Buyer Guide When Google Rewrites It Anyway: What Gets Shown, What Gets Replaced, and the 120 Characters That Survive
Every SEO plugin has a field for the meta description, a traffic-light for its length, and a preview of how it will look in Google. Then Google ignores it. On a buyer guide, for most of the queries that send traffic, the snippet under your title isn't the description you wrote; it's a sentence from the page, chosen because it contains the words the searcher typed.
That's not a bug to work around. It tells you where the real meta description is, and it's in the first two lines of the verdict.
This post covers how often Google replaces a meta description on a buyer guide and why it's higher on long-tail queries, what it pulls instead and where on the page it tends to find it, and why that makes the first 120 characters of the verdict paragraph the description most searchers see.
It also covers the cases where the written description is shown, how to check which is happening in Search Console and a live search, and what to write in the field so that when it's shown it earns the click.
The meta descriptions and slugs post covers writing the field; this is what happens to it afterwards.
The short answer
Google replaces the description most of the time, more on long-tail queries, with the on-page passage that contains the query's words, usually the verdict. Write the verdict paragraph so its first 120 characters name the pick, the reader and the reason, in the words people search.
Write the description field for the main keyword only, to about 150 characters with the point in the first 120. Check both in a live search for your top three queries.
How often, and why
| Query | What Google tends to show | Why |
|---|---|---|
| The main keyword ("best bike lights for commuting") | Often your description, if it contains the keyword and describes the page | The description was written for this query and matches it |
| A long-tail variant ("best bike lights for commuting under $50 with usb-c") | Almost always a passage from the page | The description doesn't mention $50 or USB-C; a sentence on the page does |
| A question ("are bike lights with a cut-off beam better") | A FAQ answer or the sentence that answers it | Google wants an answer-shaped snippet |
| A product name | The sentence in that pick's section | The description doesn't name the product; the section does |
| Navigational ("affserp blog bike lights") | Your description | No competing passage |
Google's documentation is plain about it: the description is used when it's a good summary for the query, and otherwise a snippet is generated from the page.
Industry studies of large result sets have put the replacement rate around 60 to 75 percent, and a buyer guide ranks for dozens of long-tail queries per main keyword, so the share of your impressions showing your written description is smaller than the share of your queries.
What it pulls instead
The passage that best matches the query, trimmed to roughly 150 to 160 characters on desktop and around 120 on mobile, starting at a sentence boundary when it can.
On a buyer guide that passage is, in rough order of frequency: the verdict paragraph (it's near the top and names the pick and the reader); the first sentence of the pick's section for product-name queries; a FAQ answer for question queries; and a list item when the query matches one.
It almost never pulls from the intro's throat-clearing, which is one more reason the intro should be short. The verdict box post covers the first sixty words for the reader who lands; this is the same sixty words doing a second job in the results.
The 120 characters that survive
Put the two together and the verdict paragraph's opening is the description most searchers see. Its first 120 characters, the part mobile shows before the ellipsis, should therefore read as a description: the pick, the reader, the reason, in the words people type. Compare:
- Reads badly as a snippet: "After weeks of looking at every option on the market, we've narrowed down the field to the ten lights that deserve your attention this year, and one stands out." (The pick isn't in the first 120; the searcher sees preamble.)
- Reads well as a snippet: "The Cygolite Metro Pro 800 is the best bike light for commuting: a cut-off beam that doesn't blind drivers, 4 hours at a usable brightness, and a mount that survives a lock-up." (Pick, keyword, three reasons, in 160 characters; the first 120 carry the pick and the beam.)
The second is also the better verdict for the reader on the page, which is the point: there's no conflict between writing for the snippet and writing for the reader, because both want the answer first.
When the written description is shown
- The main keyword query, when the description contains it and summarises the page. This is usually the single highest-impression query, so the field still matters.
- Navigational and brand queries.
- Queries where the page has no better passage, which on a well-written guide is rare.
- Some social and messaging previews use the og:description, which you set to the same text; Google isn't the only reader of the field.
Checking which is happening
- Search Console → Performance → Pages → the guide → Queries. Note the top three queries by impressions.
- Search each in a private window and read the snippet under your result. Your description, or a page passage? Note which, and which passage.
- If it's a passage you wouldn't have chosen (the intro, a caveat, a half-sentence), the fix is on the page: make the verdict's first 120 characters the sentence you'd want shown, or make sure the pick's section opens with its one-line case.
- If it's your description but the CTR is below the position's norm, rewrite the field; the CTR post covers the test and the four-week read.
- Recheck a month after any change; Google re-snippets as it recrawls.
What to write in the field
- For the main keyword, since that's when it's shown: the keyword in the first few words, what the page delivers (the pick, the count, the reader), and a reason. "The 10 best bike lights for commuting, ranked by beam shape and runtime, with the Cygolite Metro Pro 800 as our pick for city riders."
- About 150 characters, point in the first 120.
- Not a restatement of the title; the title is already shown above it. Add the thing the title didn't say.
- No "click here", no "in this article we will"; the snippet is the only sentence the searcher reads before deciding.
- Same text in og:description and the Article schema's description, so every reader of the field sees one version.
- Don't rewrite it every month. Change it with a reason and a before-and-after, like a title.
Doing it with AffSERP
Guides written by AffSERP's X Best Review tool open with a verdict box whose first sentence names the pick, the keyword and the reason, which is the 120 characters above by construction, and the meta description is written for the main keyword with the pick and the count rather than as a restatement of the title. Both are editable in WordPress before publishing.
The live-search check against the top three queries is yours, monthly, and on most guides it shows the verdict's first line doing the job the field was supposed to.
FAQ
Why is Google not using my meta description?
Because it found text on the page that matches the query better. Google's documentation says it uses the meta description when it accurately describes the page for the query and otherwise generates a snippet from the page's content, and for most buyer guides on most queries, the second happens: the query is 'best bike lights for commuting under $50' and the description was written for 'best bike lights', so Google pulls the sentence on the page that contains the words typed. Studies of large result sets put the rewrite rate around two-thirds to three-quarters of the time, higher on long-tail queries.
What does Google show instead of the meta description?
The passage on the page that best matches the query, usually the first sentence or two that contain the query's words, trimmed to about 150 to 160 characters on desktop and fewer on mobile. On a buyer guide that's most often the verdict paragraph near the top, sometimes a list item or a FAQ answer when the query is a question. Which means the first 120 characters of your verdict paragraph are shown as your description far more often than the field you wrote.
Does the meta description affect rankings?
No, and Google has said so for years. It affects clicks: when it's shown, a description that says what the page delivers in the searcher's words earns more clicks at the same position than a vague one. When it's rewritten, the pulled passage does that job. So the description matters for CTR on the queries where it's shown (usually the main keyword), and the on-page text matters for CTR everywhere else, which is the larger share.
How long should a meta description be?
Write to about 150 characters so it survives whole on desktop and loses only the tail on mobile, which cuts around 120. Put the point in the first 120: the pick or the promise, in the searcher's words, with a reason. Google doesn't enforce a length, it truncates with an ellipsis, so a longer description isn't penalised; it just ends mid-sentence where the searcher is deciding whether to click.
AffSERP guides open with a verdict sentence naming the pick, the keyword and the reason, and a description written for the main keyword, so both jobs are done before publishing.
Start with free words