An address takes a long chain of redirects

In the reportLong redirect chain

redirect_chain · Review item

Short answer

This appears when an address the crawl requests passes through three or more redirects before its final answer. The length of the chain is kept for review; a final answer that is an error needs attention on its own. Check where the chain ends: if the destination works, point links straight to it; if it answers with an error, fix or replace it first.

Severity: Low. Review it when you next tidy redirects. It is Medium for a homepage chain, or a known sitemap-listed chain when the sitemap-redirect check is not selected; otherwise it is Low.

Why it matters

Google follows up to ten redirects, but its guidance on moving a site advises redirecting to the final destination directly and, where that is not possible, keeping chains short: ideally no more than three and fewer than five. Each step is also one more request before the final answer.

What to do

  1. Review the requested address, observed redirect steps, final address and final status in the evidence.
  2. If the final answer is an error, repair or replace the destination.
  3. If the destination works, update links you find to point straight to it, and redirect old addresses directly to it rather than through older ones. This finding does not list referring links.

When to leave it as it is: if the chain comes from a recent move, ends on a working page, and your links already point to the new addresses, a three-step chain is within what Google's guidance calls acceptable; tidy it when convenient.

What we read

For every admitted requested address, we count the HTTP redirects observed by the shared crawl. Three or more steps with a final response are reported, including a delivered error response. A partial redirect trace can prove the threshold, but cannot prove that a shorter chain is clean. Loops and walks stopped at the redirect limit belong to the redirect-loop check.

A known sitemap-listed long chain is left to the sitemap-redirect check only when that check is selected. Otherwise this check keeps the finding and records the known listing as importance. Missing sitemap input or nonmembership in a partial sitemap never suppresses a finding.

A complete observation of fewer than three redirects is clean here even when the address is listed. Meta refresh and JavaScript redirects are not followed. Each starting address keeps its own identity.

Example & evidence

Illustrative example — one linked address, not a live audit.

The homepage contains <a href="/old-menu">Old menu</a>, and /old-menu is not in the sitemap:

GET https://bakery.example/old-menu   → 301  Location: /menu-2024
GET https://bakery.example/menu-2024  → 301  Location: /menu-2025
GET https://bakery.example/menu-2025  → 301  Location: /menu
GET https://bakery.example/menu       → 200 OK

Three redirects precede the final response. The finding keeps /old-menu as its starting address and records the three steps and the final address /menu.

A possible correction: point the homepage link at /menu, and redirect /old-menu straight to /menu with one permanent redirect.

Confirm & check again

Check for yourself: open the address in a redirect checker, or in your browser's developer tools, count the steps before the final answer, and check what that answer is.

Check again: Full audit — Run a new audit of the same starting address. A complete response and redirect observation showing fewer than three steps confirms this finding fixed; the sitemap check can still report a remaining one- or two-step redirect. A long chain handed to the sitemap check leaves the earlier finding carried, never fixed by ownership alone. Missing or incomplete observations cannot confirm a fix. Dismissal is an independent judgment and remains in history.

Limits & sources

Three redirects are a review threshold, not proof of a fault or lost rankings. The check does not distinguish permanent from temporary steps and does not see script redirects. Search Console importance and referring-link evidence are outside this check.

Confidence: High because each step is followed and recorded.

Sources

  • Google, How HTTP status codes affect Google's crawlers — says Google's crawlers follow up to ten redirect hops. Checked 25 September 2026.
  • Google, How to move a site — advises redirecting to the final destination directly, and keeping chains short, ideally no more than three and fewer than five. Checked 25 September 2026.

Editorial review: 4 November 2026