SEO Redirect Checker
Redirects keep old links working, but every extra hop costs time and crawl budget, and the wrong type sends the wrong signal. Paste up to 20 URLs and the checker follows each redirect to the end, showing every hop with its status code. It flags chains of more than one hop, 302 and 307 redirects used for permanent moves, loops, redirects from HTTPS back to HTTP and chains that end in an error. It can also test the four http/https and www/non-www versions of your domain.
- Encrypted connection
- No sign-up
- Free to use
How to use SEO Redirect Checker
- Paste one or more URLs, one per line.
- Keep the variant test on to check the host versions.
- Click “Check redirects”.
- Point links and redirects straight at the final URL.
SEO Redirect Checker features
Bulk check
Up to 20 URLs at once.
Full chains
Every hop and status code.
Clear findings
Chains, loops and temporary redirects.
Host variants
http, https, www and non-www.
GET requests
Results match what browsers see.
Safe fetching
Only public http(s) addresses; private networks are blocked.
When to use SEO Redirect Checker
- Checking redirects after a site migration.
- Cleaning up old marketing links.
- Verifying the preferred domain is enforced.
- Finding loops reported by users or crawlers.
SEO Redirect Checker FAQ
301 or 302 – which should I use?
Use 301 or 308 when a page has moved permanently; search engines then transfer signals to the new URL. Use 302 or 307 only for genuinely temporary moves.
How many redirects are too many?
Google follows up to about ten hops, but one is ideal. Each hop adds latency for visitors, especially on mobile.
Why test www and http versions?
If several versions of your home page answer without redirecting to one preferred address, links and signals are split between duplicates.
How is the page fetched?
Our server downloads the page once through a guarded fetcher: only public http and https addresses, a limited number of redirects, a size cap of 2 MB and a short timeout. The HTML is then analysed in your browser; scripts on the page are never run.
Redirects and SEO
A redirect tells browsers and search engines that content has moved. Permanent redirects consolidate signals onto the new address, which is why they are the standard tool for migrations, merged pages and changed slugs.
Problems appear when redirects pile up over the years: a page moved twice becomes a chain, a CMS rule and a server rule may bounce a URL back and forth, and an old HTTP rule can send visitors from HTTPS to HTTP. The checker makes these visible in one table so you can fix them at the source.
For a detailed look at the headers of a single hop, use the HTTP Redirect Checker.
Results reflect the page at the moment of the check. Pages that serve different content to different visitors, countries or devices may show different results in a crawler; when in doubt, compare with the URL Inspection tool in Google Search Console, which shows what Google itself fetched.
Privacy: the address you enter is fetched by our server only to run this check. The downloaded HTML is passed to your browser for analysis and is not stored, and the results are not saved on our side. Requests are rate-limited to keep the service fair for everyone, so if you check many pages in a row you may need to wait a few minutes.
Limits: pages are read up to 2 MB of HTML, redirects are followed up to eight hops and each request has a short timeout. Very large pages, servers that block automated requests or pages behind a login cannot be analysed this way; for those, open the page in your browser, copy the page source and use the paste option where it is available.