Skip to content
Raptor home
Menu

Redirect loop

response_codes.internal_redirect_loop
Priority
Fix now
Severity
Critical

What we look for

Raptor followed the redirects (rules that forward one address to another) from these addresses and came back to an address it had already passed through.

Why it matters

Search engines stop following a loop, so the page these addresses should lead to cannot be reached or listed through them.

How to fix

Correct the redirect rules in your server, CDN or CMS settings so each address forwards once, straight to a page that loads. Then point links at that final address.

What it cannot know

Raptor sends no cookies, as most search engine crawlers do not. A loop that a browser escapes with a cookie still shows here.

Seen in a real crawl

From a crawl of Millbrook Hardware (the broken fixture), a test site from Raptor’s fixture suite.

Fix now

1 address redirects in a loop

  • /loop-aRedirect chain loops back to the same URL: /loop-a -> /loop-b -> /loop-a -> /loop-b -> /loop-a -> /loop-b
Paths on http://127.0.0.1:8001raptor 0.3.0, 17 Oct 2026

Open this finding in that crawl’s report

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: response_codes.internal_redirect_loop
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "response_codes.internal_redirect_loop"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=response_codes.internal_redirect_loop
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "response_codes.internal_redirect_loop"
}