July 23rd, 2015
You may have noticed that you are now experiencing a Chrome https issue as your site is causing access problems for your WordPress site – for this you can thank a new Google Chrome update. It was picked up here this morning after a systematic look at a client site, so after a few checks, Gary and the team jumped into action.
From what we can see, Chrome is by default sending an HTTPS=1 flag in requests and disrupting sites with this flag. At first we thought might be a WooCommerce issue, but after experiencing the issue with a client sites that are not running WooCommerce, it’s clear that the underlying issue is elsewhere.
Whilst you perform your own tests, you can fix this Google Chrome https access issue by undertaking the following fix option:
- Add a header to your Apache .htacceyss file until you can identify the plugin or set up issue within WordPress, and add the following code:
RequestHeader unset HTTPS
We hope this helps, but if you can add any information to help the community, please post here. We of course will update this post as and when we discover how it is affecting the variety of site we manage.
Google notified us some time ago about its intentions to throw ranking weight to sites with https, all in the name of building trustworthy experiences, but has this been an oversight in the strategies of the search and product teams? Either way, our development team needs to make the changes to allow access to Google Chrome users and their experience with your managed brands are not tarnished.
It’s another little reminder that online work is never done, it is never complete and needs a beady eye to overlook and manage whatever is thrown at our clients. This of course also relates to SEO work, so even though you may have gone through this, when is the last time you reviewed your SEO? Do you regularly pay attention to the Panda and Penguin updates?…No?…Well if it has been a while or you think you may need to recap, our guide below may help you.