Server Status Checker

Enter up to 100 URLs (Each URL must be on separate line)

About Server Status Checker

Which HTTP status codes are relevant for SEO and the Checker?

HTTP Code 200: Found

The HTTP status code 200 stands simply for the answer: "Okay, your request has been successfully processed and the transmission of the element can start". The server thus signals to the browser and the search engines that the file called up, for example an HTML page or an image, exists and can be loaded. In short: Everything is great!

HTTP Code 301: permanently moved

Using HTTP status code 301, the server tells the browser and bots that the request has been processed, but that the item is now in a different location. Permanent redirect therefore forwards the request to the new URL and indicates that the desired content has been moved there permanently. In terms of SEO, this response code should therefore be used deliberately and forwarding chains or loops strictly avoided. You have to consider this when redirecting using HTTP code 301.

HTTP Code 404: Not found

The HTTP status code 404 signals browsers and bots that the element cannot be found under the called URL. This is both a curse and a blessing for SEO: You can ensure that deleted resources are removed from the index, but you can also remove content that has only been moved and not redirected.

General information about HTTP status codes

What are HTTP status codes and how do they work?

With every request to the server - for example, when a browser or search engine crawler calls a specific URL - the request is answered with a specific HTTP code. An HTTP response code is a three-digit number that tells the requesting HTTP client information about the availability of the requested data.

Why do we need HTTP status codes?

Based on this response, the client will know the status of the requested resource and will act accordingly. For example, if the file is available (Code 200), the browser downloads the source code data and attempts to display it. Search engines basically act identically and subsequently interpret the source code to evaluate the content against statistical algorithms and place it in search results.

How does the tool check the status code of my URL?

The HTTP Status Code Checker provided here for free sends a GET request to the entered URLs and retrieves their HTTP status code. Google's User Agent is used to draw conclusions about the site's behavior during the search engine indexing process. The tool follows redirects and automatically detects possible loops in redirection chains. The status of a URL is evaluated using traffic light colors from an SEO point of view, so the result is ideal for optimizing its status codes specifically for search engine indexing.

301-Routing cables correctly inserted

Forward changed URLs permanently via HTTP Code 301

URLs change over time. Of course, page visitors and search engines should be influenced as little as possible negatively, so HTTP Status 301 must be used to ensure that the server forwards the old URL permanently to the new storage location. The HTTP code 301 literally stands for "moved permanently" and ensures that browsers and search engine crawlers are sent directly to the new location of the requested file. This is indispensable with regard to usability and search engine optimization (SEO) as soon as your URL structure changes.

When should a 301 redirect be used?

It makes sense to use the HTTP code 301 whenever a URL - i.e. the location of a content - changes permanently. In short: If content can now be found in a new location, it makes sense to use the HTTP code 301, because it ensures that both visitors and search engines can continue to access exactly the content they originally expected. Existing backlinks and read drawings will continue to work and search engines will replace the old URL with the new version. Within a short time Google and Co. will only display the new URL in the search results. In the following application cases the use of a 301-forwarding is meaningful thus:

  • The website is moved to a new domain.
  • The URL of a subpage - for example a blog entry - changes.
  • Visitors can access the same content via different URLs, e.g. with and without SSL encryption (https://).

What must be considered when setting 301 forwarding lines?

In principle, the forwarding destination must of course be accessible. If a redirection leads to nirvana - i.e. to an error page - it has no added value for visitors and search engines. In addition, the content of the redirection target must match the original content. It therefore makes no sense to simply redirect non-existing shop products to the start page of an online shop. If the URL of a content changes several times, you have to make sure that no forwarding chains are created. All old URL variants should therefore lead directly to the target URL. In addition, all redirects must remain permanent. This means summarized:

  • Forwarding destinations must be accessible.
  • Forwarding destinations must match the original content thematically.
  • Forwarding chains should be avoided if possible.
  • 301 redirects must be permanently retained.

How can URL redirects be checked and monitored?

You can easily check and monitor the correctness of your URL redirects with the HTTP Status Code Checker. The tool uses traffic light colors to indicate possible problems and at the same time shows you which targets your redirects really lead to. It is advisable to correct existing errors immediately in order to avoid visitor jumps and to be placed in the search result with the new URL in the future.