Duplicated titles and descriptions: what they cost

Two pages carrying the same title tag are not being punished for it. What they are doing is failing to tell anybody which is which, including the engine deciding which of them to show. That decision then gets made without your input, and the cost of duplicates is entirely contained in that sentence.

Where they come from

Duplicates come from templates and structure rather than from carelessness, and none of the sources below is a mistake on its own.

• A template that names the section rather than the page

  Every HTML page in a section inherits the same pattern, and the variable part is either missing or sits so late that the first words are identical across hundreds of pages.

• Pagination

  The second, third, and fortieth page of a listing are generated by the same code and described by the same words. It is often the largest source by count and the least noticed, because nobody looks at page fourteen.

• Filters and facets

  Every combination of options produces a URL, and every one of them inherits the description of the thing being filtered. A modest catalogue can generate thousands of pages this way, all correctly described and all described identically.

• Near-identical items

  Product variants, locations, or entries that differ in one attribute and share everything else. Here the duplication in the metadata honestly reflects duplication in the content, which is a different problem wearing the same clothes.

What they actually cost

Duplicates cost you the choice of which page is shown, set your pages competing with each other, and make the description less likely to be used; the first cost is usually the one that matters.

• You stop choosing which page is shown

  When several of your pages answer a query equally, something has to pick, and if your metadata gives no basis for preferring one, the pick is made on other grounds. Sometimes it selects the page you would have chosen. Often it selects a filtered view, a paginated page, or an old variant, and the visitor arrives somewhere adequate rather than somewhere good.

• Your pages compete with each other

  Two pages aiming at the same phrase divide the evidence that either is the right answer. Neither is stronger for the other's existence, and the version of this that hurts is the one where a strong page and a weak page both target the same thing.

• The description is less likely to be used at all

  Descriptions are suggestions rather than instructions, as the section on meta tags sets out, and a description that describes a hundred pages equally is the least useful suggestion available. Generic text is the text most likely to be replaced by something drawn from the page.

Absent from the list: there is no penalty here, and treating duplicates as an infraction leads people to fix them cosmetically rather than structurally.

Pagination deserves its own answer

A paginated page should say plainly what it is, including its position in the sequence; a cleverer title does not help page two.

A paginated page usually should not be competing for anything. It exists so that people can reach further items, and its metadata should say plainly what it is rather than repeat the ambitions of the first page. Making the position in the sequence part of the title is enough to distinguish it, and it also stops the page from claiming to be the main answer to a query it should not win.

If pages deep in a sequence do attract visitors, that is worth understanding before optimising: it usually means the content people wanted is buried, and the fix is in the structure.

Filters are a structural decision

With facets, the metadata is downstream of a decision nobody wrote down.

The question is not how to describe ten thousand filtered views. It is which of them should exist as separate addresses at all. A filter combination that matches real demand deserves a page and its own description. One that exists only because the interface can produce it does not, and no amount of writing will make it distinct, because it is not distinct.

Where such pages should exist but should not be found separately, the instrument is a canonical declaration or an exclusion rather than a rewritten title. That is a decision of a different class from writing metadata.

Finding them

Export the pairs and count, rather than looking page by page.

Take every URL you publish with its title and its description, then count exact repeats. Sort the result by how much traffic the affected pages receive, because a duplicate on two pages nobody visits is not worth an hour and a duplicate across your busiest section is worth a day.

Then look for near-duplicates, which the exact count misses: identical openings with a different word at the end, or strings differing only by a number. Those behave like duplicates to a reader scanning results, since the part that distinguishes them arrives after the point where the eye stops.

Fixing them, in order

1. Make the pages different, or merge them

   If two pages genuinely say the same thing, one page saying it well is better than two saying it identically.

2. Lead with what distinguishes

   Where pages differ in one attribute, that attribute belongs at the front rather than after the words they share. This single change resolves much of the duplication a template produces.

3. Decide which pages should be found at all

   Pagination and facets are answered by structure, not by wording, and once that decision is made the metadata question usually disappears with it.

4. Do not manufacture variety

   Padding titles with filler to make strings differ produces different text and identical meaning. It satisfies a report and helps nobody, and it makes the next person believe the problem was solved.

FAQ