Skip to content
Aback Launch
Guides9 min read

Canonical Checker Guide: What a Canonical Tag Does and How to Check Yours

How to use a canonical checker, and what it is checking for: what rel canonical means, HTML and HTTP header examples, when to use a canonical tag, the mistakes that drop pages from Google and how to read Search Console's canonical reports.

Devvrat Hans

Founder

November 19, 2026
Canonical Checker Guide: What a Canonical Tag Does and How to Check Yours

A canonical checker reads a page's rel canonical tag (and its HTTP Link header, if there is one) and tells you which URL the page asks search engines to index, whether that URL is the page itself, and whether it actually works. Paste any address into the free canonical URL checker to see where the canonical points, the status code that URL returns, and warnings when it redirects, fails or sits on another host.

Canonical tags are one of the quietest ways to lose rankings. A template bug that points every blog post at the home page, or a staging domain baked into production, can drop whole sections from Google without a single visible error on the site. This guide explains what a canonical URL is, when to set one, the mistakes to look for, and how to check canonical URLs and keep tracking them as your site changes.

What a canonical tag is

The same content often answers at more than one address. Your pricing page might load at all of these:

  • https://example.com/pricing
  • https://example.com/pricing/
  • https://www.example.com/pricing
  • https://example.com/pricing?utm_source=newsletter
  • https://example.com/pricing?ref=badge

To a search engine, each of those is a separate URL with identical content: duplicate content. Without guidance, Google groups the duplicates and picks one to show. It usually picks well, but it may choose an address you did not want, and links pointing at the other versions may not consolidate where you expect.

The canonical tag is how you state your preference. It goes in the head of the page:

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

Every version of the pricing page carries that same tag, so all of them point at one clean address. The clean address points at itself. That last part is called a self-referencing canonical, and it is the safe default for every indexable page on your site.

The HTTP header version

Files that have no HTML head, such as PDFs, can declare a canonical in the HTTP response instead:

HTTP/1.1 200 OK
Content-Type: application/pdf
Link: <https://example.com/guides/launch-checklist>; rel="canonical"

This is useful when you publish the same content as a web page and a downloadable PDF, and want the page to rank. Use the header or the tag, not both with different values. When they disagree, search engines have no reliable way to tell which you meant. You can see every header a URL returns with the HTTP header checker.

A canonical tag is a hint, not a command

Google treats rel canonical as a strong signal, but it weighs it against everything else it knows about the page. Google's documentation lists the main canonicalization signals roughly in order of strength: redirects are a strong signal, rel canonical is a strong signal, and listing a URL in a sitemap is a weak one. Internal links, hreflang annotations and whether the page is served over HTTPS also count.

So if your canonical says one thing and the rest of your site says another (internal links all point at the www version, the sitemap lists URLs with trailing slashes, the canonical says neither), Google may ignore your tag and choose for itself. The fix is consistency: the canonical, the internal links, the sitemap and your redirects should all name the same URL. Our XML sitemap guide covers keeping the sitemap in line.

When to use a canonical tag

SituationExampleWhat to do
Tracking and referral parameters/pricing?utm_source=xCanonical to the URL without parameters
Sort and filter parameters/launches?sort=newCanonical to the unfiltered list, unless the filtered view deserves its own ranking
Trailing slash variants/blog/post and /blog/post/Pick one form, redirect the other, canonical to the chosen one
http and https, www and non-wwwhttp://www.example.com/301 redirect to one host, plus a self-referencing canonical
Same product in several categories/shoes/runner and /sale/runnerCanonical every copy to one primary URL
Syndicated articlesYour post republished on a partner siteAsk the partner to noindex their copy, or to add a canonical back to your original
Printer friendly or AMP versions/post?print=1Canonical to the main version

Canonical or redirect?

If users never need the duplicate URL, redirect it. A 301 redirect sends people and crawlers to the right page and is the stronger signal. Use a canonical when the duplicate has to keep working for visitors: tracking parameters, filtered views, a product that genuinely lives in two categories. For host and protocol duplicates (http, https, www) a redirect is always the right tool, with the canonical as backup. Our 301 redirect guide has the code for each server.

A note on syndication

A cross-domain canonical is allowed: a partner who republishes your article can point their copy at your original. Google's current guidance, though, is that when you want to avoid your syndicated copies outranking you, the most reliable option is for partners to block their copy from indexing with noindex. A canonical back to your page is still better than nothing, and Google's documentation remains the reference here: consolidate duplicate URLs.

Common canonical tag mistakes

These are the problems a canonical tag checker should catch, roughly in order of how much damage they do.

  1. Every page canonicalized to the home page. Usually a template that hardcodes the site URL instead of the page URL. Google may treat every page as a duplicate of the home page and drop them.
  2. Canonical pointing at a staging or old domain. An environment variable left on the staging value. The page asks to be treated as a copy of a site that is not public.
  3. Canonical pointing at a redirect or a 404. The page names a URL that does not resolve to a working page. Point it at the final URL that returns 200.
  4. Two or more canonical tags with different URLs. Often one from the CMS and one from an SEO plugin. Google may ignore all of them. Keep exactly one.
  5. http canonical on an https page. A leftover from before the move to https. The canonical should match the protocol you serve.
  6. Canonical and noindex on the same page. The canonical says "index that other URL instead", the noindex says "drop this". Mixed signals; pick the one you mean.
  7. Paginated pages canonicalized to page one. Page 2 of a list has different content from page 1. Each paginated page should carry its own self-referencing canonical.
  8. Canonical in the body, or added only by JavaScript. Google reads rel canonical in the head. Put it in the HTML your server returns rather than injecting or changing it with scripts.
  9. Relative URLs. A relative path such as /pricing in the href works in principle, but an absolute URL with protocol and host removes any doubt. Use absolute URLs.

