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
-
Old sitemaps after site migration.
Hi, I was wondering if it's safe to remove all the sitemaps from the old site in search console? It's been 3 months since site migration from http://sitea.com (301 redirected) to http://siteb.com. Therefore, can I delete the old sitemap from the http://sitea.com from search console? Thanks.
Intermediate & Advanced SEO | | ggpaul5620 -
Should I migrate .co.uk to .com?
I have previously searched the forum and could not find a definitive answer on this subject so would appreciate any guidance. I have just joined a new company, we have a .co.uk site which gets lots of traffic. We have a .com site which is targeting USA and .com/de/ targeting Germany. 'hreflang' is configured on the .com (between the USA and German sites) but not on .co.uk. This means that in the eyes of search engines (and Moz Pro) the 2 domains are competitors (and the .co.uk has much more presence than the .com in the USA). I know how to fix this and I am in the process of doing so. My question is whether it would make sense to migrate the .co.uk site to .com As previously mentioned the .co.uk site already does very well both in the UK and around the world (as our product is well known in our niche). As .co.uk can only primarily be targeted to UK would our global reach increase enough to justify migrating it to .com? We have dealers/distributors in maybe 30 countries and are continuing to expand, we will at point point add additional languages so my suggestion is that we migrate now as the authority of the .co.uk will help the emerging markets as well as increase our visibility in markets that are not currently primary targets. We are also in the process of hiring new staff specifically to focus on Content Marketing. So again this suggests having the 1 domain will make sense in the long run (as any value gained from content marketing success will be seen by all country/language focussed sites). I am also planning to rebuild the sites in the next few months as the current ones are not fit for purpose so the migration would coincide with this (I know this is not ideal). Apologies for the lengthy question, I hope the additional background information will help in providing some feedback to help me make the decision. David
Intermediate & Advanced SEO | | JamesCrossland0 -
Migration Strategy
Hi guys, Just want to check on this site migration strategy. Basically we have an Australian based ecommerce site which is going to launch globally. The company has two site. One is (http://www.domainUS.com – for US market) and one is Australian based (http://www.domain.com.au). Basically the plan is to have one single global .com site (like ASOS.com) on a new domain which would be domain.com and put both the current http://www.domainUS.com (US VERSION) and http://www.domain.com.au (AUSTRALIAN VERSION) on the new domain: domain.com (global) To make it even more complicated the new global domain (domain.com) is in the process of being purchased (someone else has the domain) and won’t be available till January 2016. But the company wants to execute the new global setup in November 2015 temporary on the .com.au version The current migration plan is to create two different sub-folders one for US e.g. http:www.domain.com.au/us and one for AUD http://www.domain.com/au on the current domain Australian domain.com.au for the global launch in November 2015. Then once domain.com is ready in January 2016, then migrate to domain.com with the countries as sub-folder (as shown below in stage 3). I was wondering if you guys think this would be an ideal migration strategy given the circumstances. Link to screenshot of current migration strategy: http://c714091.r91.cf2.rackcdn.com/4c2aae21dcbd548f27d96840227b81bc6b8b00c592.png Any advice would be very much appreciated! Cheers, Chris
Intermediate & Advanced SEO | | jayoliverwright0 -
Can I have my blog on http and the rest of the site on https?
I have an ecommerce site that is on https. We have a Wordpress blog for blogging, but we also have our help section located on it. I used a plugin to switch the blog to https but now have a few problems. 1. My sitemap generator still shows the blog as http and Google gives me a warning for the redirect. 2. When trying to use the Moz page grader I was told that I was in a redirect loop. 3. The pages do not seem to be getting indexed. It is a blog so there is never any information exchanged that is private. Would I be ok with just switching it to http? Or would Google see that as two different sites even though they have the same domain?
Intermediate & Advanced SEO | | EcommerceSite0 -
Switched to HTTPS, now Google ALWAYS changes Page Title & Meta in SERPs
Wordpress website using Yoast. Website switched over from HTTP to HTTPS successfully about 6 months ago. Noticed after the fact that Google almost never displays the Page Title or Meta Description I've created in Yoast. Yoast is the only SEO plug-in enabled. Yoast is set to Force Rewrite the Page TItles. The Page titles & Meta Descriptions are always within the character limit. They also contain either an exact or partial match the queries in which Google shows a different Page Title & Meta Description. For some Queries, Google will display the URL as the Page Title for certain queries. Concrete example, search for: public administration jobs Screenshot of results attached. First time working with HTTPS. The redirects appear to be have done correctly. I'm not sure what the issue is. uOnFjNt
Intermediate & Advanced SEO | | 2uinc0 -
Multiple 301 redirects for a HTTPS URL. Good or bad?
I'm working on an ecommerce website that has a few snags and issues with it's coding. They're using https, and when you access the website through domain.com, theres a 301 redirect to http://www.domain.com and then this, in turn, redirected to https://www.domain.com. Would this have a deterimental effect or is that considered the best way to do it. Have the website redirect to http and then all http access is redirected to the https URL? Thanks
Intermediate & Advanced SEO | | jasondexter0 -
Best practices for handling https content?
Hi Mozzers - I'm having an issue with https content on my site that I need help with. Basically we have some pages that are meant to be secured, cart pages, auth pages, etc, and then we have the rest of the site that isn't secured. I need those pages to load correctly and independently of one another so that we are using both protocols correctly. Problem is - when a secure page is rendered the resources behind it (scripts, etc) won't load with the unsecured paths that are in our master page files currently. One solution would be to render the entire site in https only, however this really scares me from an SEO standpoint. I don't know if I want to put my eggs in that basket. Another solution is to structure the site so that secure pages are built differently from unsecured pages, but that requires a bit of re-structuring and new SOPs to be put in place. I guess my question is really about best practices when using https. How can I avoid duplication issues? When do I need to use rel=canonical? What is the best way to do things here to avoid heavy maintenance moving forward?
Intermediate & Advanced SEO | | CodyWheeler0