Google indexing https sites by default now, where's the Moz blog about it!

[Deacyde]

Hello and good morning / happy Friday!

Last night an article from of all places " Venture Beat " titled " Google Search starts indexing and letting users stream Android apps without matching web content " was sent to me, as I read this I got a bit giddy. Since we had just implemented a full sitewide https cert rather than a cart only ssl.

I then quickly searched for other sources to see if this was indeed true, and the writing on the walls seems to indicate so.

Google - Google Webmaster Blog! - http://googlewebmastercentral.blogspot.in/2015/12/indexing-https-pages-by-default.html

http://www.searchenginejournal.com/google-to-prioritize-the-indexing-of-https-pages/147179/ 

http://www.tomshardware.com/news/google-indexing-https-by-default,30781.html

https://hacked.com/google-will-begin-indexing-httpsencrypted-pages-default/

https://www.seroundtable.com/google-app-indexing-documentation-updated-21345.html

I found it a bit ironic to read about this on mostly unsecured sites.

I wanted to hear about the 8 keypoint rules that google will factor in when ranking / indexing https pages from now on, and see what you all felt about this.

Google will now begin to index HTTPS equivalents of HTTP web pages, even when the former don’t have any links to them. However, Google will only index an HTTPS URL if it follows these conditions:

• It doesn’t contain insecure dependencies.
• It isn’t blocked from crawling by robots.txt.
• It doesn’t redirect users to or through an insecure HTTP page.
• It doesn’t have a rel="canonical" link to the HTTP page.
• It doesn’t contain a noindex robots meta tag.
• It doesn’t have on-host outlinks to HTTP URLs.
• The sitemaps lists the HTTPS URL, or doesn’t list the HTTP version of the URL.
• The server has a valid TLS certificate.

One rule that confuses me a bit is :

• **It doesn’t redirect users to or through an insecure HTTP page. **

Does this mean if you just moved over to https from http your site won't pick up the https boost? Since most sites in general have http redirects to https?

Thank you!

[Njnbiure45r4]

Can you please make a concrete example of a key-word for that you do not rank nicely. Please also specify the thing which in your opinion need to appear nicely inside the serch and the object for the blog of nextgenapk .

[Malika1]

Thanks for your response, Peter! As I said, I could be totally wrong - glad I asked this question

Cheers!

[Mobilio]

bit.ly, t.co and goo.gl are HTTPS shorteners. So you will keep links in page to HTTPS only resources/links.

[Malika1]

_"Or you can leave but change their links to pass some URL shortener - bit.ly or t.co until they comes with HTTPS version." _

looking at it from technical standpoint, these shortners are also not https (when crawling. Would they not have the same effect as other non https links?

Sorry, I could be going totally wrong about this and this question doesnt make sense at all.

[Deacyde]

Touche, good sir, these are certainly some great ways to go about this. Especially number 3.

Thanks!

Wonder how long we got until http2 implementation...

[Mobilio]

Or you can leave but change their links to pass some URL shortener - bit.ly or t.co until they comes with HTTPS version.

Or you can also make some page as "partners" where you can link only HTTP external sites.

Or you can also make internal page redirector to HTTP site. Like HTTPS -> HTTPS (inside redirector and dummy page) -> HTTP. On this case redirector won't be indexed and that's why it's dummy.

And this is just three ideas that i think for one minute. Probably mine favorite is #3. But it's IMHO.

[Deacyde]

So if my manufacturers don't have https sites, I should remove the links to them since it's going to hinder indexing?

Thanks for the http redirecting to https response.

[Mobilio]

Some sites comes with redirectors or "beacons" for detecting user presence. Example i'm on site X page A and there i click on link to go on page B. But due marketing department this pass via HTTP redirector or pure HTTP (and there 301 redirect to HTTPS). Then this page B can be not indexed.

This mean that once you set sitewide 301 redirect to encrypted connection you must make few more steps:

• you must check all resources to pass via this encrypted channel. Images, CSS, JS - just anything.
• you must check canonical to be set to HTTPS
• you must check that link between pages to be also HTTPS
• you must see any 3rd party tools for encrypted connection. Can be analytics software or "tracking pixels" or heat maps or ads.
• you must check if outgoing links from your site can be via other sites with encryption. Can be Wikipedia, Moz, Google. Since everything there is already encrypted you will skip frustrating HTTPS -> HTTP -> HTTPS jump too.

So then your site can be indexed in HTTPS. It's tricky procedure with many traps.