Duplicate Content
The same or very similar content at more than one URL. Google picks a canonical URL; some duplication is normal and not a spam violation, but it splits signals and wastes crawling.
Reviewed by Alexander Yarovenko · Updated: 2026-10-08
Duplicate content is the same or very similar content reachable at more than one URL, on one site or across several. Google clusters such pages, picks one as the canonical URL and shows that one in results. Google says some duplicate content is normal and not a violation of its spam policies. The real costs are quieter: a confusing experience for people, split signals and harder tracking, and crawling time spent on copies.
What it is and where the boundary lies
Duplicates come from ordinary site mechanics. Google lists five reasons: region variants with essentially the same content in the same language, device variants such as separate mobile and desktop URLs, protocol variants such as HTTP and HTTPS, site functions such as sorting and filtering, and accidental variants such as a demo copy left open to crawlers. Language versions are duplicates only when the main content is in the same language: if only the header and footer are translated, the pages still count as duplicates.
How it differs from similar terms
| Term | What it is | Relation to duplicate content |
|---|---|---|
| Duplicate content | one content at several URLs | the situation |
| Canonical tag | a link element naming the preferred URL | a signal for choosing among duplicates |
| 301 redirect | a permanent move to another URL | a strong signal that the target is canonical |
| Keyword cannibalization | several different pages competing for one query | different pages, not copies |
| URL parameters | query strings added to a URL | a common source of duplicates |
Why it matters
Google gives the reasons itself. A person may wonder which page is the right one, and it becomes harder to see how a piece of content performs when several URLs share it. Signals from other sites, such as links, are also split across the versions unless they are consolidated onto one preferred URL. And Googlebot may spend crawling time on copies instead of new or updated pages: the canonical is crawled most regularly, and duplicates less often. Google describes these as reasons to specify a canonical, not as a penalty.
How to find and handle it
- Look at the Page indexing report. Statuses such as “Alternate page with proper canonical tag”, “Duplicate without user-selected canonical” and “Duplicate, Google chose different canonical than user” show how Google grouped your URLs. The first usually needs nothing.
- Inspect a URL. The URL Inspection tool shows both the canonical you declared and the one Google selected.
- Find the cause. Check sorting and filter parameters, HTTP and HTTPS, www and non-www, trailing slashes, session or tracking parameters, and test or staging copies.
- Pick the preferred URL and signal it. Use a permanent redirect when you are retiring a duplicate, a rel="canonical" link when both URLs must stay available, and list only canonical URLs in your sitemap.
- Link to the canonical. Link internally to the URL you consider canonical, consistently.
Practical example
| URL | Treatment |
|---|---|
| https://example.com/dresses/ | the canonical, with a self-referential rel="canonical" |
| https://example.com/dresses/?sort=price | stays available for users, rel="canonical" points to the clean URL |
| http://example.com/dresses/ | permanent redirect to the HTTPS URL |
Google may still choose a different canonical than you declare, because a declared preference is a hint, not a rule.
Common mistakes
- Blocking duplicates in robots.txt: Google says not to use it for canonicalization, because URLs disallowed there may still be indexed without their content.
- Using noindex to choose a canonical: Google does not recommend it within one site, since it removes the page from Search entirely.
- Using the removal tool for it: it hides all versions of a URL.
- Sending conflicting signals: do not name one URL in the sitemap and another in rel="canonical" for the same page.
- Using relative canonical URLs: Google supports them but recommends absolute ones.
How to validate the result
After the change, inspect an affected URL and check that Google’s selected canonical matches yours. Watch the Page indexing report for the duplicate statuses to shrink on the URLs you consolidated, and compare equal periods of clicks and impressions for the preferred URL with the same filters. Allow time for recrawling: duplicates are crawled less often.
More questions
Does duplicate content cause a penalty?
Google says some duplicate content on a site is normal and not a violation of its spam policies. The cost is split signals, a confusing experience and wasted crawling.
Do I need a canonical tag?
Not strictly. Google says none of the methods is required, and that without a preference it picks the version it considers best. Specifying one is useful when you care which URL appears.
Is a translated page a duplicate?
Not when the main content is in another language. Use hreflang for language versions, and note that canonical annotations carrying hreflang are not used for canonicalization.
Next practical step
Open the Page indexing report, filter for the duplicate statuses and pick the three URLs that matter most. Inspect them and write down which canonical you want. See also the canonical tag entry.
Related concepts
- Canonical tag — the signal for the preferred URL.
- 301 redirect — retiring a duplicate for good.
- URL parameters — a common source of copies.
- Hreflang — marking language and region versions.
- Crawl budget — crawling time spent on copies.