301 Redirect Problems: Find and Fix Chains, Loops and Errors
Short answer Test the old address and count hops. Healthy is one 301 straight to a live page. Several hops is a chain: point it at the final page. An endless circle is a loop: two rules disagree, so remove one. A redirect to your home page or an http page misleads Google: point it at the closest matching https page.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat's wrong with my 301 redirect?
A 301 is a permanent forwarding rule: anyone who asks for the old address gets sent to the new one. Almost every problem is one of five shapes. Find yours by testing the old address (next section), then match what you see:
| What you see | Problem | Fix |
|---|---|---|
| Old page → page B → page C → final page | Chain: one move stacked on another | Point every old address straight at the final page |
| The browser says "too many redirects" | Loop: two rules send visitors back and forth | Find the two rules and delete one |
| Old service page → home page | Wrong target | Point it at the page that replaced it, or let it return 404 |
| Old page → http:// or the other www version | Mixed signal: the target isn't your preferred address | Point it at the exact https address you want in Google |
| A 302 or 307 where the move is permanent | Temporary code for a permanent move | Change it to 301 (or 308) |
| You fixed it, but your browser still goes the old way | Cached redirect | Test in a private window or with the command below |
Google's position on the type to use is plain:
"we recommend that you use a permanent server-side redirect whenever possible." (Google Search Central: Redirects and Google Search)
"Server-side" means the rule lives on your host or in your site's redirect settings, not in a script on the page; Google may never see a JavaScript redirect.
How do I check a redirect?
You want to see every hop, not just where the browser ends up. A free online redirect checker shows this. So does one command in Terminal (Mac) or Command Prompt:
`curl -sIL https://yoursite.com/old-page`
It prints one block per hop: a status (`301`, `302`, `200`, `404`) and a `location:` line naming the next address. Healthy is two blocks: one `301`, then `200` (the page loaded). curl stops after 50 redirects by default, so a loop ends with an error instead of running forever (curl manual: --max-redirs).
Test the four versions of your home page too: http and https, with and without www. Three should forward in one hop to the fourth.
Don't use Search Console's URL Inspection tool to trace a chain. Google says its inspection tools don't follow redirects; they report only the first hop (Google Search Central: HTTP status codes). In the Page indexing report, "Page with redirect" is normal for an address you moved on purpose. See crawled or discovered, currently not indexed for what each status means.
How do I fix a redirect chain?
Chains build up quietly. You moved /services to /plumbing-services in 2022, then to /plumbing in 2025, and each move added a rule on top of the last. Google follows a chain, up to a limit:
"By default, Google's crawlers follow up to 10 redirect hops." (Google Search Central: HTTP status codes)
Its site move guide still asks for one hop:
"we advise redirecting to the final destination directly. If this is not possible, keep the number of redirects in the chain low, ideally no more than 3 and fewer than 5." (Google Search Central: Site moves with URL changes)
Chains add delay for visitors, and some browsers don't support long ones, the guide adds. To fix one:
- List every old address that still gets visits or has links pointing at it.
- Edit each rule so it points at the final page, not at the next old address.
- Update your own menus, buttons and internal links to the final address, so your site doesn't send its own visitors through redirects.
- Test each old address again: one `301`, then `200`.
Crawl budget (how many pages Google will fetch from your site) is rarely the reason on a small site: Google's crawl budget guide is written for sites with 10,000 to over 1 million pages (Google Search Central: Crawl budget management).
Why does my site say "too many redirects"?
That's a loop: rule A sends visitors to B, and B sends them back to A. Browsers give up and show an error; Chrome's is ERR_TOO_MANY_REDIRECTS. The internet's HTTP standard says a client "SHOULD detect and intervene in cyclical redirections" (RFC 9110), which is why you see an error instead of a frozen tab.
The usual cause is two places that both control http vs https or www vs non-www. Cloudflare's documentation describes the most common case:
"Redirect loops will occur if your origin server automatically redirects all HTTP requests to HTTPS." (Cloudflare SSL/TLS docs: ERR_TOO_MANY_REDIRECTS)
That applies in Cloudflare's Flexible encryption mode. The fix: remove the https redirect at your host, or switch to Full or higher, which needs a security certificate on your host.
Without Cloudflare, look for the same pattern: your host forces www while a plugin forces non-www, or two plugins hold rules for one address. Keep one place in charge.
Fixed but still looping? A 301 "is heuristically cacheable" (RFC 9110): your browser may replay the stored answer. Test in a private window or with curl.
Is my redirect pointing at the wrong page?
Two wrong targets cost you the most.
The home page. It's tempting to send every deleted page home. Google warns against it:
"Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site." (Google Search Central: Site moves with URL changes)
Google says it "might be treated as a soft 404 error": the old page counts as gone anyway. Send each old page to its closest replacement, or let it return 404. Merging several pages into one is fine, Google says.
A version you don't want indexed. Redirects are, in Google's words, "A strong signal that the target of the redirect should become canonical" (Google Search Central: How to specify a canonical URL). The canonical is the one address Google shows for a page. If your rule points at http://, or at www when the rest of your site is non-www, you are telling Google to prefer the wrong address. Google lists an HTTPS page that "redirects users to or through an HTTP page" as a conflicting signal.
Then check that your other signals agree with the redirect:
| Signal | Should name |
|---|---|
| Redirect target | The final https address |
| The canonical tag on that page | The same address |
| Your sitemap | Only final addresses, never old ones or http versions |
| Your internal links | The final address |
Google says not to name different canonical addresses for the same page with different methods.
Do 301 redirects lose SEO value?
No, when they point at a matching page. Google's site move guide says:
"301 and other permanent redirects don't cause a loss in PageRank." (Google Search Central: Site moves with URL changes)
PageRank is Google's measure of the value links pass to a page. Google treats a 308 like a 301, and a 302 or 307 as only a "weak signal" (Google Search Central: HTTP status codes). A 308 also stops browsers turning a form submission into a plain page request, which a 301 allows (MDN Web Docs: 301).
Keep redirects "generally at least 1 year", Google says, and as long as possible. Value is lost when redirects are deleted early, point at an unrelated page, or vanish in a redesign. If you're leaving your agency or changing platforms, get the full list of old addresses first.
Example
A plumber with a three-hop chain
/services goes to /plumbing-services, then /plumbing, then /plumbing/. The owner points the first two rules at /plumbing/ and fixes the menu link. Each old address now shows one 301, then 200.
A dental office locked out of its own site
After adding Cloudflare on Flexible mode, every visit shows "too many redirects" because the host also forces https. Switching Cloudflare to Full, with a certificate on the host, stops the loop.
A law firm that sent 40 old posts home
A redesign pointed 40 deleted posts at the home page. The firm maps the 12 with links or visits to their closest current page and lets the other 28 return 404.
FAQ
Should I use a 301 or a 302?
301 for a permanent move, 302 if the old page returns. Google shows the new address for a 301, the old one for a 302.
Can I delete old redirects after a year?
Google says keep them "generally at least 1 year", longer if possible. Keep any rule whose old address still gets visits or outside links.
Should a deleted page redirect to my home page?
Not unless the home page replaces it. Google may treat that as a soft 404. Redirect to a real replacement, or let it return 404.
Different for you?
- Moving to a new domain name: redirects are one part of a site move, along with Search Console's change of address step. Before you rename, see keyword domain names.
- Search Console shows many redirected or missing pages: read crawled or discovered, currently not indexed and Search Console for a small business.
- Changing agencies or website platforms: secure your domain and old address list first with leaving your marketing agency.
- Redesigning or rebuilding the site: plan the redirect map with the build on the Website page; track rankings afterward on the SEO page.