Arclab® Website Analyzer


List all HTTP 3xx Redirects on Your Website
Check Your Web for Temporary and Permanent Redirects (HTTP 301, 302, etc.)



Download Trial Version   Purchase

What is a HTTP 3xx Redirect?

A "redirect" redirects users and search engines to a different URI. This means the server sends the client a new URI for the requested resource. In contrast to a META or page redirect, the forwarding URI is sent in the HTTP response header. The HTTP response header is essentially the web server's response to a request from the client (browser). The response header always contains a status code, which is in the 3xx range in the case of a redirect.

Redirects are commonly used in order not to lose incoming external links after changing the structure of directories or pages. This is especially important since inbound links are one of the most important signals search engines have for ranking a page. A redirect is not an error on your website, but simply a forwarding, whereby internal redirects are avoidable in most situations, since instead of the redirect you could change the corresponding link in the web page.

How can I Scan My Website for HTTP 3xx Redirects?

An analysis of your website is easy with Arclab® Website Analyzer. First, let the program scan your website.
After the scan of your website is completed, you will receive a detailed report containing all errors found on your website and other information.
Please note that this is not an error report, just information about existing redirects.


Website Analyzer Report


In the "Redirect HTTP 3xx" line, click "Show Details" to display details about the redirects:


Details: Redirects HTTP 3xx


  • When requesting the web page or URI (B), the server returned the status code (A).
  • The forwarding URI (C) was returned in the server response together with the status code.
  • This means that the client or browser should display or download the URI (C) instead of the URI (B).
    In other words: the page or URI (B) was redirected to the page or URI (C).
  • Under (D) you will find all pages that contain a link to the URI (B).
    So if you want to avoid internal redirects, you would have to change all the links in the pages listed under (D).
  • Please note that the program can only check links within your website.
    The report therefore only shows redirects that were triggered by links within your website.

More Information on HTTP 3xx Redirects

HTTP redirects should be the preferred method of redirection. The HTTP redirect allows different types of redirect by returning a status code together with the new URI. You can either add a line to your .htaccess file (in the root of your web server) or create a php page for it.


Redirect in .htaccess file:

Open the .htaccess file (located in the web root)  in an editor and add e.g.
RedirectPermanent source target
RedirectPermanent will send a "301 Moved Permanently" to the clients browser or search engine and is the recommended for most situations.

RedirectPermanent /a.html http://www.yourdomain.tld/b.html
Redirect permanent /a.html http://www.yourdomain.tld/b.html
Redirect 301 /a.html http://www.yourdomain.tld/b.html

"RedirectPermanent", "Redirect permanent" and "Redirect 301" are equal.


Redirect in .php page:

Create a php file, e.g. index.php with the following content:

header("HTTP/1.1 301 Moved Permanently");

What "Redirect" should I use?

From a SEO perspective the recommended redirect is a HTTP "301 Moved Permanently" redirect.
Use a 302 or 307 redirect if you want to redirect mobile users on a mobile friendly page or for a temporary condition.


  • 301 Moved Permanently
    A permanent redirect, which passes most link juice to the target page.
  • 302 Moved Temporarily (HTTP 1.0) - 302 Found (HTTP 1.1)
    A temporary redirect, which passes no link juice to the target page.
  • 307 Moved Temporarily (HTTP 1.1)
    Successor of 302 in HTTP 1.1.
  • META Redirect
    A page level redirect, which passes some link juice to the target. META redirects should only be used in special situations.