Free tool · On-page SEO
To check meta descriptions properly, check them in a batch: length and pixel width matter, but the finding you can only get from a set is the same description repeated across pages. Paste up to 25 below, one page per line, to see width, truncation and duplication together.
Free, and the checking happens in your browser. The live check against a deployed page needs a free sign-in.
Checked in your browser. Nothing is sent to us.
AEO depth layer
The live description and rewrite risk is computed from your own page and costs nothing to run. We ask for a free account because the expensive tools on this shelf stay free, and because it lets us tell you when your result changes. No card, no trial clock.
Signing in saves the details you entered above so we can follow up about your results. See our privacy policy for what we keep and why. The Meta Description Checker result you already have stays free either way. Privacy policy.
These four are the cases where a rewrite is close to certain. There is no matching set of signals that predicts the opposite. Google replaces descriptions routinely when an on-page extract answers the query better, so avoiding all four means there is no obvious reason to discard yours, not that yours will be shown.
| Signal | Why it triggers a rewrite |
|---|---|
| No description at all | With nothing to use, Google extracts a passage from the page. That is not a failure state, but it does mean the snippet is chosen for you. |
| Too short to answer anything | Under 70 characters there is rarely room to say what the page offers, and an on-page extract will usually serve the query better. |
| Shares almost nothing with the title | When the description and the title describe different things, Google has no reason to trust the description represents the page. |
| Used on more than one page | A description repeated across pages cannot be specific to any of them, so it is among the first things replaced with an extract. |
The thresholds this tool applies are ours, not Google's: under 70 characters counts as too short, and the 990px desktop budget is widely observed, not published by Google. Google states no limit for this field at all.
Where the usual checkers are equal, the table says so.
| Capability | This tool | Typical free checker |
|---|---|---|
| Length and truncation warning | Yes | Yes |
| Pixel width rather than character count | Yes | Usually characters |
| Batch of up to 25 pages | Yes | One at a time |
| Duplicate detection across pages | Yes | No |
| Accepts a crawler export paste | Yes | Form fields |
| Runs without sending your text anywhere | Yes | Usually posts it |
| Labels the budget as observed, not published | Yes | Shows it as a limit |
| Says Google often ignores the field | Yes | Implies you control it |
| Names the reasons a rewrite is likely | Yes, four of them | No |
| Live check against a deployed page | Yes, with a free account | No |
Checking a draft tells you whether it is well formed. Checking the page tells you whether the draft is what is actually live, which is a different question and more often the wrong answer than people expect.
For the visual version of the same check, the SERP snippet preview renders one title and description as they would appear and measures them with your browser's own text metrics. Then the h1 checker reports how far the heading and title agree, and the readability checker reads whether the page a snippet leads to can be quoted at all.
Step 1
Duplication is the finding worth having, and it only appears in a batch. Paste a URL and description per line, tab or pipe separated, which is what a crawler export gives you.
Step 2
One description across twelve pages is a bigger problem than twelve descriptions that are slightly too long, and it is the more common one on templated sites.
Step 3
A page with no description hands the snippet choice to Google entirely. A page with a short one usually gets overridden anyway. Both matter more than trimming a few pixels.
Step 4
Google replaces descriptions routinely when it judges an on-page extract a better answer. Write something specific and true, check it is not duplicated, and move on.
When you outgrow this tool
The batch check is free and complete on its own. Linkeddit is what you use once the descriptions are written and the question is which pages earn impressions and no clicks, which is where a snippet is actually costing you.
FAQ
How much the field is actually worth, why Google so often ignores it, and which problems are worth fixing first.
Long enough to say something specific, and the ceiling is a pixel question rather than a character one. The widely observed desktop cut is around 990 pixels, which is roughly 155 to 160 characters of ordinary prose. Google publishes no limit for this field. Below about 70 characters there is rarely room to say anything useful, which matters more than the upper bound because a thin description tends to get replaced.
Often not, and this is the single most important thing to understand before optimising them. Google replaces the description with its own extract from the page whenever it judges that a better answer to the specific query, which it does frequently and has confirmed doing. Writing one is still worth it for the queries where it is used verbatim, and treating it as a controllable field is a mistake.
Because the query asked something your description did not answer, so an extract from the body served the searcher better. The cases where a rewrite is close to certain are predictable: no description at all, one too short to answer anything, one duplicated across pages so it cannot be specific to any, and one sharing almost no meaningful words with the page's own title. This tool reports those four. What no tool can do is promise the reverse, and any that implies it is overselling.
Not as a penalty, and that framing misses the cost. A description repeated across twenty pages cannot be specific to any of them, so it is among the first things Google discards in favour of an extract, and you lose the chance to influence any of those snippets. It is also a reliable symptom of a template writing descriptions rather than a person, which usually means the underlying pages are thin too.
It is a lost opportunity rather than an error. Google will extract a passage from the page, and on a well-written page that extract is often good. The difference is that you did not choose it. For pages where the snippet matters, a landing page or a product page, write one. For a long tail of archive pages, letting Google choose is a perfectly defensible allocation of effort.
The live check. It fetches a page and shows the description actually deployed beside the one you drafted, so you can see whether the change ever shipped, and it flags an og:description that disagrees with it. It then reports which of the four rewrite signals apply to that page. It costs nothing to run and no model is involved.
Bulk mode with duplicate detection, which most free checkers do not have, and honest framing about what the field is worth. It measures pixels rather than characters, labels the budget as observation rather than a published limit, and says plainly that Google often ignores the field. Most of the category shows a green tick at 155 characters and implies you have secured your snippet.
Every tool on the shelf is free, with no card and no trial. Most need no account at all. See all free tools.
See where a title and description get cut on desktop and mobile, measured in your own browser rather than estimated from a character count.
Word and phrase frequency with the denominator stated, plus an honest note that density is not a ranking factor.
Flesch scores with every count they are derived from, long sentences listed, and passive voice shown as clauses you can overrule.
Thirty-five checks worth a hundred points, with every weight and every threshold printed before you enter a URL.