Free tool · SEO

Free Canonical URL Checker

Paste a URL. We'll fetch it, follow redirects, parse the head, and tell you the canonical URL, robots meta, redirect chain, title, description, and hreflang annotations — plus flag common SEO issues.

How to use this checker

  1. Paste the URL. Enter the full URL, including https://.
  2. Run the check. The tool fetches the page, follows up to 5 redirects, and parses the head for canonical, robots meta, hreflang, title, and description.
  3. Fix what it flags. A missing canonical, a redirect chain of 2+ hops, a noindex robots tag, or a truncated title/description each show up as a specific, actionable issue.

What this checks

  • Canonical tag — present? Self-referencing? Or pointing elsewhere?
  • Redirect chain — every hop between your input URL and the final destination. Multi-hop chains bleed link equity.
  • Robots meta — is the page accidentally noindexed?
  • Title + description — present? Within optimal length (60 / 160 chars)?
  • Hreflang — international-SEO annotations for multi-language sites.
  • HTTP status — final page returning 200? Or 4xx/5xx?

Common canonical mistakes this tool catches

  • No canonical tag at all — Google is left to guess which URL is authoritative when duplicates exist.
  • Canonical points somewhere other than the final URL — sometimes intentional (pagination, tracking params), sometimes a misconfiguration that quietly deindexes the page you meant to rank.
  • Page is noindexed — a robots meta tag with noindex that shouldn't be there, often left over from staging.
  • Multi-hop redirect chains — two or more redirects before the final URL. Each hop bleeds link equity; flatten to a single 301.
  • Final URL returns a 4xx or 5xx — search engines will drop it from the index entirely.
  • Missing or oversized title/description — no <title>, or one over ~60 characters that Google will truncate; no meta description, or one over ~160 characters.

Frequently asked questions

What is a canonical URL?

A canonical URL is the version of a page you want search engines to treat as authoritative when the same or similar content exists at multiple URLs. You declare it with <link rel="canonical" href="..."> in the page head. Google consolidates ranking signals to the canonical URL.

Why does the canonical tag matter?

Without canonicals, Google has to pick a canonical itself when it finds duplicate content (with/without trailing slashes, with tracking params, on multiple subdomains). Its choice may not match yours, which dilutes link equity and can let the wrong URL rank.

How do redirects affect SEO?

301 redirects pass ~95% of link equity to the destination, 302s pass less, and chains of redirects (A → B → C) bleed equity at each hop. Flatten chains to single hops, and use 301 for permanent moves.

My canonical points to a different URL than the page I'm on — is that a bug?

Not necessarily. Cross-URL canonicals are the normal pattern for pagination (page 2 canonicalizing to page 1), tracking-parameter URLs (?utm_source=...) canonicalizing to the clean URL, or print/AMP variants canonicalizing to the main page. It's a bug only when it's unintentional — check that the canonical target actually contains the same content and returns 200.

What's the difference between a canonical tag and a 301 redirect?

A 301 redirect sends visitors and crawlers to a different URL — the old URL stops existing as far as users are concerned. A canonical tag leaves both URLs reachable but tells search engines which one to index and rank. Use a redirect when a page has genuinely moved; use a canonical when both URLs need to keep working (e.g. a product reachable from two category paths).

Why does the checker flag my hreflang even though I don't have a multi-language site?

It doesn't — hreflang only appears in the results when the page declares it. If you're not running a multi-language site, you can ignore that row entirely. It exists for the sites that do, where a missing or non-reciprocal hreflang annotation is a real, common bug.

What happens to the URL I check?

The checker fetches the page server-side, follows redirects, and parses the head for the fields above. We don't store the audited page's content.

Never worry about canonicals

InBuild emits self-referencing canonical tags on every page automatically. No duplicate content issues, no redirect chains, no manual configuration.