Pro's & contra's: http vs https
-
Hi there,
We are planning to take the step and go from http to https. The main reason to do this, is to mean trustfull to our clients. And of course the rumours that it would be better for ranking (in the future).
We have a large e-commerce site. A part of this site ia already HTTPS.
I've read a lot of info about pro's and contra's, also this MOZ article: http://moz.com/blog/seo-tips-https-ssl
But i want to know some experience from others who already done this. What did you encountered when changing to HTTPS, did you had ranking drops, or loss of links etc?I want to make a list form pro's and contra's and things we have to do in advance.
Thanx, Leonie
-
We don't use Comscore. Analytics transparently kept tracking everything without any change. We don't use Tagmanager url matching tracking, but unless you have not defined rules which include the url protocol it should not need any attention either.
-
Hi, did you encountered problems with other tools, like Google Analytics and or Tagmanager, Comscore?
Thanx, Leonie
-
We have expensive certificates now for the payed section, i think we'll use the same
i'll ask about the server support SNI, not sure about that, thanx
-
In case you choose the most expensive EV certificates as we did, for whatever is not directly visible, like the cdn serving js, css and images you can just use cheap 8 $/€ certificates.
One thing I forgot, if your server support SNI, don't use it.
We did initially, but soon found out some price engines could not read feeds, moz crawler could not crawl, and everyone on XP+IE was left out. So we disabled it.
-
Hi Max, Thansk, and good to read that you didn't lost ranking. that's my concern and also the backlinking. although you should say with a redirect all the external links i can't control will redirect to https.
We have 2 different ssl certificates now, we are looking for what we need and if we have the right ones.
If i've finished the plan and list i'll think i'll publish it here
Grtz, Leonie
-
I did it a month and half ago for a couple of websites.
Transition was smooth. I had to buy more ssl certificates than I thought for the many domains serving js css and so on... But was not a big hassle.
Just after moving from http to https I didn't notice any ranking change, and to have a good level of accurancy I monitor the same keywords with both moz ranktracker, proranktracker and semrush.
But in fact google is slowly recognizing the move few urls at time, each day you will notice some google serp start serving https url in place of http ones.
After a month we had a big jump in ranking, around +30% more keywords in the top 100 and a general increase in ranking for all the keywords already in top 10, top 30 and top 50.
But I have no idea if it's connected with the shift to https since we also constantly do many other things, get backlinks, improve on-page, etc...
At least it didn't seem to penalize the websites.
-
Hi Pixelbypixel, thanx for your reply.
Right now i'm making a plan for the switch, i'm not in a rush, so i really want to make it all clear before we go, or maybe decide not to..
I don't think most of our clients know what's secure and what isn't. But we want the opportunity to comunicate about this with our clients, something we don't have right now (only when the order something)
The ranking factor, what i read about it, is not a big thing at this moment, but indeed, in the future and can be a bigger one, so that's also a good reason to go.
Thanx for the linked articles!
Grtz, Leonie
-
I'm going to give my opinion more than a list of pros and cons, most people who switch over tend to see a drop in traffic and if you don't ensure you get it all right it can be a nightmare so make sure you've got your plan ready.
Are you sure most "clients" know what https is? Most people outside our world have no idea what it is combine with the fact that the so called ranking boost has yet to be well documented it can be fairly certain its tiny.
Now it is possible that your clients know what it is and will see it and go to your site but in most cases I suspect like the ranking boost other factors would play a bigger role. My advice is to really make sure you have all the bases covered for your transfer. Also wanted to point out in the future it may be a bigger factor.
As for advice on people who have already done it oodles of info here on Moz here are a few -
http://moz.com/community/q/http-to-https-transition-large-drop-in-search-traffic
http://moz.com/community/q/https-sitewide-move-has-resulted-in-huge-rankings-drop
http://moz.com/community/q/authority-site-drastic-ranking-drop-after-google-https-switch-please-help
Obviously people tend to come here for problems more than a shout out for how great it is so don't take that as a massive negative and all of the above is my opinion I'm sure some others will give other opinions and I don't want you to be put off just to be aware that there is a lot to cover in a switch over.
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
-
GoogleBot still crawling HTTP/1.1 years after website moved to HTTP/2
Whole website moved to https://www. HTTP/2 version 3 years ago. When we review log files, it is clear that - for the home page - GoogleBot continues to only access via HTTP/1.1 protocol Robots file is correct (simply allowing all and referring to https://www. sitemap Sitemap is referencing https://www. pages including homepage Hosting provider has confirmed server is correctly configured to support HTTP/2 and provided evidence of accessing via HTTP/2 working 301 redirects set up for non-secure and non-www versions of website all to https://www. version Not using a CDN or proxy GSC reports home page as correctly indexed (with https://www. version canonicalised) but does still have the non-secure version of website as the referring page in the Discovery section. GSC also reports homepage as being crawled every day or so. Totally understand it can take time to update index, but we are at a complete loss to understand why GoogleBot continues to only go through HTTP/1.1 version not 2 Possibly related issue - and of course what is causing concern - is that new pages of site seem to index and perform well in SERP ... except home page. This never makes it to page 1 (other than for brand name) despite rating multiples higher in terms of content, speed etc than other pages which still get indexed in preference to home page. Any thoughts, further tests, ideas, direction or anything will be much appreciated!
Technical SEO | | AKCAC1 -
Should 'View All' filters on ecommerce sites be indexable?
Hi, I’m looking at a site at the moment that has a lot of products. For some of their category pages they have a ‘View All’ feature available. The URL uses this structure: domain.com/category/sub-category/product domain.com/category/sub-category/view-all < currently noindex applied Should the view all page be available for indexing? The individual sub-categories and products are indexable My immediate reaction is no, so long as the individual sub-cats are?
Technical SEO | | daniel-brooks0 -
301 Redirecting http to https
In the Moz Site Crawl issue, I was seeing an error that said we were temporarily redirecting our homepage to https URLs. So I changed the code in htaccess to make it 301 redirect but I'm still getting the same error. I implemented it last week and we just had a new crawl yesterday. Here is the new code: RewriteEngine on
Technical SEO | | Heydarian
RewriteCond %{HTTP_HOST} ^heritagelawmarketing.com [NC]
RewriteRule ^(.*)$ http://www.heritagelawmarketing.com/$1 [L,R=301,NC] Does anyone know why I'm still getting 302 redirects? Thanks0 -
Which URL do I request Google News inclusion for: the http or the non-http?
In Google WMT/Search Console, I've marked the non-www. version of my site as the preferred. But I haven't run into a choice between http:// and non-http:// before. Should I choose the one listed at the top, which is the non-http (AND the non-www) version? Thanks! Unknown.png
Technical SEO | | christyrobinson1 -
Should we use & or and in our url's?
Example: /Zambia/kasanka-&-bangweulu or /Zambia/kasanka-and-bangweulu which is the better url from the search engines point of view?
Technical SEO | | tribes0 -
Toggle Menu's and Collapsible Nav Structure Good For SEO?
Does anyone have any insights on toggle menu's or collapsible navigation structure and if its good/bad for Search?
Technical SEO | | Your_Workshop0 -
What's the best URL Structure if my company is in multiple locations or cities?
I have read numerous intelligent, well informed responses to this question but have yet to hear a definitive answer from an authority. Here's the situation. Let's say I have a company who's URL is www.awesomecompany.com who provides one service called 'Awesome Service' This company has 20 franchises in the 20 largest US cities. They want a uniform online presence, meaning they want their design to remain consistent across all 20 domains. My question is this; what's the best domain or url structure for these 20 sites? Subdomain - dallas.awesomecompany.co Unique URL - www.dallasawesomecompany.com Directory - www.awesomecompany.com/dallas/ Here's my thoughts on this question but I'm really hoping someone b*tch slaps me and tells me I'm wrong: Of these three potential solutions these are how I would rank them and why: Subdomains Pros: Allows me to build an entire site so if my local site grows to 50+ pages, it's still easy to navigate Allows me to brand root domain and leverage brand trust of root domain (let's say the franchise is starbucks.com for instance) Cons: This subdomain is basically a brand new url in google's eyes and any link building will not benefit root domain. Directory Pros Fully leverages the root domain branding and fully allows for further branding If the domain is an authority site, ranking for sub pages will be achieved much quicker Cons While this is a great solution if you just want a simple map listing and contact info page for each of your 20 locations, what if each location want's their own "about us" page and their own "Awesome Service" page optimized for their respective City (i.e. Awesome Service in Dallas)? The Navigation and potentially the URL is going to start to get really confusing and cumbersome for the end user. Think about it, which is preferable?: dallas.awesomcompany.com/awesome-service/ www.awesomecompany.com/dallas/awesome-service (especially when www.awesomecompany.com/awesome-service/ already exists Unique URL Pros Potentially quicker rankings achieved than a subdomain if it's an exact match domain name (i.e. dallasawesomeservice.com) Cons Does not leverage the www.awesomecompany.com brand Could look like an imposter It is literally a brand new domain in Google's eyes so all SEO efforts would start from scratch Obviously what goes without saying is that all of these domains would need to have unique content on them to avoid duplicate content penalties. I'm very curious to hear what you all have to say.
Technical SEO | | BrianJGomez0 -
Internet Explorer and Chrome showing different SERP's
Well the title says it all really. Same query, different browsers, same computer and different search results. I thought at first it may have differed because I was logged into my google profile on chrome but I logged out and tested and still different results. Is this normal ?
Technical SEO | | blinkybill0