Google clarifies the SharedArrayBuffer notification
After much confusion, Google explained why it send out these notifications and what your next steps should be.
Earlier this week, Google sent out a notice through Google Search Console with SharedArrayBuffer warnings to site owners. And honestly, it caused a huge amount of confusion and concern amongst those who received it.
Today Google published a blog post with clarifications around why Google sent out the message and what site owners can do to address the potential issue.
The confusion. Many site owners, consultants and SEOs were confused by the messaging, which likely prompted Google’s response:
How to find these issues. Google provided methods to find this SharedArrayBuffer issues listing these two options:
- Use Chrome DevTools and inspect important pages.
- (Advanced) Use the Reporting API to send deprecation reports to a reporting endpoint.
Google’s recommendations. Google then listed these next steps to take if you received the Search Console message:
- Determine where the
SharedArrayBufferobject is used on your website.
- Decide if the usage is necessary.
- Fix the issue by either removing the functionality or by enabling cross-origin isolation.
Why we care. If you received this message, we recommend you review both Google’s clarification blog post and our story here on Search Engine Land. This should not impact your Google rankings or the way you are seen in Google. This is specific to a Chrome and Firefox update that is coming in the future.
Google explained “After Chrome 91 is released, the
SharedArrayBuffer object without cross-origin isolation will no longer be functional. In practice, this means that Chrome users on your site may experience degraded performance similar to other situations where the
SharedArrayBuffer object is not supported.”