---
title: "\"Redirect error\" in Search Console on WordPress"
url: https://wpministry.co/errors/redirect-error-search-console/
description: "Google could not finish the redirect. The causes are a long chain, a loop, a URL past the length limit, or a bad address in the chain."
lang: en-US
---

Skip to content

# "Redirect error" in Search Console: a chain, a loop, or a bad address

"Redirect error" means Google could not finish following a redirect. The help page names four causes: a chain that was too long, a loop, a URL that grew past the maximum length, and a bad or empty URL in the chain. Google's crawlers follow up to 10 hops.

By

WP Ministry

Published

November 15, 2026

## In short

- Google lists four causes: a chain that was too long, a loop, a redirect URL past the maximum length, and a bad or empty URL in the chain.
- Its crawlers follow up to 10 hops by default. The HTTP page says Inspection Tools do not follow redirects. The indexing report says the live test does.
- "Page with redirect" is the other status. There Google followed the redirect to an end. Here it could not.
- A browser that reports ERR_TOO_MANY_REDIRECTS is the same loop, seen by a visitor. This page is the report's wording.
- Point each old address at its final URL in one hop. A 301 and a 308 are the permanent codes Google treats as a strong signal.
- The report clears when Google can follow the chain. A sandbox is not a Search Console property.

"Redirect error" means Google tried to follow a redirect and could not finish. The Page indexing report's help names four causes, and no others: a chain that was too long, a loop, a redirect URL that grew past the maximum length, and a bad or empty URL in the chain. It points at a debugging tool such as Lighthouse for the detail.

