Skip to content
pageinspection

The same description on ninety pages, and what it signals

This is the finding most likely to consume a week and return nothing. A repeated description does not split rankings, does not cannibalise anything and is usually rewritten before anyone reads it. It is still worth knowing what it tells you.

The short answer

A description repeated across pages costs almost nothing directly, because Google rewrites most snippets anyway. What it signals is a template that does not distinguish its pages, and the same template usually produces duplicate titles too. Fix the pattern where it is worth fixing, and leave a shared description alone where the pages genuinely differ only by a variable.

RefinementAudit check · Unique descriptions

What a repeated description actually costs

Nothing in the index. The meta description has not been a ranking input for a very long time, and repeating one does not create competing candidates the way a repeated title does. Two pages sharing a description are two pages that both still rank on their own merits.

What it costs is smaller and real. When Google does use your description, a generic one performs worse than a specific one, because the reader is scanning for confirmation that this result answers their question and a template cannot provide that. Multiply a small difference in click-through across a category of four hundred product pages and it stops being nothing.

The second cost is diagnostic and it is the better reason to look. A description repeated on ninety URLs is a template speaking, and templates that fill this field carelessly usually fill other fields carelessly too. It is a cheap way to find the ninety pages nobody has edited since they were imported.

One per page does not scale, and does not need to

The standard advice is a unique description for every URL, which is achievable on a sixty-page site and dishonest advice for a catalogue of nine thousand. Nobody is going to write nine thousand of these, and a plan that requires it produces nine thousand generated strings, which is where you started.

Three positions, and all three are defensible depending on the page.

  • Write them by hand on pages you compete for. Your twenty or fifty most important URLs. This is where a specific line earns its keep, and where you know enough about the query to write one.
  • Generate them from real fields on templated pages. Not from a fixed sentence with the product name dropped in, but from attributes that actually vary: material, size, price band, the two specifications a buyer compares. A generated description built from four differing values is unique because the values are, and it reads as information rather than as filler.
  • Leave the tag off entirely on the long tail. This is the option nobody mentions and it is often the best one. With no description, Google composes a snippet from the page body, matched to the query that was actually typed. That is frequently better than a generic sentence, because it is responsive and your string is not.

Omitting the tag is not the same as leaving it empty.

An empty content="" is a declaration that this page has no description, and some tools will read it as one. If you have decided not to write a description, do not emit the tag at all. This distinction matters more than anything else on this page, because a template that outputs an empty string on every URL with no description has turned a reasonable decision into a site-wide defect.

The rule that follows: decide per template, not per page. A category template writes them from fields, an editorial template asks the author, a tag-archive template omits the tag. Three decisions cover the whole site.

The useful finding is the template, not the string

Knowing that a sentence repeats is easy and not very actionable. What you want is which template produced it and how many URLs it covers, because that is the unit the fix applies to, and a template only becomes visible once you have seen a set of its pages together.

This one needs the full crawl

The useful output is not that a string repeats, it is which template emitted it and across how many URLs, and a template only becomes visible once you have seen its pages together.

The instant search on this site audits a single page, so rather than show you a verdict it cannot support, this guide sends you to the place the check actually runs.

Run the full audit, free

For what to write when you do write one, including the length band and why Google replaces yours, see the descriptions guide.

Why the bottom of the scale is the honest place for this

Everything about this check argues for a Refinement. The pages work. They are indexed, they rank, they are found. The tag is not a ranking input. Google rewrites it much of the time regardless of what you put there. And the recommended fix on a long tail is frequently to remove the tag rather than to improve it.

It is in the catalogue rather than omitted because the effect on click-through is real, and because a repeated string is a reliable marker for pages nobody has looked at. Both of those are worth surfacing. Neither is worth a place ahead of a finding that keeps a page out of the results.

There is a version of this that deserves a higher rating and it is not the one the check measures. If your descriptions are duplicated because the pages are duplicated, the finding under it is a duplicate cluster, and that is rated Critical for good reasons. The description was just the first place you noticed.

Grouping repeats by the template behind them

The count is not the interesting output. The URL pattern is, because it names the template you need to change.

description-groups.sh
curl -s https://example.com/sitemap.xml \
  | grep -o '<loc>[^<]*</loc>' | sed 's/<[^>]*>//g' \
  | while read -r url; do
      d=$(curl -s "$url" | tr '\n' ' ' \
        | grep -o 'name="description" content="[^"]*"' \
        | sed 's/.*content="//;s/"$//')
      printf '%s\t%s\n' "${d:-MISSING}" "$url"
    done > /tmp/desc.tsv

# how many URLs share each description
cut -f1 /tmp/desc.tsv | sort | uniq -c | sort -rn | head

# the path segment behind the biggest group: that is the template to change
biggest=$(cut -f1 /tmp/desc.tsv | sort | uniq -c | sort -rn \
  | awk 'NR==1 { sub(/^ *[0-9]+ /, ""); print }')

grep -F "$biggest" /tmp/desc.tsv | cut -f2 | cut -d/ -f4 | sort | uniq -c

A MISSING group is not a failure, and reading it as one is how a site ends up emitting an empty tag everywhere. Check whether those pages are the long tail you deliberately left alone before you do anything about them.

If the largest group covers one path prefix, you have found your template and the whole finding collapses to a single change. If repeats are scattered across unrelated prefixes, they were written by people copying each other, and that is a style guide problem rather than an engineering one.

Questions this check raises

Do duplicate meta descriptions hurt rankings?
No. Descriptions are not a ranking signal, duplicated or otherwise, and Google replaces most of them with a query-matched snippet regardless. The finding is useful as a symptom: the same template producing repeated descriptions is usually producing repeated titles, and those do cost you.
Should every page have a unique meta description?
On a site of a few hundred pages, yes, where you have something specific to say. Past that, no: writing 4,000 unique descriptions by hand produces 4,000 near-identical sentences, which is the same problem with more work. Leave the tag off where you cannot say something different.
Is it better to delete a duplicate description or rewrite it?
Delete it, unless you have a genuinely different pitch to write. A blank tag lets the engine assemble a snippet matched to the query, which usually beats a generic sentence. A rewritten description that differs only in word order is a duplicate with extra steps.