Http > https Switch Before Platform Migration?
-
We are planning a series of large site migrations over the next 12-18 months, moving from one platform to another. It's likely the first will be completed by around Aug this year, with the process running until the back end of 2018.
The sites are currently on http, and the plan is to first of all migrate all sites to https in the next couple of months. The concern is that, due to the http>https 301 redirects that will be in place, are we putting ourselves at unnecessary risk by effectively carrying out 2 migrations in the space of a year (in terms of loss of potential authority caused by redirects)? Would we be better to wait, and implement https at point of platform migration instead?
Thoughts appreciated.
-
"The concern is that, due to the http>https 301 redirects that will be in place, are we putting ourselves at unnecessary risk by effectively carrying out 2 migrations in the space of a year (in terms of loss of potential authority caused by redirects)?"
In February 2016, Google’s John Mueller announced that SEO equity or PageRank will no longer be lost when a 301 or 302 redirect is used in conjunction with an HTTP to HTTPS migration. While some of us doubted this statement, Gary Illyes tweeted the same thing in July 2016 and Barry Schwartz at Search Engine Land confirmed it. There is no loss of authority caused by redirects when you implement HTTPS.
"Would we be better to wait, and implement https at point of platform migration instead?"
I think the approach you're taking (convert to https first) is a good one. It affords you better control and is a good use of available resources.
-
Do you have a list of all links pointing to the webpages you are trying to redirect on the new launch? If the structure of your website changes, I would use my remaining development time to minify the time you are going to invest in changing them. So 301 is good, but it is better if you can change the external and internal links that you can to point to the new pages. After that, do the 301s. The migration will take development changes but also a lot of link fixing. Although https is a ranking factor, I don't see it as an urgent move. It is your call but I would use the time to prepare a really good migration. Good luck!
-
Thanks for the responses both.
The only reason we are splitting is because the new platform is still being completed (custom built), whereas we have spare development resource on the legacy platform. From that point of view, it would appear to make sense to complete the http>https migration now. Of course, the earlier we implement, the earlier we stand a chance of seeing a positive impact.
I am just slightly wary of the potential for ranking losses, based off migrating our URLs twice in one year. What would be your thoughts on this?
We do process sensitive data, but on those relevant pages we do already implement secure protocol. The above relates to site wide pages.
-
Hi Nicola! What are your reasons for splitting the migration? Is your site processing sensitive data? If yes, https is an ASAP problem for you since Chrome will already give your users some trouble when navigating your website. If not, I think you will be better of with a single migration. But again, could you give some details regarding your thoughts and reasoning about this? There could be multiple aspects that influence this decision.
-
Hey Nicola,
I'll share my thought about this issue. However, I'm sure there are many approaches to that.
I would suggest to do firstly the HTTP -> HTTPS migration as far as it's one of the ranking factors according to Google - see the official Google blog here: https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html
You'll save the precious time, Google will see that you "upgraded" your website and that you keep pace with the trends. If you would start firstly with the platform migration, you would loose several months waiting for this to be done before starting HTTP -> HTTPS.
Hope you get my idea. Cheers, Martin
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Consolidating product pages during website migration
Hello, We are an e-commerce & content site undergoing a website migration and redesign in the coming months. We will be getting an entirely new website. Many of our URLs will be changing: Current URL setup: www.mysite.com/catalog/SKU12345/product-title-here
Intermediate & Advanced SEO | | katelynroberts
Future URL setup: www.mysite.com/catalog/product-title-here So we're aware we will be using plenty of 301 redirects to achieve this. Further to this though, we currently have a product page for each configuration of a product - for example, a single-sided bookmark has its own page and URL, and the double-sided version of the same bookmark has its own page and URL. In our site redesign, we are hoping to consolidate each of these instances into one product page where users can select single or double-sided and the price will update accordingly. The bookmark URLs would then go from:
_www.mysite.com/catalog/SKU12345/bookmark-single-sided _(call this URL A for simplicity)www.mysite.com/catalog/SKU67890/bookmark-double-sided (call this URL B) To (after migrating to the new URL structure for the new site, and the now-consolidated single- & double-sided product pages):
www.mysite.com/catalog/bookmark (call this URL C) What is the best way to make this transition without losing too much of our SEO value? I understand there is nearly always traffic loss with URL changes but I'd like to at least minimize the damage as best I can. We have backlinks and ranks for many product pages so I want to make sure we pass as much of this as we can. (And is this at all further complicated by the fact that URL A & B won't exist on the new site, and URL C doesn't exist on the current site? Does this impact the use of the 301 redirects and if so, how?) Are we better off to approach this page consolidation after the site migration and treat it as a separate project? This is something that is important to our user experience, and is definitely a change we want to make. Any advice is appreciated - thank you! I'm a fairly beginner-intermediate SEO so this is all somewhat new but I want to be able to at least convey some understanding to our developer of what we need to do. I was able to find this discussion (https://mza.seotoolninja.com/community/q/merging-pages-and-seo) which describes a similar situation and solutions if we were just consolidating the pages but doesn't quite have the complicating factor of the entire site migration happening at the same time. Thanks so much!0 -
Redirecting Pages During Site Migration
Hi everyone, We are changing a website's domain name. The site architecture will stay the same, but we are renaming some pages. How do we treat redirects? I read this on Search Engine Land: The ideal way to set up your redirects is with a regex expression in the .htaccess file of your old site. The regex expression should simply swap out your domain name, or swap out HTTP for HTTPS if you are doing an SSL migration. For any pages where this isn’t possible, you will need to set up an individual redirect. Make sure this doesn’t create any conflicts with your regex and that it doesn’t produce any redirect chains. Does the above mean we are able to set up a domain redirect on the regex for pages that we are not renaming and then have individual 1:1 redirects for renamed pages in the same .htaccess file? So have both? This will not conflict with the regex rule?
Intermediate & Advanced SEO | | nhhernandez0 -
HTTPS website migration and internal links
Hey Moz! I read Moz's guide on migrating websites from http to https, and it seems changing all relative internal links to absolute https is recommended (we currently use relative internal links). But is doing this absolutely necessary if we will already have a redirect in our .htaccess file forcing all http pages to https? Changing all of our internal links to absolute https will be very time consuming, and I'd like to hear your thoughts as to whether it's absolutely recommended/necessary; and if so, why? Thanks!
Intermediate & Advanced SEO | | TheDude0 -
Help needed on HTTPS
Hi Can anyone help me. I need some help with some example of large e-commerce sites going to https. Ideally these need to be e-commerce sites but any large site will be great, so that I can show the impact. The site can be based anywhere in the world, its more the impact I am after. Thanks Andy
Intermediate & Advanced SEO | | Andy-Halliday0 -
Using a 302 re-direct from http://www to https://www to secure customer data
My website sends Customers from a http://www.mysite.com/features page to a https://www.mysite.com/register page which is an account sign-up form using a 302 re-direct. Any page that collects customer data has an authenticated SSL certificate to protect any data on the site. Is this 302 the most appropriate way of doing this as the weekly crawl picks it up as being bad practise? Is there a better alternative?
Intermediate & Advanced SEO | | Ubique0 -
Best way to migrate to a new URL structure
Hello everyone, We’re changing our URL structure from something like this: example.com/index.php?language=English To something like this: example.com**/english/**index.php The change is implemented with mod_rewrite so all the old URLs can still work We have hundreds of thousands of pages that are currently indexed with the old URL structure What’s the best way to get Google to rapidly update its index and to maintain as much ranking as possible? 301 redirect all the old URLs to the new equivalent format? If we detect that the URL is in an old format, render the page with a canonical tag pointing to the new equivalent format as well as adding a noindex, nofollow tag? Something else? Thanks for your input!
Intermediate & Advanced SEO | | anthematic0 -
Re-platform effects on Page Rank
We are performing a major replatform for an ecommerce client who has many top listings on page 1 in Google SERPs for very competitive terms. We are implementing a 301 redirect for all existing URLs that they have now to the appropriate new URLs, but the client is concerned with how deploying a new site with 100% new URLs and site structure will impact their Page Rank. From our experience, the 301 redirects should cover it but wanted to see if there is a way to predictively forecast page rank effects as a result of re-platforming.
Intermediate & Advanced SEO | | Bucktown0 -
HTTP Errors in Webmaster Tools
We recently added a 301 redirect from our non-www domain to the www version. As a result, we now have tons of HTTP errors (403s to be exact) in Webmaster Tools. They're all from over a month ago, but they still show up. How can we fix this?
Intermediate & Advanced SEO | | kylesuss0