JavaScript Rendering: A Common Content-Accessibility Risk

Scope note: This article explains the topic using public research and common engineering patterns. Retrieval, reranking, generation, and source-selection pipelines vary by product. Nothing here represents a disclosed universal ranking weight or a citation guarantee.

When primary content appears only after client-side JavaScript runs, some crawlers or parsers may receive an incomplete page; others can render it. Test actual accessibility instead of claiming that all AI crawlers ignore JavaScript.

Why this is an accessibility issue

Raw HTML, the rendered DOM, search-indexed content, and the content available to different AI products can differ. Risk depends on rendering architecture, resource access, timeouts, client-side routing, and the crawler.

How to verify

Compare the initial HTML with the rendered page and check whether the title, core answer, product facts, and internal links are present. Then review server logs and actual indexing or source-use results in the target product.

Practical implications for content teams

Prefer server rendering, static generation, or progressive enhancement for primary content.
Do not rebuild an accessible application merely for GEO.
Test Google Search and target AI products separately, with dates.

Boundary and conclusion

JavaScript rendering is a common diagnostic item, not a fatal issue for every site and crawler.

References

https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics

I use WordPress. Am I definitely fine?

WordPress renders server-side by default, so core content is usually in the initial HTML. But two scenarios require caution: lazy-loading or deferred-rendering plugins may cause some content to become JS-loaded; highly customized WordPress themes may introduce client-side rendering. Run the ten-second test to confirm.
Doesn’t Next.js support SSR by default?

Next.js supports multiple rendering modes, including SSR, SSG, and client-side rendering. Default settings vary by version and configuration. The key is confirming that your core content pages actually use SSR or SSG mode, rather than assuming “I use Next.js, so I’m fine.” The ten-second test is the most direct verification.
Besides body content, what else commonly gets hidden behind JS rendering?

Product spec tables (especially those loaded dynamically via components), user review modules, FAQ accordion panels, and pricing information — these are frequently JavaScript-loaded, and also frequently the content AI most wants to extract. Check each one.