"Page fetch: Failed: Redirect error": how to fix it

What it means

The page sends visitors to another address. Google tried to follow it and failed, so Google has no page to index.

Google's help lists four causes: a chain that is too long, a loop, an address that grows too long, and a bad or empty address in the chain. Google's docs say its crawler follows up to 10 redirect hops by default.

This is not the same as Page with redirect. Page with redirect means the redirect worked, and Google looks at the target instead. Redirect error means the redirect did not work.

Where it shows: Page indexing > Crawl > Page fetch. The Page indexing report lists the same pages under Redirect error.

Common causes

1. A loop: two rules send the page back and forth, for example http to https and back, or with and without www.
2. A long chain after a site move: the old address goes to a newer one, then to the newest, one hop at a time.
3. Two rules fight over the slash at the end: one adds it and another removes it.
4. A redirect points to a broken or empty address, often from a typo in a plugin rule.
5. The redirect depends on cookies, language, or location, so Google is sent somewhere a browser is not.

How to check which cause applies

1. Run curl -sIL with the page address, or use a redirect checker, and read each hop.
2. Count the hops. An address that shows up twice is a loop.
3. Check the final address. It should answer 200 OK.
4. Click Test live URL. Google's help says the live test follows redirects without saying so, so a pass means the final page works now. It does not show the chain.

How to fix it

1. Point the old address straight at the final page, with one 301 redirect.
2. Remove the rule that makes the loop. Make your https, www, and slash rules agree with each other.
3. Use the final address in your sitemap and internal links, so Google does not start at a redirect.
4. Click Test live URL on the old address. Then click Request indexing for the final address.

When you can ignore it

The address is old, nothing links to it, and it is out of your sitemap. Fix it when the page matters.

With CrawlCoach

CrawlCoach groups the pages with Redirect error in one list. On paid plans, its crawl of your site also flags links that point to a redirect or a chain of redirects, and gives the final address to link to instead. Google makes the final call on what it indexes.

Related Page indexing reasons

• Redirect error: The redirects for this page are broken, too long, or go in a circle.
• Page with redirect: The page sends visitors to another page, so Google shows that one instead.

Questions

Sources

Checked on October 8, 2026. Google can change its tools and wording after that date.

• Search Console Help: URL Inspection tool
• Search Console Help: Page indexing report
• Google Search Central: How HTTP status codes affect Google's crawlers