Google Updates JavaScript SEO: Accessibility Advice Removed

```json
{
  "alt": "Google logo overlaying colorful source code on a dark background, indicating technology and programming.",
  "caption": "The iconic Google logo interacts with vivid lines of code, symbolizing the tech giant's deep integration into the world of programming and development.",
  "description": "This image features the Google logo prominently displayed over a background of colorful, glowing source code. The code, in shades of yellow, red, blue, and orange, appears on a black screen, creating a high-contrast visual effect. The composition highlights Google's connection to technology, programming, and innovation. Keywords: Google, logo, source code, technology, programming, innovation."
}
```

I recently discovered that Google has adjusted its JavaScript SEO guidelines by removing the ‘design for accessibility’ section. This decision was made because the advice was deemed outdated. Nowadays, Google handles JavaScript smoothly.

When Google announced the change, they explained the section was no longer as useful as it once was. Previously, they warned that JavaScript might obscure content from Google, but clearly, that’s not an issue anymore.

The Old Advice. Here’s what the original guidance stated:

“Design for accessibility: Create pages for users, not just search engines. When designing your site, consider users who might not use a JavaScript-capable browser, like those with screen readers or less advanced mobile devices. Test your site’s accessibility by viewing it with JavaScript turned off or in a text-only browser like Lynx. This can help identify content hard for Google to see, such as text in images.”

Why It Was Removed. Google clarified:

  • “The information was outdated and less helpful. Google Search has successfully rendered JavaScript for years, so using it for content loading doesn’t hinder visibility.”
  • “Most assistive technologies can now handle JavaScript as well.”

The Importance. Even though Google is adept at processing JavaScript, it’s still critical to verify what Google Search sees. I recommend using the URL inspection tool within Google Search Console to ensure everything checks out.

Remember, while Google and probably Microsoft Bing manage JavaScript efficiently, some emerging AI engines might not render it as effectively.


Inspired by this post on Search Engine Land.


crushpress.ai community screenshot

FAQs

What change did Google make to its JavaScript SEO guidelines?

Google removed the design for accessibility section because the guidance was outdated. The article notes that Google Search has rendered JavaScript for years, and most assistive technologies can now handle JavaScript.

Why was the accessibility advice removed?

The information was outdated and less helpful. Google Search has successfully rendered JavaScript for years, and most assistive technologies can now handle JavaScript.

What tool does the author recommend using to verify what Google sees?

Use the URL inspection tool within Google Search Console to verify how Google views your page. This helps ensure everything checks out.

What does the article say about other engines?

The article notes that Google and probably Microsoft Bing manage JavaScript efficiently, but some emerging AI engines might not render it as effectively. This highlights the need to verify JavaScript visibility across engines.

What was the original guidance before removal?

The original guidance advised designing for accessibility and testing with JavaScript turned off or in a text-only browser like Lynx. This was to identify content hard for Google to see.

Comments

Leave a Reply

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