What is a canonical tag and why does it matter for SEO?

A canonical tag is a element placed inside the HTML head. It tells search engines which URL is the definitive version of a page when multiple URLs serve similar or identical content — for example https://example.com/product and https://example.com/product?ref=email. Without it, search engines may split ranking signals across duplicate URLs, diluting your authority. With it, all link equity consolidates on the canonical URL.

Should the canonical URL always match the page URL?

Not necessarily. A self-referencing canonical (canonical = the page itself) is correct for most pages and tells crawlers there is no preferred alternative. A non-self-referencing canonical is correct for syndicated or duplicate content, telling crawlers the original lives elsewhere. Both are valid — what matters is intentionality. This tool flags non-self-referencing canonicals as informational rather than errors so you can verify the intent.

Is a relative canonical URL acceptable?

Google officially accepts relative canonical URLs, but an absolute URL is the safer choice. Relative URLs can behave unexpectedly when a CDN or proxy rewrites the base path, when a page is fetched out of context by a crawler, or when the canonical is later copied to a different domain. Use absolute URLs to be unambiguous.

What happens if a page has more than one canonical tag?

Most search engines, including Google, use only the first canonical tag encountered and ignore subsequent ones. Having multiple canonical tags is a configuration error — it signals that your CMS, theme, or analytics tag is injecting an extra tag without your knowledge. The most common culprit is a WordPress plugin or a tag manager snippet.

Does the canonical tag affect pages in a pagination series?

For paginated content (page 1, page 2, ...) the recommended approach is a self-referencing canonical on each individual page rather than canonicalising all pages back to page 1. Canonicalising all paginated pages to page 1 causes search engines to drop the interior pages from the index entirely, which can hurt discovery of long-tail content buried deep in a series.

What is the difference between a canonical tag and a 301 redirect?

A 301 redirect tells the browser and crawler to go to a different URL — it is a strong, permanent signal. A canonical tag is a hint that stays on the page — it suggests but does not force the preferred URL, and the page itself remains accessible at its original address. For URLs you want fully deindexed and consolidated, a 301 redirect is the stronger mechanism. For duplicate parameter variants (?sort=, ?ref=) where the page still needs to be reachable, a canonical tag is more appropriate.

Can a canonical tag on one domain point to a different domain?

Yes. Cross-domain canonicals work the same way as same-domain ones and are the correct implementation for content syndicated from a partner site. The receiving site should accept the canonical signal — Google says it will generally honour cross-domain canonicals, though it is treated as a hint rather than a directive.

Canonical Tag Checker

The canonical tag checker analyses raw HTML you paste in and immediately tells you whether your <link rel="canonical"> element is present, correctly formed, self-referencing, and free of duplicates. It is aimed at SEO engineers, developers, and site owners performing technical audits without leaving the browser.

What the tool checks

Every canonical tag is evaluated across four dimensions:

Presence — does a <link rel="canonical" href="..."> exist in the <head>?
Uniqueness — is there exactly one, or are there conflicting duplicates injected by a CMS, plugin, or tag manager?
URL form — is the href an absolute HTTPS URL, or a relative path that could be misinterpreted by crawlers?
Self-referencing — does the canonical point to this page (correct for most pages) or to a different URL (correct for syndicated/duplicate content)?

Where a problem is found, the tool produces a colour-coded issue card (Error / Warning / Info) with a plain-English explanation and a ready-to-copy corrected tag.

How canonicalisation works

When the same content is reachable at more than one URL — for example:

https://example.com/article
https://example.com/article?utm_source=newsletter
https://www.example.com/article
http://example.com/article

— search engines must decide which URL to store in their index and accumulate links to. Without guidance they may split ranking signals across all four variants.

A canonical tag resolves this ambiguity. Placed in the <head> of each variant, it reads:

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

Google, Bing, and other crawlers then treat https://example.com/article as the authoritative copy and consolidate all link equity there.

Worked example

Suppose your CMS generates this head section:

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

The checker would flag:

Error — two canonical tags found (only the first /article is used)
Warning — first canonical is a relative URL, not absolute
Suggestion — replace both with a single <link rel="canonical" href="https://example.com/article" />

Self-referencing vs cross-domain canonical

Scenario	Correct canonical
Standard page, no duplicates	Points to itself (self-referencing)
Page reachable with tracking params	Points to the clean URL without params
Content syndicated on a third-party site	Points to the original on your domain
Paginated series (page 2, 3…)	Each page points to itself
HTTP version of an HTTPS page	Points to the HTTPS URL

Privacy

All processing happens in your browser via JavaScript string matching — no HTML is sent to any server and nothing is stored.