Canonical tag guide: when to use it and mistakes to avoid

A canonical tag tells search engines which URL is the main version of a page when the same or very similar content is reachable at several addresses. It is a single line in the page's head, and when it points to the wrong place it can pull a page out of Google without any warning.

This canonical tag guide covers how the tag works, when to use it, and the errors that cause the most damage.

In this guide

• What a canonical tag is
• When you need a canonical tag
• How to add a canonical tag correctly
• Canonical tag mistakes that hurt rankings
• How to audit canonicals across a site

What is a canonical tag?

A canonical tag is a link element with rel="canonical" that names the preferred URL for a page, such as <link rel="canonical" href="https://example.com/shoes/" />. Search engines use it to decide which URL to show in results and where to combine ranking signals.

Duplicate URLs appear more often than most site owners realise:

• Tracking parameters, such as ?utm_source=newsletter
• Sorting and filter options, such as ?sort=price
• Protocol and host versions, such as http:// and www
• Printer or session versions of the same page
• Syndicated copies of an article on another site

Google treats the canonical tag as a strong hint, not a command. It weighs the tag together with redirects, internal links and sitemaps, and it can choose a different URL when those signals disagree.

When do you need a canonical tag?

You need a canonical tag on every indexable page. Use a self-referencing canonical by default, and point to another URL only when the page truly duplicates that URL.

How to add a canonical tag correctly

Add one canonical tag in the <head> of each page, using an absolute URL that returns 200 and is indexable. That is the whole recipe, and every step of it matters.

1. Use an absolute URL. Write https://example.com/page/, not /page/.
2. Keep exactly one. Two canonical tags with different targets make Google ignore both.
3. Put it in the head. A canonical tag in the body is ignored.
4. Match your other signals. The canonical URL should be the one in your sitemap, your internal links and your hreflang tags.
5. Use the HTTP header for files. For PDFs and other non-HTML files, send Link: <https://example.com/guide.pdf>; rel="canonical" as a response header.

Canonical tag mistakes that hurt rankings

These canonical tag mistakes are among the most damaging technical SEO errors, because they look harmless in the code and only show up as lost traffic.

1. Every page canonicalised to the home page. A template bug sends all signals to /, so Google drops the inner pages.
2. Canonical to a URL that redirects or returns 404. The target must be a live, final URL with a 200 status.
3. Canonical to a noindex page. This sends mixed signals: "this is the main page" and "do not index this page".
4. Paginated pages pointing to page 1. Google then stops indexing the products or posts on later pages.
5. Translated pages pointing to English. Each language version should canonicalise to itself and use hreflang for the connection.
6. Relative or mixed-protocol URLs. A canonical to http:// on an https:// site invites Google to pick its own answer.
7. Canonical tags added by JavaScript only. Put the tag in the server HTML so it is there on the first read.

How to audit canonicals across a site

Audit canonicals by crawling the whole site and comparing each page's canonical with its own URL, its status code and the URLs in your sitemap.

1. Crawl the site. The Website Audit records the canonical of every page and lets you filter for pages whose canonical points elsewhere.
2. Check the targets. Every canonical target must return 200 and be indexable. The SEO Issue Checker flags canonicals that are missing, duplicated or pointing to a bad URL, and saves the URL, the canonical value and the target's status as proof.
3. Compare with the sitemap. Any URL in your sitemap should canonicalise to itself.
4. Watch for sudden changes. A deploy can rewrite canonicals across a template overnight. The Change Monitor groups those changes into one incident instead of hundreds of alerts.

Google explains how it picks a canonical in its guide to consolidating duplicate URLs.

The short version

Give every indexable page one self-referencing, absolute canonical tag in the head, and point elsewhere only for true duplicates. Keep canonicals consistent with redirects, sitemaps and internal links, and audit them after every major release. If several pages fight for the same query, read the keyword cannibalization guide next.