Check the HTTP status code, redirect chain and response headers of any URL, with bulk checking and crawler simulation
| 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.
|
Status codes are one piece of technical SEO. Run a complete audit to check speed, mobile-friendliness, meta tags, and more.
Run Free Website AuditEvery 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.
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.
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.
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.
Whenever someone visits a website, clicks a link, or a search engine requests a webpage, the browser or crawler communicates with the website's server. The server responds with a three-digit HTTP status code indicating what happened to the request.
These codes help browsers, search engines, developers, and website administrators understand whether a page loaded successfully, moved to another address, could not be found, or encountered a server problem.
For example, a 200 OK response generally means the request succeeded, while a 301 Moved Permanently response indicates that a resource has permanently moved to another URL. A 404 Not Found response means the requested resource could not be found, and a 500 Internal Server Error indicates that the server encountered an unexpected problem.
Understanding these responses is important for website maintenance and technical SEO. Incorrect redirects, broken URLs, server errors, and unexpected indexing restrictions can affect how visitors access your content and how search engines discover and process your pages.
The Auditest HTTP Status Code Checker helps you investigate these issues by sending requests to the URLs you provide and reporting the responses received. It displays the final HTTP status code, redirect chain, server response time, and response headers.
You can test up to 10 URLs at once, choose between HEAD and GET requests, and select different request identities, including desktop browser, mobile phone, Googlebot, and Bingbot. This makes it useful for identifying URL accessibility problems, investigating redirects, and checking selected technical SEO signals.
Search engines use HTTP responses to understand what happens when they request website pages. These responses provide important information about whether content is available, whether it has moved, or whether the server cannot fulfil a request.
A website with correctly configured status codes gives visitors and search engines clearer information about its pages.
However, incorrect status codes can create technical problems.
For example, imagine you redesign your website and change several page URLs. If the old addresses are not redirected correctly, visitors may encounter 404 errors, and search engines may have difficulty discovering the replacement pages.
Similarly, if a page that should remain accessible accidentally returns a 500 error, search engines may be unable to retrieve its content. If a page returns a 200 response but includes a noindex directive in its response headers, it may also be excluded from search results.
Checking HTTP status codes can help you:
Identify broken URLs and pages returning unexpected errors.
Find unnecessary or lengthy redirect chains.
Detect temporary redirects that may need permanent redirects.
Check whether a response includes an X-Robots-Tag: noindex instruction.
Identify URLs that redirect to non-HTTPS destinations.
Investigate server response delays.
Examine HTTP response headers for technical information.
Compare responses when using different request identities.
It is important to understand that a successful HTTP response does not automatically mean a page is indexed or will rank in Google. Status codes are only one part of technical SEO.

The tool combines several useful URL testing features in one interface.
The checker requests each URL and reports the final HTTP status code returned after any redirects have been followed.
This helps you determine whether a page is accessible, has moved, or is experiencing an error.
For example:
200 OK – The request was successful.
301 Moved Permanently – The resource has permanently moved.
302 Found – The resource is temporarily redirected.
403 Forbidden – The server refuses to fulfil the request.
404 Not Found – The requested resource could not be found.
500 Internal Server Error – The server encountered an unexpected error.
Knowing the final response makes it easier to investigate whether a URL behaves as expected.
A redirect occurs when a server sends a browser or crawler from one URL to another.
Redirects are useful when changing domain names, moving pages, switching from HTTP to HTTPS, or reorganising website content. Problems arise when redirects are unnecessarily complicated.
For example, a URL might follow this sequence:
http://example.com/page
→ https://example.com/page
→ https://www.example.com/page
→ https://www.example.com/new-page
Although the final destination may work, multiple redirects create additional requests and can introduce unnecessary delays or configuration problems.
The Auditest checker displays the redirect chain so you can identify intermediate URLs and understand how the final destination was reached.
A shorter, direct redirect is generally preferable when it can be implemented safely without breaking other URLs.
Website performance involves several stages, including DNS resolution, connection establishment, server processing, and content delivery.
The checker reports how long the server took to respond to the request, giving you a useful indication of the URL's response performance during the test.
Long response times may be associated with server overload, slow application processing, database delays, hosting limitations, or network conditions.
Remember that this measurement is not the same as a complete page-speed test. It does not independently measure all browser rendering activities, image loading, JavaScript execution, or Core Web Vitals.
For a broader performance assessment, use the Auditest Page Speed Test.

