Migration to https
-
Hi there,
For several reasons we consider to switch from http to https. My question about this:
- Does this change impact organic search results since the URL changes? Is a simple 301 on the highest level enough to keep all of our positions with every page?
Are there any other possible issues we might think about before deciding?
I'm talking about a webshop with over 50k indexed pages and lots of running marketing channels all setted up based on the http URL structure.
Thanks in advance.
Marcel -
Hi Kevin & TorontoV,
Thanks for your responses, and your warning signs concerning a migration to https. We recently launched a new website and we are going to 'migrate' this one first before taking any action on our main webshop. Since we had'nt received any backlinks until now on the new domain, there is no thread for this one.
@Kevin: I'll definitely follow your advice not migrating until Google gives a countdown message for our main domain.
Thanks again!
Marcel
-
Ey Kevin, we experienced the same thing. our blog traffic got decimated after moving to https and I can see some other sites that did the move and also went into instant nosedive in Semrush. How are the results now?
we are considering moving the blog back.
Marcel, you too. did you do the move and what were your results?
I have a hunch that it is not the "positive" thing all the preachers claim it is.
-
Patrick, everybody should definitely check external links. We had hundreds of linking domains to our site, but after the switch to HTTPS we lost them all. Google now shows only one single linking domain in GA. Our rankings for performing key words have dropped six to ten spots from our page one 1-4 rankings in less than a month. Indexed pages went from nearly 300 to only six in the same time. Structured data records show a drop from nearly 220 to only 17.
Since Google recommends this, we'll give this another month or two, but if this Google recommendation switch to HTTPS doesn't start showing positive results, we'll surely switch back. My recommendation for now is to only use HTTPS for pages that transmit sensitive data.
Marcel, wait until Google gives the countdown notice to HTTPS like they did with mobile before you migrate your whole site.
Background: I run a Magento 1.9.2/WordPress 4.2.3 multilingual site on LEMP with fine-tuned Google PageSpeed module, Magento FPC on dedicated Memcached instance, and Redis session caching. I know what I'm doing here, but if anyone has suggestions please do share. https://www.88k.com.tw
-
Hi Andy & Jonathan,
Thanks again. I'm going to use this information when we are ready to migrate.
Cheers,
Marcel -
Hi Marcel,
301s can be done in the htaccess, just make sure as Patrick noted above that your site does not link to http version but directly to the https. You will want to avoid redirecting people from one version to another without need.
Another thing that might be important. Webmaster tools might require you to add another property as if I'm not mistaken it considers http and https as separate entities, it will be good to set it up and monitor both versions to notice that you don't have strange errors during and/or after the migration.
-
Is the htaccess code enough and does it fix a correct 301 redirect?
You also wouldn't specify a direct 301 when forwarding http to https. You can read about this within the Apache wiki here.
-Andy
-
Hi Andy & Jonathan,
Thanks for your response. This helps me a lot :).
Actually we do a lot of 3rd party advertising. I realize that we need to change all scripts but also URL's in tools of 3rd parties. This will be an important process I need to execute carefully.
Is the htaccess code enough and does it fix a correct 301 redirect?
Tnx!
Marcel -
Hi there
Along with the great points above, I would check your internal links, as well as your sitemap, to make sure URLs now reflect the https:// structure. Don't worry about updating your external backlinks.
If you have any major structure or URL structure changes, I recommend reading this migration guide.
Hope this helps! Good luck!
-
Hi Marcel,
A switch to https shouldn't hurt but would most likely have a positive impact on your baseline. Which is significantly more important than any loss in traffic. That said if you do the strategy properly and you redirect all the pages to the equivalent in https it should be fine (assuming you are not changing URLs and/or content).
What you might want to be wary of is the following.
1. Make sure that your CMS is able to automatically serve all your assets in https. So if you have images which are linked directly with
http://domain.com/image.jpg
you'd have to run a script to change the http into an https.2. Any third party scripts / images also need to be run over https. As you have a web shop I don't think you're doing some kind of third party advertising but check in case you have any other http content.
Any of the above two will mark your site as unsafe, which will deter visitors and possibly be a negative flag to google.
Good luck on the migration.
-
Hi Marcel,
Please have a look at this similar post here. You will find lots of useful information.
http://moz.com/community/q/moving-main-site-from-http-to-https-seeking-quick-items-to-consider
****Does this change impact organic search results since the URL changes? ****
In theory, it should be a positive move. Last year Google advised this was to be a new positive ranking signal.
Is a simple 301 on the highest level enough to keep all of our positions with every page?
I would advise you do this through htaccess. The code below should work fine for you. However, add it and then do your testing.
RewriteEngine On RewriteCond %{HTTPS} off RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R,L]
Are there any other possible issues we might think about before deciding?
Check how internal images are referenced and don't continue to point to http. The same goes with external resources like Google Fonts.
-Andy
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
-
Resolving 301 Redirect Chains from Different URL Versions (http, https, www, non-www)
Hi all, Our website has undergone both a redesign (with new URLs) and a migration to HTTPS in recent years. I'm having difficulties ensuring all URLs redirect to the correct version all the while preventing redirect chains. Right now everything is redirecting to the correct version but it usually takes up to two redirects to make this happen. See below for an example. How do I go about addressing this, or is this not even something I should concern myself with? Redirects (2) <colgroup><col width="123"><col width="302"></colgroup>
Technical SEO | | theyoungfirm
| Redirect Type | URL |
| | http://www.theyoungfirm.com/blog/2009/index.html 301 | https://theyoungfirm.com/blog/2009/index.html 301 | https://theyoungfirm.com/blog/ | This code below was what we added to our htaccess file. Prior to adding this, the various subdomain versions (www, non-www, http, etc.) were not redirecting properly. But ever since we added it, it's now created these additional URLs (see bolded URL above) as a middle step before resolving to the correct URL. RewriteEngine on RewriteCond %{HTTP_HOST} ^www.(.*)$ [NC] RewriteRule ^(.*)$ https://%1/$1 [R=301,L] RewriteCond %{HTTPS} !on RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] Your feedback is much appreciated. Thanks in advance for your help. Sincerely, Bethany0 -
Old site selected as canonical on GSC 3 years after migration?
Recently my company started consulting for a SaaS company. They're clearly the best known, most trusted company on their area of work and they have the strongest brand, best product and therefore more users than any of their competitors by a big margin. Still, 99% of their traffic comes from branded, despite having 3x more domains, better performance scores and more content. Even using tools such as SimilarWeb for comparing user satisfaction metrics, they seem to have lower bounce rates and more visits per session. Still, they rank for almost nothing that is non branded on Google (they rank extremely well for almost everything on bing and DuckDuckGo). They don't have any obvious issues with crawling or indexation - we've gone to great depths to tick off any issues that could be affecting this. My conclusion is that it's either a penalty or a bug, but GSC is not flagging any manual actions. These are the things we've identified: All the content was moved from domain1.com to domain2.com at the end of 2017. 301s were put in place, migration was confirmed on GSC. Everything was done with great care and we couldn't identify any issues with it. Some subdomains of the site, especially support, rank extremely well for all sorts of keywords, even very competitive ones but the www subdomain ranks for almost nothing on Google. The www subdomain has 1,000s of domains pointing to it while the support has only a few 100s. Google is performing delayed rendering attempts on old pages, JS and CSS particularly versions of assets that were live before the migration in 2017, including the old homepage. Again, the redirects have been in place for 3 years. Search Console frequently showing old HTML (at least a year old) in cache despite a recent crawl date and a current 301. Search Console frequently processing old HTML (at least a year old) when reporting on schema. Search Console is sometimes selecting pages from the old domain as the canonical of a URL of an existing page of the current domain, despite a long-standing 301 and the canonicals being well configured for 3 years now. Has anyone experienced anything similar in the past? We've been doing an analysis of old SEO practices, link profile, disavow... nothing points to black hat practices and at this point we're wondering if it's just Google doing a terrible job with this particular domain.
Technical SEO | | oline1230 -
Https & http
I have my website (HTTP://thespacecollective.com) marked on Google Webmaster Tools as being the primary domain, as opposed to https. But should all of my on page links be http? For instance, if I click the Home button on my home page it will take the user to http, but if you type in the domain name in the address bar it will take you to https. Could this be causing me problems for SEO?
Technical SEO | | moon-boots0 -
How bad is it to have duplicate content across http:// and https:// versions of the site?
A lot of pages on our website are currently indexed on both their http:// and https:// URLs. I realise that this is a duplicate content problem, but how major an issue is this in practice? Also, am I right in saying that the best solution would be to use rel canonical tags to highlight the https pages as the canonical versions?
Technical SEO | | RG_SEO0 -
Migration to new URL structure
Hi guys, Just wondering what your processes are when moving a large site to a completely new URL structure on the same domain. Do you 301 everything from old page to new page, or are your more selective - i.e. only 301 pages that have a certain page authority, for example. Thanks!
Technical SEO | | A_Q0 -
Multi Domain SSL Certs re HTTPS migration
Hi How important is it that when migrating sites to HTTPS they have their own SSL certificates as opposed to choosing the much cheaper multi domain certificate options such as: https://www.namecheap.com/security/ssl-certificates/comodo/ev-multi-domain.aspx I have been told really should have 1 certificate per domain and people generally unsure about multi domain certsificates ? All Best Dan
Technical SEO | | Dan-Lawrence0 -
Migrating a better performing domain to a less well performing domain
I have a customer who has many domain names and assets but she's wanting to consolidate some of them to help her simplify things for her customers but mostly she wants to build up her website through which she sells products. Grief Reflection - www.griefreflection.com is a personal journal that she's keeping to process the impending death of her husband and it's also linked to her business website which sells healing from grief types of products. Storybooks for Healing - www.storybooksforhealing.com is the website through which she sells workbooks and memory books for people who want to keep the memory of their loved one alive after they've gone. I've setup both of these domains as campaigns and have been looking at the metrics for both. The grief reflection blog out performs the storybooks for healing website. If we merge the two then the Grief Reflection blog would likely become a subdirectory under www.storybooksforhealing.com and be more fully integrated which she thinks will help her visitors not get confused while navigating her website. www.griefreflection.com has 12,637 links while www.storybooksforhealing.com has 1,462. Also, Google has indexed 380 pages of Grief Reflection and only 100 pages for Storybooks for Healing, though that may be because there are fewer pages to index. Grief reflection also has a 4.36 mozRank and 5.30 mozTrust, where Storybooks has 4.13 mozRank and 5.15 mozTrust. Should I counsel her to keep these domains separate? If not, would simply setting up 301 redirects from the www.griefreflection.com domain name to the new subdirectory under www.storybooksforhealing.com be the way to go? Thank you ever so much for any wisdom anyone can provide.
Technical SEO | | ChristiMc0 -
Disallowing https URLs
It there a problem disallowing all https URLs to be indexed in order to avoid duplication? This is the article recommending this practice - http://blog.leonardchallis.com/seo/serve-a-different-robots-txt-for-https/ Thanks!
Technical SEO | | theLotter0