Redirect error in Search Console: fixing loops and chains on WordPress
Where you see it: Search Console → Indexing → Pages → Why pages aren’t indexed
Googlebot followed a redirect from this URL and never reached a page. Google’s help lists four kinds: a chain too long to finish, a loop, an address that grew past the maximum URL length, or a bad or empty URL in the chain. Until the chain ends on a working page, Google has nothing to index from it.
Fix it, starting with URLs you link to or list in your sitemap.
A loop that stops Googlebot stops people too; Cloudflare’s docs say one makes a site inaccessible. Leave only junk addresses nobody uses, after checking that the rule behind them isn’t catching real pages.
Check the URL Search Console listed
Paste one example URL exactly as the report lists it, http or https and www included. The checker follows up to 10 redirects, the number Google’s crawlers follow by default, and stops early when an address repeats.
Redirect report
Enter a URL to see every hop it passes through, with the status code at each step.
Reading the result
- Chain complete reads No, the chain loops: the two URLs alternating in the Hops table name the rules undoing each other, often www against no www, or http against https.
- No, hop limit reached, with Redirects at 10: too long for Google too. URLs that grow at each hop mean a rule keeps adding to the address, Google’s maximum URL length case.
- No, the last redirect has no usable target, or Redirect status with no Location header: the bad or empty URL case. Give that rule a full target.
- A hop from HTTPS down to HTTP: a rule still targets http://, and another layer forcing https turns the pair into a loop.
- Redirect chain looks healthy, Final status 200: it works now. The report reflects Google’s last crawl, so go on to validation.
The same tool with its full guide: Redirect Checker
Why it happens on WordPress
A request to a WordPress site can be redirected by the CDN, the host, the web server, core and plugins. Most of these causes are two layers disagreeing.
Settings → General disagrees with your host on www
Core 301s a request to the Site Address hostname when the two differ only by www. If your host, CDN or .htaccess forces the other form, each layer sends the request back to the other.
Cloudflare Flexible mode with HTTPS forced at the server
Flexible mode reaches your server over plain http. If an SSL plugin, an .htaccess rule or your host sends all http to https, every request bounces, and Cloudflare warns against exactly this.
A reverse proxy that hides HTTPS from WordPress
When a host ends HTTPS at a proxy and passes requests on over http, WordPress thinks the visit is insecure. Its HTTPS guide warns that forcing SSL there, as FORCE_SSL_ADMIN does, loops endlessly.
Rules stacked across plugins and .htaccess
Redirection, Rank Math’s Redirections module and Yoast SEO Premium each keep their own list, and .htaccess holds more. Rules made months apart can point at each other; Cloudflare lists conflicting rules as a loop cause too.
A slug changed, then changed back
Rank Math adds a redirect when you change a post’s URL, and its docs warn that changing it back redirects the post to itself. Redirection and Yoast SEO Premium also add rules on a URL change, so renaming a post twice can leave old → middle → new.
Trailing slashes and permalink changes
Core 301s to add or strip the trailing slash your permalink structure uses, so a rule target missing it costs a hop. Each permalink change stacks new rules onto old ones.
How to fix it
Trace one example to its rule, fix the rule where it lives, then recheck every URL with the same pattern.
1. Name the layer behind each hop
Run each Hops table URL through curl -sI and read X-Redirect-By. Core sends WordPress, and plugins redirecting through core can send their own name; no header points to the server, host or CDN.
2. Match Settings → General to your host
Set WordPress Address (URL) and Site Address (URL) to the exact form visitors should land on, https and www or not, as your host or CDN forces it. Greyed-out fields come from WP_HOME and WP_SITEURL in wp-config.php. Back up first.
3. Let one layer send http to https
Then make sure nothing else argues with it.
- Cloudflare: in SSL/TLS → Overview, leave Flexible for Full or Full (strict). Full needs a certificate on your server, though a self-signed one will do.
- Behind your host’s reverse proxy: add the X-Forwarded-Proto check from WordPress’s HTTPS guide to wp-config.php so WordPress sees https.
4. Fix the rule pair in your redirect plugin
Correct the rule with the wrong target instead of adding another to cover it.
- Redirection: Tools → Redirection; it can also save rules into .htaccess.
- Rank Math: Rank Math SEO → Redirections, in Advanced mode. Debug Redirections shows administrators which rule fired.
- Yoast SEO Premium: Yoast SEO → Redirects, plain and regex rules apart.
- .htaccess on Apache: Redirect and RewriteRule lines. Keep a copy before editing.
5. Collapse each chain to one hop
Point the first rule straight at the final URL, written as the server answers it: https, the right host, your trailing slash. Google follows 10 hops but advises redirecting to the final destination directly, and otherwise ideally 3 at most. Update internal links too.
6. Purge caches and retest
Clear the caching plugin, host cache and CDN, then rerun the checker; Rank Math notes redirects may misbehave on cached pages.
Redirect error or Page with redirect?
Page with redirect means the redirect worked: Google reached a page and left the old address out of the index. Redirect error means it reached no page at all, so fix these first. Once a chain ends on a page, its old address moves to Page with redirect as Google recrawls.
Where each redirect lives on WordPress
Check them in the order a request meets them: CDN, server, core, plugins.
| Redirect | Where it is set | Worth knowing |
|---|---|---|
| www or no www | Settings → General or wp-config.php, plus your host or CDN | Core sends X-Redirect-By: WordPress |
| http to https | Cloudflare, your host, .htaccess or an SSL plugin | Flexible mode plus a server rule loops |
| Trailing slash | Settings → Permalinks | Match it in rule targets |
| Moved posts and pages | Redirection, Rank Math or Yoast SEO Premium | Each can add rules when a URL changes |
| Rules outside WordPress | .htaccess or the Nginx configuration | Redirection, Rank Math PRO and Yoast SEO Premium can write there |
Check the fix in Search Console
Validate once the checker shows every example ending on a page; the run fails if too many rechecked URLs still break.
- Purge caches, then confirm each example reads Chain complete: Yes, with a Final status of 200.
- Open Redirect error under Indexing → Pages and click Validate fix. Google emails progress, and its help says a run usually takes up to about two weeks.
- Don’t restart validation mid-run; wait for Passed or Failed.
- Inspect important final pages in URL Inspection and request indexing. A live test on an old address follows redirects silently and reports the last page.
If it fails, trace the URLs still listed, starting with layers you haven’t checked.
Can RankHive fix this?
Partly. RankHive can write the one-hop 301 that replaces a chain and repoint redirects it added before. Loops set in Settings → General, a CDN, the host or another plugin must be fixed there.
What it writes, once you approve
- An exact-path 301, served by its plugin, from a listed URL to its final page.
- Its own earlier redirects, repointed at the final address.
- Post and page links into a chain, changed to the final URL.
What it can’t do here
- Change WordPress Address, Site Address, or wp-config.php.
- Edit .htaccess, Nginx, host settings or Cloudflare, including its SSL mode.
- Edit rules in Redirection, Rank Math or Yoast SEO Premium; one there that answers first still wins.
- Write regex rules, delete redirects or send a 410.
- See the Redirect error list in Search Console or start validation.
Every change is drafted next to the current value and waits for your approval. Each one written is logged in the Change Log, with Revert.
Check the rest of your site while you’re here
The free site check reads your public pages for titles, meta descriptions, headings, canonical tags and schema, and shows what needs fixing. If you sign up, RankHive reads your Google Search Console data every week, drafts the fixes, and writes the ones you approve to WordPress. Nothing changes on your site until you say yes.
Related issues
- Page with redirectUsually leave it; tidy your own links that still use the old address.
- Not found (404)Fix the 404s that had traffic or links; leave the rest.
- Soft 404Worth fixing, but first decide whether the page should exist.
- URL Inspection toolNothing to fix: it’s the tool you diagnose and confirm fixes with.
Common questions
How many redirects will Googlebot follow?
Up to 10 hops by default. Google’s site move guide still says to redirect straight to the final URL and keep chains ideally to 3 hops, since long chains add latency.
Why does my WordPress site show ERR_TOO_MANY_REDIRECTS?
That browser error is a redirect loop, the fault Google lists here. On Cloudflare, check for Flexible mode first; otherwise compare Settings → General with your host’s rules.
Should I delete the looping redirect?
Only if nothing replaces the old page. Removing it ends the loop, but the address then shows whatever is left, often a 404; pointing it at the right page keeps its visitors and links.
I use Blogger, not WordPress. Does this apply?
The Google side does: the error types, the 10-hop limit and Validate fix. The fixes here are WordPress ones; Google notes that platforms like Blogger may have built-in redirect tools.
Read next
Sources
Checked against these pages on .
- Google Search Console Help: Page indexing report
- Google: How HTTP status codes affect Google’s crawlers
- Google Search Central: Site moves with URL changes
- Google Search Central: Redirects and Google Search
- WordPress Documentation: Settings General screen
- WordPress Advanced Administration: HTTPS
- WordPress Developer Reference: redirect_canonical()
- WordPress Developer Reference: wp_redirect()
- Cloudflare: ERR_TOO_MANY_REDIRECTS
- Cloudflare: Flexible encryption mode
- Cloudflare: Full encryption mode
- Redirection plugin on WordPress.org
- Rank Math: Solving redirection issues
- Rank Math: How to set up redirections
- Yoast: Redirecting a post or page in Yoast SEO Premium
- Yoast: Redirect manager
- Yoast: Do I need to disable PHP redirects?