Consolidate duplicate URLs

Define a canonical page for similar or duplicate pages

If you have a single page accessible by multiple URLs, or different pages with similar content (for example, a page with both a mobile and a desktop version), Google sees these as duplicate versions of the same page. Google will choose one URL as the canonical version and crawl that, and all other URLs will be considered duplicate URLs and crawled less often.

If you don't explicitly tell Google which URL is canonical, Google will make the choice for you, or might consider them both of equal weight, which might lead to unwanted behavior, as explained below in Why should I choose a canonical URL?

What is a canonical URL?

A canonical URL is the URL of the page that Google thinks is most representative from a set of duplicate pages on your site. For example, if you have URLs for the same page (for example: example.com?dress=1234 and example.com/dresses/1234), Google chooses one as canonical. Note that the pages do not need to be absolutely identical; minor changes in sorting or filtering of list pages do not make the page unique (for example, sorting by price or filtering by item color).

The canonical can be in a different domain than a duplicate.

More details

When Googlebot indexes a site, it tries to determine the primary content of each page. If Googlebot finds multiple pages on the same site that seem to be the same, it chooses the page that it thinks is the most complete and useful, and marks it as canonical. The canonical page will be crawled most regularly; duplicates are crawled less frequently in order to reduce Google crawling load on your site.

Google chooses the canonical page based on a number of factors (or signals), such as whether the page is served via http or https; the user's declared preferred domain; page quality; presence of the URL in a sitemap; and any "rel=canonical" labeling. You can indicate your preference to Google using these techniques, but Google may choose a different page as canonical than you do, for various reasons.

Different language versions of a single page are considered duplicates only if the main content is in the same language (that is, if only the header, footer, and other non-critical text is translated, but the body remains the same, then the pages are considered to be duplicates).

Google uses the canonical pages as the main sources to evaluate content and quality. Google Search result usually points to the canonical page, unless one of the duplicates is explicitly better suited for a user: for example, the search result will probably point to the mobile page if the user is on a mobile device, even if the desktop page is marked as canonical.

Why would I have similar/duplicate pages?

There are valid reasons why your site might have different URLs that point to the same page, or have duplicate or very similar pages at different URLs. Here are the most common:

To support multiple device types:

https://example.com/news/koala-rampage
https://m.example.com/news/koala-rampage
https://amp.example.com/news/koala-rampage

To enable dynamic URLs for things like search parameters or session IDs:

https://www.example.com/products?category=dresses&color=green
https://example.com/dresses/cocktail?gclid=ABCD
https://www.example.com/dresses/green/greendress.html

If your blog system automatically saves multiple URLs as you position the same post under multiple sections.

https://blog.example.com/dresses/green-dresses-are-awesome/
https://blog.example.com/green-things/green-dresses-are-awesome/

If your server is configured to serve the same content for www/non-www http/https variants:

http://example.com/green-dresses
https://example.com/green-dresses
http://www.example.com/green-dresses

If content you provide on a blog for syndication to other sites is replicated in part or in full on those domains:
https://news.example.com/green-dresses-for-every-day-155672.html (syndicated post) https://blog.example.com/dresses/green-dresses-are-awesome/3245/ (original post)

Why should I choose a canonical URL?

There are a number of reasons why you would want to explicitly choose a canonical page in a set of duplicate/similar pages:

To specify which URL that you want people to see in search results. You might prefer people reach your green dresses product page via https://www.example.com/dresses/green/greendress.html rather than https://example.com/dresses/cocktail?gclid=ABCD.
To consolidate link signals for similar or duplicate pages. It helps search engines to be able to consolidate the information they have for the individual URLs (such as links to them) into a single, preferred URL. This means that links from other sites to http://example.com/dresses/cocktail?gclid=ABCD get consolidated with links to https://www.example.com/dresses/green/greendress.html.
To simplify tracking metrics for a single product/topic. With a variety of URLs, it's more challenging to get consolidated metrics for a specific piece of content.
To manage syndicated content. If you syndicate your content for publication on other domains, you want to consolidate page ranking to your preferred URL.
To avoid spending crawling time on duplicate pages. You want Googlebot to get the most out of your site, so it's better for it to to spend time crawling new (or updated) pages on your site, rather than crawling the desktop and mobile versions of the same pages.

Which is my canonical URL, according to Google?

Use the URL Inspection tool to learn which page Google considers canonical. Note that even if you explicitly designate a canonical page, Google might choose a different canonical for various reasons, such as performance or content.

Troubleshooting

If a canonical URL is in a property that you don't own, you won't be able to see any of the traffic for your duplicate page. Here are some common reasons that a canonical can exist in a separate property:

Incorrectly marked language variants: If you have multiple websites that serve substantially the same content localized to different users around the world, be sure to follow our guidelines for localized sites.
Incorrect canonical tags: Some content management systems (CMS) or CMS plugins can make incorrect use of canonicalization techniques to point to URLs on external websites. Check your content to see if this is the case. If your site is indicating an unexpected canonical URL preference, perhaps through incorrect use of rel="canonical" or a 301 redirect, fix that issue directly.
Misconfigured servers: Some hosting misconfigurations may cause unexpected cross-domain URL selection. For example:
- A server may be misconfigured to return content from a.com in response to a request for a URL on b.com
- Two unrelated web servers may return identical soft 404 pages that Google fails to identify as error pages.
Malicious hacking: Some attacks on websites introduce code that returns an HTTP 301 redirect or inserts a cross-domain rel=”canonical” link element into the HTML <head> or HTTP header, usually pointing to a URL hosting malicious or spammy content. In these cases our algorithms may select the malicious or spammy URL instead of the URL on the compromised website.
A copycat website: In rare situations, our algorithm may select a URL from an external site that is hosting your content without your permission. If you believe that another site is duplicating your content in violation of copyright law, you may contact the site’s host to request removal. In addition, you can request that Google remove the infringing page from our search results by filing a request under the Digital Millennium Copyright Act.

Specify a canonical page

There are a few different ways to specify the canonical page among a duplicate set, depending on your usage:

Method	Description
General guidelines	Follow these guidelines for all canonicalization methods.
Specify the preferred domain	Use Search Console to specify URLs on one domain as canonical over their counterparts on another domain. For example, example.com rather than www.example.com. Use this only when you have two similar sites that differ only by subdomain. Don't use this for http/https counterpart sites. Pros: Very easy to implement, manage, and change Use if you have identical sites on different domains. Cons: Works only at the domain granularity, and the pages must have identical paths and names to be considered duplicates. Enables only a single page-to-page mapping for identical path named pages.
rel=canonical <link> tag	Add a <link> tag in the code for all duplicate pages, pointing to the canonical page. Pros: Can map an infinite number of duplicate pages. Cons: Can add to the size of the page. Can be complex to maintain the mapping on larger sites, or sites where the URLs change often. Only works for HTML pages, not for files such as PDF. In such cases, you can use the rel=canonical HTTP header.
rel=canonical HTTP header	Send a rel=canonical header in your page response. Pros: Doesn't increase page size. Can map an infinite number of duplicate pages. Cons: Can be complex to maintain the mapping on larger sites, or sites where the URLs change often.
Sitemap	Specify your canonical pages in a sitemap. Pros: Easy to do and maintain, especially on large sites. Cons: Googlebot still must determine the associated duplicate for any canonicals that you declare in the sitemap. Less powerful signal to Googlebot than the rel=canonical mapping technique.
301 redirect	Use 301 redirects to tell Googlebot that a redirected URL is a better version than a given URL. Use this only when deprecating a duplicate page.
AMP variant	If one of your variants is an AMP page, you will need to follow the AMP guidelines to indicate the canonical page and AMP variant.

While we encourage you to use any of these methods, none of them are required. If you don't indicate a canonical URL, we'll identify what we think is the best version or URL.

General guidelines

For all canonicalization methods, follow these general guidelines.

General guidelines

Don't use the robots.txt file for canonicalization purposes.
Don't use the URL removal tool for canonicalization: it removes all versions of a URL from search.
Don't specify different URLs as canonical for the same page using the same or different canonicalization techniques (for example, don't specify one URL in a sitemap but a different URL for that same page using rel="canonical").
Don't use noindex as a means to prevent selection of a canonical page. This directive is intended to exclude the page from the index, not to manage the choice of a canonical page.
Do specify a canonical page when using hreflang tags. Specify a canonical page in same language, or the best possible substitute language if a canonical doesn't exist for the same language.
Do link to the canonical URL rather than a duplicate URL, when linking within your site. Linking consistently to the URL that you consider to be canonical helps Google understand your preference.

Prefer HTTPS over HTTP for canonical URLs

Google prefers HTTPS pages over equivalent HTTP pages as canonical, except when there are issues or conflicting signals such as the following:

The HTTPS page has an invalid SSL certificate.
The HTTPS page contains insecure dependencies (other than images).
The HTTPS page redirects users to or through an HTTP page.
The HTTPS page has a rel="canonical" link to the HTTP page.