This is not "Page with redirect" (https://wpministry.co/errors/page-with-redirect/). There the address redirected and Google followed it to a page. The address is not indexed, and the page it lands on can be. Here Google did not get to a page.

Google's documentation of HTTP status codes says its crawlers follow up to 10 redirect hops by default, and that Google Inspection Tools do not follow redirects. The Page indexing report says something else about a redirect that did finish: the live URL Inspection test follows redirects and then tests the final URL, without saying that it followed one. Both pages were current on the day this page was written. The hops you can list yourself are in the next section.

## See the chain

The redirect checker (https://wpministry.co/tools/redirect-checker/) follows an address and lists each hop: the status and where it leads. Run it on an example from the report before you change a rule. A loop shows the same address twice. A chain shows how many steps there are before a `200`. A hop with no location, or one that is not an address, is the bad or empty URL the help page names.

What each status means to Google, from that same HTTP document:

- `301` and `308` are followed, and Google uses them as a strong signal that the target should be processed.
- `302` and `307` are followed, and used as a weak signal.
- Whatever the code, content on the redirecting URL is ignored. The final URL is what gets processed, if the chain ends.

A redirect that should be permanent is a `301` or a `308`. How to set up redirects in WordPress (https://wpministry.co/blog/set-up-wordpress-redirections/) covers a plugin, the server and code, including the codes WordPress sends when you do not set one.

## What causes it

- ### The redirect chain is longer than Google will follow
  Common
  Google's help names a chain that was too long as one redirect error. Its crawler documentation says crawlers follow up to 10 redirect hops by default. Each extra rule that points at an address which itself redirects adds a hop.
  Fix: Point each old address at its final URL
- ### The address redirects to itself, or two rules point at each other
  Common
  A loop is the second cause the help page names. The browser's version of the same fault is ERR_TOO_MANY_REDIRECTS. The report's version is that Google could not finish the chain.
  Fix: Break a loop
- ### A hop is empty, not a URL, or the URL grew past the length limit
  Sometimes
  The help page's other two causes are a redirect URL that eventually exceeded the maximum URL length, and a bad or empty URL in the chain. A rule with a blank target, or one that appends to the address on every hop, matches those words.
  Fix: Point each old address at its final URL

## How to fix it

### Point each old address at its final URL

- Takes care
- Low risk
- About 30 minutes
1. #### Step 1: List the hops
   Run the redirect checker on one example, and on two more if the list is long. Write down each status and each target. Count the hops. More than 10 is past the default Google documents.
2. #### Step 2: Find the rule that adds a hop
   WordPress already redirects several forms of an address in one hop: a missing slash, a `?p=` link, `www` against the bare host, and a post's old slug. Those are listed on Page with redirect (https://wpministry.co/errors/page-with-redirect/). A chain usually means a second rule, in a plugin or at the host, points at an address WordPress then forwards again. A blank target is the empty URL in the help's list. A rule that adds a query to the address on every pass is the length cause.
3. #### Step 3: Make it one hop
   Edit the earliest rule so it sends the old address straight to the final URL, with a `301` or a `308`. Remove the intermediate rules that only existed to forward to the next old address. Fetch the old address again. One redirect, then a `200`, is the shape you want.
4. #### Step 4: Leave addresses that already end
   An example that redirects once to the right page is "Page with redirect" (https://wpministry.co/errors/page-with-redirect/), not this status. Do not delete that redirect to chase a different row of the report.

### Break a loop

- Takes care
- Low risk
- About 20 minutes

A loop is the same fault a browser calls ERR_TOO_MANY_REDIRECTS (https://wpministry.co/errors/err-too-many-redirects/). Start with that page when visitors see the error. The Search Console row is the record that Google hit it too.

1. #### Step 1: Confirm the repeat
   The redirect checker shows the address repeating. Two hops that point at each other are enough. So is one rule that points at itself.
2. #### Step 2: Remove one of the pair
   Keep the redirect that matches the address the site is supposed to use, the one in Settings. Delete the other. A CDN that redirects to `https` while WordPress redirects back to `http`, or a host that adds `www` while WordPress removes it, is a pair split across two accounts. Change one side so both agree.
3. #### Step 3: Fetch it again
   One hop to the final address, then a `200`. Ask Google to recrawl only after that fetch looks right. The status in the report changes when Google crawls, not when you save the rule.

The help page says validation is how you ask Google to confirm a fix, and that it stops if a single instance remains. Validate when every example was a chain or a loop you have removed. An address that is meant to redirect once should not be in this list at all.

A WordPress SEO audit (https://wpministry.co/services/wordpress-seo-audit/) includes the redirect map when the chains come from a redesign or a domain move and the list is long. The migration checklist (https://wpministry.co/resources/website-migration-checklist/) is the same work written as steps.

## Common questions

Is a 301 the same as a redirect error?

No. A single `301` to the right page is a redirect Google could follow. The report files that under "Page with redirect". "Redirect error" means the chain did not end in a page Google could use.

How many redirects are too many?

Google's crawler documentation says the default is 10 hops. Specific products can differ, and it says the Inspection tool does not follow redirects at all. One hop is the shape to aim for, because each extra hop is another request and another place for a loop.

The site loads in my browser. Why is the report still red?

You may be seeing a cached hop, or the chain may be long enough for a browser and too long for the crawl that filled the report. Run the redirect checker, which does not use your browser's cache. The report itself updates when Google crawls the address again.

Will this keep the page out of Google?

The address with the error is not indexed. If the chain is repaired to one hop, the old address stays a redirect and the final address can be indexed. Google's HTTP documentation says a `301` is a strong signal that the target should be processed. It does not promise that the target will be indexed.

## When to get help

When the chain includes the host, a CDN and a plugin and you cannot see which hop is wrong from the outside. The redirect checker shows the hops. The account that can delete one of them is whoever set it.

## More on this subject

- WordPress SEO: https://wpministry.co/topics/wordpress-seo/
- WordPress errors and troubleshooting: https://wpministry.co/topics/wordpress-troubleshooting/
- Guide Bing Webmaster Tools for WordPress: setup, IndexNow, and what it means for ChatGPT and Copilot: https://wpministry.co/blog/bing-webmaster-tools-wordpress/
- Guide Did AI Overviews cause your traffic drop? What Search Console can show, and what it cannot: https://wpministry.co/blog/traffic-drop-ai-overviews/
- Guide Favicon not showing in Google: the Site Icon WordPress writes: https://wpministry.co/blog/wordpress-favicon-not-in-google/
- Guide Google shows the wrong site name: what you can set on WordPress: https://wpministry.co/blog/google-shows-wrong-site-name-wordpress/
- Guide Generative engine optimization (GEO): what is documented, what was studied and what is guesswork: https://wpministry.co/blog/generative-engine-optimization/
- Guide How to track ChatGPT traffic in Google Analytics 4, and what the count leaves out: https://wpministry.co/blog/track-ai-referral-traffic/

## Would you rather we fixed it?

SEO audit is $249. A written audit, each finding with its source, and up to 2 hours of fixes done and tested again.

More about this work: WordPress SEO audit (https://wpministry.co/services/wordpress-seo-audit/)

May we measure how this site is used?

A yes notes the pages of this visit and loads Google Analytics. A no keeps and loads nothing. See the cookies page (https://wpministry.co/legal/cookies/).

If you say yes, we note the pages you look at during this visit and load Google Analytics. If you say no, nothing is kept and nothing is loaded. The site works the same either way. The cookies page (https://wpministry.co/legal/cookies/) has the details.

## Structured data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://wpministry.co/#organization",
      "name": "WP Ministry",
      "url": "https://wpministry.co/",
      "logo": "https://wpministry.co/brand/logo.png",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "1309 Coffeen Ave STE 1200",
        "addressLocality": "Sheridan",
        "addressRegion": "WY",
        "postalCode": "82801",
        "addressCountry": "US"
      },
      "sameAs": [
        "https://www.linkedin.com/company/wp-ministry/",
        "https://x.com/wpministryco",
        "https://www.instagram.com/wpministryco/",
        "https://www.facebook.com/wpministryco",
        "https://www.tiktok.com/@wpministryco",
        "https://www.pinterest.com/wpministryco/",
        "https://www.youtube.com/channel/UCOZRuAukk5QSTRPG6BaHl3Q"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://wpministry.co/#website",
      "name": "WP Ministry",
      "url": "https://wpministry.co/",
      "inLanguage": "en-US",
      "publisher": {
        "@id": "https://wpministry.co/#organization"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://wpministry.co/errors/redirect-error-search-console/#article",
      "headline": "\"Redirect error\" in Search Console: a chain, a loop, or a bad address",
      "description": "Google could not finish the redirect. The causes are a long chain, a loop, a URL past the length limit, or a bad address in the chain.",
      "url": "https://wpministry.co/errors/redirect-error-search-console/",
      "mainEntityOfPage": "https://wpministry.co/errors/redirect-error-search-console/",
      "inLanguage": "en-US",
      "image": "https://wpministry.co/og/errors/redirect-error-search-console.png",
      "author": {
        "@id": "https://wpministry.co/#organization"
      },
      "publisher": {
        "@id": "https://wpministry.co/#organization"
      },
      "datePublished": "2026-11-15T00:00:00.000Z",
      "dateModified": "2026-11-15T00:00:00.000Z"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://wpministry.co/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Error fixes",
          "item": "https://wpministry.co/errors/"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "\"Redirect error\" in Search Console: a chain, a loop, or a bad address"
        }
      ]
    }
  ]
}
```