Duplicate Content in SEO: Causes, Canonicals and Fixes

What counts as duplicate content?

Consider a guide available at both https://example.com/guide/ and https://example.com/guide/?utm_source=email. If the tracking parameter makes no difference to the article, the two addresses lead to the same main content. Print-friendly versions, session identifiers and HTTP or HTTPS variants can create similar situations.

Not every URL parameter creates a duplicate. A filter that changes the products shown on a category page may produce a useful, distinct result. Nor is the navigation or footer text repeated across a website, on its own, a reason to treat every page as duplicate content. What matters is the main content and the purpose of each URL.

Why Google selects one version

When Google detects duplicate or very similar pages, its systems select a canonical URL to represent the group in Search. Other versions may remain accessible but need not appear as separate search results. This is normal canonicalisation, not evidence that the site has received a duplicate-content penalty. Separately, copying material as part of manipulative spam practices can raise other policy concerns; duplication alone does not establish that.

Site owners can express their preference through redirects, canonical annotations and consistent internal URLs. Google may still choose another version. For detailed implementation, see MOCOBIN’s guide to canonical tags and URL selection.

When duplication becomes an SEO problem

The clearest problem is a mismatch: Google selects a URL that is not the version you want visitors to reach. Perhaps it chooses a parameter-based address, an outdated article or a page with less useful navigation. That warrants investigation. Simply seeing ‘Alternate page with proper canonical tag’ in Search Console does not.

Link signals are not automatically lost

If links point to several versions of the same material, Google can consolidate signals around its chosen canonical URL. It is therefore misleading to say that duplicate pages always divide link equity or that adding a canonical tag guarantees higher rankings. Consistent redirects and internal links to the preferred URL make your intentions clearer, but they do not promise a particular search position.

Crawl budget depends on scale

Large sites with many parameter combinations can spend substantial crawler activity on URLs that offer little new content. That can matter when important new or updated pages also need to be discovered. Google frames advanced crawl-budget management primarily around very large or frequently updated sites and sites with substantial discovery backlogs. For a smaller publication, checking indexing and keeping the sitemap accurate is generally a more useful starting point than trying to eliminate every duplicate URL.

How to check duplicate URLs in Google Search Console

Use the Page indexing report, which replaced the old Coverage report terminology. Its duplicate-related classifications include ‘Alternate page with proper canonical tag’, ‘Duplicate without user-selected canonical’ and ‘Duplicate, Google chose different canonical than user’. These descriptions are starting points, not automatic instructions to fix every excluded URL.

1. Find an affected URL. Review the relevant category in Page indexing and identify a representative page, especially one you expected to be indexed.
2. Inspect that exact URL. Use URL Inspection to compare the user-declared canonical with Google’s selected canonical and check when the URL was last crawled.
3. Check what the site actually serves. Review the HTTP response, redirects, canonical annotation in the rendered page, relevant internal links and the XML sitemap. A 301 redirect and a canonical tag pointing back to the retired address send conflicting signals.
4. Decide whether the duplicate is intentional. If Google has selected the intended version and users can reach it, you may not need to change anything.

A site-restricted search with a quoted phrase may reveal possible repeated pages, but it is not a reliable inventory of every indexed duplicate. For substantially copied text on other websites, a plagiarism-checking service serves a different purpose; MOCOBIN covers that task in its Copyscape guide. Neither method replaces URL Inspection when the question is which version Google considers canonical.

Which fix fits the URL?

Choose the method according to what visitors and search engines should be able to do with the alternate address. These controls are not interchangeable.

• Permanent redirect: Use a 301 or 308 when an old URL has genuinely been replaced and should take visitors directly to a relevant new location. A permanent redirect is a strong canonical signal, not a promise of a specific ranking outcome.
• Canonical annotation: Use rel="canonical" when two pages are duplicate or very similar but both need to remain accessible. Point to the preferred, crawlable page. Google treats this as a strong signal, although it can select another canonical.
• Noindex: Use it when a page may remain available to visitors but should not appear in search. It is an indexing directive, not a substitute for canonicalisation or a way to transfer signals to another page. Google must be able to crawl the page to see the directive.
• Robots.txt: Use crawl rules selectively when low-value URL patterns, such as large faceted-navigation spaces, consume unnecessary crawling. Blocking a URL does not reliably remove it from the index, and it can prevent Google from seeing a noindex tag on that page. See MOCOBIN’s robots.txt guidance before changing rules.
• URL parameter cleanup: Reduce unnecessary parameter variants, keep internal links consistent and decide whether filtered pages have a distinct search purpose. Google’s old Search Console URL Parameters tool is no longer available. Google announced its retirement on 28 March 2022 and removed it about a month later. There is no replacement setting in Search Console for manually defining each parameter’s function.
• Content consolidation: When two editorial pages answer essentially the same question, compare their useful material before choosing a primary page. Merge what readers still need, then redirect a retired URL if the remaining page is a genuine replacement. If no relevant replacement exists, a proper 404 or 410 can be appropriate.

Keep your signals consistent after the fix

Canonical problems often come from disagreement between otherwise reasonable settings. For example, redirecting /old-guide/ to /guide/ while the new page declares /old-guide/ as canonical is contradictory. So is listing one version in the sitemap while continually linking to another, even though those signals do not all carry the same weight.

As part of routine technical SEO checks, make sure the intended page returns HTTP 200, its canonical points to the correct accessible URL, and retired URLs have appropriate responses. Avoid linking to tracking variants or redirect chains when the preferred address is known. Standardise HTTPS and URL casing where your server treats variations as separate paths.

Editorial duplication deserves a separate judgement. Two articles do not need merging merely because they share definitions or navigation. They do need clearer roles if both answer the same searcher’s question without adding distinct value. Consider that when planning new pages alongside your on-page SEO work, rather than waiting for Search Console to identify a technical duplicate.

A final check after publishing

Test the original and preferred URLs, inspect the canonical in the page source, update internal links and sitemap entries, then review URL Inspection after Google has recrawled the pages. A correct canonical annotation does not guarantee immediate reindexing, and an excluded alternate is not necessarily a problem to solve.