Google drops its advice to test pages with JavaScript turned off
Summary
Google renders JavaScript, so for Google the better check is URL Inspection in Search Console, which shows the page after rendering. Turning JavaScript off was only ever a rough stand-in for that view.
The JavaScript-off view still answers a different question: what a crawler that does not run scripts receives. Google's own documentation says not all bots can, so keep checking that key templates carry their main content and links in the raw HTML.
Google deleted the “Design for accessibility” section from its JavaScript SEO basics page on March 4, 2026. The section told developers to preview a site with JavaScript turned off, or in a text-only browser such as Lynx. It said the text-only view could reveal content “which may be hard for Google to see, such as text embedded in images.” Search Engine Journal’s report counts the edit as the fifth change to that page since December, each one swapping a broad caution for narrower technical advice.
Google’s documentation changelog, as quoted by Search Engine Journal (SEJ), gave the reason: “The information was out of date and not as helpful as it used to be. Google Search has been rendering JavaScript for multiple years now, so using JavaScript to load content is not ‘making it harder for Google Search’. Most assistive technologies are able to work with JavaScript now as well.”
For Googlebot, that reasoning holds. The JavaScript-off preview was always a rough guess at what Google could see, and Search Console gives a direct answer instead: the URL Inspection tool shows what Googlebot sees after rendering. SEJ’s piece recommends that tool for JavaScript-heavy pages.
Googlebot is not the only crawler reading the page, though. The same Google documentation page, after the edit, still says server-side rendering or pre-rendering “is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript.” SEJ makes the same point: Google’s renderer improvements do not extend to other search engines and crawlers, which may not render pages the way Google does. Neither names those bots, so the safer assumption is that any crawler other than Googlebot, including the AI crawlers and fetchers behind answer engines, may read only the HTML the server sends.
In a made-up example, a retailer’s product template loads the description and specs with client-side JavaScript after the page arrives. URL Inspection shows the full product, so the page looks fine from Google’s side. With JavaScript turned off, the same URL is a header and footer around an empty container, and that empty container is all a non-rendering crawler receives.
What to do
Run both checks, because they answer different questions.
- Use URL Inspection in Search Console for Google’s view. It shows the rendered result that the JavaScript-off preview only approximated.
- Keep a raw-HTML check on your key templates for every other crawler. Confirm the main content is there, and that navigation uses
<a>elements with anhref, which Google’s page says is the only kind of link it can discover. A quick test is to fetch the page without a browser and search for a phrase from the body copy:
curl -s https://example.com/products/blue-widget | grep -c "phrase from the product description"A count of zero means the phrase only appears after JavaScript runs.
- Set the canonical in the HTML. Google’s page calls HTML the best place for it, and says that if JavaScript touches the canonical, it must set the same value as the original HTML.
- If key templates fail the raw-HTML check, server-side rendering or prerendering is the fix Google’s page still recommends. A Next.js case study from a government jobs aggregator shows what moving listing content into server-rendered HTML involves in one framework.