URL Redirect Check - Search Engine Friendly
This online tool helps to analyze HTTP Response headers and check your URL redirect working correctly and it is search engine friendly URL redirect: 301 Moved Permanently.
URL Redirect Check - Search Engine Friendly
Online URL Redirect Check tool check URL redirect is search engine friendly by checking HTTP response headers return from the server. Tool identifies the main types of search engine friendly URL redirect: 301 Moved Permanently. With URL redirects, incoming links to an outdated URL can be sent to the correct location. These links might be from other sites that have not realized that there is a change or from bookmarks/favorites that users have saved in their browsers. The same applies to search engines. They often have the older/outdated domain names and links in their database and will send search users to these old URLs. By using a "301 moved permanently" redirect to the new URL, visitors will still end at the correct page. Also, in the next search engine pass, the search engine should detect and use the newer URL.
HTTP Status Codes
|HTTP Status Code||Description|
|200 OK||The request has succeeded. The information returned with the response is dependent on the method used in the request.|
|301 Moved Permanently||The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.|
|Allow||Valid actions for a specified resource. To be used for a 405 Method not allowed|
|301 Moved Permanently||Tells all caching mechanisms from server to client whether they may cache this object|
|302 Found||The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.|
|304 Not Modified||If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.|
|307 Temporary Redirect||The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.|
|400 Bad Request||The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.|
|401 Unauthorized||The request requires user authentication. The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource.|
|403 Forbidden||The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.|
|404 Not Found||The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.|
|410 Gone||The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 Not Found SHOULD be used instead. This response is cacheable unless indicated otherwise.|
|500 Internal Server Error||The server encountered an unexpected condition which prevented it from fulfilling the request.|
|501 Not Implemented||The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.|
It is quite possible that one redirect leads to another redirect. Sometimes, however, a mistake can cause the redirection to point back to the first page, leading to an infinite loop of redirects. Browsers usually break that loop after a few steps and display an error message instead.
The HTTP standard states:
A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection.
Previous versions of this specification recommended a maximum of five redirections; some clients may exist that implement such a fixed limitation.
Online URL Redirect Check Information:
- Purpose of this Tool : Search Engine Friendly URL Redirect Check, SEF URL Redirect Check, Examine HTTP Request Headers
- Intended Audience : Webmasters, Web Developers, Programmers, System Administrators