HTTP response headers contain additional information sent by the server when responding to a request.
Depending on the server and application, these headers may reveal:
The content type returned by the server.
Cache-related instructions.
Redirect information.
Security-related policies.
Search engine indexing directives.
Other response metadata.
One particularly important header for SEO is X-Robots-Tag.
For example:
X-Robots-Tag: noindex
This instructs compliant search engine crawlers not to index the relevant resource.
A page can return a successful 200 status code and still carry a noindex instruction. Therefore, checking the status code alone may not reveal every indexing-related issue.
The response header inspection feature helps you identify this type of configuration and investigate whether it is intentional.
The checker flags several technical issues that may deserve attention, including:
Long redirect chains.
Temporary redirects where permanent redirects may be more appropriate.
Responses containing a noindex instruction in the response headers.
URLs served without HTTPS.
These warnings help you identify potential configuration problems, but they should be interpreted in context.
For example, a temporary redirect is not automatically incorrect. It is appropriate when a move is genuinely temporary. Similarly, a non-HTTPS response may be intentional in a testing environment, although public websites should generally use HTTPS.
Checking URLs individually can become time-consuming when managing a large website.
Auditest allows you to submit up to 10 URLs in one batch, making it easier to compare their HTTP responses.
This is useful when:
Auditing important website pages.
Checking URLs after a website migration.
Reviewing redirects after changing permalink structures.
Investigating broken internal links.
Testing selected landing pages.
Comparing the responses of several website addresses.
Bulk testing helps you identify patterns and prioritise URLs that need further investigation.
The tool supports two HTTP request methods: HEAD and GET.
HEAD request: A HEAD request asks the server to return the response headers without the response body. It can be useful for checking basic response information without requesting the full page content.
GET request: A GET request asks the server to return the resource itself, including its response body when available. This can provide a more representative test of how the requested page responds to a normal retrieval request.
Some servers, applications, and security systems handle HEAD and GET differently. A HEAD request may return a different status or behave differently from a GET request.
If you are investigating a page that appears broken or behaves unexpectedly, testing with GET can help confirm what happens when the resource is actually requested.
Websites can respond differently depending on the identity presented by the requesting client.
Auditest allows you to select request identities representing:
Desktop browser.
Mobile phone.
Googlebot.
Bingbot.
This can help you investigate whether a website returns different responses to different request identities.
For example, a page may load normally for desktop visitors but return an unexpected error when requested with a mobile user-agent. Similarly, comparing browser-style and crawler-style requests can help identify possible differences in redirect behaviour or accessibility.
Important: Selecting Googlebot or Bingbot changes the request identity used by the tool. It does not authenticate the request as an official Google or Microsoft crawler. Therefore, these tests are useful for identifying possible differences, but they do not prove how genuine search engine crawlers will experience the website.\

