Are your redirects short, correctly typed, and easy for AI crawlers to follow?
Short, properly typed redirect chains keep AI crawlers from giving up before they reach your real page.
What this signal tests
We check three things about redirects on your site. First, that each redirect resolves in two hops or fewer rather than chaining through multiple intermediate URLs. Second, that permanent moves use the correct status codes (301 or 308) and temporary moves use the right codes too (302 or 307). Third, that you are not using HTML meta-refresh tags as a substitute for proper server-side redirects.
Why it matters for your visibility in AI
AI search crawlers typically follow far fewer redirect hops than classic Googlebot. Where Google might follow up to ten hops, ChatGPT, Claude, and Perplexity crawlers often give up after two or three. If your old URLs go through long redirect chains - site move plus protocol change plus tracking redirect plus CMS slug change - your destination page is never reached and your historic backlinks deliver zero AI visibility. Incorrect status codes cause a different but related problem. Using a temporary 302 for a permanent move tells AI crawlers not to update their stored URLs, so they keep hitting the old address every time. Using meta-refresh confuses them entirely. The net effect is that your refreshed content gets less citation traffic than it should, and competitors with cleaner redirects keep their historic visibility intact.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| >=95% of sampled redirects <=2 hops and use 301/308 for permanent moves. |
How we test it
We pick a sample of redirecting URLs across your site and follow each one carefully, allowing up to five hops before declaring the chain too long. We record the status code at each step, flag any chain longer than two hops, flag any permanent move that uses a 302 status, and inspect destination HTML for meta http-equiv refresh tags that act as redirects.
Show technical detection method
Follow redirects with max=5 hops; flag chains >2; 302 used for permanent moves; meta http-equiv=refresh with delay 0.
If your site fails: how to fix it
- Audit your redirect rules. Most web servers and CDNs have a redirect rules file or dashboard - collect every rule into a single list and look for chains where rule A redirects to rule B which redirects again.
- Collapse chains by rewriting each rule to point directly at the final destination. For example, if /old goes to /middle which goes to /new, change /old to go straight to /new in one hop.
- Replace any 302 or 307 status used for permanent moves with 301 or 308. Most servers default to 302 when no status is specified explicitly - be deliberate about the code you set.
- Remove any HTML meta-refresh redirects you find. Replace them with server-side redirects at the web server or CDN level, which are faster and more universally followed.
- Re-run the AI Ready Test to confirm at least 95% of sampled redirects now resolve in two hops or fewer with the right status code.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | medium |
| Category | Crawlability |
Primary sources
Related signals
Frequently asked questions
What is the difference between 301 and 308?
Both signal a permanent redirect. 301 is the older standard; 308 is its modern equivalent that also preserves the HTTP method (important for non-GET requests). Either is acceptable for permanent moves. Use 301 for general web content; use 308 when redirecting API endpoints.
Why are long redirect chains a problem?
Every extra hop adds latency, increases the chance of a transient error, and gets closer to the crawler's hop limit. AI crawlers tend to be impatient - three hops is often the practical ceiling. Direct one-hop redirects always win on both speed and reliability.
Is meta-refresh ever acceptable?
Not as a redirect mechanism. Meta-refresh was a workaround from the early web before server-side redirects were widely accessible. Today every host and CDN supports proper 301/308 redirects; meta-refresh should be reserved for in-page user-facing notices like 'this page will reload in 5 seconds'.
Where do redirect chains usually come from?
Common causes: an old HTTP-to-HTTPS rule layered on top of a non-www-to-www rule layered on top of a CMS slug change. Each migration adds a hop and nobody collapses them. Periodically auditing and flattening the rule file is the cure.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.