Canonical URL Match
Checks that the canonical URL matches the current page URL (or an intentional alternate).
What this check measures
We compare the current URL to the canonical tag value. Mismatches are flagged — they may be intentional (consolidation) or accidental (template bug).
Why it matters
If canonical points elsewhere, Google indexes the target, not this URL. Great when intentional (reducing duplicates). Disaster when accidental (every page's canonical points to homepage).
How our audit detects it
Parse <link rel="canonical">, compare href to current URL. Flag mismatches with comparison.
Typical findings
- error_outlineAll pages canonical to the homepage — Google indexes only the homepage.
- error_outlineCanonical includes tracking parameters — pattern breaks.
How to fix
Canonical should equal the current URL (self-referential) unless you want to consolidate duplicates. Use `metadata.alternates.canonical` in Next.js for auto-generation.
Frequently asked questions
Self-referential canonical — necessary?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
TechnicalHTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.