Redirect chain monitoring follows your URL's redirect hops and alerts when chains are too long, end in errors, or form loops. Excessive redirects hurt Core Web Vitals and can drop pages from Google's index.
⚙️How it works
Uptrue follows redirects manually (not automatically), recording each hop's URL and status code. If the chain exceeds your configured maximum hops, or the final destination returns an error, an alert fires.
✓What Uptrue checks
- Full redirect chain (each hop URL and status)
- Total hop count
- Final destination status code
- Loop detection
⚠Alert conditions
- Chain exceeds maximum hop limit
- Final destination returns 4xx or 5xx
- Redirect loop detected
Why this matters
Google recommends fewer than 3 redirect hops for optimal crawling. Long chains increase page load time for every user. Broken chains cause 404s that accumulate link equity loss.
Set up in 60 seconds
Free plan · 3 monitors · No credit card required
?Frequently asked questions
What's the default maximum redirect hops?
5 hops. You can configure this per monitor.
Does it detect HTTP to HTTPS redirects?
Yes. Each redirect hop is recorded, so you'll see the full chain including HTTP→HTTPS transitions.
Related Monitor Types
🔗
Ready to set up Redirect Chain Monitoring?
Join teams who monitor their infrastructure with Uptrue. Free plan, no credit card required. Want to spot-check first? Run our free redirect chain checker.
Start Monitoring Free