Canonical Checker

Resolved the canonical to https://gampangin.example/tools/json-formatter/?utm_source=newsletter with 2 finding(s).

How it works

• Parsed the canonical and the page URL.
• Resolved a relative canonical against the page origin when possible.
• Checked absolute/relative form, origin, self-reference, protocol, host case, tracking parameters and fragments.

• A canonical is a hint Google may override; it does not guarantee consolidation.

Methodology

1. Parse both URLs with the platform URL parser.
2. Resolve a relative canonical against the page origin.
3. Compare origin, path and query after normalising a trailing slash; flag tracking parameters, fragments, http and uppercase hosts.

Usage

1. Enter the canonical URL from the page's rel=canonical tag.
2. Enter the page's own absolute URL.
3. Run the check and read the findings.
4. Normalise the URL and re-run until the findings are notes only.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

A self-referential canonical with tracking parameters

{
  "canonical": "https://gampangin.example/tools/json-formatter/?utm_source=newsletter",
  "pageUrl": "https://gampangin.example/tools/json-formatter/"
}

A clean absolute canonical

{
  "canonical": "https://gampangin.example/tools/json-formatter/",
  "pageUrl": "https://gampangin.example/tools/json-formatter/"
}

Limitations

Canonical URLs and duplicate variants

Variants of a URL (tracking parameters, protocol, host case, trailing slash) can be crawled as separate pages. A self-referential canonical tells search engines which one is preferred.

Keep the canonical absolute and free of tracking parameters so the signal is unambiguous.