Although our systems prefer HTTPS pages over HTTP pages by default, you can ensure this behavior by taking any of the following actions:

Add redirects from the HTTP page to the HTTPS page.
Add a rel="canonical" link from the HTTP page to the HTTPS page.
Implement HSTS.

To prevent Google from incorrectly making the HTTP page canonical, you should avoid the following practices:

Bad SSL certificates and HTTPS-to-HTTP redirects cause us to prefer HTTP very strongly. Implementing HSTS cannot override this strong preference.
Including the HTTP page in your sitemap or hreflang entries rather than the HTTPS version.
Implementing your SSL/TLS certificate for the wrong host-variant: for example, example.com serving the certificate for www.example.com. The certificate must match your complete site URL, or be a wildcard certificate that can be used for multiple subdomains on a domain.

Advanced users only: Tell Google to ignore dynamic parameters

Use Parameter Handling to tell Googlebot about any parameters that should be ignored when crawling. Ignoring certain parameters can reduce duplicate content in Google's index and make your site more crawlable. For example, if you specify that the parameter sessionid should be ignored, Googlebot will consider the following two URLs as duplicates:

https://www.example.com/dresses/green.php?sessionid=273749
https://www.example.com/dresses/green.php

Specific methods

Choose one of the following methods to specify a canonical URL for duplicate URLs or duplicate/similar pages.

Be sure to follow the general guidelines above for all methods.

Set a preferred domain

Use Search Console to tell Google which version of your site's URL you prefer as canonical for your domain:

https://www.example.com
https://example.com

If you set your preferred domain as https://example.com, Google treats similar URLs or pages on www.example.com as duplicates of pages on example.com.

Read Set your preferred domain for details.

Use rel="canonical" link tag

You can use a <link> tag in the page header to indicate when a page is a duplicate of another page.

Suppose you want https://example.com/dresses/green-dresses to be the canonical URL, even though a variety of URLs can access this content. Indicate this URL as canonical with these steps:

Mark all duplicate pages with a rel="canonical" link element. Add a <link> element with the attribute rel="canonical" to the <head> section of duplicate pages, pointing to the canonical page, like this one:
<link rel="canonical" href="https://example.com/dresses/green-dresses" />
If the canonical page has a mobile variant, add a rel="alternate" link to it, pointing to the mobile version of the page:
<link rel="alternate" media="only screen and (max-width: 640px)" href="http://m.example.com/dresses/green-dresses">
Add any hreflang or other redirects appropriate for the page.

Use absolute paths rather than relative paths with the rel="canonical" link element.

Use this structure: https://www.example.com/dresses/green/greendresss.html
Not this structure: /dresses/green/greendress.html

Use rel="canonical" HTTP header

If you can configure your server, you can use rel="canonical" HTTP headers (rather than HTML tags) to indicate the canonical URL for non-HTML documents such as PDF files.

For example, if you expose a PDF file through multiple URLs, you can return a rel="canonical" HTTP header such as the following for the duplicate URLs to tell Googlebot what is the the canonical URL for the PDF file:

Link: <http://www.example.com/downloads/white-paper.pdf>; rel="canonical"

Google currently supports this method for web search results only.

Use absolute paths rather than relative paths with the rel="canonical" link element. That is:
Use this structure: http://www.example.com/downloads/white-paper.pdf
Not this structure: /downloads/white-paper.pdf

Use a sitemap

Pick a canonical URL for each of your pages and submit them in a sitemap. All pages listed in a sitemap are suggested as canonicals; Googlebot will decide which pages (if any) pages are duplicates, based on similarity of content.

We don't guarantee that we'll consider the sitemap URLs to be canonical, but it is a simple way of defining canonicals for a large site, and sitemaps are a useful way to tell Google which pages you consider most important on your site.

Don't include non-canonical pages in a sitemap. If using a sitemap, specify only canonical URLs in the sitemap.

Use 301 redirects for retired URLs

Use this method when you want to get rid of existing duplicate pages, but need to ensure a smooth transition before you retire the old URLs.

Suppose your page can be reached in multiple ways:

https://example.com/home
https://home.example.com
https://www.example.com

Pick one of those URLs as your canonical URL and use 301 redirects to send traffic from the other URLs to your preferred URL. A server-side 301 redirect is the best way to ensure that users and search engines are directed to the correct page. The 301 status code means that a page has permanently moved to a new location.

If you are on a website hosting service, do a search for their documentation on setting up 301 redirects.

Was this helpful?

How can we improve it?