What Is a Canonical Tag? How to Set It Up and Use It Correctly for SEO

The canonical tag (rel="canonical") tells search engines which URL you want treated as the canonical page when identical or similar content exists at multiple URLs. It prevents evaluation from being split and consolidates it onto the page you're targeting.

That said, a canonical is not something that always produces the result you specify. It is one signal among several, and Google makes the final call. This article covers how canonical tags work, how to set them, when to use them, common mistakes, and how to verify them.

What is a canonical tag?

A canonical tag is written in the HTML head to tell search engines to evaluate a given URL as the canonical page. The word canonical means authoritative or standard.

Why URL canonicalization is necessary

When the same content is reachable at multiple URLs, search engines have to decide which one to index. In that situation, the evaluation that should accumulate on a single page gets split across several URLs instead.

Duplicate URLs arise unintentionally in cases such as these.

• With and without www (https://example.com versus https://www.example.com)
• http versus https
• With and without index.html, and with or without a trailing slash
• URLs carrying tracking parameters (such as ?utm_source=...)
• Variations produced by sort and filter parameters (such as ?sort=price)
• Cases where desktop and mobile have separate URLs

Note that having duplicate content on a site is normal in itself, and it does not on its own violate Google's spam policies or incur a penalty. The problems are split evaluation and the confusion it causes for user experience and measurement.

The canonical page is the center of Google's evaluation

Google treats the canonical page as the main source for evaluating content and quality. Canonical pages are also crawled more frequently, while duplicate URLs are visited less often. URL canonicalization therefore affects not just the consolidation of evaluation but also crawl efficiency.

That said, crawl budget is only a serious concern for large sites in the range of a million pages, or sites with over ten thousand pages that update daily. For a site of typical size, thinking of it purely as preventing split evaluation is enough.

How to set a canonical tag

The basic syntax (in the HTML head)

This is the most common method. Write the URL you want treated as canonical in the head of each page, in the following form.

<link rel="canonical" href="https://example.com/page-a">

Key points when writing it:

• Place it in the head (it is ignored if written in the body)
• Specify an absolute URL (relative paths invite unintended interpretation, so avoid them)
• Don't write more than one per page (multiple tags cause search engines to ignore them)
• Don't include a URL fragment (anything after #). Google generally does not support fragments
• Set a self-referencing canonical on the canonical page itself as standard practice

Specifying it in an HTTP response header

Non-HTML documents such as PDF and Word files have no head tag, so you return the canonical in an HTTP response header instead. This requires an environment where you can change server settings, and it is supported for web search results only.

Including it in your sitemap

URLs included in a sitemap indicate candidates for the canonical page, but this is a weak signal. Rather than relying on it alone, use it alongside canonical tags to strengthen the effect.

Specifying it with a 301 redirect

Redirects are the strongest canonicalization signal. When you want to retire an old URL and consolidate entirely onto a new one, use a 301 redirect rather than a canonical.

Choosing between a canonical and a 301 redirect is simple. If users need to see the duplicate page (you need to keep it), use a canonical; if they don't, use a 301 redirect.

Combining multiple methods

Google states that combining these methods is more effective. Using two or more raises the likelihood that your preferred canonical URL appears in search results.

The prerequisite, however, is that you don't specify contradictory URLs across different methods. Avoid situations such as designating one URL in your sitemap while specifying a different URL for the same page via canonical.

When you should set a canonical tag

When parameterized URLs are generated

For URLs carrying tracking UTM parameters or sort and filter parameters, specify the parameter-free URL as canonical when the content is the same. This matters especially on sites with faceted search, such as e-commerce and job listings.

When similar content exists across multiple pages

When several pages have nearly identical content, such as product pages differing only by color or size, specify a representative page as canonical to consolidate evaluation.

When desktop and mobile have separate URLs

If you serve separate desktop and mobile URLs rather than using responsive design, specifying the desktop version as the canonical page is the common approach.

When you don't need to set one

On sites without duplicate pages, there's no need to force the issue. Google objectively determines a suitable URL to display even when no canonical URL is specified. In fact, Google explicitly states that while these methods are recommended, they are not required. That said, adding a self-referencing canonical across all pages is useful insurance against unexpected parameterized URLs.

Common mistakes and points to watch

Consolidating pagination onto page one

This point deserves particular attention. There was once a convention of specifying page one as the canonical on page two and beyond of a listing, but Google's current recommendation is different.

For pagination, set a self-referencing canonical on each page: page two specifies page two's URL, page three specifies page three's. Each page lists different items, and Google treats each as a separate page. Consolidating onto page one risks the content on page two and beyond not being indexed.

Using noindex or robots.txt for canonicalization

Using noindex as a way to prevent a page from being selected as canonical within the same site is not recommended, because it blocks the page from Google Search entirely. Using rel="canonical" is the recommended method.

Likewise, blocking duplicate content with robots.txt is inappropriate. If a page isn't crawled, the canonical tag itself is never read, and you lose the evaluation each page carries.

Relying on cross-domain canonicals

For syndicated articles, pointing a canonical from the syndicated copy back to the original has fallen out of the recommended approach (though it is not prohibited). Cross-domain canonical specifications are frequently ignored. If you want to preserve the original article's evaluation, the recommended approach is to have the syndication partner apply noindex.

The target is a redirect or a 404

This is where the URL specified as canonical itself redirects elsewhere, or points to a URL that doesn't exist. It commonly happens when canonical updates are overlooked during site revisions or URL changes.

Conflicting with CMS or plugin settings

In a CMS such as WordPress, the theme or an SEO plugin may already output a canonical automatically. Adding one manually creates a duplicate, which results in search engines ignoring them. Check the source to see whether one is already output before you configure anything.

How to verify a canonical tag is working

Check the source code

View the page source in your browser and search for rel="canonical" in the head. Confirm the intended URL is specified and that there aren't multiple instances.

Check Google's decision with the URL Inspection tool

This is the definitive check. Inspecting the target URL in Search Console's URL Inspection tool displays two things.

• User-declared canonical: the URL the site specified via canonical
• Google-selected canonical: the URL Google actually treats as canonical

If the two match, things are working as intended. If they diverge, it means Google is not adopting the site's specification.

"Alternate page with proper canonical tag" is not a problem

This message in Search Console's page indexing report is not an error. It reflects the normal state in which Google has read the canonical tag and is prioritizing the specified canonical page. If you set the canonical deliberately, no action is needed.

If you instead see "Duplicate, Google chose different canonical than user" or "Duplicate without user-selected canonical," duplicate pages exist without a canonical URL specified, so consider setting one.

What to do when the wrong URL becomes canonical

Even with a canonical specified, Google may select a different URL as canonical. That's because a canonical is not a directive, only one signal among several.

In this case, you need to align the full set of signals indicating URL identity, not just the canonical tag on its own.

• Point all internal links at the canonical URL (don't link to duplicate URLs)
• List only canonical URLs in your XML sitemap
• Consolidate with 301 redirects wherever consolidation is possible
• Raise the content quality of the canonical URL (low quality means Google won't select it)
• Where the differences between duplicate pages are too small, consider merging the pages

Note that before troubleshooting, Google recommends considering whether the URL it selected might actually be more useful for users.

Summary

The canonical tag prevents split evaluation across duplicate and similar pages and consolidates it onto the canonical page. The basics are to write it in the head with an absolute URL, one per page.

The key thing to keep in mind is that a canonical is a signal, not a directive. It works as intended only once you align the signals across the whole site, including internal links, sitemaps, and redirects, rather than just inserting the tag.

Watch out too for differences from older advice, such as setting a self-referencing canonical on each paginated page and not using noindex or robots.txt for canonicalization. After configuring, always check both the user-declared canonical and the Google-selected canonical in Search Console's URL Inspection tool.