Canonical Tags Explained

A canonical tag tells search engines which version of a URL is the “master” copy when multiple pages contain the same or very similar content. It’s an HTML element that looks like this:

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

Without canonical tags, search engines might index multiple versions of the same page — with or without trailing slashes, with different parameters, or with duplicate content across subdomains. This splits your ranking signals and dilutes your SEO efforts.

Why canonical tags matter

Search engines use canonicalization to determine which URL to show in search results. When they find identical or near-identical content at multiple URLs, they have to guess which one to index. Sometimes they guess wrong.

Canonical tags remove the guesswork. You explicitly tell search engines: “This is the URL I want indexed. Ignore the others.”

The consequences of missing canonicals

• Split link equity: If 100 sites link to example.com/page and 50 link to example.com/page/, search engines split the ranking signals between two URLs instead of consolidating them.
• Duplicate content issues: Multiple URLs with the same content can trigger duplicate content filters.
• Crawl budget waste: Crawlers spend time indexing duplicate pages instead of discovering new content.
• Incorrect ranking URLs: Google might show a parameterized URL instead of your clean URL in search results.

Self-referencing canonicals

The simplest and most common use case is a self-referencing canonical. The page points to itself:

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

This tells search engines that https://example.com/page is the canonical version, even if no other versions exist. It’s a safety net against URL variations like:

• https://example.com/page vs https://example.com/page/
• http:// vs https://
• www. vs non-www.

Every page on your site should have a self-referencing canonical tag unless you have a specific reason not to.

Cross-domain canonicals

When the same content exists on multiple domains, cross-domain canonicals tell search engines which domain is the primary source:

<link rel="canonical" href="https://main-domain.com/article" />

This is common when:

• Syndicating content to partner sites
• Managing multiple brand domains
• Migrating from one domain to another

The original domain receives the ranking signals, and the syndicated versions are treated as copies.

Common canonical issues

Missing canonical tags

The most basic problem. If pages don’t have canonical tags, search engines must guess which URL is the master copy.

Conflicting signals

A page might have a canonical tag pointing to one URL while HTTP headers or sitemaps point to another. Search engines will try to reconcile these signals, but the result is unpredictable.

Canonical chains

Page A points to Page B, which points to Page C. Search engines may not follow the full chain. Always point canonical tags directly to the final URL.

Canonicalizing to redirected pages

If your canonical points to a URL that returns a 301 redirect, search engines may ignore the canonical. Point to the final destination URL.

Self-canonical on paginated pages

Paginated pages (/blog?page=2) should not canonicalize to page 1. Each paginated page is a distinct resource and should have its own canonical pointing to itself.

Using canonical instead of redirect

If content has permanently moved, use a 301 redirect, not a canonical tag. Canonicals are for duplicate content, not moved content.

Canonical tags vs 301 redirects

Both consolidate signals, but they work differently:

Feature	Canonical Tag	301 Redirect
User sees original URL	Yes	No
Browser loads original page	Yes	No
Search engines consolidate signals	Yes	Yes
Requires server access	No	Yes
Passes link equity	Yes (approximately 90-99%)	Yes (approximately 99%)

Use a canonical when you want to keep the original URL accessible to users but consolidate SEO signals.

Use a 301 when the original URL should no longer exist and all traffic should go to the new URL.

Checking canonical tags

To verify canonical tags are implemented correctly, view your page’s HTML source and look for the rel="canonical" link element. You can also use the NodSEO Canonical Tag Checker to scan multiple pages and verify their canonical tags.

What to check

1. Every page has a canonical tag — No pages should be missing this
2. Canonical points to the correct URL — No typos, no broken URLs
3. Canonical matches the current page (for self-referencing) — Unless intentionally cross-referencing
4. No canonical chains — Each canonical should point to the final destination
5. Canonical is consistent with sitemap URLs — The canonical URL should match what’s in your sitemap

Implementation

WordPress

Most SEO plugins (Yoast, Rank Math, AIOSEO) add self-referencing canonical tags automatically. Check your plugin settings to confirm this is enabled.

Static sites

Add the canonical tag in your HTML <head>:

<link rel="canonical" href="https://yourdomain.com/current-page" />

For dynamic sites, use your server-side language to generate the canonical URL based on the current request.

Shopify

Shopify adds canonical tags automatically to products, collections, and pages. You can customize them in your theme’s theme.liquid layout.

FAQ

Do canonical tags prevent indexing?

No. Canonical tags suggest which URL to index but do not prevent other URLs from being indexed. If you need to prevent indexing, use noindex robots meta tags or X-Robots-Tag headers.

Can I use canonical tags with HTTPS redirects?

Yes. If your canonical points to an HTTPS URL but the page loads over HTTP, the canonical tells search engines to index the HTTPS version. Pair this with an HTTP-to-HTTPS redirect for best results.

How do I check canonical tags on multiple pages?

Use the NodSEO Canonical Tag Checker to scan your website and verify all pages have correct canonical tags.

Should I canonical to my homepage?

Only if the page is genuinely a duplicate of your homepage. Canonicalizing unrelated pages to the homepage is a common mistake that causes those pages to lose ranking potential.