--- title: "Canonical Tag Checker — Free Canonical URL Test" description: "Free canonical tag checker. Verify the rel=canonical URL of any page, catch conflicts between HTML and HTTP headers, and fix self-reference errors. No signup." canonical: "https://lemwatch.com/tools/canonical-checker" source: "https://lemwatch.com" --- # canonical tag checker > Check the canonical URL of any page. Finds missing, conflicting, relative, and cross-domain canonical tags so you can review your preferred-URL signals. A canonical tag expresses which URL you prefer search engines to treat as the representative version of duplicate or very similar content. It is a strong signal, not a guarantee. Enter a URL above and the check reports the canonical the page actually declares in the HTML and HTTP headers, so you can review whether those signals are consistent. ## Why this is the quiet cause of lost rankings Nothing about a mistaken canonical is necessarily visible to a visitor. It may come from a template that hardcodes one URL across a section, a staging URL left after launch, or two systems emitting conflicting values. Because canonicalization also considers redirects, internal links, sitemap inclusion, and content similarity, review the whole set of signals rather than treating a single tag as a final instruction. ## Conflicting signals are worse than a missing tag Using an HTML canonical and an HTTP-header canonical is supported, but it is more error-prone because the values can drift. Conflicting signals, a redirecting target, or a target that does not closely match the content reduce the clarity of your preference. Keep canonical-related signals consistent so search engines can evaluate the intended representative URL. ## What correct looks like Use a self-referential canonical on the preferred HTML page. For duplicate parameterized or filtered URLs, point at the clean representative version when the content is genuinely the same. Paginated pages generally canonicalize to themselves. Prefer an absolute HTTPS URL and keep its host, path, redirects, internal links, and sitemap entries consistent. Choose either HTML or HTTP headers where practical; if you use both, make their values identical. ## Canonicals and redirects solve different cases Use a permanent redirect when you are retiring a duplicate URL. Use a canonical when duplicate URLs need to remain reachable. Both are canonicalization signals, so they work best when the preferred target is consistent across your site. ## What this tool checks - rel="canonical" declared in the HTML - Link: rel="canonical" sent as an HTTP header - Conflicts between the HTML and header canonical - Whether the canonical self-references the requested URL - Relative, cross-domain, and redirecting canonical targets ## Why it matters A canonical tag is one signal that helps search engines identify a preferred URL among duplicates. Keep it consistent with internal links, sitemaps, redirects, and page content; conflicting signals can lead a search engine to select a different canonical. ## How to fix what it finds - Use a self-referential canonical on the preferred version of an HTML page - Use consistent canonical signals across HTML, headers, redirects, internal links, and sitemaps - Use self-referential canonicals for each page in a paginated sequence - Point a canonical at a stable, accessible preferred URL - Prefer absolute HTTPS URLs to avoid relative-path ambiguity ## Methodology We request the URL you enter over HTTPS with a crawler-like user agent, following redirects, and record the final URL we land on. From the final response we read two things independently: every rel="canonical" declaration in the HTML head, and any canonical sent as a Link HTTP header. Each declared value is resolved against the page's base URL so relative canonicals are reported as the absolute URL a search engine would derive. We then compare: whether the canonical self-references the URL requested, whether the HTML and header values agree, whether the target is on the same host, and whether the target resolves to a 200 rather than a redirect or an error. Canonicals placed outside the head, which search engines ignore, are flagged separately. We do not execute JavaScript — a canonical injected client-side is unreliable for crawling anyway, and reporting it as present would give false confidence. ## This tool also answers ### Should a canonical tag point to itself? Google recommends a self-referential canonical on the preferred version of an HTML page. It clarifies your preferred URL for duplicate variants such as parameters or protocol variants. ### What happens if two pages have the same canonical? This is appropriate when the pages are genuine duplicates and you want to express one preferred version. Search engines still assess similarity and other canonical signals, so do not use it to hide materially different content. ## Frequently asked questions ### Is a canonical tag a directive or a hint? A hint. Google weighs it alongside internal links, sitemaps and redirects. If those signals contradict your canonical, Google may choose a different URL and report it as "Duplicate, Google chose different canonical" in Search Console. ### Can a canonical point to another domain? Yes, cross-domain canonicalization can be used for syndicated or duplicate content. Make sure the destination is the version you genuinely want search engines to prefer. ### Do I still need canonicals if I use redirects? Redirects are a strong canonicalization signal for a URL you are retiring. Canonicals are useful when duplicate URLs must remain reachable. Keep the signals consistent. ### Should a canonical tag point to itself? Google recommends a self-referential canonical on the preferred version of an HTML page. It clarifies your preferred URL for duplicate variants such as parameters or protocol variants. ### What happens if two pages have the same canonical? This is appropriate when the pages are genuine duplicates and you want to express one preferred version. Search engines still assess similarity and other canonical signals, so do not use it to hide materially different content. ## Lemwatch at a glance - What it is: website monitoring that checks uptime, page changes, SEO, security, SSL and speed in one tool. - Free plan: 10 sites, no time limit, all check types. - Pro: $19/mo, 50 sites, public API and webhooks. - Agency: $59/mo, 150 sites, white-label status pages. - Source: https://lemwatch.com/pricing (facts verified from the product's own plan limits). ## Related - [All free tools](https://lemwatch.com/tools) - [noindex checker](https://lemwatch.com/tools/indexability-checker) - [hreflang checker](https://lemwatch.com/tools/hreflang-checker) - [meta tag analyzer](https://lemwatch.com/tools/meta-tag-analyzer) - [Sitemap Checker](https://lemwatch.com/tools/sitemap-checker) - [domain age checker](https://lemwatch.com/tools/domain-age-checker) - [Lemwatch pricing](https://lemwatch.com/pricing) - [All monitoring checks](https://lemwatch.com/features)