Canonical Consistency Checker

Why the variants matter

If http://, https://www., the trailing-slash version, and ?utm_source= all resolve differently, or worse, all return 200, search engines see several competing URLs where you see one page. Link equity splits, crawl budget goes to waste, and you get those “Duplicate without user-selected canonical” rows in Search Console that nobody enjoys diagnosing.

What it checks

• Eight variants of your URL: as given, the other scheme, www toggled, trailing slash toggled, an uppercased path, and a tracking-parameter version
• The full redirect chain for each one, and whether it consolidates in a single hop or wanders through a chain. Every hop leaks a little signal and costs a little crawl time.
• rel=canonical in the HTML and the Link: rel=canonical HTTP header. CDNs and plugins misconfigure the header version constantly, and when the two disagree, Google picks for you.
• Whether the tracking-parameter variant stays a 200 with a clean self-referencing canonical, which is what you want. Redirecting it breaks your campaign tracking.

What you get

One verdict (consistent, mostly consistent, or fragmented) and a per-variant breakdown showing exactly which version misbehaves, along with the conventional fix.