This check finds URLs that pass through one or more redirects before reaching their final destination. Redirects are useful for moved content, but avoidable hops add work for users, crawlers, and servers.
Why this matters
Each hop adds another request and can delay navigation. Long or inconsistent chains also make canonicalization harder to understand, waste crawl activity, and increase the chance that a link ends at a loop or broken destination.
How to fix it
- Update internal links, canonicals, hreflang entries, sitemap URLs, and structured data to point directly to the final canonical URL.
- Replace multi-hop rules with one server-side 301 or 308 redirect from the old URL to the final destination.
- Keep HTTP-to-HTTPS and hostname normalization consistent.
- Remove loops and verify that query strings are preserved only when they are required.
When the finding appears across many URLs, fix the shared component or layout that produces it instead of patching generated HTML page by page. Recheck representative templates and responsive states after deployment so the correction does not create a regression elsewhere.
How to verify the fix
Request representative old URLs and record every response status and Location header. The intended result is one redirect at most for a genuinely moved URL, while links published on the current site should normally return a successful response directly.
Keep before-and-after evidence for the affected URL, original output, correction, and verification method. If markup changes after load, test consent states, localization, responsive variants, and client-side navigation because the initial HTML and rendered DOM can differ.