Scan at scalePages with a relative canonical URL
Pages with a relative canonical URL
A per-URL report: one row per page that matches, over the pages a crawl reached.
What this report returns
These pages declare their canonical with a relative href. RFC 6596 permits it, but a relative canonical inherits whatever base URL the page resolves against, so staging hostnames, protocol switches, and trailing-slash differences silently change what it points at.
How to fix it. Make the href absolute: <link rel="canonical" href="https://www.example.com/page">. A best-practice nudge, not a validity failure: a relative href alone leaves the page valid, which is why the Usability Issue Detected column is here — it is false on a page whose only quirk is this one, and true where the canonical also has a real defect (an empty href, a tag outside the head, conflicting tags, an unusable URL) worth fixing first.
Security checks are provisional; precision has not yet been measured. A clean row is not a security assessment.
The columns it shows
Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.
- Canonical Relative
canonicalRelative - Canonical Usability Issue Detected
canonicalUsabilityIssueDetected - Canonical Security Risk Detected
canonicalSecurityRiskDetected - Canonical Findings
canonicalFindings - Canonical URLs as Written
canonicalHrefs - Ruleset Version
rulesetVersion - Security Check Status
securityCheckStatus - Related Security Frameworks
securityFrameworkReferences
About Canonical URL
Tells an agent which address is the real one for this page.
Read how Canonical URL is checked, including the specification it is validated against and a worked correct and broken example.
Running it
This report comes with Agentic Readiness in Lumar and appears on every crawl of any project that has it turned on. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.