Skip to content
Raptor home
Menu

Redirect chain

response_codes.internal_redirect_chain
Priority
Medium
Severity
Warning

What we look for

Each of these addresses forwards to another address that forwards again: two or more redirects (rules that send one address to another) before the final answer.

Why it matters

Each extra hop makes visitors wait longer and costs search engines another request. Very long chains may not be followed to the end.

How to fix

Point each redirect straight at the final address in your server, CDN or CMS settings. Then update links, and the sitemap (the file that lists your pages for search engines), to use the final address.

Seen in a real crawl

From a crawl of Fernhollow Outdoor, a test site built for this site’s demo.

Medium

1 address redirects more than once

  • /shop/sale.html2 hops: /shop/sale.html -> /sale -> /sale/
Paths on http://127.0.0.1:8006raptor 0.3.0, 17 Oct 2026

Open this finding in that crawl’s report

It also fired on Millbrook Hardware.

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_chain
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_chain"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=response_codes.internal_redirect_chain
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_chain"
}