Our team of SEO Web Design gurus are standing by to assist you achieve your online marketing goals.


SEO Web Design, LLC aims to improve business by delivering effective solutions based on innovative technologies and professional designs. Discover the variety of services we offer and convince yourself on the basis of the latest works that we've done. We love building fresh, unique and usable websites optimized specifically for your niche.

Responsive Web Design

SEO / SEM / Social Media

Conversion Rate Optimization

Email Marketing

Online Presence Analysis

Web Hosting
SEO Web Design / SEO  / Google clarifies the SharedArrayBuffer notification

Google clarifies the SharedArrayBuffer notification

Earlier this week, Google sent out a notice through Google Search Console with SharedArrayBuffer warnings[1] 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[2] 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:

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

  1. Use Chrome DevTools[6] and inspect important pages.
  2. (Advanced) Use the Reporting API[7] 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[8].

Why we care. If you received this message, we recommend you review both Google’s clarification blog post[9] and our story here on Search Engine Land[10]. 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.”

About The Author

Barry Schwartz a Contributing Editor to Search Engine Land and a member of the programming team for SMX events. He owns RustyBrick[11], a NY based web consulting firm. He also runs Search Engine Roundtable[12], a popular search blog on very advanced SEM topics. Barry’s personal blog is named Cartoon Barry[13] and he can be followed on Twitter here.


  1. ^ SharedArrayBuffer warnings (
  2. ^ accurately explained (
  3. ^ @GoogleAnalytics (
  4. ^ March 15, 2021 (
  5. ^ March 15, 2021 (
  6. ^ Chrome DevTools (
  7. ^ Reporting API (
  8. ^ enabling cross-origin isolation (
  9. ^ clarification blog post (
  10. ^ here on Search Engine Land (
  11. ^ RustyBrick (
  12. ^ Search Engine Roundtable (
  13. ^ Cartoon Barry (

Powered by WPeMatico

Search Engine Land is the leading industry source for daily, must-read news and in-depth analysis about search engine technology.