How to check a canonical URL

With the canonical URL checker

Paste a page URL into the canonical checker. It fetches the page (following any redirects and telling you if it did), reads every canonical tag in the HTML and any canonical Link header, and reports:

  • the canonical URL, and whether it is self-referencing
  • a warning when the canonical points to a different URL, or to another host
  • an error when there are several different canonical tags, or when the tag and the header disagree
  • a warning when the canonical uses http on an https page
  • the status code the canonical URL returns, so you see at once if it redirects or fails

By hand in the browser

View the page source (not the inspector, which shows the DOM after scripts run) and search for rel="canonical". Check there is exactly one, that it is in the head, and that the URL in it loads the same page. For the header version, open the browser's network tab, select the document request and look for a Link header.

In Google Search Console

Run the URL through URL Inspection. Under Page indexing it shows two lines: the user-declared canonical (what your tag says) and the Google-selected canonical (what Google decided). If they match, you are done. If they differ, Google overruled you, and the next section explains why.

"Google chose different canonical than user"

In the Page indexing report, the status "Duplicate, Google chose different canonical than user" means you declared a canonical, but Google picked another URL as the main version. Its sibling statuses are worth knowing too:

Search Console statusWhat it meansAction
Alternate page with proper canonical tagThis URL points elsewhere and Google agreedUsually none; this is the system working
Duplicate without user-selected canonicalGoogle found duplicates and you gave no canonicalAdd a canonical to the version you prefer
Duplicate, Google chose different canonical than userYou set a canonical and Google overruled itFind the conflicting signal and fix it

When Google overrules you, look for the conflict. Do your internal links point at the other version? Does the sitemap list the other version? Does the URL you chose redirect, return an error or carry a noindex? Is the content on the two URLs actually different, so your canonical looks like a mistake? Fix the signals so they agree, then request indexing again. If the content on the two pages is genuinely different, the canonical was the wrong tool: let each page stand on its own with a self-referencing canonical.

How to track canonical tags over time

Canonical problems almost always arrive with a deploy: a new template, a framework upgrade, a change to how the site URL is configured. That makes them easy to prevent if you check at the right moments.

  • Check one URL per template after each release. Home page, a blog post, a product or listing page, a docs page. Four checks with the canonical checker cover most sites.
  • Watch the Page indexing report weekly. A sudden rise in "Alternate page with proper canonical tag" or "Google chose different canonical" is usually a canonical bug, and it shows up there before traffic drops.
  • Include canonicals in your on-page checks. The on-page SEO checker reports whether a page has a canonical as part of a full audit, which is handy when you are reviewing a page for other reasons.
  • Check multilingual pages together. Each language version should be self-canonical and linked with hreflang, not canonicalized to the English page. Our hreflang tags guide explains how the two work together.

Run your most important page through the free canonical tag checker now. It takes a few seconds, and it is the fastest way to rule out the problem that costs the most when nobody notices.

FAQ

What is a canonical tag in SEO?

A canonical tag is a link element in a page's head, written as rel="canonical", that names the preferred URL for content reachable at several addresses. It tells search engines which URL to index and show, and where to consolidate signals like links.

Should every page have a self-referencing canonical?

Yes, for every page you want indexed. A self-referencing canonical names the page's own clean URL, so parameter and tracking variants of it all point back to one address. It costs nothing and protects you against duplicates you did not know existed.

How do I check the canonical URL of a page?

Paste the page into a canonical checker, which reads the tag and the HTTP Link header and tests the URL it points to. You can also view the page source and search for rel="canonical", or use URL Inspection in Search Console to see both the declared and the Google-selected canonical.

Does Google always respect the canonical tag?

No. Google treats it as a strong hint, not a directive. If redirects, internal links, the sitemap or the content itself point another way, Google may choose a different canonical. Making all those signals agree is the way to have yours respected.

Is duplicate content a penalty?

Not in itself. Google filters duplicates rather than punishing sites for having them, as long as the duplication is not an attempt to manipulate results. The real cost is that Google may show the wrong URL and links may be split across copies, which is what canonical tags fix.

Can a canonical tag point to another domain?

Yes. Cross-domain canonicals are supported, typically for syndicated content. Make sure it is deliberate: a canonical that points your own pages at another domain by mistake asks Google to drop them in favor of that domain.

Written by

Devvrat Hans

Founder

Share
Newsletter
Get the Monday launch email
The week's new launches and winners, in one short email.

By subscribing, you agree to get our newsletter by email. Unsubscribe any time in one click. See our Privacy policy and Terms.

Launch your startup on Aback Launch

Get a launch page that search engines and AI assistants can read, a place in the weekly launch list, and a review by a real person. Free to join.