Google rewrites meta descriptions in approximately 70 percent of search results, primarily because the page description does not match the user query. The other seven causes (wrong length, duplicates, keyword stuffing, stale descriptions, promise-mismatch, rich extractable content, and featured snippets) account for the remaining ~50 percent of rewrites between them. The good news: six of the eight causes have mechanical fixes you can ship in an afternoon. The other two need editorial judgment but are still solvable. This guide walks through all eight, in order of frequency, with the exact fix for each.
The underlying length rules sit in the meta description character limit guide; the hub for the length checker is /meta-description-length-checker. Here we focus on the why and the how-to-fix.
Quick diagnostic: the 8 causes at a glance
Use this table as a triage tool. Start at the top and stop at the first cause that describes your page. The order reflects frequency: the top causes hit far more pages than the bottom ones.
| Cause | Share of rewrites | Fix | Effort |
|---|---|---|---|
| Description does not match the query | ~50% of rewrites | Rewrite to lead with the page topic and the dominant query phrase | Medium |
| Too short (under 100 chars) or too long (over 165) | ~15% | Rewrite to 140 to 155 chars; use a pixel-aware checker | Easy |
| Duplicated across multiple pages | ~10% | Audit sitemap, dedupe, write unique descriptions per page | Easy |
| Keyword stuffed (same phrase 3+ times) | ~8% | Use the keyword once near the front, never repeat verbatim | Easy |
| Description older than page content | ~7% | Refresh descriptions whenever you substantially edit a page | Medium |
| Page does not deliver what description promises | ~5% | Match the promise to the actual page; rewrite either side as needed | Hard |
| Page has rich extractable content Google prefers | ~3% | Often a positive; consider letting the auto-snippet stand | No action needed |
| Featured snippet replaces the description | ~2% | Not a rewrite; verify in SERP. Optimize for the snippet position. | No action needed |
Notice that the top three causes account for roughly 75 percent of rewrites and all three are easy or medium effort to fix. Most rewrites are not deep editorial problems; they are length, uniqueness, and query-match issues that can be batch- solved across a site in a day.
Cause 1: Description does not match the query
This is the largest single cause of rewrites and it is also the most misunderstood. A meta description does not need to match every keyword a page ranks for. It needs to match the dominant query: the one that drives the most impressions in Search Console.
When Google picks a snippet, the model first checks whether your meta description contains the key terms from the query. If it does, Google often keeps your description. If the query terms are absent or buried in the back third of the description, Google generates a new snippet from page text that does contain the query terms, even if that page text is less polished than your tag.
Fix. Open Search Console for the page. Sort queries by impressions. Identify the top one or two queries. Rewrite the description so the dominant query phrase appears in the first 60 characters. Do not stuff; one instance is enough. The query-match signal is usually strong enough to flip a rewrite back to your tag within two weeks.
Cause 2: Description is too short or too long
Google's snippet system has implicit length quality signals. Descriptions under about 100 characters look incomplete and trigger auto-snippet generation in a high percentage of cases. Descriptions over 165 characters get truncated, and the truncation itself can push Google to substitute a tighter snippet from page text instead.
The exact thresholds shift over time, but the working range has been stable for more than five years: descriptions between 140 and 155 characters survive at the highest rate. Under 100 or over 165 and the rewrite rate climbs sharply.
Fix. Audit your descriptions for length and rewrite anything outside the 140 to 155 character window. The meta description length checker shows both character count and pixel width so you can validate the final draft before publishing.
Cause 3: Description is duplicated across multiple pages
Duplicates are common on e-commerce sites (variant pages sharing a template description) and on category pages with shared boilerplate. When Google sees identical or near-identical descriptions on two pages, it cannot decide which description belongs with which result, so it defaults to rewriting both with page-specific text.
Search Console flags duplicate descriptions in the Coverage report (look under "Excluded" and "Duplicate"). For larger sites, a sitemap-level audit with any technical SEO tool (Screaming Frog, Sitebulb, Ahrefs Site Audit) lists every duplicate description grouped by content.
Fix. Group pages by duplicate description text. Rewrite each description to include the variable that differentiates the page: the city, the product variant, the date, the category. For programmatic content, update the template so the description pulls dynamic fields rather than static boilerplate.
Cause 4: Description is keyword-stuffed
Google's snippet quality systems flag descriptions that repeat the primary keyword three or more times, or that cram in too many secondary keywords back-to- back. The trigger is not the keyword itself; it is the unnatural pattern. A description like "buy running shoes, running shoes for sale, best running shoes online" reads as spam to both the model and the searcher.
Stuffing was once an SEO tactic but has been a rewrite trigger since at least 2018. The current generation of snippet selection models is even stricter, partly because stuffed descriptions also tank click-through rate, which provides Google an extra quality signal beyond the text pattern.
Fix. Use the primary keyword exactly once, near the front. Allow at most one related modifier elsewhere. Replace any remaining instances with synonyms or with concrete information (numbers, outcomes, product names). The 5-part formula in our meta description examples guide gives the structure to follow.
Cause 5: Description is older than page content
A common pattern: a page was published in 2020 with a fitting description, the content has been updated three times since, but the description has not changed. The description still loosely describes the page but no longer matches the latest content or angle. Google detects the divergence (the page mentions things the description does not, or vice versa) and rewrites.
This is especially common on evergreen guides and reference articles. The article gets refreshed with new statistics, examples, and sections. The description never gets touched, so over time it falls behind.
Fix. Whenever you do a major content update on a page (more than 20 percent of the content changed, or a new section added), rewrite the meta description to match the new content. A useful rule: if the page now answers a question the description does not hint at, the description is out of date.
Cause 6: Description does not deliver what page promises
This is the hardest cause to diagnose and fix. The description sets an expectation (free template, complete guide, 25 examples) and the page does not actually deliver on it. Google's relevance systems detect the mismatch through bounce rate, pogo-sticking back to the SERP, and direct content analysis, and respond by rewriting the snippet.
Promise-mismatch tends to cluster on pages where the description was written aspirationally before the content was finished, or where the page was built from a template that did not get fully populated. It also shows up on landing pages where the ad-driven copy promises one thing and the page delivers something slightly off.
Fix. Read the description and the page together. Ask: does the page actually do what the description claims? If yes, the description is fine and the cause is elsewhere. If no, decide whether to upgrade the page to match the description or revise the description to match the page. The right answer depends on which is more aligned with the search query.
Cause 7: Page has rich content Google prefers to surface
Sometimes Google rewrites your description because your page contains a paragraph, list, or table that directly answers the query better than your description does. This is not a punishment; Google is choosing the best searcher-facing text it can find on the page, and your page's body content is the winner.
This pattern is common on FAQ pages, how-to articles, and reference content with strong subheadings. The auto-snippet often outperforms a generic description because it answers the query directly. CTR usually goes up, not down, when this kind of rewrite happens.
Fix. Usually no fix needed. Verify the rewritten snippet is accurate and on-brand. If it pulls from the wrong paragraph, restructure the page so the right paragraph is the most prominent on-topic answer. If it pulls well, leave it; the auto-snippet is doing what a perfect meta description would have done anyway.
Cause 8: A featured snippet replaces the description entirely
Strictly, this is not a rewrite. A featured snippet is a separate SERP feature that takes a direct answer from your page and shows it in a box at position zero, above the regular results. The regular result still appears below, with your normal meta description. The "rewrite" appearance is just the featured snippet pulling page text into the position-zero box.
Confusion between rewritten descriptions and featured snippets is common because both show non-meta-description text on the SERP. The difference: a featured snippet has its own box with the URL, title, and answer text laid out differently from a regular result. A rewritten description appears in the normal result slot below the blue title.
Fix. Verify in an incognito SERP whether you see a featured snippet, a rewritten regular result, or both. If you have the featured snippet, you are winning. Optimize the answer paragraph for completeness rather than the description.
How to verify which cause applies to your page
Before you fix, diagnose. Pick the one or two pages with the lowest CTR relative to their average ranking position and run them through these checks. Most rewrites turn out to be one of the top three causes once you actually look.
| Method | What it tells you | Accuracy |
|---|---|---|
| Incognito Google search | Search your exact title or URL; compare SERP to HTML | High for current state |
| Search Console URL Inspection | Check the live SERP description for a specific URL | High and authoritative |
| Rank tracker with SERP snapshots | See description shown for each tracked keyword | High at scale |
| SERP API (Serpapi, Dataforseo, etc.) | Programmatic access to live snippet text | High; best for audits |
For most teams, the practical workflow is: Search Console URL Inspection for the live snippet, plus an incognito search of the dominant query to see how the description renders in context. Together those two checks reveal both the technical state and the user-visible result.
The two-minute audit that finds 80% of issues
Most teams discover their rewrite problem in batches: one underperforming page turns up in a quarterly review and a flood of similar issues surface. A faster approach is a routine two-minute audit on any page where the description matters, run before publish. Five quick checks catch roughly 80 percent of rewrites before they happen.
Check 1. Read the description aloud. If it sounds robotic, stilted, or unnaturally keyword-heavy, Google's snippet quality systems will likely rewrite it. Natural-reading descriptions survive at a much higher rate, even when they are slightly less keyword-optimized on paper.
Check 2. Confirm the dominant query phrase appears in the first 60 characters. Open Search Console for the page (or for the parent topic if the page is new). The phrase with the highest impression count should be visible at the start of the description, not buried in the back half.
Check 3. Verify the description is unique site-wide. A quick Ctrl-F search of your sitemap export or a dedupe pass in a SEO tool flags any shared descriptions in seconds. The fix is usually a small per-page tweak.
Check 4. Count primary keyword instances. One is ideal. Two is acceptable if both reads naturally. Three or more is keyword stuffing and a rewrite trigger; replace duplicates with synonyms or specific information.
Check 5. Verify the page delivers on the description's promise. If the description hints at a free template, the page should have one above the fold. If the description promises 25 examples, the page should have 25. Mismatched promises are the slowest cause to fix because they often require editing the page, not just the description.
These five checks take roughly two minutes per page. Doing them before publish avoids the more expensive cleanup of finding rewrites in Search Console six months later and trying to identify root causes after the fact.
What rewrites look like in Search Console
Google Search Console does not have a dedicated "rewritten description" report, but the data is there if you know where to look. The Performance report shows impressions and clicks per query per page. Pages with high impression counts but CTR well below the position-average baseline are usually being rewritten on their highest-traffic queries.
A useful benchmark: for a result in position 1, expected CTR is roughly 28 to 30 percent on commercial queries and 35 to 40 percent on informational queries. Position 5 expectation is 6 to 7 percent. Position 10 is 2 to 3 percent. Pages consistently 30 percent or more below those benchmarks usually have a description-quality issue worth investigating.
The URL Inspection tool gives a direct view of the live snippet for a specific URL. Submit the URL, wait for the inspection, and compare the description shown in the SERP preview with the description in the page's HTML head. If they differ, you have confirmation of a rewrite for that specific URL on that specific recent crawl.
When you should accept the rewrite (yes, sometimes)
Not every rewritten description is a problem. There are three scenarios where Google's auto-snippet is better than what you would write yourself.
Long-tail queries with unique intent. A single page can rank for hundreds of long-tail queries. No human-written description can match all of them. Google's per-query snippet generation gives each searcher a response tuned to their query, which usually outperforms a fixed description.
Pages with strong extractable answers. If a page contains a short, well-written answer paragraph in the body, Google pulling it for the snippet often beats your description in click-through rate. This is especially true on FAQ-style content and how-to pages with clear answer sentences.
Featured snippet candidates. If your page is winning featured snippets for high-volume queries, do not fight the rewrite. The featured snippet is more valuable than control of the regular-result description.
In all other cases, especially branded queries and high-CTR money pages, fix the cause and reclaim control. For broader perspective on how plugin tools handle this, see the Yoast meta description guide. For a fast char-count check while drafting, the character counter works in the browser.
The honest summary
Google rewrites meta descriptions about 70 percent of the time, but the cause is almost always one of three fixable issues: the description does not match the dominant query, the length is wrong, or the description is duplicated across pages. Together those three explain roughly 75 percent of rewrites. Each has a mechanical fix you can ship in an afternoon.
Audit Search Console for the queries each page actually ranks for. Rewrite descriptions to lead with the dominant query. Validate length against the 920- pixel desktop and 580-pixel mobile budgets. Dedupe across the sitemap. Do those four things and your description-retention rate climbs from roughly 30 percent to 70 to 80 percent across the site. The other two percent of rewrites you cannot fix are not worth the effort to chase.