Fix library

How to fix a missing meta description

You fix a missing meta description by writing 1 unique description per page, phrased as the answer that page gives a searcher. Know what you are buying first. Google's snippet documentation says “Google sometimes uses the meta description HTML element if it might give users a more accurate description of the page than content taken directly from the page.” Sometimes. It is a suggestion for the snippet, not a ranking factor, and we will not sell it as one.

The symptom: the snippet is whatever Google scraped

Search for one of your pages and read the two lines under the title link. If the meta description is missing, those lines are whatever Google pulled from the page body: a cookie notice, the first line of your navigation, a sentence cut off mid-thought. The page still ranks where it ranks. It just makes its case to the searcher with words nobody chose.

The scaled version of the symptom is quieter. A site has four hundred pages, and every one of them carries the same description, pasted in by a theme or left at a plugin's default. The doc is direct about why that fails: “Identical or similar descriptions on every page of a site aren't helpful when individual pages appear in search results.” A duplicated description is functionally a missing one. It describes the site when the searcher is deciding between pages.

The cause: nobody owns the second line

Meta descriptions go missing or duplicate at scale for structural reasons, not lazy ones. A CMS template renders the field only when someone fills it in, and nobody fills it in. An ecommerce platform generates product pages from a feed that has no description column, so thousands of pages ship blank. A site-wide default gets set once, "Acme is your trusted partner for quality solutions", and cascades onto every URL. Or a migration drops the field silently and no one notices, because the pages look identical in a browser.

The underlying cause is that the description is invisible on the page itself. It never shows up in a design review. Its only audience is the search results page and the machines that read the head of your HTML, which is exactly why it is one of the most common failures we find and one of the cheapest to fix.

The fix: write the answer, one per page

Write each description as the short, plain answer a searcher would want from that page. Not a slogan, not a keyword string, not a restatement of the title. If someone asked "what will I get if I click this," the description is your reply. Include the concrete facts that page actually has: what it covers, what it costs, where you are, what makes it the right result.

<!-- Before: missing, or a site-wide default on every page -->
<meta name="description" content="Acme is your trusted partner for quality solutions.">

<!-- After: the specific answer this page gives -->
<meta name="description" content="What a metal roof repair costs in Austin,
what drives the price, and when a patch beats a replacement.
Licensed, with same-week inspections.">

Three rules keep it working at scale. One description per page, in the head, and only one, because duplicate tags force a machine to pick. Unique across pages, because two pages with the same description are telling searchers they are interchangeable. And truthful to the page, because a description that promises what the content does not deliver earns a click and loses it in five seconds. For generated pages, build the description from the same data as the page: product name, price range, location, availability. Specific beats polished. This is the same discipline as writing a citable first paragraph, which our answer block guide covers for the body of the page.

Be honest: this tag does not rank you, and Google often ignores it

Two truths the folklore leaves out. First, the meta description is not a ranking factor. It does not move your position. What it moves is the pitch your result makes once a position is earned, which affects whether people click. Treat it as ad copy for a slot you already hold. Second, Google frequently replaces it. The doc says snippets are primarily created from the page content itself. Your description is used when Google judges it more accurate than what it can extract, and skipped when it does not. Write a description that is genuinely the best summary of the page and it gets used more often. That is the whole lever.

And there is no official length rule. The doc states there is no limit on how long a meta description can be, and that the snippet is truncated in results as needed, typically to fit the device width. Truncation is display behavior on a screen, not a quality score. Any tool that fails your description at a fixed character count is enforcing a rule Google never wrote. Front-load the substance and the cut costs you little.

Verify: check the head, then check the results

View source on your key pages and confirm each has exactly one meta name="description" in the head, with text specific to that page. Then search for a few pages and compare the snippet Google shows against what you wrote. A match means your summary won. A mismatch is not an error, but if Google consistently prefers its own extraction, your description is not yet the best two lines about that page.

Then check it at scale, the way we would. Paste your URL into the Brimm audit and we will flag missing, duplicated, and boilerplate descriptions across the pages we crawl. If duplication runs deeper than the description tag, our duplicate content guide is the next read, and the title tag guide covers the line above this one.

See which of your pages pitch themselves, and which stay silent.

Paste your link. We check every description we can reach for missing, duplicate, and default text. The preview is free.