Response handling
Free Redirect Checker
Check up to 20 URLs at once. See each HTTP redirect, status code and final destination, with warnings for loops and long chains. No account required.
Checks run on our server against public HTTP and HTTPS URLs on ports 80 and 443. Enter URLs you can share with this service; JavaScript and meta refresh redirects are not followed.
How to Check a URL Redirect
- Paste the original URL, including
http://orhttps://. Add up to 20 URLs on separate lines. - Select Check redirects. Each result lists the responses in order and the last URL reached.
- For a permanent move, check that the old URL reaches its intended replacement through a 301 or 308, and that the replacement returns 200.
A 200 response confirms an HTTP response, not that a page is indexed or useful. Open the final page to confirm its content, then check its canonical and indexing status separately.
A Real Redirect Example From GIndexa
On September 29, 2026, our old redirect-checker URL returned a 301 to its new category URL, which returned 200. The sample button loads the old URL so you can check the current response yourself.
| Step | URL | Observed status | Meaning |
|---|---|---|---|
| 1 | https://gindexa.org/tools/redirect-checker/ | 301 | The old page has moved permanently. |
| 2 | https://gindexa.org/tools/seo/redirect-checker/ | 200 | The destination responds successfully. |
This is one redirect and two HTTP responses. Timings vary by network and server conditions; this check measures requests from our server, not a visitor's browser load time.
What Your Redirect Results Mean
- 301 or 308: permanent redirect
- Appropriate for a lasting URL change. Google uses a permanent redirect as a signal that the destination should be canonical.
- 302 or 307: temporary redirect
- Appropriate when the original URL should return. A temporary status is a prompt to check intent, not automatically an error.
- Several redirects before the final page
- Where you control the rules, point old URLs directly to the final replacement. Keep redirects that external links still rely on.
- A loop, timeout, 403 or 429
- A loop needs a rule change. A timeout or blocked response may be specific to this checking server; compare with your browser and server logs before changing the site.
- 404 or 410 at the destination
- Check whether the replacement is missing. If a removed page has no relevant replacement, a genuine 404 or 410 can be correct.
Use our HTTP redirect code guide for status-code decisions, or the canonical checker to examine the destination's canonical signal.
Do Redirect Chains Lose SEO Authority?
Google states that 301 and other permanent redirects do not cause a loss in PageRank. There is no fixed percentage of authority lost at every hop. Long chains still add request latency and complicate crawling, so redirect directly to the final page wherever possible.
For a measured example, our redirect migration case study compares search performance on the old and canonical hosts. A single case does not predict the outcome of every migration.
Check Redirects After a Site Migration
Start with the old URLs that have traffic or links. Match each to a relevant replacement, run them in batches, and compare the final destination with that map. Update internal links and the sitemap to the final URLs. Keep watching Google Search Console as Google revisits the old and new pages.
For implementation, follow how to create a URL redirect. For repeated hops or loops, use the too many redirects troubleshooting guide. Choose one place to own each rule, whether that is the server, CDN or application.
Redirect Checker Questions
Can I check several URLs at once?
Yes. Enter up to 20 unique URLs, one per line. Each URL gets its own result. Split a larger migration list into separate batches.
Does it detect JavaScript or HTML redirects?
No. It follows HTTP responses with a Location header. It does not execute scripts or follow meta refresh instructions. A page can return 200 here and still redirect a browser; use the HTML redirect guide to investigate that case.
Why does the result differ from my browser?
The check runs without your browser's login cookies or JavaScript. Location rules, bot protection and rate limits can also change the response. A blocked check alone does not prove that Googlebot is blocked.
Does a successful check mean Google has indexed the new URL?
No. This tool checks HTTP behavior. Use Google Search Console URL Inspection for Google's recorded indexing status and selected canonical.