Generate a canonical link tag from a URL, and get flagged on common issues like using http instead of https or an inconsistent trailing slash.
Google AdSense Banner
This area will contain advertisements after approval.
Google AdSense Banner
This area will contain advertisements after approval.
A canonical tag (<link rel="canonical" href="...">) tells search engines which URL is the 'master' version of a page when the same or similar content is reachable through multiple URLs, like with and without a trailing slash, with tracking parameters, or through http vs https. This consolidates ranking signals onto one URL instead of splitting them across duplicates.
Pointing the canonical to an http:// URL when your site actually serves https:// (or vice versa), including tracking query parameters in the canonical URL, and inconsistent trailing slashes are all common mistakes that undermine what a canonical tag is meant to fix. This tool flags each of these automatically.
Entering http://example.com/blog/post/ produces the tag <link rel="canonical" href="http://example.com/blog/post/">, but the checks flag two issues: the URL uses http:// instead of https://, and it has a trailing slash on a non-root path. If your site actually serves this page at https://example.com/blog/post (no trailing slash), that's the version you should actually use as the canonical, this tool builds the tag from exactly what you type, it doesn't correct these issues for you.
Pasting in whatever URL happens to be in the address bar (with tracking parameters or a session ID attached) rather than the clean, preferred URL, the canonical should point to the version you actually want indexed, not whatever variant a visitor arrived on.
Setting a canonical tag but not actually checking it against the page it's on, a canonical pointing to a different page entirely (a copy-paste mistake) tells search engines to ignore the current page in favor of another one.
Mixing http and https across a site's canonical tags, if your site has fully migrated to https, every canonical should consistently use https, a stray http:// canonical undermines the migration's consolidation of ranking signals.
It's widely considered good practice for every indexable page to have a self-referencing canonical tag (pointing to itself), even when there's no known duplicate, as a safeguard against unexpected duplicate URLs appearing later.
Yes, cross-domain canonicals are valid and used when the same content is intentionally published on multiple domains, pointing all copies to a single preferred domain.
Google AdSense Banner
This area will contain advertisements after approval.