Redirect Checker

What this redirect checker does

Paste a URL and the tool requests it the way a browser would, following every redirect for up to 10 hops. For each step you see the HTTP status code (301, 302, 307, 308, or a final 200, 404, 500…), the address it points to and how long the server took to answer. The bulk redirect checker does the same for up to 50 URLs at once, so you can audit an old sitemap, a list of backlinks or the result of a site migration and download the table as CSV.

Requests are sent from Cloudflare's network without cookies or cached redirects, so you see what a first-time visitor or a search engine crawler sees.

301, 302, 307 and 308: what the redirect status codes mean

301 Moved Permanently

The classic permanent redirect. Search engines transfer ranking signals to the new URL and update their index. Use it for moved pages, domain changes and the switch from HTTP to HTTPS.

302 Found

A temporary redirect. Search engines usually keep the old URL in the index, and if a “temporary” redirect stays in place for a long time they may start treating it as permanent. Use it for short-lived situations such as A/B tests or maintenance pages; for permanent moves prefer 301.

307 Temporary Redirect

Like 302, but the browser must repeat the request with the same method (a POST stays a POST). Also temporary.

308 Permanent Redirect

Like 301, but method-preserving. Search engines treat it as permanent. Some older tools handle it less reliably, so 301 remains the safe default for normal web pages.

Meta refresh and JavaScript redirects are not HTTP redirects: they live inside the page body and are slower and less reliable for crawlers. This tool reports HTTP redirects only.

Redirect chain checker: why chains hurt SEO

A redirect chain is a sequence of two or more redirects between the requested URL and the final page, for example http → https → www → trailing slash. Chains usually appear when migrations are layered on top of each other: a move to HTTPS, then a new domain, then a new URL structure, each adding its own rule.

• Slower pages. Every hop is a full round trip to the server, so users wait longer and Core Web Vitals suffer.
• Crawl waste. Googlebot follows up to 10 hops and may postpone long chains; other crawlers stop earlier.
• Diluted signals. Each hop is another place for a mistake, and a mix of 301 and 302 makes the intended destination ambiguous.
• Loops break pages completely. If a chain returns to an earlier URL, browsers show an error and the page drops out of the index.

How to fix redirect chains and loops

1. Check the chain with this tool and note the final URL that returns 200.
2. Update the first redirect rule so it points directly at that final URL. Repeat for every intermediate URL that still receives traffic or links.
3. Use 301 for permanent moves: check for 301 redirects on every moved URL and replace 302 and 307 unless the redirect is genuinely temporary.
4. Fix internal links, XML sitemaps and canonical tags so they reference the final URL directly and no redirect is needed at all.
5. Re-check in bulk after deploying. Keep old redirects live for at least a year: backlinks and bookmarks keep using them.

Bulk redirect checker for migrations and audits

Checking URLs one by one does not scale. The bulk URL redirect checker does it in one go: switch to the bulk tab, paste up to 50 URLs and get a table with the number of hops, the final status and warnings for each one. Export it as CSV to share with developers or attach to an audit.

Redirect mapping for site migrations is the classic case: after a domain change, paste the old URLs and confirm that every one lands on its new counterpart in a single hop. Other typical uses: checking that old URLs from Search Console or your backlink profile still land on live pages, and spotting pages that return 404 after a CMS update.