Skip to content
MrKeyword
Technical SEO

Redirect error in Google Search Console: what it means and how to fix it

A Redirect error status means Googlebot could not follow the URL's redirect to a final page, because of a loop, a chain that is too long, a redirect to an invalid or empty URL, a URL that exceeds the maximum length, or a redirect to a 4xx or 5xx page. Here is what each cause looks like and the step-by-step fix.

A dashboard of redirect and indexing checks on a desktop monitor
The short version
  • A Redirect error means Googlebot could not follow the URL's redirect to a final page, so the URL is not indexed.
  • The usual causes are a redirect loop, a chain longer than Google follows (up to 10 hops), a bad or empty target, an overlong URL, or a redirect to a 4xx or 5xx page.
  • Fix it by tracing the hops, then pointing the old URL straight at the final 200 URL in one 301.
  • Remove conflicting server, CDN and CMS redirect rules so nothing re-adds a hop or a loop.
  • Update internal links and the sitemap to the final URL, then use Validate fix in Search Console.

What does Redirect error mean?

Redirect error means Googlebot could not follow the URL's redirect to a final page, because of a loop, a chain that is too long, a redirect URL that is too long or a bad/empty target. The URL answers with a 3xx status, but the redirect never resolves to a normal 200 page, so Google has no content to index and reports the URL as a Redirect error in the Page indexing report. Google's redirects guide explains how it follows a 301, and our 301 vs 302 redirect guide covers which status to use. For where this status sits among the others, read the Search Console Page indexing report guide.

What causes a redirect error?

Almost every Redirect error comes from one of five causes: a loop, a chain that is too long, a bad target, an overlong URL, or a redirect to an error page. Each one looks different when you trace the URL:

  • Redirect loops. The chain never ends because two rules send the URL back and forth, for example http to https to http, or trailing-slash rules fighting each other (/page to /page/ and back). Googlebot eventually stops and reports a Redirect error.
  • Chains longer than Google follows. Googlebot follows up to 10 hops in a redirect chain. A chain of 11 or more redirects is reported as a Redirect error even if the last URL is a healthy 200 page.
  • A redirect to an invalid or empty URL. The Location header is malformed, relative in a way the server resolves wrong, contains spaces or illegal characters, or is simply empty.
  • A URL that exceeds the maximum length. The redirect target is longer than the URL length Google will follow, so the next hop cannot be requested.
  • A redirect to a 4xx or 5xx page. The redirect resolves, but the final URL returns 404, 410 or a server error, so there is still no indexable page at the end.

Old redirects that were correct once are the most common source: a site changes its domain, HTTPS, trailing slashes or CMS permalinks, and the old rule now points at a URL that has its own redirect. Conflicting rules in the server config, the CDN and the CMS can also stack into a chain or a loop without anyone writing a bad rule on purpose.

How do I fix a redirect error?

Trace every hop, point the old URL straight at the final 200 URL in one 301, remove the conflicting rule, update links and the sitemap, then validate. Work through the steps in order:

  1. Trace the hops with a redirect checker

    Run the reported URL through a free redirect checker and note every status code and Location header until the chain stops. A loop shows the same URL repeating; a long chain shows many 301s; a bad target shows a malformed or empty Location. Test both the http and https versions and both the trailing-slash and non-slash versions, because the loop often appears only on one variant.

  2. Point the old URL straight at the final 200 URL in one 301

    Replace the whole chain with a single 301 from the old URL to the final URL that returns 200. Never redirect A to B and B to C when you can redirect A straight to C. Keep the redirect permanent (301) for a moved page, and send it to a live page with the same topic so visitors and Google land somewhere useful.

  3. Fix conflicting server, CDN and CMS rules

    A loop usually means two layers disagree: the web-server config, the CDN or edge rules and the CMS permalink settings each add a redirect. Find which layer adds the extra hop and remove it there. Common culprits are an HTTPS rule that sends https back to http, a canonical-host rule fighting a www rule, and a trailing-slash setting on both the CDN and the CMS.

  4. Update internal links and the sitemap to the final URL

    Change internal links that point at the old URL so they go straight to the final URL, and list only that final URL in your XML sitemap. That removes the redirect from the crawl path and stops Google from rediscovering it. Use a self-referencing canonical tag on the final page so its canonical points at itself.

  5. Validate the fix in Search Console

    After the change is live, open the Page indexing report, find the Redirect error row, and use Validate fix. Google re-crawls a sample of the URLs; once each one resolves to a 200 page, it moves out of the Redirect error list. Give it a few days and recheck, and use the HTTPS report if the loop started with an HTTPS migration.

