Check where a URL really goes. Paste one URL to see every redirect hop and status code, or upload a CSV of up to 1,000 URLs and get a spreadsheet back showing whether each one uses a 301, 302 or something worse, and whether it lands where your migration map says it should. It is free and one of my free SEO tools.
Follows up to 10 redirects, the same limit as Googlebot, including meta refresh redirects. Requests come from this site's server, so firewalls that verify real bot IPs may respond differently.
How Do You Use the Redirect Checker?
- Single URL: paste a URL and hit Check redirects. You get every hop with its status code, where it points, how long it took and, where the server says so, what created the redirect.
- Bulk check: switch to Bulk check, paste a list or upload a CSV or TXT file, and hit Check all. Up to 1,000 URLs per run.
- Migration map: put the expected destination in a second column. The checker tells you, row by row, whether each old URL lands on the right new one.
- Export: filter to the problems, then download a CSV or copy the table straight into Google Sheets or Excel.
Tip: every status code in the results links to its explanation further down this page.
How Do You Check Redirects After a Site Migration?
Take the redirect map you gave the developers: old URL in the first column, new URL in the second. Upload it as it is. A header row is fine, and so are commas, semicolons or tabs.
The checker traces every old URL and flags the problems that cost rankings after a migration:
- Wrong destination. The old URL ends somewhere other than the URL in your map.
- Not redirected. The old URL still returns its own page, or a 404.
- Temporary redirects. A 302 or 307 where you meant a permanent move.
- Chains. More than one hop, typically http to https to www to the new path. Each extra hop wastes crawl time.
- Redirects to the homepage. Google often treats a deep URL redirected to the homepage as a soft 404.
- Loops and dead ends. Redirects that circle back, run past 10 hops, or finish on a 4xx or 5xx.
In my experience, the map is rarely the problem. The implementation is. A rule written in the wrong order, a trailing slash added by the CMS, a CDN rule nobody remembered. Check the live behaviour, not the spreadsheet you handed over.
301 vs 302 vs 307 vs 308: Which Redirect Should You Use?
- 301 Moved Permanently for anything permanent: migrations, domain changes, merged or renamed pages. It is the default, and every system understands it.
- 308 Permanent Redirect when the request method must not change, for example an API endpoint that receives POST requests. Google treats it the same as a 301.
- 302 Found for genuinely temporary moves: a short promotion, a test, or sending visitors to a local version of a page.
- 307 Temporary Redirect for temporary moves where the method must not change. Search engines treat it like a 302.
Use permanent redirects for permanent changes. A temporary redirect tells Google to keep the old URL indexed, and that is the opposite of what you want after a migration.
How Does Google Handle Redirects?
Googlebot follows up to 10 redirect hops in a row. Past that, it gives up and the URL is reported as a redirect error in Search Console. This checker uses the same limit.
Permanent redirects (301 and 308) are a strong signal that the destination should be indexed in place of the old URL. Temporary redirects (302, 303 and 307) are a weak signal, so Google usually keeps the original indexed, though it may treat a long-standing 302 as permanent.
Google also follows instant meta refresh redirects and JavaScript redirects, but it treats a delayed meta refresh as temporary and has to render the page before it sees a JavaScript redirect. Server-side redirects are faster and more reliable, which is why this checker flags the other kinds.
Every HTTP Status Code Explained
Every status code you are likely to meet, official and unofficial, explained on one page. Jump to a group:
- 1xx Informational Status Codes
- 2xx Success Status Codes
- 3xx Redirection Status Codes
- 4xx Client Error Status Codes
- 5xx Server Error Status Codes
- Unofficial and Vendor Status Codes
1xx Informational Status Codes
Interim responses sent before the final answer. You will almost never see them in a browser or a redirect trace, because the client and server deal with them on their own.
100 Continue
The server has received the request headers and the client can send the body. Clients use it with the Expect: 100-continue header before large uploads.
101 Switching Protocols
The server agrees to change protocol at the client’s request, most often to open a WebSocket connection.
102 Processing (WebDAV)
The server has accepted a long WebDAV request and is still working on it, so the client should not time out. It is deprecated in current specifications.
103 Early Hints
Sent before the final response with Link headers, so the browser can start loading CSS, fonts or scripts while the server is still building the page. For SEO: It can improve page speed, and it has no effect on indexing.
2xx Success Status Codes
The request was received, understood and accepted. For SEO, the only one that matters is 200: every page you want indexed should end on it.
200 OK
The request worked and the content is in the response. This is what a healthy page returns. For SEO: Every page you want indexed should end on a 200. A 200 on a page that says the content is missing is a soft 404, and Google treats it like one.
201 Created
A new resource was created, usually after a POST to an API. The Location header points to it.
202 Accepted
The request was accepted but has not been processed yet, typical of queued jobs and batch APIs.
203 Non-Authoritative Information
The response is a modified copy from a proxy or transforming service rather than the original server.
204 No Content
The request worked and there is deliberately no body. Common for API calls, form autosaves and tracking pixels. For SEO: There is nothing to index, so a page URL returning 204 is treated as empty.
205 Reset Content
The request worked and the client should reset the form or view that sent it.
206 Partial Content
The server is sending only the byte range the client asked for, which is how video streaming and resumable downloads work.
207 Multi-Status (WebDAV)
The body holds separate status codes for several operations in one request.
208 Already Reported (WebDAV)
Members of a collection were already listed earlier in the same response, so they are not repeated.
226 IM Used (HTTP delta encoding)
The server returned the result of changes applied to the resource, such as a delta, rather than the whole thing.
3xx Redirection Status Codes
The client has to take another step to complete the request, usually by following the URL in the Location header. Not every 3xx is a redirect: 304 is about caching.
300 Multiple Choices
More than one version of the resource exists and the client should choose one. Browsers do not pick automatically, so it is rarely used. For SEO: Avoid it. Use a single redirect, or hreflang for language versions.
301 Moved Permanently
The resource has moved for good to the URL in the Location header. Browsers cache it hard, and clients may switch a POST to a GET when they follow it. For SEO: The standard redirect for migrations, domain changes and merged pages. Google treats it as a strong signal to index the destination and passes ranking signals through.
302 Found
The resource is temporarily at another URL, and the client should keep using the original. Like 301, clients may switch a POST to a GET. For SEO: Google keeps the original URL indexed while the redirect looks temporary, but may treat a long-lived 302 as permanent. Use it for short-term moves, tests and geo or language routing, and a 301 or 308 for anything permanent.
303 See Other
Tells the client to fetch a different URL with GET, most often after a form submission so a refresh does not resubmit it. For SEO: Google treats it as a temporary redirect.
304 Not Modified
The copy the client already has is still current, so no body is sent. It answers conditional requests that use If-Modified-Since or If-None-Match. For SEO: Not a redirect. Googlebot sends conditional requests, and a correct 304 saves crawl capacity on large sites.
305 Use Proxy (Deprecated)
Told the client to access the resource through a proxy. Browsers ignore it for security reasons.
306 Unused (Reserved)
Reserved. It was Switch Proxy in an early draft and is no longer used.
307 Temporary Redirect
Like 302, but the client must repeat the request with the same method and body. Browser developer tools also show an internal 307 when HSTS upgrades http to https before any request is sent. For SEO: Treated the same as 302. If you see a 307 for http to https in your browser but not here, that is HSTS in the browser, not your server.
308 Permanent Redirect
Like 301, but the method and body must not change when the client follows it. For SEO: Google treats 308 the same as 301, so it is safe for permanent moves.
4xx Client Error Status Codes
The request is wrong, unauthorised, or asks for something that does not exist. Google does not index pages that return a 4xx.
400 Bad Request
The server cannot process the request because it is malformed, for example invalid syntax, a broken header or an oversized cookie.
401 Unauthorized
Authentication is missing or wrong. The response includes a WWW-Authenticate header describing how to log in. For SEO: Google cannot index content behind a 401, which makes it the right way to protect a staging site.
402 Payment Required (Reserved)
Reserved for future use. Some APIs and paid services use it when a quota or subscription has run out.
403 Forbidden
The server understood the request and refuses it, and logging in will not help. For SEO: Google does not index 403 pages and drops them over time. A 403 for Googlebot but not for people usually means a firewall or bot rule is blocking crawlers.
404 Not Found
Nothing exists at this URL, or the server will not say whether it does. For SEO: Normal and harmless for pages that never existed or are gone for good. In a migration, important old URLs that return 404 lose their links and rankings, so redirect them.
405 Method Not Allowed
The URL exists but does not accept this method, for example a POST to a page that only allows GET. The Allow header lists the methods it accepts.
406 Not Acceptable
The server cannot produce a response that matches the Accept headers the client sent.
407 Proxy Authentication Required
Like 401, but the client has to authenticate with a proxy first.
408 Request Timeout
The server gave up waiting for the client to finish sending the request.
409 Conflict
The request clashes with the current state of the resource, such as two edits to the same record.
410 Gone
The resource was removed on purpose and will not come back. For SEO: Google treats 410 much like 404, but may drop the URL a little faster. Use it for content you removed deliberately with no replacement.
411 Length Required
The server needs a Content-Length header and the request did not include one.
412 Precondition Failed
A condition in the request headers, such as If-Match, was not met.
413 Content Too Large
The request body is bigger than the server allows. It was called Payload Too Large in older specifications.
414 URI Too Long
The URL is longer than the server will process, often caused by runaway parameters or a redirect that keeps appending to the URL.
415 Unsupported Media Type
The request body is in a format the server does not accept.
416 Range Not Satisfiable
The requested byte range falls outside the size of the file.
417 Expectation Failed
The server cannot meet the requirement in the request’s Expect header.
418 I’m a teapot (RFC 2324 joke)
An April Fools joke from 1998. Some sites return it to turn away bots and scrapers.
421 Misdirected Request
The request reached a server that cannot answer for that host name, often after an HTTP/2 connection was reused or a certificate did not match.
422 Unprocessable Content (WebDAV origin)
The request is well formed but the data fails validation. Common in APIs. It was called Unprocessable Entity in older specifications.
423 Locked (WebDAV)
The resource is locked and cannot be changed.
424 Failed Dependency (WebDAV)
The request failed because another request it depended on failed.
425 Too Early
The server will not process a request that could be replayed, used with TLS early data.
426 Upgrade Required
The client must switch to the protocol named in the Upgrade header.
428 Precondition Required
The server requires conditional requests to stop people overwriting each other’s changes.
429 Too Many Requests
The client has been rate limited. The Retry-After header says when to try again. For SEO: Google treats 429 like a server error and slows its crawling. If Googlebot gets 429s, your rate limits are too tight.
431 Request Header Fields Too Large
The request headers are too big, usually because of bloated cookies.
451 Unavailable For Legal Reasons
The content is blocked for legal reasons, such as a court order, censorship or a regulatory geo-block. The number is a nod to Fahrenheit 451. For SEO: Common in regulated sectors such as gambling. Google treats it as a 4xx in the market that receives it.
5xx Server Error Status Codes
The server failed to complete a valid request. Short blips are normal, but persistent 5xx responses make Google crawl less and eventually drop URLs.
500 Internal Server Error
A generic server failure, such as a crashed script, a fatal PHP error or a broken configuration. For SEO: Occasional 500s do no harm. Persistent ones make Google crawl less and eventually drop the affected URLs.
501 Not Implemented
The server does not support the method or feature the request needs.
502 Bad Gateway
A proxy, CDN or load balancer got an invalid response from the server behind it. For SEO: Treated like any 5xx. It usually means the origin server is down or overloaded.
503 Service Unavailable
The server cannot handle the request right now because of overload or maintenance. For SEO: The correct code for planned downtime, ideally with a Retry-After header. Google keeps pages indexed through a short outage, but they can drop if it lasts days.
504 Gateway Timeout
A proxy or CDN waited too long for the server behind it to respond.
505 HTTP Version Not Supported
The server does not support the HTTP version used in the request.
506 Variant Also Negotiates
A content negotiation misconfiguration on the server.
507 Insufficient Storage (WebDAV)
The server does not have the storage space to complete the request.
508 Loop Detected (WebDAV)
The server found an infinite loop while processing the request. Some shared hosts also return 508 when an account hits its resource limits.
510 Not Extended (Obsolete)
Further extensions to the request are required. It is now obsolete.
511 Network Authentication Required
The client must log in to the network first, as with hotel and airport Wi-Fi portals.
Unofficial and Vendor Status Codes
Not part of the HTTP standard, but you will meet them in server logs, CDN dashboards and redirect traces. Search engines treat them by their first digit, so a 52x from Cloudflare counts as a server error.
No Response (Connection Failed)
The connection failed before any status code came back, because of a DNS error, a refused connection, an SSL problem or a timeout. For SEO: If the server cannot be reached at all, Google treats it like a server error and will retry later.
419 Page Expired (Laravel)
A form’s CSRF token expired, usually because the page was left open too long.
420 Enhance Your Calm (Twitter, historical)
Used by the old Twitter API for rate limiting. Spring Framework once used 420 for a method failure.
440 Login Time-out (Microsoft IIS)
The user’s session has expired and they need to log in again.
444 No Response (nginx)
nginx closes the connection without sending anything, a common way to drop bad bots. Most tools, this one included, see it as no response.
449 Retry With (Microsoft IIS)
The request should be retried after the client supplies missing information.
460 Client Closed Connection (AWS Elastic Load Balancing)
The client closed the connection before the load balancer’s idle timeout.
463 Too Many Forwarded IPs (AWS Elastic Load Balancing)
The X-Forwarded-For header contained more than 30 IP addresses.
494 Request Header Too Large (nginx)
The request headers were too large for nginx to accept.
495 SSL Certificate Error (nginx)
The client sent an invalid client certificate.
496 SSL Certificate Required (nginx)
The server requires a client certificate and none was sent.
497 HTTP Request Sent to HTTPS Port (nginx)
A plain http request arrived on a port that expects https.
499 Client Closed Request (nginx)
The client disconnected before the server finished responding. You see it in server logs, not in a browser.
509 Bandwidth Limit Exceeded (Apache and cPanel)
The hosting account has used up its bandwidth allowance. For SEO: Treated like any 5xx, so a site stuck on 509 loses crawl and eventually rankings.
520 Web Server Returned an Unknown Error (Cloudflare)
The origin server returned something empty, unknown or unexpected to Cloudflare.
521 Web Server Is Down (Cloudflare)
The origin server refused the connection from Cloudflare.
522 Connection Timed Out (Cloudflare)
Cloudflare could not open a connection to the origin server in time.
523 Origin Is Unreachable (Cloudflare)
Cloudflare could not reach the origin, usually because of DNS or routing problems.
524 A Timeout Occurred (Cloudflare)
Cloudflare connected to the origin, but the origin did not send a response within 100 seconds.
525 SSL Handshake Failed (Cloudflare)
Cloudflare could not complete the SSL handshake with the origin.
526 Invalid SSL Certificate (Cloudflare)
The origin’s certificate is not valid for Cloudflare’s strict SSL mode.
527 Railgun Error (Cloudflare, retired)
An error between Cloudflare and the origin’s Railgun server. Railgun has been retired.
530 Origin Error (Cloudflare)
Returned alongside a Cloudflare 1xxx error, often an origin DNS problem.
561 Unauthorized (AWS Elastic Load Balancing)
The load balancer could not authenticate the user with the identity provider.
598 Network Read Timeout Error (Some proxies)
Used by some proxies when reading the response from the server timed out.
599 Network Connect Timeout Error (Some proxies)
Used by some proxies when connecting to the server timed out.
What Are the Limits?
- Requests come from my server. Firewalls that verify real bot IP addresses, geo-redirects and bot protection may treat it differently from Googlebot or a visitor in another country.
- JavaScript is not run. Likely JavaScript redirects are flagged but not followed. Check those in a browser.
- 1,000 URLs per bulk run. Split bigger migration maps into several files. Fair use limits apply per visitor.
- Browsers can differ. HSTS, cached 301s and extensions change what you see in your own browser. This tool sees what the server actually sends.
Frequently Asked Questions
How do I check if a URL is redirected?
Paste it into the redirect checker. It follows every hop and shows each status code, so you can see whether the URL redirects, how many times, and where it ends.
How do I check redirects in bulk?
Switch to Bulk check, then paste a list or upload a CSV or TXT file of up to 1,000 URLs. Download the results as a CSV with the first status code, redirect type, chain, final URL and any issues.
What is the difference between a 301 and a 302 redirect?
A 301 is permanent and tells search engines to index the new URL. A 302 is temporary and tells them to keep the old URL indexed. Use 301 for migrations and renamed pages.
How many redirects will Google follow?
Googlebot follows up to 10 redirect hops. Keep chains to one hop where you can, because every extra hop slows crawling.
Does the checker follow meta refresh redirects?
Yes. Meta refresh redirects are followed and labelled as such. JavaScript redirects are flagged but not followed, because the tool does not run JavaScript.
Is the redirect checker free?
Yes. There is no sign-up. Fair use limits apply so the tool stays fast for everyone.
Who Built This?
I’m Dan Smullen, Senior Director of Group SEO at Grandstand and former Head of SEO at Independent.ie. Site migrations and M&A integrations are a big part of my job, and checking every redirect against the map is the step I never skip. This is the tool I wanted for it.
Need this level of rigour across an international portfolio? Let’s talk.