Healthy page
- Input
- https://example.com/blog/post
- Output
- Canonical matches the final URL — self-referencing
This is what most pages should look like. The canonical points at itself, so there is no ambiguity about which URL to index.
A canonical tag tells search engines which URL is the preferred version of a page when the same content is reachable at several addresses. This checker fetches a live page, finds its canonical tag, follows any redirects, and reports whether the tag points back at the page itself. Paste a URL to see exactly what a crawler sees.
Runs entirely in your browser — nothing you type is uploaded.
How to
Enter the full address of a public page, including https://.
The page is fetched server-side with a real user agent, following any redirects along the way.
You get the canonical URL found, the final URL after redirects, the status code, and whether the two agree.
A missing, relative or mismatched canonical is reported with what to change.
Examples
This is what most pages should look like. The canonical points at itself, so there is no ambiguity about which URL to index.
The checker follows redirects and compares the canonical against the final URL, not the one you typed.
Relative canonicals are valid but easy to get wrong. The tool resolves them against the page URL so you can see what Google would.
Why use it
The page is fetched server-side rather than read from your browser, so the result reflects what a search engine receives.
You find out when the URL you entered is not the URL that finally served the page, which is where most canonical confusion starts.
A canonical of /page is resolved to its absolute form, so comparisons are meaningful instead of always failing.
URLs are compared after normalising trailing slashes and default ports, so cosmetic differences are not reported as mismatches.
Check any public page. Requests are rate limited to keep the service available for everyone.
Good to know
Summary
FAQ
Discover