Redirect error problems, examples and fixes

Match the problem to the fix

ProblemExampleFix
Redirect loophttp://example.com/page → https://example.com/page → http://example.com/pageKeep one HTTPS and one host rule, and delete the rule that redirects back to http.
Trailing-slash rules fighting/page → /page/ → /page, foreverPick one form (with or without the slash), set it in one place, and remove the opposing rule from the CDN or CMS.
Chain longer than Google followsA → B → C → D → E → F → G → H → I → J → K → 200Replace the chain with one 301 from A straight to the final 200 URL.
Invalid or empty targetLocation: (empty), or a URL with spaces or illegal charactersFix the rule so it emits one encoded absolute URL.
URL exceeds the maximum lengthA redirect target far longer than the page URL, often built from stacked parametersRedirect to the short, clean final URL instead of the overlong one.
Redirect to a 4xx or 5xx pageOld URL → 404 page, or old URL → a page returning 500Point the redirect at a live 200 page, or restore the target so it returns 200.
The rule of thumb: every redirect should resolve to a 200 page in one hop. If you need a second hop, the rule is in the wrong place.

Follow the hops before you change a ruleCheck any URL's redirect path, status codes and final page, free.

Check a redirect

Bing Webmaster Tools

Bing does not have an identical Page indexing report, but Bing Webmaster Tools has URL Inspection and Site Explorer for the same questions. URL Inspection shows one URL's index status, crawlability and response code, and Site Explorer shows what Bing has discovered for a site. Use IndexNow or the Submit URLs tool when a page is new or has changed. Our Bing Webmaster Tools guide covers the setup.

Questions and answers

Redirect error questions

What does 'Redirect error' mean in Google Search Console?

It means Googlebot could not follow the URL's redirect to a final page, because of a loop, a chain that is too long, a redirect URL that is too long or a bad or empty target. The URL is not indexed until the redirect resolves to a 200 page.

How many redirects will Googlebot follow?

Googlebot follows up to 10 hops in a redirect chain. A chain of 11 or more redirects is reported as a Redirect error even when the last URL is a healthy 200 page, so collapse the chain into one 301.

What is the difference between a Redirect error and Page with redirect?

Page with redirect means the URL redirects cleanly to another URL and Google followed it. Redirect error means Google could not reach a final page: a loop, too many hops, a bad target or a redirect that ends in a 4xx or 5xx.

Should I use a 301 or a 302 to fix a redirect error?

Use a 301 when the move is permanent, which is the usual case for a changed URL. Use a 302 only for a temporary redirect. Either way, point the old URL straight at the final 200 URL in one hop.

How long does Validate fix take for a redirect error?

Validation is a request for Google to re-crawl a sample of the URLs, so it can take a few days to about two weeks. It clears only when each sampled URL resolves to a 200 page, so fix the redirect before you press it.

About this article

Written by the MrKeyword team, who build an SEO workspace on first-party Search Console and Bing data. Outside facts link to their original source below. We update this page when the product or the sources change.

Sources

  1. Redirects and Google Search — Google Search Central, on 301 redirects and how Google follows them
  2. Page indexing report — Search Console Help, on the Page indexing report and the Redirect error status
Keep reading

More on technical SEO, plus the feature and free tool for the same job. All technical SEO guides →

Check a URL's redirect path.

Follow every hop to the final page with the free redirect checker. Free plan for one website, no card; paid plans from $10 a month.