Groew / Learning Hub / What Is a Redirect Loop?

SEO Technical Updated recently 13 minutes

What Is a Redirect Loop?

A redirect loop happens when one URL sends the browser to another URL and that page sends the browser back again, or into another circle. The route never reaches a stable final page.

Simple answer: A redirect loop is a broken route that keeps bouncing between URLs. Fix the rule that sends traffic back into the circle.

What you will learn

What a redirect loop is
How loops happen
Why loops break crawling and trust
How to find the bad hop
How to stop the loop quickly

Time to read13 minutes

Tool mentionedSEO Audit Tool

Key takeawayA redirect loop traps the browser between URLs. The route never settles on a final page, so users and crawlers waste time.

Plain meaning: this lesson connects the beginner definition to the business system Groew builds around it.

A loop means the route never finishes

A redirect loop is not just a long path. It is a path that keeps circling without landing on a stable final page. The browser asks for one URL, gets redirected, and then gets redirected again back into the same problem.

That can happen with server rules, canonical confusion, script redirects or a mix of old and new route rules.

For the user, the result feels broken. For the crawler, it wastes time and can stop useful discovery.

RequestThe browser asks for a page

RedirectThe browser is sent elsewhere

LoopThe browser circles back

Loops usually come from two pages disagreeing about ownership

The common cause is simple. Page A sends to Page B and Page B sends back to Page A. Another pattern is a longer circle where several pages keep passing the request around until nothing resolves.

This can also happen when a redirect rule and a canonical signal disagree, or when a script redirect meets a server rule that points back the other way.

The loop is a symptom of route disagreement. The fix is to find the disagreement and remove it.

Drag sideways to see more columns

Pattern	Loop risk	What it means
A to B to A	High	Two pages disagree
A to B to C to A	High	A longer circle exists
Redirect plus canonical mismatch	Medium	Signals fight each other
Script plus server conflict	Medium	Different layers send different answers

Loops waste crawl time and make route ownership unclear

Google Search Central treats redirects as part of site move work. If the route never resolves, the move work fails. The crawler can spend time following the loop instead of finding the page that should be indexed.

That makes loops especially dangerous during redesigns and migrations. The team thinks the route is live, but the crawler cannot settle on a final answer.

A stable final URL matters more than a clever route path.

Find the first bad hop and test the full circle

The fastest way to diagnose a loop is to start at the first URL and follow the chain step by step. When the browser comes back to a page it already saw, the loop is found.

Then check the server rules, internal links, canonical tags and any script redirects that could be sending traffic in circles. The first bad hop is usually where the fix belongs.

Once the bad hop is removed, retest until one clean destination remains.

The common mistake is fixing only one side of the circle

Teams sometimes change one redirect rule and assume the loop is gone. If another rule still points back into the circle, the problem stays alive. Every side of the route has to agree.

Another mistake is leaving old internal links or a stale sitemap entry in place after the redirect is changed. Those old references can drag the site back into the loop.

The fix must include the rule, the links and the final URL.

Loops destroy trust because they turn a useful path into a dead end

A redirect loop blocks owned demand from reaching the page that should receive it. That hurts user trust, wastes crawler effort and makes migration recovery slower.

Groew treats loop cleanup as Revenue Infrastructure because a business cannot compound on routes that keep trapping visitors. The route has to land somewhere stable.

The real goal is not only to break the circle. The goal is to make the route easy to govern the next time the site changes.

Research and expert notes

Use these notes to understand how current search updates, AI answer surfaces and audit platforms change the way this topic should be checked.

Loops are a route failure, not a content problem The page cannot settle on one destination, so the route itself has to change.

Find the first bad hop The fastest fix usually starts at the first redirect rule that sends the browser back.

Signals have to agree Redirects, canonicals, internal links and sitemaps should all point to one answer.

Stop the circle, then simplify After the loop is removed, clean up the supporting signals so the issue does not return.

Search standards to keep in mind

Use these rules as guardrails before changing page structure, links or crawl settings. They keep the lesson connected to current search standards instead of one off tactics.

Help first, ranking secondGoogle continues to reward people first content. Start with direct answers, then add depth, proof and clear navigation paths.

No scaled low value publishingAvoid mass output without original value. Add unique expertise, examples, and practical judgment on every page.

Use snippet controls carefullynosnippet and max-snippet can limit visibility in search features and AI surfaces. Restrict only when there is a real legal or business reason.

Protect crawl and index clarityKeep important pages crawlable, internally linked and mapped. If systems cannot reach or understand pages, quality alone will not help.

Design for answer extractionUse clear headings, concise first answers, structured tables and explicit terms so engines and models can retrieve meaning correctly.

Google redirects and Search W3C Use standard redirects MDN 307 Temporary Redirect RFC 9110 HTTP Semantics

Alokk's perspective

Alokk Founder and Lead Growth Architect, Groew

Redirect loops are one of the clearest signs that the site lost route discipline. The browser is being sent in circles because two or more signals disagree about ownership. In one recovery, the site had more than 200 technical errors before the foundation was repaired and the decline stopped within 90 days. That is why loops should be treated as a priority fix, not a cosmetic issue.

Questions about What Is a Redirect Loop?

It is when URLs keep sending the browser in circles.

It wastes crawl time and keeps the page from settling on one final URL.

Usually two or more rules disagree about where the page should go.

Find the first bad hop and remove the rule that sends the browser back into the circle.

Yes. Old links can help keep the bad route alive.

From Groew's Search Authority Team

The Complete Beginner Guide to What Is a Redirect Loop

This guide turns the lesson into practical business judgment. Use it to understand the concept, avoid the common mistake and connect the idea back to Revenue Infrastructure.

Start With The Circle, Not The Symptom

A redirect loop is a route problem that repeats itself. The browser keeps going because no final page takes ownership. The first job is to see the loop as a circle, not as a random error. Once the pattern is obvious, the team can follow the path and find the first place where it starts to send traffic back the wrong way. That first bad hop is usually where the fix belongs.

Read the complete guide

Trace The Full Route Once

Do not guess. Follow the URL hop by hop until the browser returns to a page it already saw or hits a dead end. Write down each hop, because loops are often easier to solve when the route is visible on paper or in a sheet. If there is a server redirect, a script redirect and a canonical mismatch all in one path, the route can be more confusing than it first looked. A clean trace shows where the circle begins.

Check Every Layer That Can Redirect

The loop may live in server rules, page scripts, old maintenance pages or a mix of all three. If a canonical tag points one way and a redirect rule points another way, the site can keep creating confusion even after one fix. The browser only needs one stable destination. Everything else should support that destination instead of competing with it.

Remove The Old Signal, Not Only The New One

Fixing a loop usually means deleting or changing one old rule, but the job is not finished until the rest of the site stops pointing to the bad path. Internal links, navigation, sitemaps and any cached references should all be updated. If one old reference remains, the loop can come back later. That is why loop cleanup needs a full sweep, not a narrow patch.

Test The Route Again After The Fix

After the bad hop is removed, run the route again. The old URL should land on one final page without bouncing back into the circle. If it still loops, another rule is still active. Keep testing until there is one clean landing point. Verification matters because redirect loops can hide behind small config differences that are easy to miss during a rushed launch.

Protect Future Changes With A Route Check

Once the loop is fixed, put the route into a simple review habit. Redesigns, CMS changes and content merges are the moments when loops reappear. A short check of redirects, canonicals and internal links before launch can prevent the next circle. That kind of prevention is part of Revenue Infrastructure because the business owns the route only if it can keep it stable over time.

Turn The Fix Into A Clear Ownership Map

After the loop is gone, document who owns the redirect rule, who owns the canonical tag and who owns the page list. Route problems recur when ownership is vague. A simple ownership map keeps the site readable and makes the next migration less risky. Groew treats that discipline as infrastructure because the business cannot grow on paths that keep turning back on themselves.

Connect This To Revenue Infrastructure

This topic matters because growth should compound, not reset. Groew connects this lesson to technical SEO foundation so the business owns more of the system that creates revenue.

Where this connects next

Use these links after the core lesson is clear. Each route takes the internal linking idea into a file, tool, service or next decision.

Use this when you want the broader redirect map first. What Are Redirects?

Use this when you need to understand the extra hop problem first. What Is a Redirect Chain?

Use this when the page should be the only canonical version. What Is a Canonical URL?

Use this when the route sits inside a wider technical review. What Is Technical SEO?

Use this when old URLs still need a clean destination. What Is a 301 Redirect?

Use this when a page needs a temporary notice instead of a broken path. What Is a Maintenance Page?

Do this next: Use the SEO Audit Tool, then continue to What Is a Redirect Chain?.

Continue learning

Learn the next topic here.

These lessons continue the same business problem from a different angle. Use them to move from one definition to a working acquisition system.

What Is a Redirect Chain? Continue with the next connected lesson in this learning path. Your Learning What Is SEO? Start with the plain meaning of Search Engine Optimization before going deeper. Your Learning What Is an SEO Audit? A useful SEO audit finds the constraint that blocks search growth and puts fixes in the right order. Your Learning

Explore More Topics

Related insights

Read the deeper Groew analysis.

These insights connect the lesson to search visibility, AI answers, and Revenue Infrastructure decisions.

Why B2B Companies Are Losing Organic Traffic Use this when looped routes are part of a larger traffic decline. Read My Related Insight How Long Does SEO Take For A B2B Website Use this when you need recovery timing after route fixes. Read My Related Insight The B2B Content Audit For 2026 Use this when the page should be kept, fixed or removed. Read My Related Insight

Explore More Insights

Check what this means for my business.

Use Groew's free tool to turn this lesson into a practical next step for your website, ads or acquisition system.

Run My Free Check