Technical SEO

Redirect Checker

Enter a URL to trace every redirect between it and the final page: the HTTP status code of each hop (301, 302, 307, 308…), where it points and how long it took. The checker follows up to 10 redirects — the same limit Googlebot uses — and flags redirect chains, loops, temporary redirects on permanent moves, and redirects that end on a 404 or a server error.

Leave the box ticked to also check the http, https, www and non-www versions of the address — and see whether all four end on the same page.

FreeNo signupChecks the live pageUpdated October 2026

Redirect Checker

Our server fetches the public page you name and keeps no copy of it.

Also check http / https and www variants

HTTP status codes and what they mean for SEO

200OK: The page loads normally. Every URL you link to should end here.
301Moved Permanently: Moved for good. Search engines index the new URL and pass the old one's signals to it.
302Found: Moved for now. Search engines may keep the original URL in the index.
303See Other: Temporary redirect, normally after a form is submitted. Not meant for pages that moved.
304Not Modified: Unchanged since the last visit, so the stored copy is reused. Valid only as an answer to a conditional request.
307Temporary Redirect: Temporary redirect that keeps the request method. Same SEO meaning as 302.
308Permanent Redirect: Permanent redirect that keeps the request method. Same SEO meaning as 301.
400Bad Request: The server rejected the request as malformed. There is nothing to index.
401Unauthorized: Login required. Crawlers cannot see the page, so it stays out of the index.
403Forbidden: Access denied, often by a firewall or bot protection. If crawlers get it, the page drops out of the index.
404Not Found: The page does not exist. Fine for a deleted page, but links and redirects should never lead to one.
410Gone: Removed on purpose. Google handles it like a 404: the URL drops out of the index.
429Too Many Requests: Too many requests. Google treats it like a server error and slows down crawling.
451Unavailable For Legal Reasons: Blocked for legal reasons, often by region. If crawlers get it, the page cannot be indexed.
500Internal Server Error: The server failed. Google slows down crawling and drops the URL if the error persists.
502Bad Gateway: A proxy or CDN got no valid answer from the origin server. Treated like any other 5xx.
503Service Unavailable: Temporarily unavailable. Right for short maintenance, since crawlers come back later; if it lasts for days, pages start dropping out.
504Gateway Timeout: A proxy or CDN timed out waiting for the origin server. Treated like any other 5xx.

How it works

How to check a redirect

01
Paste the URL
Use the old address — the one people and links still use. Without a scheme, https:// is assumed; type http:// to test the insecure version.
02
Read the chain
Each card is one response: the URL, its status code and how long it took. Between the cards you see what each redirect changed — http to https, www, a trailing slash or a whole new path.
03
Fix what is flagged
Loops, chains, temporary codes and broken targets each come with the fix. The versions list shows whether http, https, www and non-www all end on one final URL.
04
Update your links
Once the redirects are clean, point internal links, canonical tags and the sitemap straight at the final URL, so nobody has to take the detour.

Honest notes

What this checker does and does not do

It follows server-side redirects only: 3xx responses with a Location header. JavaScript redirects (window.location and the like) never show up as a 3xx, so they are not followed; a meta refresh on the final page is reported but not followed either.

Servers can answer differently depending on where a request comes from and what sends it — geo-redirects, separate mobile sites and bot protection all do this. The checks run from our server, so a redirect that only fires in some countries or on some devices may not appear, and the times show what each hop costs from there, not what a visitor elsewhere will see.

The checker identifies itself with its own user agent (SeonixFreeTools) — not as Googlebot or a browser — and sends plain GET requests without cookies. A site that treats unknown bots differently may answer it differently than it answers Google.

Our server requests the public URL you enter — and, with the box ticked, its http/https and www versions — returns the result and keeps no copy of the pages or the result.

Seonix does this on autopilot

Find every redirect problem on your site, not just on this URL

The free Seonix site audit crawls your whole site and flags redirect chains and loops, broken redirects, internal links that point at redirects, redirected URLs in your sitemap and a missing http-to-https redirect — alongside broken links and the rest of your technical SEO. On paid plans Seonix also researches, writes and publishes articles built to rank in Google and get cited in AI answers.

Analyze my site free

For your stack

SEO on autopilot for the site you have

Seonix researches, writes and publishes articles — and keeps the technical side in check — wherever your site lives.

WordPress sites

The free Seonix plugin connects in one click: articles publish as native posts, and SEO fixes and llms.txt are handled for you.

WordPress SEO automation

SaaS products

Your AI coding agent connects your app to Seonix from one prompt; keyword-backed articles then publish to your own domain on schedule.

SaaS SEO on autopilot

Custom-built websites

No WordPress needed: your site exposes one small endpoint and articles arrive as native pages in your own design.

SEO for custom websites

Also onShopify Webflow Wix Ghost

Frequently asked questions

What is the difference between a 301 and a 302 redirect?

A 301 says the page has moved permanently: search engines treat the new URL as the one to index and pass the old URL's signals to it, and browsers remember the redirect. A 302 says the move is temporary, so the original URL can stay in the index. Use 301 — or 308 — for anything permanent: migrations, changed slugs, http to https. Google may eventually treat a long-standing 302 as permanent, but a 301 says so from day one. 307 and 308 are the versions of 302 and 301 that keep the request method.

How many redirects are too many?

Aim for none between your own links and your pages, and at most one when a URL has moved. Googlebot follows up to 10 redirect hops and reports a redirect error beyond that; browsers give up at around 20. Long before those limits, every hop costs another round trip — often hundreds of milliseconds on mobile — and makes crawlers spend requests on detours, so collapse chains into a single redirect to the final URL.

Do redirects lose link equity?

Not by themselves, as far as Google is concerned: it has said that 3xx redirects do not lose PageRank, so the old rule that every redirect leaks part of a link's value no longer applies. What does lose value is a chain long enough that crawlers stop following it; a redirect to an unrelated page — sending every removed URL to the homepage is often treated as a soft 404; and a temporary redirect on a permanent move, which can leave the old URL in the index instead of the new one. One permanent hop to the closest matching page keeps the signals intact.

What is a redirect chain?

A redirect chain is a URL that redirects to another URL that redirects again before the real page loads — for example http://example.com → https://example.com → https://www.example.com/. Chains usually build up over years: an https migration, a switch to www and a few renamed pages stacked on top of each other. Fix them by redirecting every old URL straight to the final one and by updating internal links to point at the final URL.

How do I check where a URL redirects, or a page's status code?

Paste the URL into the checker above: it lists every hop with its status code, the Location it points to and the time it took, ending with the final page's status. In a browser, open developer tools, tick Preserve log on the Network tab and load the URL — each redirect shows up as its own 3xx request. From a terminal, curl -sIL https://example.com prints the status line and the Location header of every hop.

Free tools