What is Shared Array Buffer? How it Works in SEO?

On 15 March, Google Search Console sent emails to some webmasters about the new Requirements for Shared Array Buffer subject and it was a new word for most people. Not only for SEO but also for junior developers, this is a new topic and there was so much confusion in the SEO community for these emails so that Google stopped this email and also released the clarification

How is a shared array buffer issue created on a website? And how you should resolve this in your website and how you can do it and if you get such notification or email for your website, then maybe from May 2021 some functions or features of your website do not work, so it is important for everyone to understand this issue.

You may find a client whose website has received such a message from Google. Or are you creating a website for which you get such a message from Google?

Whether it is a desktop, a laptop or a smartphone, or all kinds of electronic devices in which the Internet can be accessed, one thing that is common in this is the processors. In easy language is the CPU, which processes what is done to complete the task to run a program, hence it is called processor.

These processors create a kind of object called Shared Array Buffers to save memory temporally by performing a task. In this, some data is stored which can be shared with other tasks, this saves the time of the processor. Because the common element does not have to make them again and store them, this saves the time of the CPU and increases its speed.

Many years ago, computer scientists say that there is a weakness in CPUs, due to which programs can use any other program’s shared array buffers. The Weakness was named “SPECTRE“.

This was a serious vulnerability because suppose you are sitting on a tab in your phone’s browser by logging into your Net Banking account. And in the second tab, you are using a website in which SPECTRE Vulnerability is being used. So they can steal your net banking details by jumping from then on.

SPECTRE vulnerability becomes even more dangerous because, in a modern website, many different resources are used in a website. As fonts are coming from Google, the theme CSS is loading somewhere else, images CDN are loading from somewhere else. You have just your domain name.

If a free theme has a program in the edit javascript files that uses SPECTRE Vulnerability and steals your payment processor data. So the hackers could not take advantage of this weakness, so the web browsers had disabled the shared array buffers for the website.

But in May 2021, Chrome is going to enable Shared Array Buffers with some conditions from 2021 and Firefox has already enabled this feature.  This is the condition that a file with the same domain will be allowed to use shared array buffers

If you get an email from Google Shared Array Buffers, what do you have to do?

This email from Google means that somewhere in your website, an element is happening to it that is using shared array buffers. Either you have done an asset that is using Shared Array Buffers or has a theme, or an element, or plugin that is using shared array buffers.

You will have to check your website and find out which one is a plugin or an asset that is using Shared Array Buffers. And whatever asset, theme, font, and icon pack you are using, they have to be removed from your website. Or enable cross-origin isolation in your website, then only these assets will be able to do that and till then you will not make that asset in your website.

You should know how to find the asset using the shared array buffer in your website, and it is running on the error and its method is very simple.

Open your website in the Chrome browser and open the Chrome devtool panel by pressing the F12 button; you will have to go to the Console tab. And then there will be a one-way warning show in it, in which the Shared Array Buffers Mention will be there and they can also see a file under it because of which this error showing.

By checking that file, you can find out which is that plugin or Theme or Icon Pack or which is the asset that is doing this error generate, and then you can solve this error by removing it from your website.

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: