We are now starting to index HTTPS pages by default!
37 plus ones
Shared publicly•View activity
View 7 previous comments
- From day of latest HTTPS announcement, there is some confusion, could you clarify the same?
1) Now Google can itself find https pages along with http pages. So, it does not depends on site owners to inform them for https version of the pages.
2) HTTPS pages will be indexed by default, when HTTP version of the same page is available.
e.g between https//www.mysite.com/name and http://www.mysite.com/name, Google will now indexed only https version of the page and ignore http version.
3) The rankings boost given to pages with HTTPS URLs over HTTP URLs is the same, as it was announced in August 2014. And new announcement will not have any impact on ranking of the website.
4) Google recent announcement, does't mean that website with only http:// version will not be indexed.
IndiaDec 21, 2015
1) If the site owner doesn't tell googlebot to do otherwise, then yes, we will index the HTTPS version by default, if the latter has a valid certificate. If the site owner specifically redirects the HTTPS page to the HTTP page, or has a canonical linik element pointing tot he HTTP page, then we will index the HTTP page.
2) Only if the HTTPS page has a valid certificate, and no contradictory signals like the ones listed in the blog announcement (redirects, canonical...).
4) Right.Dec 21, 2015
- Thank youDec 21, 2015
How will Google search treat SHA-1 certificate?
In other words, when will Google index system begin treating SHA-1 certs as invalid,
and avoid indexing HTTPS pages with SHA-1 as default?
As you know, Chrome and other major browsers will stop supporting SHA-1 certs in 2016-2017.
I worry this could happen.
1: Google indexes HTTPS pages with SHA-1 as default, since SHA-1 is now treated valid.
It is happenig with some of my clients.
2: When browsers stop supporting SHA-1, there are many HTTPS pages with SHA-1 on Google index.
3: When users click those SHA-1 results from Google search, they will encounter fatal error message.
I know it's best to upgrade to SHA-2 ASAP, but it takes some clients for a long time to do so.
If google index system begin to treat SHA-1 as invalid long before browsers do, I guess such problem won't happen.Dec 23, 2015
- if your website doesn't work in browsers because of the certificate, I think indexing in search would be the least of your worries, that's something which you should fix regardless (or just remove the HTTPS version of the site completely).Dec 24, 2015
- We just tookto HTTPS today, but one of the topics I hear a lot of webmasters concerned about is the loss of authority they will have redirecting everything from HTTP to HTTPS.
Are you looking at allowing a full authority pass if from same domain HTTP to HTTPS, to help eliminate this concern. It is keeping a LOT of webmasters from pulling the trigger.Dec 24, 2015
Add a comment...