Canonical consistency auditor
Compare intended canonicals against an uploaded crawl export.
Your inputs
Your results
Ready when you areYour results will appear here.
How it works
Compare recorded canonical declarations and source statuses against an explicit intended canonical in a crawl export, flagging discrepancies without remote requests.
Read the source reference ↗A few things to know
Requires exact CSV headers and absolute URLs. Cross-origin canonicals can be intentional. Results describe supplied data only, not live responses, target indexability or search-engine canonical selection.
When to use this tool
Audit declared canonicals against the intent you supply. A comparison can find migration mistakes without assuming every page should be self-canonical.
- Review a migration export.
- Find mismatched canonical intent.
- Identify missing declarations.
How to use canonical consistency auditor
Prepare the inputs
Paste or upload the requested source or crawl-export columns.
Choose the settings
Run the local check; no remote website requests are made.
Review and export
Review flagged rows and confirm them against the actual site.
Try the supplied example
Inputs
data: URL,Canonical,Expected,Status https://example.com/a/,https://example.com/a/,https://example.com/a/,200 https://example.com/b/,https://example.com/a/,https://example.com/b/,200
Result
The example flags page b because its recorded canonical differs from the expected page b URL.
What it means
Confirm target eligibility and search-engine selection separately.
Common mistakes to avoid
Declared canonical is a signal, not a selection guarantee
Declared canonical is a signal, not a selection guarantee.
Review the target’s response and indexability separately
Review the target’s response and indexability separately.
Frequently asked questions
Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗
Does this crawl my site?
No. It reads a pasted or uploaded CSV snapshot.
Which columns are required?
URL,Canonical,Expected,Status with exact header spelling.
Can canonicals intentionally point elsewhere?
Yes. Put the intended target in Expected.
Is a cross-origin canonical always wrong?
No. It is flagged for deliberate confirmation.
Does this find Google’s selected canonical?
No. Use Search Console URL inspection for that evidence.
Are target responses checked?
No. This tool only has the supplied source status and canonical values.
Are my inputs uploaded or stored?
Processing happens locally in your browser. This tool does not upload inputs. Downloads stay on your device; sharing or opening them in another service is your choice.
What should I check before using the output?
Requires exact CSV headers and absolute URLs. Cross-origin canonicals can be intentional. Results describe supplied data only, not live responses, target indexability or search-engine canonical selection.
Explore the topic in the blog
Sources and method
Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.