What is a navigation loop?
A navigation loop is a user moving back and forth between the same small set of pages without progressing toward a goal. Loops mean the user is searching for something your navigation promises but does not deliver where they expect it.
A navigation loop is a user bouncing between the same pages: A to B, back to A, back to B, sometimes for minutes. Loops are the interface equivalent of watching someone walk the same hallway twice, checking the same doors.
A loop is not wandering. Wandering visits new pages. A loop revisits the same ones, which means the user believes the thing they want is in one of these places and cannot find it in either. The belief came from somewhere: a nav label, a link name, a heading that promised more than the page delivered.
What loops reveal
Loops are an information architecture signal more than a bug signal. Common causes:
- A label that lies. The page called "Settings" does not contain the setting. The user keeps returning because the label keeps insisting.
- Split content. The answer is half on one page and half on another, so the user shuttles between them assembling it.
- A missing page. The thing they want does not exist, and two pages each gesture toward it. Loops between a pricing page and a features page often mean a specific question, like a limit or a plan detail, is answered on neither.
- Back-button traps. A flow that re-enters itself, where leaving a step returns the user to the start of it.
The loop's pages tell you where the user looked. What they did on each page, the scrolling, the dead clicks, the hesitation, tells you what they were looking for.
How to detect navigation loops
The rule: repeated transitions between a small set of pages inside one session, beyond a threshold that separates a quick double-check from a search. As with every frustration signal, the count matters less than the aggregation. One person looping might be distracted. Forty sessions this week looping between the same two pages is a hole in your navigation with a location.
What to do about a loop
Find what the loopers wanted. The fastest way is to look at what the loop's sessions did next: the search they typed, the page they eventually landed on, the support message they sent, or the exit. Then either move the content to where the labels promise it is, fix the label, or build the missing page.
Loops respond well to small fixes because the user's intent is already strong. They wanted the answer badly enough to keep looking. Meet them where they already are. A free scan shows whether your site is producing loops today.