Google JavaScript problems
The Fixing JavaScript for Google,
as documented
What Google documents about fix javascript problems, in its own words. Verified from Google's page on 2026-10-09.
Google's guide is a checklist for JavaScript issues that can keep content out of Search. This page lists its statements with the exact wording from Google.
What Google says
| Topic | What Google says | Source |
|---|---|---|
| Resources not fetched | “Googlebot and its Web Rendering Service (WRS) component continuously analyze and identify resources that don't contribute to essential page content and may not fetch such resources.” | Google docs Verified 2026-10-09 |
| Analytics | “Client-side analytics may not provide a full or accurate representation of Googlebot and WRS activity on your site.” | Google docs Verified 2026-10-09 |
| Monitoring | “Use the crawl stats report in Google Search Console to monitor Googlebot and WRS activity and feedback on your site.” | Google docs Verified 2026-10-09 |
| Testing | “To test how Google crawls and renders a URL, use the Rich Results Test or the URL Inspection Tool in Search Console.” | Google docs Verified 2026-10-09 |
| Soft 404s | “When a SPA is using client-side JavaScript to handle errors they often report a 200 HTTP status code instead of the appropriate status code.”Google offers two fixes: redirect to a URL that returns a 404 status, or add or change the robots meta tag to noindex. | Google docs Verified 2026-10-09 |
| Permissions | “Expect Googlebot to decline user permission requests.” | Google docs Verified 2026-10-09 |
| URL fragments | “The AJAX-crawling scheme has been deprecated since 2015, so you can't rely on URL fragments to work with Googlebot.” | Google docs Verified 2026-10-09 |
| History API | “We recommend using the History API to load different content based on the URL in a SPA.” | Google docs Verified 2026-10-09 |
| Storage | “Local Storage and Session Storage data are cleared across page loads.” | Google docs Verified 2026-10-09 |
| Cookies | “HTTP Cookies are cleared across page loads.” | Google docs Verified 2026-10-09 |
| Caching | “Googlebot caches aggressively in order to reduce network requests and resource usage. WRS may ignore caching headers.”Google recommends content fingerprinting, such as main.2bb85551.js, to avoid outdated JavaScript or CSS. | Google docs Verified 2026-10-09 |
| Connections | “It does not support other types of connections, such as WebSockets or WebRTC connections.”Google says to provide an HTTP fallback. | Google docs Verified 2026-10-09 |
| Web components | “WRS flattens the light DOM and shadow DOM.” | Google docs Verified 2026-10-09 |
| JavaScript paywalls | “This isn't a reliable way to limit access to the content.”Google is describing paywalls that include the full content in the server response and hide it with JavaScript. | Google docs Verified 2026-10-09 |
How to apply it
A checklist built only from the guidance in Google's page.
- Test the URL with the Rich Results Test or URL Inspection and read the rendered DOM and console output.
- Make error views return a real 404 or carry noindex.
- Use the History API, not URL fragments, for separate views.
- Do not rely on cookies, Local Storage or Session Storage to serve content.
- Fingerprint your JavaScript and CSS file names, and provide an HTTP fallback for WebSockets or WebRTC features.
Questions
Can I rely on cookies or local storage for content?
Google says WRS does not retain state across page loads: Local Storage, Session Storage and HTTP cookies are cleared.
Can I use URL fragments for different views?
Google says you can't rely on them with Googlebot, and recommends the History API.
How do I stop error pages in a single-page app being indexed?
Google gives two strategies: redirect to a URL that responds with a 404 status code, or add or change the robots meta tag to noindex.
Where can I see Googlebot activity?
Google points to the crawl stats report in Search Console, and says client-side analytics may not show it fully or accurately.
How current is this page?
Every quote was read from Google's page on 2026-10-09. The page showed "Last updated 2025-12-18 UTC". Google can change its documentation, so treat the linked page as the final word.
Sources
- Fix Search-related JavaScript problems (Google Search Central), read on 2026-10-09
Let Balzac write the articles.
Type your website. Balzac finds the searches you can win, writes articles built to rank on Google and get cited by ChatGPT, and publishes them for you.
3 free articles · No card needed