SEO Analysis

Canonical URL Checker

Compare HTML and HTTP Link canonical declarations from one safely fetched page, including relative URLs and conflicts.

Remote public website analysis · No account required

Inspect a public website

Analyze URL sends the submitted URL, including its query parameters, to the WebToolspire API. The API checks public DNS and requests the target without your browser cookies or authorization. Do not submit secret URLs.

One URL, an eight-second server deadline, and at most five redirects. Remote HTML is limited to 128 KiB; JavaScript is not executed.

Add your input, then run the tool to see results.
WORK WITH CONFIDENCE

Understand your results

For maintainers comparing a page’s authored canonical signals.

The Worker fetches one public initial HTML document with the existing DNS, URL and redirect safeguards. It reports canonical link elements and basic rel=canonical HTTP Link declarations separately, resolves relative URLs against the final page, and highlights syntax problems, duplicates and conflicts.

How to use this tool

  1. Enter the public page URL.
  2. Run the check and compare requested, final and declared URLs.
  3. Review observations separately from recommendations and inspect the preferred destination yourself.

What the observations mean

HTML and HTTP declarations can conflict even if each URL has valid syntax. A canonical that differs from the current page can be intentional and needs editorial context.

Worked example

Resolve a relative canonical after an HTTPS redirect.

<link rel="canonical" href="/preferred/">

For a final page at https://example.com/page/, the declaration resolves to https://example.com/preferred/. The destination itself is unverified.

Limits and processing

One initial UTF-8 HTML page, 128 KiB and 4,000 elements. Canonicals resolve against the final URL, ignoring HTML base tags. No rendering, canonical-target fetch or Google selection check.

Common problems and practical fixes

No canonical found
Check the initial source and final HTTP Link header.
Conflicting destinations
Review the templates and response headers that publish the different declarations.
The URL check fails
The site may block automated clients or exceed the source limit. Retry a small public page.

Best practices

Verify the published preferred URL, its indexability and redirects before changing canonical declarations.

Practical tips

  • Use one consistent preferred destination.
  • Check that the selected URL is publicly reachable and intended for indexing.
A LITTLE MORE CLARITY

Frequently asked questions

Practical answers for using the Canonical URL Checker.

Will Google use this canonical?

The tool cannot determine Google’s selected canonical. A declaration is a signal.

Are relative canonicals followed?

They are resolved against the final page URL and displayed. Canonical targets are not requested.

Does the checker read HTTP Link headers?

It recognizes basic angle-bracket links with a rel=canonical parameter in the final response. Complex or oversized headers can remain outside its limits.