Something we read on Google’s pages gave us an idea and led us to add a new tool to our SEO set. What inspired it was the page on JavaScript and SEO. That Google article says the following;

When you design your site, think about the needs of your users, including those who cannot use JavaScript capable browsers (people using screen readers or mobile devices, for instance). One of the easiest ways to test how accessible your site is, is to preview it with JavaScript turned off or to view it in a text only browser such as Lynx.

Test Your Site With SEO Browser

SEO Browser

Note: if your site carries a nofollow tag, the tool will not connect to it.

Lynx Web Browser

Update: we have published the text only reader browser tool we called an important instrument for SEO. Our Lynx style web browser is ready to use.

We were working on an SEO browser some time ago. But; it has come a long way, and today it sees more or less what we see. It loads every file completely and probably records them that way in its databases. With the Evergreen version of Chromium, we believe it analyzes sites as accurately as it can.

Even though our SEO Browser does not focus purely on text, or where the tool we use for pure text is a different one, what we did in this SEO Browser work was to activate .js as well. Google, of course, loads .js and .css into its Evergreen browser and examines the page fully. Then it records the plain text into its database.

What Is Lynx?

When Google says test your sites with Lynx, what is this Lynx? Lynx is a text based browser.

What Is the Evergreen Browser Googlebot Uses?

Evergreen browsers are web browsers that update themselves automatically so the user is always on the latest version. Browsers of this kind are designed to keep supporting new features and security updates, which cuts down how much the user has to decide about updating. Googlebot, we can say, is continuously on the latest browser version.

A good SEO specialist keeps track of the latest browser releases as they land and checks the sites they work on against them. That check usually moves around the errors in the design. If a site is running a very old JS library, checking matters enormously.