Free Meta Description Checker

Meta description length, rewrites, and the sentence Google shows instead.

Two lines of grey text under a blue link decide whether a searcher opens the page. Here is how the tag works, how long it should be, when Google ignores it, and why a firm in a regulated business should read its own snippet the way a reviewer reads an ad.

What the tag is and where it sits

A meta description is one element in the <head> of an HTML page. Nothing about it appears on the page itself. It exists to be read by software: search engines that need a summary to put under the title in a result, and link-preview tools that need a line of text for a card. Each page gets its own, and each page should have exactly one.

<head>
  <title>Roth Conversions for Retirees | Example Advisors</title>
  <!-- one per page, written for this page -->
  <meta name="description"
        content="How a Roth conversion is taxed, when converting can make
                 sense for a retiree, and the questions to ask your planner
                 before you convert. Not tax advice.">
</head>

Google calls the text under a result the snippet, and the meta description is only one of its possible sources. The page title becomes the blue link, the address becomes the breadcrumb above it, and the snippet is what is left to make the case. A meta tag checker that reads every tag at once will show you the description among a dozen others; this one reads only the description, and reports on it in detail.

How long a meta description should be

There is no official meta description character limit. Google's own documentation says there is no limit on how long a description can be, and that the snippet is truncated in results as needed, typically to fit the device width. Every number you will read elsewhere is an estimate of where that cut tends to land: pages cite anything from 120 to 160 characters, often about 155, and about 920 pixels across two lines on a desktop result.

Pixels are the truer unit, because the cut is made by width, not by count. Letters are not the same width in the typeface Google uses: a line of capital Ws runs out of room long before a line of lowercase Ls. Two descriptions of 150 characters can end at different words, and a phone shows less than a desktop. That is why this checker gives you both. The verdict counts characters against fixed limits, because a count is deterministic and the same everywhere. The preview measures the actual text with Arial's character widths at 14px and greys whatever runs past about 920 pixels, which is a common estimate and nothing more.

The limits the checker uses are Verand's own: under 70 characters is flagged as short, because it leaves most of the snippet to chance, and over 160 is flagged as too long, because the end is the part most likely to be cut. The end of a description is often where the useful detail sits, such as the qualifier, the call to action or the disclosure. Put anything that must be read in the first sentence.

Not a ranking factor, and still worth writing

Google has said this directly since 2009, on its Search Central blog: even though it sometimes uses the description meta tag for the snippets it shows, it does not use the description meta tag in ranking. Adding keywords to it will not move a page up. What it can change is what a searcher reads once the page already ranks: whether the snippet answers their question, sounds like the firm, and gives them a reason to choose this result over the one beside it. Its job is to earn the click the ranking has already made possible.

When Google ignores yours, and where the snippet comes from instead

Most people assume the description is the snippet. Google's documentation says the opposite: snippets are primarily created from the page content itself, and Google sometimes uses the meta description if it might give users a more accurate description. The snippet is chosen per search. For a query that your description answers, you will often see your own words. For a query about one detail on the page, Google tends to show the passage that matches it, and the same page can carry a different snippet for every search that finds it.

When your description is set aside, the replacement comes from the visible text. In practice that is often the opening paragraph, or a sentence near a heading that matches the search, which is why the first paragraph of a page deserves the same care as the tag. You have three documented controls over what can be pulled:

<!-- keep one passage out of snippets -->
<div data-nosnippet>Past performance table and its footnotes</div>

<!-- cap the snippet length for the whole page -->
<meta name="robots" content="max-snippet:160">

<!-- no text snippet at all -->
<meta name="robots" content="nosnippet">

Use the heavy ones carefully. Google documents that nosnippet also keeps the page's content from being used as a direct input for AI Overviews and AI Mode, and that max-snippet limits that use too. data-nosnippet is the precise tool: it works on span, div and section elements, leaves the rest of the page eligible, and should be present in the HTML rather than added or removed later by a script.

Descriptions set by JavaScript

Some sites write the description into the page with JavaScript after it loads, which is common on single-page apps and in some site builders. Google says you can set or change the description that way, because it renders pages; it also says pages wait in a rendering queue that can take longer than a few seconds. Many other readers never run the script. A link-preview scraper, a monitoring tool or this checker requests the page and reads what the server sent. If the checker reports a missing description on a page where you can see one in your browser's inspector, the tag is most likely being added by script. The reliable fix is to put it in the HTML the server returns.

One page, one description

Google's guidance is plain: identical or similar descriptions on every page of a site aren't helpful when individual pages appear in results, and wherever possible each description should describe its own page. Templates are the usual culprit. A theme that fills every blog post with the site's tagline, or a product catalogue with one sentence and a changing name, produces hundreds of descriptions that say nothing specific. A single-URL check cannot see this, which is why this page does not claim to. Verand's full site audit compares every page's description against every other and flags the shared ones.

The snippet is advertising copy, read on its own

Most guides treat rewriting as a click-through problem. For a firm in a regulated business it is also a review problem. The snippet appears under your name, on a page you do not control, stripped of everything around it. Google can replace your carefully reviewed description with any sentence from the page: a return figure without the footnote that qualifies it, a client's words without the context that made them permissible to publish, a line from a disclosure that reads oddly alone. Nobody on your side signed off that snippet, because nobody wrote it.

Two habits reduce the risk. First, write the description so it is safe to show alone: no promise of an outcome, no testimonial, no number that needs a qualifier the snippet cannot carry. Second, treat the first paragraph of the page the same way, because it is the text Google most often reaches for when it sets your description aside. Where a passage must never appear without its context, data-nosnippet keeps it out of snippets while leaving it on the page. None of this replaces your own review; confirm the wording with whoever signs off your marketing.

Common mistakes

• No description at all. Google then builds a snippet from the page, which is fine for a recipe and a risk for a financial product page. The checker reports it as the first fail.
• The same description on every page. Usually a theme default. The tag is present, the length is right, and it tells the searcher nothing about this page.
• The important part at the end. The qualifier, the location or the next step placed after 150 characters is the part most likely to be cut.
• Keyword lists. A string of phrases separated by commas does not help ranking and reads badly as a snippet, so Google is more likely to replace it.
• Two description tags. A plugin and a theme each add one. Different tools read different ones; this checker reads the first.
• Written by script only. Visible in the browser, absent from the served HTML, and missing for every reader that does not render the page.
• Social copy that disagrees. The og:description on the same page says something different, so the link preview and the search result tell two stories. Check both.

What a good description looks like

One or two plain sentences, about 140 to 155 characters, that say what the page covers and for whom, in the words a searcher would use. Front-load the specific part. Leave out anything you would not want quoted without its context. Match the page: if the description promises a checklist, the page should have one. Then re-check it after any template change, because descriptions are the kind of thing a theme update quietly replaces.