Strategy After Switching To HTTPS
-
So we made a big mistake with our website last month. Without thinking things through, our entire website was switched to using a SSL certificate and https urls on all pages of the site. I know it is recommended that SSL is only used on sensitive pages, but we have a lead form on all pages.
Of course Google is taking some time to adjust to all of our urls changing. A week later we lost all of our Google search rankings. It has now been about 3 weeks and our site is showing some signs of recovery, but obviously we'd like a quicker recovery.
We have done proper 301 redirects throughout the site, but unfortunately our CMS has been a little buggy creating some other problems to fix along the way.
So my main question is, how can we speed up the process? I do understand that we stand to lose 5-10% value of our old links due to the redirects. Is there anything else we should be doing to recover quicker though?
Also, at this point, would it make any sense to switch back to http urls? Or would that just delay things further?
Thanks!
-
Thanks for the advice John.
This is very sensitive contact info due to the nature of our niche. I do agree that a more simplified lead form on all pages with the extended info on a secure page would be best, but that decision is beyond my control.
Besides, if we were to make that change now, wouldn't it just delay the recovery since all urls would change again?
So it seems like we're at a point that we should be trying to make things work as is. It is definitely not the ideal setup, but I think we should still be able to recover rankings with this setup.
-
Is it really necessary to have everything on https? What kind of information are you collecting on this lead form? Most people won't bat an eye about you collecting things like name and e-mail address on a non-secure connection, but it would depend on your customers and industry. For the visits you're getting now, are a higher percentage submitting the lead form because the pages are secure? If not, I'd flip the URLs back. https is slower and the browser won't be able to cache everything, so it makes the user suffer on every page load.
A few other thoughts (it's impossible to say without seeing your site), but having a lead form on every page may be overkill. You could just link to the form (and then have the form be secure), or you might find success collecting just the e-mail address on all of your pages, and when you collect it, have that go to a secure lead form. Then you'll have a chance to e-mail market to those who abandon the form. Something to think about and maybe A/B test.
-
I am new to this site, but i would have done the same of a 301 redirect.
However can you not use both https and http? and then drop one once the search engines are listing both? (im not sure if they will see this as duplicate content or not though, if not just run with both http and https)
not sure if you know this or not but, within your HTML links you can use just "//www.domain.com" as appose to "http://www.domain.com". the links will then work on both http and https
Hope this helps, or someone better will come along
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
-
301 redirect hops from non-https and www
It's best practice to minimize the amount of 301 redirect hops. Ideally only one redirect hop. It's also best practice to 301 redirect (or at least canonical) your non-https and/or your non-www (or www) to the canonical protocol/subdomain. The simplest (and possibly the most common) way to implement canonical protocol/subdomain redirects is through a load balancer or before your app processes the request. Both of which will just blanket 301 to the canonical domain/protocol regardless if the path exists or not In which case, you could have: Two hops. i.e. hop #1 http://example.com/foo to https://example.com/foo, hop #2 https://example.com/foo to https://example.com/bar 301 to a 404. Let's say https://example.com/dog never existed, but somebody for whatever reason linked to it (maybe a typo). If I request https://www.example.com/dog, the load balancer would 301 to a 404 page. Either scenario above should be fairly rare. However, you can't control how people link to you. Should I care about either above scenario? I could have my app attempt to check if the page exists before forwarding, but that code could be complicated.
Intermediate & Advanced SEO | | dsbud0 -
Switching URLs after acquisition to retain domain authority?
Hey everyone! My company just acquired our biggest competitor and we're switching to their platform because they have a better technical structure for SEO--what's the best way to do that, other than a 301 redirect? Can we even rename their domain to ours? How do we ensure we keep both our and their domain authority and SEO juice? Thanks!
Intermediate & Advanced SEO | | genevieveagar0 -
HTTPS - implementation question
Hello, I am looking at a site on which they haven't 301'd http to https, so each URL is there whether you have http or https at the beginning. Why would a site owner not 301 to https? Is there any logical reason not to use 301? This particular website is simply using a canonical tag to point to the https version of each URL.
Intermediate & Advanced SEO | | McTaggart0 -
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.
Intermediate & Advanced SEO | | Sayers0 -
HTTP → HTTPS Migration - Both Websites Live Simultaneously
We have a situation where a vendor, who manages a great deal of our websites, is migrating their platform to HTTPS. The problem is that the HTTP & new HTTPS versions will be live simultaneously (in order to give clients time to audit both sites before the hard switch). I know this isn't the way that it should be done, but this is the problem we are facing. My concern was that we would have two websites in the index, so I suggested that they noindex the new HTTPS website until we are ready for the switch. They told me that they would just add cannonicals to the HTTPS that points to the HTTP and when it's time for the switch reverse the cannonicals. Is this a viable approach?
Intermediate & Advanced SEO | | AMSI-SEO0 -
Https vs Http Link Equity
Hi Guys, So basically have a site which has both HTTPs and HTTP versions of each page. We want to consolidate them due to potential duplicate content issues with the search engines. Most of the HTTP pages naturally have most of the links and more authority then the HTTPs pages since they have been around longer. E.g. the normal http hompage has 50 linking root domains while the https version has 5. So we are a bit concerned of adding a rel canonical tag & telling the search engines that the preferred page is the https page not the http page (where most of the link equity and social signals are). Could there potentially be a ranking loss if we do this, what would be best practice in this case? Thanks, Chris
Intermediate & Advanced SEO | | jayoliverwright0 -
URL strategy mobile website
Hello everyone, We are facing a challenging decision about where our website (Flash Gaming website) is going. We are in the process of creating html5 games in the same theme of the flash games that we provide to our users. Now our main concern is to decide how to show this new content to the user? Shall we create brand new set of urls such as : http://www.mydomain.com/games/mobile/kids/ Or shall we adapt the main desktop url : http://www.mydomain.com/games/kids/ and show the users two different versions of the page depending on whether they are using a mobile device (so they see a mobile version) or a pc/laptop (so they a see desktop version). Or even redirect people to a sub-domain : http://m.mydomain.com/ The main idea we had is to keep the same url structure, as it seems that google is giving the same search results if you are using a mobile device or not. And creating a new set of urls or even a sub-domain, may involve a lot of work to get those new links to the same PA as the desktop URL that is here and know since a while now. Also the desktop page game should not be accessible to the mobile devices, so should this be redirected (301?) to the mobile homepage of the site? But how google will look at the fact that one url is giving 2 different contents, CSS etc, and also all those redirects might look strange... we are worried that doing so will hurt the page authority and its ranking ... but we are trying to find the best way to combine SEO and user experience. Any input on this will be really appreciated. Cheers,
Intermediate & Advanced SEO | | drimlike0 -
Is it worth switching from .net to .com if you own both domain names
For over 20 years the company I work for has used www.company.net as their TLD, because we could not register www.company.com at that time. However, currently we also own www.company.com www.company.com has a 301 re-direct to www.company.net We are a global company, and market leader in our industry. Our company name is associated with the product we make, and our competitors use our company name as their targeted keywords to attract visitors to their sites because our company name is synonym with the product we and they make. As we are a global company we also have lots of TLDcc's. The email address of all our employees worldwide have a .net email address extension. Would you advice switching from www.company.net to www.company.com??? And if so, what would be the reasons for this switch. Would it only be for branding purposes? Looking forward to some insights before taking on such an invasive switch (because of the switch of all email addresses of employees worldwide). Best regards, Astrid Groeneveld
Intermediate & Advanced SEO | | Cordstrap0