Quick answer: A redirect loop is an error where a URL redirects to another URL that eventually redirects back to the first, so browsers, Googlebot and ad crawlers never reach a final page and show errors like ERR_TOO_MANY_REDIRECTS instead.
Every redirect tells a visitor’s browser, “this page has moved, go here instead.” That works fine when the trail ends at a real page. In a redirect loop, the trail circles back on itself: Page A sends you to Page B, and Page B sends you back to Page A (or to C, which returns to A). The browser keeps following until it hits its safety limit, then gives up.
Chrome stops after about 20 redirects and shows “This page isn’t working: redirected you too many times.” Firefox and Safari show similar messages. Nobody sees your content, nobody fills your form, and every rupee spent sending traffic to that URL is gone.
Why a redirect loop matters for revenue
A redirect loop is not a cosmetic bug. It takes a page fully offline for every visitor and crawler it affects, and it usually hits the pages you redirected on purpose: your homepage after an HTTPS switch, a migrated product page, or a landing page you just moved.
On the organic side, Google’s crawlers follow up to 10 redirect hops by default. A loop never resolves, so Google cannot index the page. In Search Console’s Page indexing report, these URLs show up under “Redirect error,” which Google defines as a redirect loop, a redirect chain that was too long, a redirect URL that exceeded the maximum URL length, or a bad or empty URL in the chain. A page Google cannot index cannot rank, and cannot be cited by AI Overviews either.
On the paid side, Google Ads lists a redirect loop as a “Destination not working” error, and ads with broken destinations are disapproved until the page is fixed. Google’s policy says its crawler stops following the loop and returns an error. The costlier scenario is a loop that only some users hit (a stale cookie, a mobile-only rule, a consent banner, a location redirect). The ad stays live, Google’s crawler sees a working page, and a share of your paid clicks land on an error screen.
Redirect loop vs redirect chain
| Attribute | Redirect loop | Redirect chain |
|---|---|---|
| What happens | Redirects circle back to an earlier URL and never end | Several redirects in a row that do end at a final page |
| Example | A to B to A | A to B to C (C loads) |
| Visitor experience | Error page, no content | Page loads, but slower |
| Google indexing | Page cannot be indexed | Indexed if under 10 hops; risk grows with each hop |
| Google Ads impact | “Destination not working” disapproval | Usually approved, but adds load time and tracking risk |
| Urgency | Fix today | Clean up in your next technical audit |
How to find and fix a redirect loop
The fix for any redirect loop is the same: trace every hop, find the two rules fighting each other, and replace them with one direct 301 redirect to the final URL. Here is the process we follow.
- Confirm it is the site, not your browser. Open the URL in an incognito window and on mobile data. If it loads in incognito, a stale cookie is the likely cause (clear that site’s cookies). If it fails everywhere, the problem is on the server.
- Trace the redirect path. Run
curl -sIL https://yourdomain.com/page/in a terminal and read theHTTPstatus andlocationlines, or use a browser extension such as Redirect Path or a crawler such as Screaming Frog. You will see the exact URLs repeating. - Check the usual WordPress suspects. In Settings, General, make sure “WordPress Address (URL)” and “Site Address (URL)” match exactly (same https, same www or non-www). Check
WP_HOMEandWP_SITEURLin wp-config.php if they are set there. - Check your CDN SSL mode. On Cloudflare, Flexible SSL plus a server that forces HTTPS is one of the most common causes: Cloudflare requests the page over HTTP, the server redirects to HTTPS, and the cycle repeats. Cloudflare recommends switching to Full or Full (strict) mode, or removing the HTTPS redirect at the origin.
- Audit every place a redirect can live. Redirect plugins (Redirection, Rank Math, Yoast Premium), the .htaccess file, your host’s control panel, CDN redirect rules and Page Rules. Two of these disagreeing is the classic loop.
- Collapse to one hop. Point the old URL straight to the final URL with a single 301. Delete the conflicting rule rather than adding another one on top.
- Clear caches and retest. Purge your caching plugin, server cache and CDN cache, then rerun the trace. Then click “Validate fix” in Search Console and request a re-review of any disapproved ads.
Worked example: what a partial loop costs
This is an illustrative scenario, not client data. Say a Mumbai D2C brand spends ₹40,000 a day on Google Search at a ₹25 average cost per click, which buys about 1,600 clicks a day. A new mobile redirect rule conflicts with the cookie consent plugin, and mobile visitors (say 60% of clicks) hit a redirect loop. Google’s desktop crawl sees a working page, so the ads stay live.
- Clicks wasted per day: 1,600 x 0.60 = 960
- Spend wasted per day: 960 x ₹25 = ₹24,000
- Caught after a 3-day weekend: ₹24,000 x 3 = ₹72,000 spent on error screens
The number that matters is not the CPC. It is how long the loop runs before anyone notices, which is why a quick mobile and incognito check after every redirect change is worth more than any bid tweak.
Common mistakes
- Stacking a new redirect on top of an old one. When a page moves twice, teams add B to C without updating A to B. Over time, someone adds C back to A. Always update old rules to point to the final URL.
- Forcing HTTPS in two places. Turning on HTTPS redirects in a plugin, in .htaccess and at the CDN at the same time invites conflict. Pick one layer to own HTTPS and www enforcement.
- Testing only on desktop while logged in. Many loops only affect logged-out, first-time or mobile visitors, which is exactly who your ads reach. Test the way a new visitor arrives.
- Treating the browser error as a browser problem. Telling users to “clear cookies” fixes nothing if the server is misconfigured. If the loop appears in incognito, fix it on the site.
- Forgetting the ad account after the fix. Fixing the page does not automatically restore disapproved ads quickly. Request a re-review in Google Ads so spend resumes.
Frequently asked questions
What causes a redirect loop on a WordPress site?
The most common causes are a mismatch between the WordPress Address and Site Address settings, conflicting rules between a redirect plugin and the .htaccess file, and Cloudflare’s Flexible SSL mode combined with a server that forces HTTPS. Stale cookies can also cause a loop for individual visitors.
Does a redirect loop hurt SEO?
Yes. Google cannot reach the final page, so the affected URL cannot be indexed and appears as a “Redirect error” in Search Console’s Page indexing report. If the loop hits an important page, that page drops out of search results until the loop is fixed and Google recrawls it.
Will Google Ads disapprove an ad because of a redirect loop?
Yes. Google Ads treats a server that redirects too often, causing a redirect loop, as a “Destination not working” problem, and ads with broken destinations are disapproved. After fixing the loop, request a re-review or edit the ad so it can serve again.
How do I check if my site has a redirect loop?
Open the page in an incognito window and on mobile data. For proof, trace the hops with a command like curl -sIL followed by the URL, a browser extension such as Redirect Path, or a site crawler like Screaming Frog, and look for a URL that appears more than once.
Is a redirect loop the same as a redirect chain?
No. A redirect chain is several redirects in a row that eventually reach a working page, while a redirect loop never reaches a final page because it circles back to an earlier URL. A chain slows the page down; a loop takes it offline.
How Uginix helps
Every Uginix account audit checks the redirect path of every live ad destination on desktop and mobile, logged out, before we touch bids or creative, because there is no point optimising traffic that lands on an error. If your landing pages have moved recently or your Google Ads account has “Destination not working” warnings, ask for a free growth audit, no lock-in, no pitch deck. For the full pre-launch list, see our landing page checklist or explore our performance marketing services.
Related terms
- Redirect chain: a series of redirects that eventually reaches a working page, adding load time with each hop.
- 301 redirect: a permanent redirect that tells browsers and search engines a page has moved for good.
- Crawl budget: the number of URLs a search engine will crawl on your site in a given period.
- Canonical URL: the preferred version of a page you tell search engines to index when duplicates exist.
- Landing page: the page a visitor reaches after clicking an ad, built to turn that click into a lead or sale.
Sources: Google Ads Help, About auto-tagging, Measure School, UTM parameters in GA4, Optimize Smart, GA4 UTM parameters not working, Infinity Group, UTM tagging in GA4.