Canonical URL Checker

What Is the Canonical URL Checker?

This tool checks a page's canonical tag URL against the page's own URL for the most common canonicalization mistakes: using a relative URL (canonical tags must be absolute), a host mismatch, a non-HTTPS URL, and trailing-slash inconsistencies.

How to Use This Tool

Enter the page URL and the canonical tag's URL. Any issues appear instantly.

Why This Matters

Exactly What Is Checked

The tool takes two addresses and runs a short list of tests. Each address must parse as a full absolute URL; a relative canonical such as /blog/post/ produces the message that the canonical must be absolute. The canonical must use HTTPS. The host of the canonical must equal the host of the page. Finally, the two paths must agree on whether they end in a trailing slash. Everything found is listed as a separate issue, and if there are none you see a confirmation message. Empty fields are also reported as invalid URLs.

It is important to see what the tool does not test. It does not fetch either page, so it cannot tell whether the canonical target returns a normal page, redirects, or is blocked. It does not compare the protocol of the page URL. It ignores query strings and fragments in the comparison. And it does not require the paths to be identical, because a canonical pointing at a different path on the same site is legitimate, for example a tracking-parameter page pointing at the clean version.

Worked Examples

• Page https://www.example.com/blog/post/ with canonical https://www.example.com/blog/post/ passes with no issues.
• Page https://www.example.com/blog/post/ with canonical https://example.com/blog/post/ is reported as a host mismatch, because the www prefix makes the hosts differ.
• Page https://www.example.com/blog/post/ with canonical https://www.example.com/blog/post reports a trailing-slash mismatch.
• Page https://www.example.com/blog/post/ with canonical http://www.example.com/blog/post/ reports that the canonical does not use HTTPS.
• Page https://www.example.com/shoes/?color=red with canonical https://www.example.com/shoes/ passes, which is the intended use: the parameter version points to the clean one.

Deciding Whether a Flag Is a Real Problem

Treat each message as a prompt to look, not as an automatic verdict. A host mismatch is usually a mistake when it is only a www difference, but it is deliberate when content is syndicated on another site and points back to the original. A trailing-slash mismatch might reflect a canonical for a file such as a PDF, where no slash is expected. The HTTPS message matters when your site serves HTTPS, since a canonical pointing to HTTP asks search engines to prefer the insecure address. Decide which single version of the URL you want indexed, then make every internal link, sitemap entry and canonical tag agree with that choice.

Common Causes Behind the Issues

• A CMS or theme that builds the canonical from a hard-coded base URL that differs from the live domain.
• A staging domain or an old protocol left in a template after migration.
• Inconsistent handling of trailing slashes between the server, the CMS and the canonical tag.
• A copied template in which every page carries the home page canonical, which tells search engines to ignore the other pages.

After Fixing

Fix the source of the tag rather than editing pages one by one, then request a recrawl of key pages through your search console. Remember that canonical tags are hints rather than commands; search engines may choose a different canonical if signals conflict, such as redirects, sitemaps and internal links pointing to another version. To review how a specific page is treated, use the URL inspection feature in your search console rather than relying on this checker alone. This tool is a quick formatting and consistency test to catch typing and template errors before they cost you visibility.

Frequently Asked Questions