Tool version 1.0.0
Canonical Inspector
Compares a page address with its declared canonical and related index signals. It helps editors find conflicting or missing declarations.
Enter a public address. The report will keep evidence and explanation together.
Quick answer
- What is it?
- Compares a page address with its declared canonical and related index signals. It helps editors find conflicting or missing declarations.
- What does it accept?
- One public page URL. Reject nonweb schemes, private targets and oversized responses.
- What does it produce?
- Requested URL, final URL, canonical target, index directives, consistency verdict and evidence panel. Errors separate fetch, parse, permission and unsupported content cases.
Method
Inside the method
A secure server fetch follows a bounded redirect path, parses the final HTML, response headers, robots directives and canonical elements, then normalizes equivalent URLs.
Inputs
Before you begin
One public page URL. Reject nonweb schemes, private targets and oversized responses.
Results
Read the evidence
Requested URL, final URL, canonical target, index directives, consistency verdict and evidence panel. Errors separate fetch, parse, permission and unsupported content cases.
Advanced
Useful extras
Detects multiple canonicals, relative targets, canonical chains, cross domain targets and mismatches between HTML and HTTP headers.
Limits
Known boundaries
Input quality, browser memory, remote server behavior and public API availability can affect a result. The finding describes the supplied material at the time of the test; it does not prove intent or future behavior.
FAQ
Questions about Canonical Inspector
What does Canonical Inspector accept?
One public page URL. Reject nonweb schemes, private targets and oversized responses.
How is the result produced?
A secure server fetch follows a bounded redirect path, parses the final HTML, response headers, robots directives and canonical elements, then normalizes equivalent URLs.
What will I receive?
Requested URL, final URL, canonical target, index directives, consistency verdict and evidence panel. Errors separate fetch, parse, permission and unsupported content cases.
Is the input private?
Server processing is required. No page body is stored after analysis.
What are the main limitations?
Results depend on the quality, completeness and public availability of the supplied input. Review the evidence before making a high-impact decision.