HTTP Status Code Checker

See exactly how a URL responds

Check the HTTP status code, redirect chain and response headers of any URL, with bulk checking and crawler simulation

Enter one or more URLs

Request method

Request as

Follow redirects

Some sites answer differently to search-engine bots than to browsers. Switch “Request as” to compare.

Checking…

Summary

Success (2xx)

Redirects (3xx)

Client errors (4xx)

Server errors / failed

HTTP status code reference

Code	Name	What it means
100	Continue	The server received the request headers and the client should proceed to send the body. SEO: No direct SEO impact. Handled automatically by browsers and crawlers.
101	Switching Protocols	The server is switching to the protocol the client asked for, such as WebSocket. SEO: No SEO impact.
103	Early Hints	The server sends preliminary headers so the browser can start preloading resources. SEO: Can improve load speed. Not an indexing signal.
200	OK	The request succeeded and the server returned the content. SEO: The ideal response for any page you want indexed.
201	Created	The request succeeded and a new resource was created. SEO: Normal for APIs. Not relevant for pages meant to be indexed.
202	Accepted	The request was accepted for processing but is not finished yet. SEO: Not relevant for indexable pages.
204	No Content	The request succeeded but there is no content to return. SEO: A page returning 204 has nothing to index. Avoid it for real pages.
206	Partial Content	Only part of the resource was sent, in response to a range request. SEO: No direct impact. Used for media and large downloads.
300	Multiple Choices	There are several possible responses and the client must choose one. SEO: Rarely used. Prefer a single clear canonical URL.
301	Moved Permanently	The resource has a new permanent URL. Clients should use the new address from now on. SEO: Passes link equity to the new URL and tells search engines to replace the old URL in the index. The right choice for permanent moves.
302	Found (Temporary Redirect)	The resource is temporarily at a different URL. The original URL should still be used in future. SEO: Search engines may keep the old URL indexed. Use a 301 if the move is permanent.
303	See Other	The response is at a different URL and should be fetched with GET, typically after a form POST. SEO: Used after form submissions. Not meant for page moves.
304	Not Modified	The cached copy is still valid, so no body was sent. SEO: Good. Saves crawl budget and bandwidth when caching works.
307	Temporary Redirect	Like 302, but the request method must not change when following the redirect. SEO: Treated as temporary. Use a 308 or 301 if the move is permanent.
308	Permanent Redirect	Like 301, but the request method must not change when following the redirect. SEO: Treated like a 301: permanent, passes link equity.
400	Bad Request	The server could not understand the request because of malformed syntax. SEO: Pages returning 400 are not indexed. Check for broken URL parameters.
401	Unauthorized	Authentication is required and has not been provided or is invalid. SEO: Crawlers cannot access the page, so it will not be indexed.
403	Forbidden	The server understood the request but refuses to allow it. SEO: Pages blocked with 403 are not indexed. Check firewall, hotlink and bot-protection rules if search engines should see the page.
404	Not Found	The server cannot find the requested resource. The URL may be wrong or the page may have been removed. SEO: The page drops out of the index over time. Redirect it with a 301 if a replacement exists, and fix internal links pointing to it.
405	Method Not Allowed	The request method is not supported for this resource. SEO: Usually harmless for pages. Some servers reject HEAD requests with this.
406	Not Acceptable	The server cannot produce a response matching the Accept headers sent. SEO: Can block crawlers if content negotiation is misconfigured.
408	Request Timeout	The server timed out waiting for the request. SEO: Repeated timeouts can reduce how often crawlers visit.
410	Gone	The resource was intentionally and permanently removed. SEO: Tells search engines to drop the URL, often a little faster than a 404.
413	Payload Too Large	The request body is larger than the server allows. SEO: Not relevant to normal page fetches.
414	URI Too Long	The requested URL is longer than the server is willing to process. SEO: Check for runaway query strings or redirect loops adding parameters.
418	I'm a teapot	An April Fools joke from RFC 2324. Some sites use it to turn away bots. SEO: Treated as an error. The page will not be indexed.
429	Too Many Requests	The client has sent too many requests in a given time (rate limiting). SEO: If crawlers see this often, they slow down crawling. Review rate limits for known bots.
451	Unavailable For Legal Reasons	The content is blocked because of a legal demand. SEO: The page will not be indexed in affected regions.
500	Internal Server Error	The server hit an unexpected condition and could not complete the request. SEO: Pages are dropped from the index if the error persists. Check server logs and recent deployments.
501	Not Implemented	The server does not support the functionality required to fulfil the request. SEO: Treated as a server error. The page will not be indexed.
502	Bad Gateway	A gateway or proxy received an invalid response from the upstream server. SEO: Common with reverse proxies and CDNs when the origin is down. Persistent 502s hurt crawling and indexing.
503	Service Unavailable	The server is temporarily unable to handle the request, due to overload or maintenance. SEO: Fine for short maintenance (add a Retry-After header). Long or repeated 503s cause pages to be dropped.
504	Gateway Timeout	A gateway or proxy did not receive a timely response from the upstream server. SEO: Signals a slow or overloaded origin. Persistent 504s hurt crawling.

No status codes match that search.

Fix the errors, then audit the whole site

Status codes are one piece of technical SEO. Run a complete audit to check speed, mobile-friendliness, meta tags, and more.

Run Free Website Audit

About HTTP Status Code Checker

Every time a browser or search engine requests a page, the server answers with a three-digit HTTP status code that says whether the request worked. This tool requests the URLs you give it and reports the final status code, the full redirect chain that led there, how long the server took, and the response headers it sent back. It also flags common SEO problems: long redirect chains, temporary redirects that should be permanent, pages blocked with a noindex header, and sites served without HTTPS. You can check up to ten URLs at once, choose between HEAD and GET requests, and request the page as a desktop browser, a phone, Googlebot or Bingbot to see whether a site treats crawlers differently from visitors. The reference table above explains every common status code and what it means for search visibility.

What is the difference between 301 and 302 redirects?

A 301 says a page has moved permanently, so search engines transfer its ranking signals to the new URL. A 302 says the move is temporary, so the original URL usually stays indexed. Use a 301 for permanent changes.

Why does a page return 200 for browsers but an error for Googlebot?

Firewalls, bot-protection tools and misconfigured rules sometimes block crawlers. Switch “Request as” to Googlebot and compare. Note that this tool simulates the Googlebot user agent only and does not use Google’s IP addresses, so some protection systems may still treat it differently from real Googlebot.

Should I use HEAD or GET?

HEAD is faster because the server sends only headers. A few servers reject HEAD requests, and the tool then repeats the request with GET automatically. Choose GET to see exactly what a browser receives.