HTTP status codes are grouped into five main categories. Each category represents a different type of server response.
| Status code | Meaning | SEO interpretation |
|---|---|---|
| 200 | OK | The request succeeded; the page can be retrieved |
| 201 | Created | A resource was successfully created |
| 204 | No Content | The request succeeded, but no response body is returned |
| 301 | Moved Permanently | The resource has permanently moved |
| 302 | Found | The resource is temporarily redirected |
| 303 | See Other | The client should retrieve another resource using GET |
| 304 | Not Modified | A cached version can be used |
| 307 | Temporary Redirect | Temporary redirect that preserves the request method |
| 308 | Permanent Redirect | Permanent redirect that preserves the request method |
| 400 | Bad Request | The request could not be understood or processed |
| 401 | Unauthorized | Authentication is required |
| 403 | Forbidden | Access to the requested resource is denied |
| 404 | Not Found | The requested resource could not be found |
| 405 | Method Not Allowed | The HTTP method is not supported for the resource |
| 410 | Gone | The resource has been permanently removed |
| 429 | Too Many Requests | The server is limiting requests |
| 500 | Internal Server Error | An unexpected server-side error occurred |
| 502 | Bad Gateway | A gateway or proxy received an invalid response |
| 503 | Service Unavailable | The server is temporarily unable to handle requests |
| 504 | Gateway Timeout | A gateway or proxy did not receive a timely response |
1xx – Informational Responses: These indicate that a request has been received and processing is continuing. They are generally part of the communication process rather than the final result of a normal webpage request.
2xx – Successful Responses: These indicate that the request was successfully received and processed. The most familiar example is 200 OK.
3xx – Redirection Responses: These indicate that the client needs to take additional action, usually by requesting another URL. Common examples include 301, 302, 307, and 308.
4xx – Client Error Responses: These indicate that something about the request prevents the server from fulfilling it. Examples include 403 Forbidden and 404 Not Found.
5xx – Server Error Responses: These indicate that the server or an upstream service encountered a problem while attempting to process the request.
Understanding these categories makes it easier to interpret the results of an HTTP status code test and determine which problems require attention.
| Problem | Possible cause | Recommended action |
|---|---|---|
| Unexpected 404 error | Deleted, renamed, or incorrectly linked page | Restore the page or redirect it to a relevant replacement |
| Too many redirects | Conflicting redirect rules or repeated URL changes | Review redirect configuration and simplify the chain |
| 302 used for a permanent move | Temporary redirect configured for a permanent URL change | Consider using 301 or 308 where appropriate |
| 403 Forbidden | Server permissions, security rules, or access restrictions | Review permissions, firewall rules, and access settings |
| 500 Internal Server Error | Application, plugin, database, or server configuration problem | Check server and application error logs |
| 503 Service Unavailable | Maintenance, resource limits, or temporary server overload | Investigate server capacity and service availability |
| Unexpected noindex response | An X-Robots-Tag directive is being added by the server or application | Review the relevant header configuration |
| HTTP instead of HTTPS | Incomplete HTTPS or redirect configuration | Configure HTTPS and an appropriate permanent redirect |
Before changing anything, confirm that the response is genuinely incorrect. For example, a 404 response may be perfectly appropriate for a page that has been permanently removed and has no suitable replacement.
Likewise, do not redirect every deleted page to the homepage. Redirects should lead to relevant replacement content whenever possible.
Follow these steps to test your website URLs:
Enter your URL or URLs: Add the website addresses you want to investigate. You can test up to 10 URLs in one batch.
Choose the request method: Select HEAD or GET depending on the type of response you want to inspect.
Select a user-agent option: Choose a desktop browser, mobile phone, Googlebot, or Bingbot request identity.
Run the test: Start the check so the tool can request the submitted URLs.
Review the final status codes: Identify which URLs return successful responses, redirects, or errors.
Inspect redirect chains: Review intermediate destinations and identify unnecessary redirect steps.
Check response times and headers: Look for slow responses, noindex directives, and other relevant header information.
Fix and retest: Correct confirmed configuration problems and run the test again to verify the results.
For website migrations or major URL changes, keep a record of important old and new URLs so you can confirm that each redirect leads to the intended destination.
The Auditest HTTP Status Code Checker is useful for anyone responsible for maintaining, developing, or optimising a website.
SEO professionals: Investigate redirect problems, broken URLs, and indexing-related response headers.
Website owners: Check whether important pages are accessible and identify unexpected server responses.
WordPress administrators: Test URLs after changing permalink settings, installing plugins, or migrating a website.
Web developers: Troubleshoot HTTP responses and verify redirect configurations during development.
Digital marketing agencies: Include URL response checks in technical SEO audits and website maintenance services.
Hosting administrators: Investigate server response behaviour and identify recurring HTTP errors.
Whether you manage a small blog, business website, online store, or large content platform, checking HTTP responses is a useful part of regular website maintenance.
An HTTP Status Code Checker is an online tool that sends requests to website URLs and reports the HTTP status codes returned by the server. Depending on its features, it may also display redirects, response headers, and server response times.
A 301 redirect indicates that a resource has permanently moved, while a 302 redirect indicates a temporary move. Use the redirect type that accurately represents the intended change rather than choosing one simply because it appears more SEO-friendly.
A 404 response is not automatically harmful. It is a normal response for a page that does not exist. However, broken internal links, incorrectly removed pages, and important URLs returning unexpected 404 errors can create poor user experiences and interfere with content discovery.
A redirect chain occurs when a URL passes through multiple redirects before reaching its final destination. Long chains can introduce additional delays and make website maintenance more complicated. Where practical, redirect directly to the final relevant URL.
HEAD requests retrieve response headers without the response body, while GET requests retrieve the requested resource. Some servers handle these methods differently, so a GET test may be more appropriate when investigating unexpected page behaviour.
Different request identities can sometimes receive different responses. Comparing crawler-style and browser-style requests can help identify possible differences in accessibility, redirects, or server behaviour. However, user-agent selection alone does not verify that a request came from an official search engine crawler.
No. A 200 response indicates that the request succeeded, but indexing depends on other factors, including crawlability, index directives, canonical signals, content quality, and search engine processing.
The Auditest HTTP Status Code Checker supports up to 10 URLs in a single batch, making it convenient for checking multiple pages without testing each address separately.
A website can look perfectly normal to visitors while hiding technical problems in its HTTP responses. Broken redirects, unexpected server errors, indexing restrictions, and unnecessary redirect chains can go unnoticed without proper testing.
The Auditest HTTP Status Code Checker makes it easier to investigate these issues by showing the final response code, redirect chain, server response time, and HTTP response headers for the URLs you submit.
You can test up to 10 URLs, compare HEAD and GET requests, and investigate how different browser and crawler-style user-agent options affect the responses.
Use the tool as part of your regular technical SEO and website maintenance process to identify potential problems, verify important URL changes, and keep your website's response behaviour easier to understand.
Visit Auditest's free website analysis tools to explore more tools for technical SEO, website diagnostics, performance testing, and online visibility.
Author: Kester Terna, Founder of Auditest
Last Reviewed: November 2026