Almost every website will reach a point when they need to implement redirects. Whether it’s because you moved content around, or you’re moving to a new domain, redirects can help you keep the traffic flowing, pass the value URLs have been assigned by the engines and help keep bookmarks working for your loyal visitors.
You don’t need to fear implementing redirects, but you should understand which is best to use and their limitations. Let’s take a look at the most common redirects.
The 301 redirect defines a redirect which tells the search engine the content has moved permanently to a new location. This is preferred as it clearly states the intent to move and instructs the engine to transfer any value the URL has accrued from the old URL to the new location. It’s important to know that the 301 redirect does not pass all of the value from an old URL to a new one. The new URL does need to build its own level of trust with the engines, which is why we won’t simply transfer full value to new URLs.
The 302 redirect defines a redirect which states the content has moved temporarily and will return to its original URL shortly. This redirect will still move people to your content, but the engines are essentially being told to hold their assigned values on the original URLs and wait for the content to return to the original URL. This is not what you want. Be careful when requesting redirects be implemented, and clearly define that you need to have a 301 in place. Otherwise, you can lose value from your original URLs, leaving your new ones to struggle on their own.
Heads up now, as this is where we give you a peek under the hood and insights as to how Bing thinks of 301 and 302 redirects. While the information above is technically correct, sometimes the real world forces us to make compromises.
We are always cautious about the information we find on websites, as from past experience we know to watch in case you’ve made an error. We sometimes see 301s changing destination each time we crawl them. In such cases, even though a 301 is in place, we tend to view them as 302 redirects. The flip side to this is that we sometimes see 302s which are always linking to the same destination each time we crawl them, acting more like a 301 redirect. So our system may think about them more like 301s as we continue to crawl them again and again.
You can obviously help us by providing the right redirection. That’s always best, but this does mean that if you have a large number of 302 redirects currently in place, you can move on to other work as we’ll figure them out.
Next up, let’s take a look at the rel=canonical element, what it does and how to use it properly.
It’s important to understand that a rel=canonical is not a true redirect. There has been a lot written that it’s “basically like a 301 redirect”, which can be misleading. The purpose of the rel=canonical is to help the engines understand when an individual URL is essentially a duplicate of another. The rel=canonical element does suggest to the engine that any value assigned to the duplicate URL be assigned to the original URL, though. This is similar to how the 301 functions, which is the origin of the over-simplification noted above.
The biggest difference between the two is that while a 301 redirect physically moves a visitor to the new URL, the rel=canonical does not physically move anyone anywhere.
Something else you need to keep in mind when using the rel=canonical is that it was never intended to appear across large numbers of pages. We’re already seeing a lot of implementations where the command is being used incorrectly. To be clear, using the rel=canonical doesn’t really hurt you. But, it doesn’t help us trust the signal when you use it incorrectly across thousands of pages, yet correctly across a few others on your website.
A lot of websites have rel=canonicals in place as placeholders within their page code. Its best to leave them blank rather than point them at themselves. Pointing a rel=canonical at the page it is installed in essentially tells us “this page is a copy of itself. Please pass any value from itself to itself.” No need for that.
We do understand that doing work at scale requires some compromises, as it’s not easy to implement anything on a large site page by page. In such cases, leave the rel=canonical blank until needed.
Getting back to redirects before we wrap up this post, if you’re starting a new website, keep in mind you’ll need to control the redirects if you move domains. This is important when considering whether to start your site on a hosted service like Blogger or WordPress. Be sure to understand whether the service will turn on redirects for you if you choose to leave their service for your own, stand-alone domain. Most won’t.
The same thinking applies to services offering to optimize your pages on-the-fly by interrupting the request, rewriting the code and presenting a cleaner URL or even an entire page. Such services work by placing themselves between the requestor (say, a search crawler) and your server. You don’t need to do much, as their system will give you clean URLs on the fly. The trouble for you can begin if you ever choose to leave behind their services. At which point the URLs the search engines have indexed are coming from your service provider’s servers, not your own. If you turn theirs off, you lose the value assigned to those URLs. Your own URLs will be seen by the engines as brand new, forcing them to start over in the hunt for rankings. All links built to your website are actually pointed to the clean URLs on the service’s severs, not your own, so all direct links cease to exist as well, so this breaks bookmarks.
Now, any links pointed to your root domain will remain intact, but that doesn’t help the rest of your content and pages.
Redirects are small things that can wield a lot of power. Be sure to do your research so you understand not only what will happen when you turn them on, but how it will work as well. This is one area you don’t want to guess at. Ask your IT staff or consultants to clearly explain what type of redirect they’re going to implement, how it will work and which URLs will be covered.
For large redirect projects, you’ll need to get dirty and redirect all that you want to keep the value from. There’s no simple way around this. Skip mass redirects to a single page, as most won’t end up passing value, and remember: keep all redirects pointed to pages which are relevant to the original. Skipping this step negates the value.
As a closing thought, be sure not to stack redirects. Doing so almost ensures we won’t pass the value through to the end.