Technical Issue

Suspicious canonical host mismatch

The canonical target appears to point to a different host than the crawled page.

Quick win: Verify canonical host rules in CMS and template logic.

Plan coverage for this workflow

Free includes SEO checks, crawl health, and WordPress security posture visibility. Pro unlocks full WordPress vulnerability intelligence, weekly vulnerability monitoring, and project-level security history.

Why it matters

Cross-host canonicals can accidentally move indexing signals to the wrong domain.

How to fix

  1. Verify canonical host rules in CMS and template logic.
  2. Use cross-host canonicals only when intentionally consolidating domains.
  3. Align canonical targets with your preferred production host.

Related issue guides

Next step: run a fresh scan for current issue counts, then triage fixes in order. You can also browse by category in SEO checks and WordPress checks.