Redirect to http to https - Pros and Cons
-
Hi,
I know its best practice to redirect a website from http to https, instead of having many entry point to your website. When a website has been running for a long time on http and https, what are the SEO Pros and Cons of implementing a redirect from Http to Https?
-
Do you know how long it takes Google to drop pages from Google's index/cache?
-
(1) no, if you link to an insecure page it counts against you. Since a user or search engine would have to load and visit the insecure content to find the canonical (as that's where it would be), it does not mitigate this. You'll just have to hope it doesn't end up happening too much. Canonical tags only stop content duplication, they have no impact on SEO authority merging or insecure links
(2) If the HTTPS URLs are pretty much exactly the same as their HTTP counterparts and you 301 HTTP to HTTPS, the SEO authority should flow across to HTTPS instead. Canonical tags are not proven to do what 301s do, so you may end up in a mess with those. Most sites experience a slight dip moving from HTTP to HTTPS via proper 301s, however it's not large and doesn't last long if the 301s were done well. Staying on HTTP in the long term, you will lose a lot of rankings (gradually, over time). Since you will be constantly losing, it puts your site's progress 'on hold', so the small dip from moving from HTTP to HTTPS is the 'lesser of two evils' (IMO)
(3) Both. It will reduce the number of times Google crawls HTTP, but only after pages on HTTP are dropped from Google's index / recent cache
-
Thanks for the answer. However, have two more questions: (1) Will implementing canonical tags limit the temporary disruption and (2) If backlinks are pointing to http will these be lost or transferred, i.e. will https pages have less equity or inherit equity of the http pages. Finally, will redirecting to https reduce the number of times Google crawls your site or will google still crawl http until all http pages in the Google cache are removed?
-
Or in NginX format which is usually faster
-
There are no cons that I can think of, a simple script in a sites htaccess file is the best was to implement the redirection.
-
The idea of HTTPS has always been a good one, and most leading businesses implemented it a long time ago.
However, somewhat recently, Google announced that HTTPS is a ranking factor.
Obviously, that got SEOs talking about and debating the subject.
At the time, it was a very small ranking factor, affecting less than 1% of global searches. Even now, it’s not a big factor.
However, security is something that Google takes very seriously, and it’s likely to become more important in the future.
Some SEOs jumped right on it and made the switch.
-
This is a very solid answer. One additional point is that without a forced structure, Google can 'catch out' your secure site linking to your insecure site. Say you have a blog and a post in the blog links to one of your pages, that link is probably created as 'absolute' in your CMS. So suddenly, when you load that blog post on HTTPS, you can see a link pointing to HTTP. Google doesn't like links pointing to insecure content, so over time the situation snowballs and you lose a lot of trust
-
If your current pages can be accessed by http and by https, and if you don't have canonicals or redirects pointing everything to one version or the other, then one very significant "con" for that approach is that you are splitting your link equity. So, if the http page has 50 inbound links, and the https has another 50, you would do better to have one page with 100 inbound links.
Another difference is how browsers show/warn about non-secure pages. As well as any ranking factor they may associate with secure. Again, in favor of redirecting http to https. The visual handling can also impact conversion rates and bounce rates, which can in turn impact ranking.
As far as cons to redirecting, one would be that you might expect a temporary disruption to rankings. There will likely be a bit of a dip, short term. Another is that you will need to remove and then be careful about accidentally adding any non-secure resources (like images) on the https pages, which will then issue a warning to visitors as well as possibly impacting ranks. There is some consensus that redirects (and canonical links) do leak a very small amount of link equity for each hop they take. So, that's another "con". But my recent experiences doing this with two sites have been that after the temporary "dip" of a couple of months, if done properly, the "pros" outweigh the "cons".
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
-
Removing Multiple 301 Redirects
During my last redesign (and migration to Drupal) some of the updated SEO friendly url's on the new site were misspelled. Rather than updating the 301 redirects to point to the correct page the developer just added an additional 301 redirect. So it was redirected like this website.com/oldpage (301 to) website.com/new-paige (301 to) website.com/new-page Instead of website.com/oldpage (301 to) website.com/new-page I'll be finishing another redesign and updating to https soon, should I remove the redirect to the misspelled domain and just have one 301 from the original page? These multiple redirects have been up for over a year. Thanks for any specific advice!
Technical SEO | | talltrees0 -
301 redirect question
Hi Everyone When doing 301 redirects for a large site, if a page has 0 inbound links would you still redirect it or just leave it? Im just curious on the best practice for this Thanks in advance
Technical SEO | | TheZenAgency0 -
301 Redirect domain with penalty
Wondering if I could get a few views on this please... I have added an affiliate store to a domain I own, however I forgot to noindex the product pages which were duplicate content of the merchants. Despite a good deal of backlink building the site will not do much in the engines at all, doesn't even come up on the first few pages for it's own name! This suggests to me that I have a duplicate content penalty. Try as I may I cannot get it removed so am thinking of cloning the domain to a new domain, however, I do not want to lose the links I collected so I am planning on 301ing them. While I will not get all the link power moved over, I should at least get credit for some of them which will kick start the new domain. Can anyone forsee any potential issues with doing this? Is there a danger of 301ing a site with a penalty that the penalty would be carried over? I know there is no penalty on the links, no WMT warnings etc, it is the content causing the issue. Thanks, Carl
Technical SEO | | Grumpy_Carl0 -
Link juice and 301 redirects
Hi, I have a page with a lot of links going to it. I want to change the name of the page (thereby changing the URL). I can do a 301 redirect, but does a 301 send the "link juice" to the new page? The page in question is www.aerlawgroup.com/dui.html, and I want to change it to www.aerlawgroup.com/dui-lawyer.html. Thank you in advance for your time.
Technical SEO | | mrodriguez14400 -
.htaccess redirects
I've done some research but can't find a good answer to this question. Here's my situation: Site redirects from example.com to www.example.com just fine. However, it doesn't work so well for internal pages. My site incorrectly redirects (non-www) example.com/page2 to www.example.com when it should instead go to www.example.com/page2 So I need a method to redirect non-www internal pages to www versions. Currently I have this in my .htaccess - do I need to modify the rules? RewriteEngine on
Technical SEO | | 3plains
RewriteCond %{HTTP_HOST} !^www.example.com
RewriteRule (.*) http://www.example.com/$1 [R=301,L] Thanks0 -
Apache Rewrite Verse Redirect
I put in a request with my IT team to implement some 301 redirects. We recently launched a major redesign and there multiple version of some pages with different URLs. They asked why they could not do Apache Rewrites, so it was not necessary to return an HTTP header. I know Google's Webmasters best practices is to use 301 redirects. I am not familiar with the technical aspects of Apache et al. Are there advantages to using a rewrite? Thanks
Technical SEO | | SuperMikeLewis0 -
301 redirects on Windows server
Hi, We are soon moving www.ourumbrellaorganisationwebsite.co.uk/oldsubsidiaryname/index.aspx AND www.differentolddomainname.co.uk to just www.ourumbrellaorganisationwebsite.co.uk (an existing site which will no longer have the old subsidiary name sub section). How do we do the 301 redirects on a Windows server? Helicon has been suggested but I don't know it. I know we need to 301 redirect 'old' pages to the equivalent new ones, but is it a problem to do all of the old pages (there are lots) or should we just just do a few? is there ever a downside to doing individual redirects for an entire old site? Also, once the 301 redirects are in place from the old domain, is it possible to let the old domain expire and if so, at what point? Thanks
Technical SEO | | Houses0 -
301 redirect
What is a proper way to redirect any url containing a give word (anywhere in the url) to another sepcified url? Is it like this? RedirectMatch 301 ^thisword$ http://domain.com/newlocation
Technical SEO | | sesertin1