← Blog
SEO · November 18, 2026 · 8 min read

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

D
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

QueryWhat Google tends to showWhy
The main keyword ("best bike lights for commuting")Often your description, if it contains the keyword and describes the pageThe 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 pageThe 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 itGoogle wants an answer-shaped snippet
A product nameThe sentence in that pick's sectionThe description doesn't name the product; the section does
Navigational ("affserp blog bike lights")Your descriptionNo 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:

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

Checking which is happening

  1. Search Console → Performance → Pages → the guide → Queries. Note the top three queries by impressions.
  2. Search each in a private window and read the snippet under your result. Your description, or a page passage? Note which, and which passage.
  3. 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.
  4. 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.
  5. Recheck a month after any change; Google re-snippets as it recrawls.

What to write in the field

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.

A verdict that reads as the snippet

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
D
Written by Daniel R. SEO Lead, AffSERP

Daniel leads SEO at AffSERP. He writes about keyword research, search intent and site structure, favouring methods you can run with Google and Search Console before reaching for a paid tool.

More about Daniel →