Skip to content
  • Texas | Arizona | Virginia | Idaho | Illinois
  • (888) 705-0930
  • info@therawragency.com
Facebook-f Twitter Instagram Linkedin-in
rawr logo short
  • Home
  • About
  • Solutions
    colorized icons 04
    B2B Marketing
    colorized icons 05
    B2C Marketing
    colorized icons 06
    Online Visibility Management
  • Industries
    colorized icons 07
    Healthcare
    colorized icons 08
    Manufacturing
    colorized icons 10
    Home Services
    colorized icons 09
    Professional Services (B2B)
    colorized icons 11
    Retail
  • Services
    colorized icons 01
    Brand Strategy
    • Graphic Design
    • Corporate Brand Identity
    • Sales Enablement
    • Editorial Calendar Management
    colorized icons 02
    Website Design
    • WordPress Website Development
    • Conversion Rate Optimization
    • eCommerce Development
    • Content Strategy & Copywriting
    colorized icons 03
    Digital Marketing
    • Digital Marketing Strategy
    • Search Engine Optimization (SEO)
    • Pay-Per-Click (PPC) Management
    • Content Marketing & Digital PR
    • Account Based Marketing (B2B)
    • Marketing Automation
    • Social Media Management
  • Blog
  • Contact
Let's Talk

Google clarifies the SharedArrayBuffer notification

  • March 19, 2021
  • General
  • Agency
Facebook
Twitter
LinkedIn
Email

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.

Google defines SharedArrayBuffer. Google has defined what a SharedArrayBuffer is by explaining, “SharedArrayBuffer is a JavaScript object to share a memory space across threads on a website. It was used by websites before the vulnerability called Spectre was found. However, because Spectre was a CPU level vulnerability and it’s unlikely to be fixed in the foreseeable future, browsers decided to disable the SharedArrayBuffer object.” As Search Engine Land’s Detlef Johnson accurately explained in our story earlier this week, starting “with version 91, planned to be released in late May 2021, Chrome will gate the SharedArrayBuffer object behind cross-origin isolation,” Google wrote.

The confusion. Many site owners, consultants and SEOs were confused by the messaging, which likely prompted Google’s response:

Incomprehensible GSC error emails reaching new heights today:#SharedArrayBuffers #COOP #COEP pic.twitter.com/v02I6nh6iX

— Joost de Valk (@jdevalk) March 15, 2021

I think it’s a false positive. I’ve pinged people at Google, but not received an update from them yet. My thinking is that it’s actually page speed measurements from @GoogleAnalytics that trigger this, and it actually doesn’t have something to do with SharedArrayBuffers.

— Joost de Valk (@jdevalk) March 15, 2021

Lot of people researching what SharedArrayBuffer is thanks to all those search console emails lol.

— Chuck-Fil-YEAY (@ChuckReynolds) March 15, 2021

How to find these issues. Google provided methods to find this SharedArrayBuffer issues listing these two options:

  1. Use Chrome DevTools and inspect important pages.
  2. (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:

  1. Determine where the SharedArrayBuffer object is used on your website.
  2. Decide if the usage is necessary.
  3. 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.”

The post Google clarifies the SharedArrayBuffer notification appeared first on Search Engine Land.


Source: IAB

Facebook
Twitter
LinkedIn
Email

Recent Blog Posts

9 Hidden Revenue Blockers Every CRO Needs to Eliminate

February 3, 2025

What Is B2B Appointment Setting?

November 29, 2024

Leveraging LinkedIn for Targeted Growth

November 12, 2024

Mastering B2B Prospecting: Key Strategies for Sales Success

November 4, 2024

Maximize Marketing ROI: How Cost per Lead Can Fuel Your Business Growth

June 13, 2024
View More
rawr logo short
Facebook-f Twitter Instagram Linkedin-in
Get In Touch
  • Texas | Arizona | Virginia | Idaho | Illinois
  • (888) 705-0930
  • info@therawragency.com
Send An Email

"*" indicates required fields

Copyright 2025 | The RAWR Agency, LLC. |

Sitemap | Privacy Policy

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.OkNo