Technical Issue

Blocked cross-host redirect

A crawled URL redirected to a different host, and ScanForge excluded the destination to preserve same-host crawl boundaries.

Quick win: Standardize canonical host rules for protocol and subdomain variants.

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 redirects can fragment technical authority and hide destination content from bounded audits.

How to fix

  1. Standardize canonical host rules for protocol and subdomain variants.
  2. Update internal links to target the preferred host directly.
  3. Document intentional cross-domain redirects and monitor their impact.

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.