Canonical tag checker
Check whether a webpage declares a canonical tag and view the canonical URL it points to.
What the canonical tag checker does
This tool inspects a webpage and reports whether it contains a canonical link element, then displays the canonical URL it declares. It is a fast way to confirm which URL a page nominates as the preferred version of its content.
A canonical tag looks like this: <link rel="canonical" href="https://example.com/page/">. It lives in the document head and tells search engines that this URL should be treated as the authoritative copy when similar or identical content is available at multiple addresses.
Why canonical tags matter
Websites commonly expose the same content at several URLs: with and without trailing slashes, with tracking parameters, through HTTP and HTTPS, or via category and filter pages. Search engines try to pick one version to index, but their choice may not match yours. A canonical tag makes your preference explicit and helps consolidate ranking signals on the URL you care about.
Canonicals are especially useful for paginated series, product variants, syndicated articles, and print-friendly versions. They reduce the risk of duplicate content diluting visibility and keep analytics cleaner by pointing traffic and signals to a single address.
How to interpret the results
If a canonical tag is found, compare the declared URL with the URL you actually requested. A self-referencing canonical, where the page points to itself, is the normal and healthy pattern. A canonical pointing to a different URL means the page is intentionally delegating its authority to another address; verify that this is deliberate and that the target is correct, indexable, and returns a 200 status.
If no canonical tag is found, the page relies on search engines to choose a canonical themselves. That is not automatically a problem for unique content, but it becomes risky when the same content is reachable at multiple URLs. In that case, adding a canonical is a straightforward improvement.
Watch for relative canonical URLs. They are valid, but absolute URLs are less prone to mistakes when pages are moved or when the base URL changes. Also check that the canonical target is not blocked by robots.txt, does not redirect, and is not itself marked noindex, since contradictory signals can confuse crawlers.
Common canonical mistakes
- Pointing every page to the homepage. This tells search engines the homepage is the preferred version of all content, which can remove other pages from the index.
- Canonical chains. Page A points to B, and B points to C. Crawlers may follow the chain, but it is cleaner to point directly to the final URL.
- Canonical to a noindex page. These instructions conflict, and the outcome depends on the crawler.
- Canonical to a redirecting URL. The declared URL should be the final destination, not an intermediate hop.
- Inconsistent canonicals across paginated pages. Each page in a series usually should self-canonicalize rather than all pointing to page one.
Practical workflow
Check the canonical on a sample of template pages, not just the homepage. Compare the declared URL with the URL in your sitemap and internal links, since mismatches between these signals are a frequent source of indexation confusion. When you find a non-self canonical, confirm the intent with whoever manages the content and verify the target URL's status and indexability.
Limitations
The checker reads the canonical element present in the HTML response. It does not evaluate how search engines ultimately treat the page, and it does not detect canonicals delivered via HTTP headers. Treat the result as a factual report, then interpret it in the context of your site architecture.
Similar tools
Extract and verify the meta tags of any webpage.
Trace up to 10 redirects for a URL and see each hop in the chain.
View the HTTP response headers returned for a URL.
Popular tools
Check whether images on a webpage have alt attributes for accessibility and image SEO.
Measure the total size of a webpage, including all loaded resources.
Check whether a page is set to noindex through meta tags, HTTP headers, or robots.txt.
Compare the amount of visible text to HTML code on a webpage.