Why Should I care About Redirects When I Move Domain?
If you fail to implement proper redirects when migrating a website from one domain to another you will instantly lose any traffic to your website you currently enjoy, with new visitors often greeted by the dreaded 404 page.
If that’s not reason enough, failing to employ redirects will unquestionably impact on any good rankings your site also enjoys.
How Do I Redirect Visitors And Search Engines To My New Site?
You redirect any visitor, including search engines using the same technique: ‘301 permanent redirects’.
Is It Possible To Transfer Rankings From One Domain To Another?
Yes. If you are planning a rebrand, for example, and need to change website addresses, ensure you redirect all visitors to the new domain (and also redirect any relevant internal pages to internal pages on the new domain). It is also important to convey your old domain’s search engine rankings to the new web address – or your website will effectively be starting from zero visibility, in search engines at any rate.
Are 301 Redirects Complicated To Implement?
Not usually. It takes only a few lines of code to achieve this change of address in some instances. It is usually a simple if sometimes drawn out process.
The time it takes to complete a typical project is dependent on how large and how complex the website is you are aiming to redirect.
Success is often dependent on your access to particular files on your host server, or the CMS your website is constructed with.
How Do You Implement 301 Redirects?
I can discuss my experience on Apache servers and using “.htaccess” files and 301 permanent redirects.
With a 301 permanent redirect instruction at your server level, the age, authority and reputation of your old website in Google is transferred to this new web address.
With visitors redirected as soon as you apply the 301 redirects, search engines soon notice the change of address. If you have a very large and complex site, it could take a long time for Google to completely forget about your old site.
Upon successful implementation, the new domain ranks where the old domain once ranked.
This method has worked for most professionals for over ten years and still works today.
In 2016, you can also tell Google you’ve made the change, too, but Google still prefers you to also stick to traditional methods like I describe above as well as registering any change at Google Webmaster Tools.
How Long Do I Keep 301 Redirects In Place?
Forever. Until you die, or the website does. Whatever comes first. As soon as you remove 301s you break a connection that Google counts on to determine your domain reputation. This is important of course if you HAVE some domain reputation.
Can I Transfer A Google Penalty To My New Domain with Redirects?
YES! Do due diligence on any domain you are redirecting to your main site – you don’t want to redirect a site with a toxic link profile to your primary website, for instance. You need to disavow those links first.
Do Pages Need To Be Identical for 301 redirects to work?
NO! But only redirect users and Googlebot to equivalent pages where possible.
A good rule of thumb with any redirects (that you want to get the most benefit from) is to give visitors what they are expecting when they click on a link.
I often redirect many old URLs to one URL – if it’s relevant and a good user experience – but I avoid redirecting irrelevant pages to irrelevant destinations.
My general rule of thumb is to make sure the information (and keywords) on the old page are present in the new page copy.Most SEO already know the power of a redirect, and how you can use it to power even totally unrelated pages to the top of Google (for a time – sometimes a very long time).
Most SEO already know the power of a redirect, and how you can use it to power even totally unrelated pages to the top of Google (for a time – sometimes a very long time).
Should I 301 redirect all old pages to my home page?
NO. Google classes many improperly redirected links as soft 404s e.g. if you redirect a lot of URLs to your home page, for instance, is an example Google have given us. When redirecting visitors (and treat Googlebot as a visitor), always redirect them to equivalent pages.
For Googlebot – think about the keywords, topics and concepts of the pages you are redirecting to. If they are a good match – Googlebot usually has no problem with that – and will honour your request to redirect rankings.
I always try to find a relevant page to redirect one from another – it’s a good user experience, and that’s a good thing to focus on if you are trying to rank high in Google this year. NEVER redirect to your home page – always redirect to an internal page, if you choose to redirect at all.
Can I 301 Multiple Out-Dated Pages To A New Higher Quality Page?
YES! Sometimes content becomes stale and you end up with lots of pages that are essentially redundant in Google. This type of content can actually hurt your rankings in Google in 2016.
You can permanently redirect any and all out-of-date content to equivalent new pages that stand a better chance of ranking in Google for important keywords.
Google advises server side redirects are OK for this purpose – and so are CANONICAL LINK ELEMENTS – so I use them.
You can change the focus of a redirect but that’s a bit black hat for me and can be abused – I don’t really talk about that sort of thing on this blog.
But it’s worth knowing. You also need to keep these redirects in place in your .htaccess file going forward. Redirecting multiple old pages to one new page works for me, if the text based information, and especially target key phrase, is mentioned, and represented well, on the new page.
In my own experience, and confirmed by talking to some people who worked at Google, I can say that a 301 redirect is usually only permanent until Google recrawls the links – so, these redirects CAN be changed later, although if you know the redirect will be temporary, you are recommended (by Google and Bing) to use a 302 Temporary redirect.
I usually employ 301s and have changed them back and forth multiple times over the years, with no issues.
Can I Buy Old Domains And Redirect Them To Get High Rankings?
Say you see an old site that is ranking in Google for a lot of terms and there is an opportunity to buy that domain and redirect it to your site – will you keep those Google rankings?
I’ve not actually bought a domain for a long time myself, but I’ve redirected plenty. The way I see it, Google ranks pages because of the trust of a particular domain its on, the links that point to it and the content it has on it.
If you keep most of these quality signals intact, buying old domains and redirecting them to similar content shouldn’t be a problem. Even when redirecting pages, I usually make sure page titles and content are very similar on both pages if I want to keep particular rankings.
Be careful, though – Google is under no obligation to redirect domains and transfer rankings, and has said as much.
Make sure your new domain isn’t already blacklisted in Google for previous web spam violations before you implement any redirects!
Getting loads of unnatural links too fast may invite a GWT Notice of Unnatural Links and eventual penalty, or worse, a Google Penguin ‘Penalty’.
Be aware Black Hats know that it is probably better to resurrect a dead site (or dropped domain) that has been gone a while exactly as IT WAS when Google last saw it if you want to get back rankings. Check the WAYBACK Machine, for instance.
Note also that black hats are using 301s and old sites a lot in competitive niches, but I wouldn’t compete toe to toe with them using those strategies, as Google does seem to be getting better at dealing with them – and you probably won’t be able to compete on that front anyways.
Is There A Limit To The Amount of 301 Redirects Google Will Follow?
YES. Over the years, I’ve heard about 5 or 6. I would not rely on that though so try to ensure you have as few redirects in any chain of redirects at all times to avoid Google changing how it works. Which it does, often enough in plenty of areas to cause you challenges.
Does Google treat 302’s the same as 301’s?
Essentially YES. A 302 Temporary Redirect is not ideal, but Google has said it treats 302 redirects left in place essentially like 301’s. John Meuler said in a Hangout that Google also treats 302s in a chain like 301s.
Still – it is better to be as exact as possible with Google to ensure you get the results you need. When permanently redirecting – use a 301.
Should I tell Google About My Change Of Domain?
YES. I’ve always found it pretty painless although I can appreciate it’s easy to screw up if you don’t know what you’re doing. Now you can actually tell Google about your domain name change in Google Webmaster Tools.
If you’ve moved your site to a new domain, you can use the Change of address tool to tell Google about your new URL. We’ll update our index to reflect your new URL. Changes will stay in effect for 180 days, by which time we’ll have crawled and indexed the pages at your new URL. The change of address tool is safe, because only verified site owners can use it. You can check the tool at any time to see the information provided to Google about your domains.
This new tool from Google will be handy for some, though, you’ll still need to know your way about some technical aspects to use it. See moving your website to another domain. UPDATE – Also see Google announcing support of the cross-domain rel=”canonical” link element.
CASE STUDY: Using 301 Redirect To Keep Google Rankings
I needed to 301 an aging, out-of-date satellite site (or mini-site) into the principal website of the company I was employed by.
The goal was to keep visitors and Google rankings.
Managing multiple sites in a niche usually means some of those sites get neglected. Often, a lot of the mini-sites won’t get the required time and effort it takes to actually convert the traffic earned to leads and sales.
Information on satellite sites can often end up more out-of-date than the primary site. In this case, the decision was made to redirect lower-quality mini sites to the main corporate site to ensure the more conversion friendly corporate site ranked for the competitive term the mini-site had earned.
The image below shows the results when I redirected a mini-site that ranked no1 for a valuable query to the main site.
You can see from the illustration above and below when I achieved the no1 position with the satellite site, the actual corporate site was actually heading in a slightly different direction.
Essentially I wanted to make the main company site (in Green) be the number one result, and basically I wanted the mini-site to disappear from Google but transfer all its good rankings (as well as 600 visitors a day) to the corporate site.
I completed this employing the perfectly white-hat search engine friendly 301 Permanent Redirect in the .htaccess file on the old site (in red) to the corporate site (in Green).
redirect 301 /old.htm http://www.example.com/new.htm I ensured the new page on the corporate site was basically very similar in theme to page that Google currently ranked at No1 in the SERPs, so Googlebot wouldn’t think I was up to anything other than transfer rankings I had earned.
The end result is always (if done correctly) very satisfying as:
- The main site now ranks no1 in Google
- The main site now has absorbed the authority and trust of the old page which should help it’s overall domain reputation in the search engines.
- The page is now branded with the corporate id = better brand visibility
- Inexperienced link builders will be scratching their head for a while to come wondering what has happened and how the main site actually ranks at No1 in their attempt to reverse-engineer that particular SERP.
The images illustrate it worked exactly as expected.
The result of this simple strategy was a ‘new’ no1 position, with better branding and better conversion attributes, and 600 more visitors to the main site each day. It’s still like that today.
Things work very much the same in 2016, although Google has raised the quality bar in some instances, and I would be careful.
Time To Switch Your Website To HTTPS?
Like many SEO, I’ve naturally been telling all my clients to consider switching to HTTPS asap since Google said to a few years back to do so.
NOT because of any claimed ranking boost, but because it is the trend that Google prefers HTTPS – and it is more secure.
Many still haven’t moved to HTTPS, and I haven’t either.
The only reason I have not moved this (Hobo) site to HTTPS is that I am tidying it all up first, as much as possible, before I switch, because I see the entire process as a chance to learn as much as possible from the changeover.
I also want to ensure I don’t mess anything up, and there is plenty to mess up.
Google Chrome Will Mark Your HTTP Website ‘insecure’.
Now that Google Chrome is imminently planning on marking your website ‘insecure’ if it is NOT HTTPS, it is probably time to make switching to HTTPS a priority if it hasn’t been up to now.
This is quite a different issue, especially if you sell online, or take people’s information, and is just another example of the web evolving to focus on security and quality.
Time permitting, I still think you should clean your site up (e.g. remove redundant pages) before a switch to https to get the maximum benefit from such a move.
That time, though, may have run out.
Obviously, Chrome marking your site insecure could well be a conversion killer.
Why Is Google Chrome Marking My Website Insecure?
This goes way back to 2014, and is not unexpected:
Proposal – We, the Chrome Security Team, propose that user agents (UAs) gradually change their UX to display non-secure origins as affirmatively non-secure. We intend to devise and begin deploying a transition plan for Chrome in 2015. The goal of this proposal is to more clearly display to users that HTTP provides no data security. GOOGLE – 2014
Chrome pushing forward on marking plain HTTP as outright insecure is an incredibly strong and pro-user move,” Eric Mill, a technologist who’s been working on web encryption, told Motherboard. ”Despite how common plain HTTP can still be today, it *is* outright insecure, and a real and present danger to users and to the open web.
Should You Move To Https Immediately?
With Google Penguin on the horizon, I might wait until I see the fallout from that (although ‘waiting’ for Google to do anything in a timely fashion that benefits you is often folly.
If I had a massive site, I probably would wait. I don’t want to be going through a known major algorithm update with a massive change also underway on the site.
I don’t build any links, or buy links, but I have a lot of negative seo attacks on this site and I want to see how this site is impacted by the Penguin update.
I have a very small site (100 pages) so moving to https shouldn’t be drawn out or problematic.
In fact, with this switch to https at the back of mind for many months, I’ve focused on reducing the site in terms of pages (from about 2000 to 100) largely to improve quality but also to help manage such future migration or management challenges.
I’m ready to switch to HTTPS, and keen to do it, but very pedantic in my other priorities on this site.
I will be switching to HTTPS shortly, and suggest you think about it too, if you have not done already.
Cleaning Up Your Site Before A Changeover To HTTPS
When I say clean up my site before I move to HTTPS, I mean:
- getting rid of redundant pages on my site and sorting obvious low-quality issues before I move to HTTPS
- reducing the amount of redirect paths to important pages on the site
- reducing the amount of broken or misdirected links on pages on the site to lay down a clean, internal linking solution for the future
- speeding up a website load times
- disavowing all known low-quality backlinks
- reconnecting broken backlinks to pages on the website
- preparing templates for new internal linking requirements that minimise any redirects
Essentially – I work with sites with a lot of quality issues, and fixing them before you move has benefits in managing the site and anything you need to do in the future.
Moving to HTTPS can add a layer of complexity to some sites, so in some cases, cleaning up before you move makes analysing the impact easier, later.
As an SEO, telling clients to move to https (which is going to probably negatively impact organic traffic levels for up to a few weeks at least (sometimes months)) is not exactly news they want to hear.
This is compounded by the fact that Quality Rating Issues on a site are more important to tackle heads on, than prioritising moving to a secure server for an elusive ranking boost.
Moving to HTTPS is important from a security point of view, of course, but fixing quality issues is more important for me (as that is what I am hired to do).
I think, though, with this (not unexpected) move from Google chrome, migrating to HTTPS is going to have to be up there as a priority too.
Both for security reasons and conversion reasons.
Do I need to Register My Site With Google Search Console?
YES. Make sure your site is a manageable shape, then:
- Register all versions of your site in Google Search Console (AKA Webmaster Tools) (that’s 4 versions at the last count)
- Disavow all backlinks pointing to these domains, and upload the disavow file to all domains
- Make sure you have preferably 301 redirects on all other versions of the domain, pointing to one canonical version of the domain
I have witnessed fallout in early instances where a disavow was in place on the HTTP site, but not migrated to the https version by Google. Google neglected to point out to us in the beginning that that was necessary.
It could be said that Google prioritises migrating a penalty to another totally different domain over migrating the preventive penalty measures you put in place in good faith in a switch to https on the same domain.
That seems a little unhelpful.
You can ask yourself why we need the unnecessary complication of 4 versions of Webmaster tools, and 4 disavow files to manage all this, to ‘optimise’ a website in organic listings.
But – I would not switch to https without registering with Search Console first.
Google’s 2016 Advice on Moving To Https
The following advice is from John Mueller:
Planning on moving to HTTPS? Here are 13 FAQs! help center at https://support.google.com/webmasters/answer/6073543
# Do I need to set something in Search Console? No, just add the HTTPS site there. The change-of-address setting doesn’t apply for HTTP -> HTTPS moves.
# How can we do an A/B test? Don’t cloak to Googlebot specifically, use 302 redirects + rel=canonical to HTTP if you want to test HTTPS but not have it indexed. Don’t block via robots.txt . More about A/B testing athttps://googlewebmastercentral.blogspot.ch/2012/08/website-testing-google-search.html (302 redirects aren’t cached.)
# Will the rel=canonical guarantee that the HTTP URL is indexed? No, but it’s a very strong signal when picking the indexed URL.
# What’s the next step after testing? Follow our site-move documentation (https://support.google.com/webmasters/answer/6033049 ). Use 301 redirects from HTTP to HTTPS, confirm the new version by adding a rel=canonical on the HTTPS page, pointing to itself, and submit sitemaps including both HTTP & HTTPS URLs with new change-dates (in the long run, just keep the HTTPS sitemap).
# What about the robots.txt file? The HTTPS site uses the HTTPS robots.txt file. Check that it’s reachable or serves a 404 result code, and check that your HTTP URLs aren’t blocked by the HTTP robots.txt file.
# Is it OK to have just some pages on HTTPS? Yes, no problem! Start with a part, test it, add more.
# Should I move everything together, or is it fine to do sections? Moving in sections is fine.
# Will I see a drop in search? Fluctuations can happen with any bigger site change. We can’t make any guarantees, but our systems are usually good with HTTP -> HTTPS moves.
# Which certificate do I need? For Google Search, any modern certificate that’s accepted by modern browsers is acceptable.
# Do I lose “link juice” from the redirects? No, for 301 or 302 redirects from HTTP to HTTPS no PageRank is lost.
# Will we see search keywords in Google Analytics when we’re on HTTPS? This won’t change with HTTPS, you can see the search queries in Search Console.
# How can I test how many pages were indexed? Verify HTTP / HTTPS separately in Search Console, use Index Status for a broad look, or the sitemaps indexed counts for sitemap URLs.
# How long will a move from HTTP to HTTPS take? There are no fixed crawl frequencies, it depends on the size of your site, and the speed of crawling that’s possible. The move takes place on a per-URL basis.