Free technical SEO tool
Canonical Checker
Inspect one live URL for HTML canonicals, HTTP header canonicals, hreflang, robots directives, and canonical target health to spot self-canonicals, parameter consolidation, language conflicts, and broken targets.
Check one URL
Enter a public page URL. The checker fetches the live response, reads its head signals, and verifies whether the canonical target responds cleanly.
The check runs through Fennec’s Cloudflare API, reads only public pages, and never changes the target website.
Fetching and analyzing…
Check result
This is a live request. It reflects the current response headers, HTML head sample, and canonical target status, but Search Console still decides the selected canonical.
Detected signals
Note: if the page also carries `noindex`, canonical is not a substitute for index control.
Canonical target verification
hreflang cross-check
If the page already declares localized alternates, the checker verifies whether the current URL includes itself and flags obvious cross-language canonical risks.
| hreflang | URL |
|---|
Extracted raw tags
What does this check answer?
It is not a site-wide crawler. It answers the page-level canonical question: which live signals this URL exposes now, whether they conflict, and where to investigate next.
1
Live single-page check
Read the current HTTP status, final URL, HTML canonical, and Link header canonical on one page.
2
Parameter and duplicate-page review
Separate intentional consolidation from cases that should self-canonicalize but point away.
3
Language-conflict warning
When hreflang already exists, flag patterns such as a translated page canonicalizing back to English.
4
Target verification
For non-self canonicals, fetch the target once more to confirm whether it resolves cleanly or redirects again.
Four high-value decisions
Each card maps to a practical editorial or engineering choice, not a generic definition.
Should the primary page self-canonicalize?
If this is the version you want indexed and shared, a self-referential canonical is usually the clean baseline and leaves less room for Google to infer a different preference.
Read Google’s canonical guidanceShould a parameter page consolidate to a clean URL?
Filtered, sorted, or tracking-parameter pages can canonicalize to the clean version when the intent is truly the same and the target URL returns successfully.
Continue with Soft 404 CheckerWhy should translated pages not all canonicalize back to English?
Google recommends a canonical in the same language when localized alternates exist. Sending a Chinese page back to English usually creates two competing preferences.
Read the hreflang + canonical guideWhich Search Console fields matter most?
Start with URL Inspection for the user-declared and Google-selected canonicals, then confirm duplicate, alternate, or soft-404 states in the Page indexing report.
Open the URL Inspection docsHow to verify before publishing
Align the page check, Search Console, and internal linking so you do not fix tags while leaving the target URL strategy broken.
Real sample: a Fennec English article
Last verified on July 27, 2026. The sample returns HTTP 200, self-canonicalizes, matches `og:url`, and declares `en`, `zh`, and `x-default` alternates.
Reproducible commands
curl -sSI https://fennecseo.app/blog/fennec-seo-vs-traditional-tools/
curl -sS https://fennecseo.app/blog/fennec-seo-vs-traditional-tools/ | rg -o '<meta property="og:url" content="[^"]+"|<link rel="canonical" href="[^"]+"|<meta name="robots" content="[^"]+"|<link rel="alternate" hreflang="[^"]+" href="[^"]+"' -nOutput
HTTP/2 200
content-type: text/html; charset=utf-8
...
1:<meta name="robots" content="index, follow"
13:<link rel="canonical" href="https://fennecseo.app/blog/fennec-seo-vs-traditional-tools/"
13:<link rel="alternate" hreflang="zh" href="https://fennecseo.app/zh/blog/fennec-seo-vs-traditional-tools/"
13:<link rel="alternate" hreflang="en" href="https://fennecseo.app/blog/fennec-seo-vs-traditional-tools/"
13:<link rel="alternate" hreflang="x-default" href="https://fennecseo.app/blog/fennec-seo-vs-traditional-tools/"
13:<meta property="og:url" content="https://fennecseo.app/blog/fennec-seo-vs-traditional-tools/"What this output tells you
- The English page self-canonicalizes, which is the stable baseline for a preferred URL.
- `og:url` matches the canonical, which reduces template drift between share metadata and preferred URL hints.
- The page lists itself as `en` and also declares `zh` plus `x-default`, which is the minimum useful hreflang pattern to validate next.
Tool limits and failure modes
These boundaries are explicit so canonical issues are not confused with indexing, rendering, or access-control problems.
Not a Search Console replacement
The page shows what the live URL exposes now, but the Google-selected canonical still belongs to Search Console and Google’s indexing systems.
Private pages remain out of scope
Pages that require login, are blocked by a WAF, or vary by region may not expose enough signals for this checker to validate cleanly.
No site-wide scanning claim
This batch keeps the tool deliberately page-scoped instead of pretending to bulk-discover canonical issues without real capability.
noindex can matter more
If the page also carries `noindex` or behaves like a soft error, fix indexability and page quality before interpreting canonical alone.
Next tools and articles
Every external link sits next to the conclusion it supports. If the official source does not support a claim, the claim is removed.
Canonical questions
Should every page self-canonicalize?
No. Preferred pages usually should; parameterized, print, or obviously duplicate pages may canonicalize to the main version. The key is not “self-canonicalize everything,” but keeping the hint aligned with the URL strategy you want to preserve.
Can PDFs use canonical tags?
Yes. Google supports canonicalization through the HTTP Link header, which is especially useful for PDFs and other non-HTML resources.
If a page is already noindex, should I still care about canonical?
You can inspect it, but the jobs differ. `noindex` affects whether the page can stay in the index, while canonical affects the preferred URL inside a duplicate set.
Is it okay for a canonical to point at a 301 target?
It is better to point directly at the final 200 URL. Making the canonical go through another redirect adds friction and makes sitemap or template drift more likely.
Official references
Every external link sits next to the conclusion it supports. If the official source does not support a claim, the claim is removed.