Fixing Meta Description Quality
The meta description is the short summary a page offers search engines for the text under its headline in results. Google does not always use it, but when it does, it is often the only thing a searcher reads before deciding whether to click.
The Meta Tag Analyzer flags descriptions that are missing, copied across many pages, too thin to be useful, or broken in the markup. This guide explains how Google treats the tag, how to write one that is likely to be shown, how to fill gaps across a large site without boilerplate, and how to fix the markup errors that quietly cut descriptions short.
- How Google uses the meta description
- What the analyzer flags, and how serious each is
- What a useful description says
- Markup faults that break descriptions
- Filling gaps across a large site without boilerplate
- When Google keeps showing different text
- The fix, step by step
- Keeping descriptions healthy
- Questions and answers
How Google uses the meta description
The tag itself is simple:
<meta name="description" content="Hand-made oak benches for gardens and patios, built to order in Derbyshire. Choose a length, finish and delivery date online.">Google builds the snippet under each result from several possible sources. The meta description is one of them; text on the page is another. Google has said it uses the description when it gives a more accurate summary of the page than the visible text does for that particular search. In practice this means:
- The same page can show different snippets for different searches, because Google picks the passage that best matches each one.
- A description that accurately summarises the page is used more often than one that is vague, stuffed with keywords or unrelated to the content.
- A missing description is not a penalty. Google simply writes its own from the page, which is sometimes excellent and sometimes a fragment of a cookie notice or a navigation menu.
- The description is not a ranking factor for Google. Writing a better one will not move a page up; it can make more people choose the result where it already appears.
Other readers use the tag as well. Bing uses it for its snippets, many link preview crawlers fall
back to it when a page has no og:description, and some AI assistants and site search tools
read it as a quick summary. That is a reason to make it accurate as well as appealing.
What the analyzer flags, and how serious each is
| Finding | Typical cause | Priority |
|---|---|---|
| Missing description | Pages created without anyone filling the field; a template with no fallback | Medium on important pages, low on minor ones |
| Same description on many pages | A site-wide default in the theme or plugin; a pattern that only inserts the site name | High: it wastes the tag everywhere and makes pages look alike |
| Very short description | A placeholder such as the page name repeated, or a single word | Medium |
| Very long description | The first paragraph of the page pasted in automatically | Low: Google shortens it, but the useful part may be cut off |
| More than one description tag | Theme and plugin both printing one | Medium: readers may pick either |
| Description cut short in the source | A double quote inside the text closing the attribute | High where it happens, easy to fix |
| Description does not match the page | Copied from an older version or another page | High: likely to be ignored, and misleading if shown |
There is no single correct length. Google shortens snippets to fit the space available, which is measured in pixels and depends on the device, so a character count is only a guide. Descriptions of roughly 120 to 160 characters usually show in full on desktop, and the first 100 or so characters are what matter most on a phone. Put the essential information first and treat the rest as a bonus.
What a useful description says
A good description answers the question a searcher has at the moment they see the result: is this the page I want? The most reliable way to write one is to describe what is on the page, in the searcher's words, with one detail that sets it apart.
A simple structure
- What the page is: the product, service, answer or guide, named plainly.
- The detail that matters: the location, the size of the range, the time it takes, who it is for, or what is included.
- What the visitor can do: book, compare, download, read, order, only if that is true on the page.
Before and after
| Page | Weak | Better |
|---|---|---|
| Service page for a fictional electrician | Welcome to Brightwell Electrical, the best electricians. Quality service. Contact us today! | NICEIC-registered electricians in Sheffield for rewires, fuse board upgrades and EV charger fitting. Fixed quotes, and most jobs booked within a week. |
| Blog article | In this article we will look at everything you need to know about damp. | How to tell condensation, rising damp and penetrating damp apart, with photos of each, a simple test you can do at home and when to call a surveyor. |
| Category page | Shop our range of garden furniture at great prices. | Oak, teak and aluminium garden furniture: 60+ benches, tables and dining sets, with free delivery across mainland UK on orders over the threshold shown at checkout. |
The better versions are specific, match what a searcher would type, and make no claims the page cannot back up. Superlatives such as "best" and "number one" add nothing and can make a result look less trustworthy.
Things to leave out
- Lists of keywords. Google may show them, and they read badly.
- Prices and stock that change. If they are pulled from live data, fine; if typed by hand, they go out of date and the snippet contradicts the page.
- The site name alone. It already appears near the result.
- Anything not on the page. An offer or promise in the description that the page does not mention is misleading, and Google is more likely to replace it.
Markup faults that break descriptions
Some description problems have nothing to do with the writing. They come from the way the text is placed into the HTML.
Unescaped quotes
If a description contains a double quote and the template does not escape it, the attribute ends early:
<meta name="description" content="Our "Heritage" range of oak benches, made to order.">Parsers read the content as Our and treat the rest as junk attributes. The template
must escape the value, so the quote becomes ", or editors should use typographic
quotes or single quotes in the text. In PHP that means htmlspecialchars(); in Liquid, the
escape filter; in most modern frameworks, escaping happens automatically when the value
is passed as data rather than pasted as a string.
HTML and line breaks inside the value
When a description is built from the page's first paragraph, it can carry tags, shortcodes or line breaks. Strip tags and shortcodes, collapse whitespace to single spaces and trim the result before it is printed.
Wrong attribute names
The tag must use name="description". Variants such as property="description",
name="Description " with a trailing space, or itemprop="description" in the
head are not read as the meta description by search engines.
Description added by script
Google renders JavaScript and can read a description set by a script, but many other crawlers do not, and the change can arrive late. Print the description in the server-rendered HTML.
curl -s https://www.example.co.uk/page/ | grep -io '<meta[^>]*description[^>]*>'.
Two lines means two tags; a line that stops mid-sentence means a quote problem.Filling gaps across a large site without boilerplate
A shop with 3,000 products or a blog with 800 posts cannot have every description written by hand straight away, and does not need to. The aim is to write the ones that matter and give the rest a fallback that is at least specific to each page.
Decide which pages get hand-written text
In Search Console, open the Performance report, filter to pages, and sort by impressions. Pages with many impressions and a low click-through rate for their position are where a better description is most likely to help. Add the home page, main service or category pages and best-selling products. For most small sites this is a list of twenty to a hundred pages, which is a day or two of writing.
Build fallbacks from real page data
For everything else, build the description from fields that differ between pages. Some examples:
- Products: product name, material or key attribute, category, and a fixed line about delivery or returns that is true site-wide.
- Articles: the article's own summary or excerpt field, written by the author, rather than the first paragraph.
- Locations: service, town and the one or two services most asked about there.
- Categories: category name, number of items and the main sub-types.
A fallback built this way produces a distinct description on every page, which is better than one sentence repeated thousands of times. It is not as good as a written one, so treat it as the floor rather than the finished job.
When leaving it blank is reasonable
For large archives of minor pages, such as old news items or tag archives, a missing description can be a sensible choice: Google will write a snippet from the page that matches each search. What you should avoid is a single default description applied to all of them, which is worse than none because every result then says the same thing.
When Google keeps showing different text
If a page has a good description and Google still shows something else, check these before rewriting it again:
- Is the search one the description covers? For a long or specific query, Google often prefers a passage from the page that answers it directly. That is normal and often helps.
- Is the description actually in the served HTML? Check the source, not the plugin field. Caching, duplicate tags or a failed template variable may mean the text you wrote is not what is sent.
- Is Google still using an old copy? Changes appear only after the page is recrawled. Use URL Inspection to request indexing for important pages.
- Is a snippet control in place? A robots meta tag with
nosnippetor a smallmax-snippetvalue stops or shortens snippets whatever the description says. The robots meta guide covers those directives.
You can also keep specific text out of snippets by marking it on the page with the data-nosnippet
attribute, for example a disclaimer or a cookie message that keeps turning up in results:
<div data-nosnippet>Prices shown include VAT. Offers end when stocks run out.</div>That is a way to stop bad fragments being chosen, not a way to force your description to be used.
The fix, step by step
Step 1
Group the flagged pages by template
Run the Meta Tag Analyzer across a sample of each page type and copy the description findings into a spreadsheet with the address, the current text, its length and the page type. Sort by page type. Repeated faults on one type point to a template rule or plugin default, while scattered missing descriptions usually mean editors left the field empty. Treat those two groups separately, because the first is fixed in code and the second by writing.
Step 2
Fix broken markup before rewriting anything
Look at the raw source of a flagged page. If there are two description tags, switch one
source off. If the text stops mid-sentence, a double quote is closing the attribute, so escape the value
in the template. If the value contains tags, shortcodes or line breaks, strip them and collapse the whitespace.
Make sure the tag uses name="description" and is printed in the server HTML, not added later
by a script.
Step 3
Write descriptions for the pages that earn clicks
Use the Search Console Performance report to list pages with plenty of impressions, then add the home page and main services, categories and products. For each, write one or two plain sentences that say what the page is, give the detail that matters most to a searcher, and name what they can do there. Put the key information in the first hundred characters, and do not promise anything the page does not show.
Step 4
Give each template a useful fallback
For pages nobody will write by hand, set the fallback in your SEO plugin or template to use fields that differ from page to page, such as the product name and main attribute, an article excerpt written by the author, or a category name with its item count. Avoid a single site-wide sentence. Where a page type has no good data to build from, leaving the description empty is better than repeating the same text everywhere.
Step 5
Remove duplicates at their source
Sort your spreadsheet by description text and look for identical values. Where one sentence appears on many pages, find the default that writes it, which is often a theme option, a plugin setting for a post type or a hard-coded tag in a header file, and replace it with the fallback from the previous step. Where two or three pages share a hand-written description, rewrite each so it describes its own page.
Step 6
Check the result in the page and in search
Clear your page and CDN caches, then run the analyzer again on the same pages and confirm each now has exactly one complete, distinct description. Request indexing for the most important pages in Search Console. After a few weeks, compare the click-through rate for those pages with the period before. Remember Google may still show page text for some searches, which is expected and not a sign the fix failed.
Keeping descriptions healthy
- Make the field part of publishing. Add "description written" to the checklist for new pages, products and posts, alongside the title and main image.
- Keep the fallback specific. Review template rules whenever a new page type or post type is added, so it does not inherit a generic default.
- Re-check after migrations and plugin changes. Switching SEO plugins or themes is the most common way descriptions disappear or duplicate. The WordPress meta tags guide covers moving data between plugins.
- Update descriptions when pages change. A price change, a new service area or a rewritten article can leave the description describing a page that no longer exists.
- Look at the whole result. The description works together with the title; the title tags guide covers the headline half.
1. What is the ideal meta description length?
There is no official length, because Google cuts snippets by the pixel width available rather than a character count, and the width differs between desktop and mobile. As a practical guide, around 120 to 160 characters usually displays without being cut on desktop, and the first 100 characters carry the most weight on phones. Rather than aiming for an exact number, put the most useful information first so that a shortened version still makes sense to the reader.
2. Why does Google ignore my meta description?
Google uses the description only when it judges it a better summary of the page for that search than text from the page itself. It is more likely to replace yours when the search is very specific, when the description is vague or stuffed with keywords, when it does not match the content, or when the same text appears on many pages. Also check the description is actually in the served HTML and not blocked by a nosnippet or small max-snippet directive.
3. Do meta descriptions affect rankings?
Not in Google. Google has said for many years that the meta description is not used as a ranking signal, so rewriting it will not move a page up or down. What it can change is how many people choose your result when it appears, because a clear, relevant summary helps a searcher decide. More clicks at the same position is a worthwhile outcome in its own right, which is why descriptions are still worth writing for important pages.
4. Is it bad to have duplicate meta descriptions?
It is not a penalty, but it is a waste. When hundreds of pages share one sentence, Google will usually ignore it and write its own snippets, and any result that does show the shared text looks the same as your other pages. Duplicates normally come from a site-wide default in a theme or plugin. Replace that default with a rule that builds a different description for each page, and write the important ones by hand.
5. Should I leave the meta description blank?
For your important pages, no: a written description gives you a say in how the result reads. For large numbers of minor pages, such as old news items or archive listings, leaving it blank is a reasonable choice, because Google will build a snippet from the page that suits each search. What you should avoid is filling those pages with one generic sentence, which is worse than leaving the field empty and letting Google choose.
6. Can I use emojis or special characters in a meta description?
You can, and Google sometimes shows them, but it does not promise to, and it may remove symbols it considers misleading or spammy. Plain text is the safer choice for most businesses. If you use characters such as ampersands, quotes or angle brackets, make sure the template escapes them, because an unescaped double quote will close the attribute and cut the description short. Ticks and stars used to imitate ratings or approval are best avoided.
7. How long does it take for a new meta description to show in Google?
Only after Google recrawls the page, which can take anything from a day to several weeks depending on how often the page is visited by its crawler. You can speed this up for individual important pages by using URL Inspection in Search Console and requesting indexing. Even after a recrawl, Google may still show page text for some searches, so check a few different queries before deciding the change has not worked.
The Meta Tag Analyzer reads the head of your page and checks description quality alongside title length and uniqueness, the canonical, robots directives, viewport, Open Graph and X card tags.
Open Meta Tag Fixes →