4 ms·

I was thinking about switching my sites to https-only also, because https-only is a good thing in general, but after doing some research it seems that it's uncl

by acabal 14y ago

I was thinking about switching my sites to https-only also, because https-only is a good thing in general, but after doing some research it seems that it's unclear what will happen in terms of Google SEO. There's even a video on Youtube from Matt Cutts addressing that specific question from July or so, and his answer is basically something like, "I don't know for sure, but it I don't see why it would make a difference." What would be helpful is some sort Google-recognized meta tag that says, "this site is https only, please index it as such." 301 redirects might work in theory, but theory isn't good enough when your business relies on how it appears in Google's results. Even a temporary demotion could mean lots of money and confidence lost.

deleted 14y ago
[deleted]
- EricBurnett 14y ago
  (Disclaimer: I work for Google, but not in websearch, and this is my personal opinion only) If this is a serious statement, then let me give you a serious answer: any minor increase in processing power won't inconvenience Google in the slightest. And even if it did, that still wouldn't matter. If it is good for web security and users - which I believe it is - then we're in favour of it. The consideration here is whether the algorithms are going to do the right thing, forwarding people, pagerank, referers, etc in the same way as before. That's not a question I can answer, but I'd go with whatever Matt Cutts has said.
Matt_Cutts 14y ago
I think you're referring to this video: http://www.youtube.com/watch?v=xeFo4ytOk8M http://www.youtube.com/watch?v=xeFo4ytOk8M At the time of that video, the indexing team was still working on one (very minor, corner case) type of issue, but I believe that was resolved. I'll double-check with the indexing team, but at this point I'd say feel free to go HTTPS. As always, I'd test it out first, ideally with a lower-traffic domain name. But if you like the results you get, you should be able to use our existing tools like 301s and rel=canonical to help Google discover that the site has gone HTTPS.
- X-Istence 14y ago
  Does Google's bot do SNI?
lucisferre 14y ago
We use all https and there is no notable problems in indexing or SEO that I can see. We get indexed quickly and show up well I search results.

by acabal 14y ago

deleted 14y ago

[deleted]

EricBurnett 14y ago
(Disclaimer: I work for Google, but not in websearch, and this is my personal opinion only) If this is a serious statement, then let me give you a serious answer: any minor increase in processing power won't inconvenience Google in the slightest. And even if it did, that still wouldn't matter. If it is good for web security and users - which I believe it is - then we're in favour of it. The consideration here is whether the algorithms are going to do the right thing, forwarding people, pagerank, referers, etc in the same way as before. That's not a question I can answer, but I'd go with whatever Matt Cutts has said.

Matt_Cutts 14y ago

I think you're referring to this video: http://www.youtube.com/watch?v=xeFo4ytOk8M http://www.youtube.com/watch?v=xeFo4ytOk8M At the time of that video, the indexing team was still working on one (very minor, corner case) type of issue, but I believe that was resolved. I'll double-check with the indexing team, but at this point I'd say feel free to go HTTPS. As always, I'd test it out first, ideally with a lower-traffic domain name. But if you like the results you get, you should be able to use our existing tools like 301s and rel=canonical to help Google discover that the site has gone HTTPS.

X-Istence 14y ago
Does Google's bot do SNI?

lucisferre 14y ago

We use all https and there is no notable problems in indexing or SEO that I can see. We get indexed quickly and show up well I search results.