A ‘301 Redirect’ is a server instruction given to all requests for a page by a browser (an Internet user), a search engine bot, or any other server request for that matter. A 301 redirect means, essentially, “this page has permanently moved, it has moved to…”.
As there is now a permanent instruction that the page address has moved, this also means that backlinks to your pages will also continue to count towards your backlink profile.
The backlink profile around each of the pages on your website form part of the analysis of Google’s ranking algorithm when determining the value (or authority) of each page.
With the 301 redirect instruction implemented, the value of existing backlinks pointing to the old URL will still be retained. This is sometimes referred to as ‘301 redirect link juice’ – essentially, you’re retaining the value of the external link to the old page by redirecting it to the new one.
301 redirects will retain most of the value of the original, but not all. Google’s Matt Cutts explains that Google’s crawler drops around 10% of the value for each redirect of a URL.
Redirecting from URL A to URL B retains around 90% of the link juice.
Redirecting from URL A to URL B, URL B to URL C and then from URL C to URL D would dilute the value by 10% at each stage, leaving only around 66% of the value for URL D by the time that redirect chain has completed.
Multiple 301 redirects are generally not good practice and should be avoided wherever possible.
A step by step guide to 301 redirects: If you’re upgrading your website and URLs will change.
If you’re not particularly tech-savvy, editing your htaccess file could easily cause a heap of problems. You’ll need FTP access to your server, or a friendly php developer or possibly even your web host.
The .htaccess file is generally found in the root of your domain and is a plain text file which you can edit with notepad or any number of other editors. The .htaccess file does a number of things, but think of it as a 301 redirect page.
Keep a backup of the .htaccess file at every stage just in case you make a mess!
For a 301 redirect for each page, each URL will need a single line in the .htaccess file.
301 redirect code example:
Redirect 301 /Page1.html http://www.domain.com/NewPage.html
The 301 denotes a permanent redirection. The command will work without it, but will default to a 302 redirect which is temporary.
There is no need to use the full ‘http://domain.com/’ version of the link. URLs are relative so you can just use everything from the forward slash ‘/’ onwards in the URL. The server knows which domain it is on.
Test the first redirect to make sure you have the 301 redirect syntax correct before implementing the remaining URLs, testing each one as you go.
Step Three (B): Alternative 301 Redirects
Depending on the CMS platform you use and your host, it is quite likely that you’ll be able to implement 301 redirects without getting your hands mucky via FTP and editing server files. If you’re not confident with that, it is best avoided.
Content Management Systems such as WordPress, Joomla, Magento and others will typically have an option in the admin or you might need a third-party plugin for 301 redirects which you can access more simply.
Alternatively, you will find that some web hosts provide access to cPanel or Plesk which may also have an option to add the 301 redirect. Check with your web host if this access is available.
301 Redirect Best Practice
The 301 redirect instructions are always implemented on the server where your domain is hosted. Typically, you’ll have created a new website with your existing host. The 301 redirects should be implemented on that same domain.
If you’ve moved an entire site from one host to another, but not changed any URLs, no action is necessary.
There are further options for redirecting pages contained with subfolders of a domain and options for redirecting every page from a domain to a single page (a homepage, for example). You can find more technical 301 redirect syntax here.
Make sure that you take a backup before you do anything and continue to take backups of the .htaccess file at every opportunity. It’s pretty easy to screw it up with disastrous (albeit temporary) consequences.
Here’s an example, for reference:
https://tillison.co.uk/curry – it redirects to a slightly different page address on our site. The old URL still works and any links around the web which reference it still have value.
Comments are closed.
Get early access to digital marketing news and all the highlights from the Tillison blog.