Uh oh. Google confirms it's giving HTTPS sites higher search rankings. What do we do?

Report · Aug 10, 2014

This recent change in the Google algorithm is bad for our clients because BC's solution for HTTPS requires the use of https://companyname.worldsecuresystems.com – which my clients would NEVER want to make their default URL.

So BC, what's your next move? If we can't install our own SSL certs, our clients will be penalised by Google.

That will make start to make BC harder to sell, especially to those who value their Google rankings.

Ref: Google confirms it's giving HTTPS sites higher search rankings | ZDNet

Report · Aug 10, 2014

Hi there Matt,

There are several threads here and on Linked in about this already.

I will quote one of the key things Google said that people have glossed over or omitted:

"For now it's only a very lightweight signal - affecting fewer than 1% of global queries, and carrying less weight than other signals such as high-quality content - while we give webmasters time to switch to HTTPS," Google's Zineb Ait Bahajji and Gary Illyes said in the blog post.

"But over time, we may decide to strengthen it, because we'd like to encourage all website owners to switch from HTTP to HTTPS to keep everyone safe on the web."

So right now - Its not a factor that will ruin your ranking.

Note how the quote has words like "MAY" decide etc.

Report · Aug 10, 2014

Thanks Liam.

I read those points and understand it's not an immediate threat to rankings. However SEO is top of mind of many of our clients and they like to stack ALL the cards in their favour, and HTTPS will start to become one of them. And given the many public security issues publicised by the media it would be a fare bet that in 1-3 years then SSL will be a standard for all sites.

BC have a window to sort it out. I think it would be unwise for BC not to have a contingency for SSL becoming a given for all sites. The current solution is not great. But I understand why they've done it that way... and I'm glad that installing SSL certs is something we've not had to deal with thanks to the current implementation.

Report · Aug 10, 2014

Thing is Matt, they have already outline the work this year and they already have a big list of things they need to jump on after these major system updates like bugs etc which they not got at for a few months.

And the work to make a change in which is a core element of how they handle secure content on the platform would be a big change. Pretty sure you would not see any movement on this, this year. BC have yet to step in and say anything in this regard but it would be a lot of work and from what they have sort of penciled in for the year I do not see it fitting in anywhere.

Report · Aug 10, 2014

Understood. Hopefully flagging it early means that it can be on BC's radar as something to watch and time will tell if it is in fact an issue.

Report · Aug 12, 2014

Man I'm sick to death of Google.

Report · Aug 12, 2014

Going on Googles track record for flagging changes, I would expect them to push this further within 18-24 months. The consideration won't be for web site owners, as much as it will be for raising the value of search results and therefore their ad revenue. There's nothing much technical about it for Google, so they could do it sooner if they see an advantage. I'd suggest to BC that they take a closer look at this issue. Perhaps BC would like to comment?

Report · Sep 12, 2014

Maybe Google has invested SSL companies, this would surely drive up revenue by making people by certs even when they didn't need them.