Does Content on a JavaScript Site Reach Crawlers?

Tomohiro Iida · Published July 2, 2026 · Updated July 2, 2026

If a JavaScript site renders its content after the page loads, and that content isn't present in the initial HTML, search engines and AI sometimes never read it.

Key takeaways

A site that renders its content with JavaScript after the page loads can go unread by search crawlers and AI if that content is missing from the initial HTML — the HTML the server returns first.
Check by reading the raw HTML with curl, checking the rendered version in Search Console's URL Inspection, and using the Rich Results Test as a supporting check.
If the content is not getting through, moving key pages to SSR or SSG so the content is present in the initial HTML is a strong fix. Re-verify after making the change.

01. Conclusion

A site that renders its content with JavaScript after the page loads can go unread by search crawlers and AI if the initial HTML — the HTML the server returns first — doesn't include that content. You can check whether your content is getting through with two methods: reading the raw HTML with curl, and checking the rendered result in Search Console's URL Inspection.

02. What this checks for

Whether the content of key pages is present in the initial HTML
If it is not, whether crawlers are still able to retrieve it after rendering

03. Background: rendering approaches

Where the content gets assembled changes how well it reaches crawlers.

Approach	How the content is assembled	How well it reaches crawlers
SSR / SSG	The server returns HTML that already includes the content	Reaches crawlers reliably
CSR	JavaScript in the browser renders the content	The initial HTML may lack the content, so it may not reach crawlers

Search crawlers sometimes render pages, but with delays and limits. Some AI crawlers do not execute JavaScript at all (check the latest information before you publish).

04. How to check (three steps)

1. Check whether the initial HTML includes the content (curl)

Check whether a distinctive line of the page's content is present in the raw HTML, before JavaScript runs.

Example: curl -s https://example.com/target-page | grep -o 'a distinctive line of the content'

Match found: the initial HTML includes the content (reaches crawlers more reliably)
No match: the page may depend on JavaScript rendering (check the next step)

You can check the same way whether structured data (JSON-LD) is present in the initial HTML.

Example: curl -s https://example.com/target-page | grep -o 'application/ld+json'

2. Check the rendered version (Search Console URL Inspection)

Inspect the URL in Search Console's URL Inspection tool and check the rendered HTML and screenshot under "Crawled page."
If the content is visible there, Google's URL Inspection was able to see the content after rendering, at the time of the check.

Button names and navigation in the tool can change over time — operate it using the current UI.

3. Supporting check with the Rich Results Test

The Rich Results Test lets you check the rendered HTML and how structured data is recognized. Here too the UI can change, so use the current screen.

If you're not sure whether your content is reaching crawlers, Netsujo SIGNAL's free web diagnostic is one place to start. We turn the findings into deliverables covering HTML structure, structured data, and measurement. It does not guarantee search rankings or AI citation.

Get content, structured data, and measurement fixed end to end

05. Common causes and fixes

Rendering with CSR only: Move key pages to SSR or SSG so the initial HTML includes the content.
Content that only expands on click (an accordion, for example): Content that depends on a click is unreliable to retrieve. Keep it present in the HTML and toggle it with CSS instead — content that JavaScript inserts into the DOM only after a click may not be retrieved.
Content that loads later via infinite scroll: Keep important content in the initial view rather than loading it later.

06. Conditions for shipping to production

Check the rendering approach (e.g. in Next.js) page by page.
After a change, re-verify with curl and URL Inspection that the content is now in the initial HTML.

07. Official documentation

Google Search Central (JavaScript SEO / rendering)
Each AI service's crawler specification (check the latest source before publishing, since JavaScript execution support varies)

Frequently asked questions

Does CSR (client-side rendering) always mean a page won't get indexed?: Not necessarily. Search crawlers sometimes render a page and can retrieve the content after rendering, but this comes with delays and limits, so it isn't certain. Having the content present in the initial HTML makes it more likely to get through.
Do AI crawlers execute JavaScript?: Some do and some don't, and it varies by provider and over time. Crawlers that don't execute JavaScript may fail to read content missing from the initial HTML. Check each service's official documentation for current behavior.
Is content hidden in an accordion read?: If the content is present in the HTML and only toggled with CSS, it can be retrieved. Content that JavaScript inserts into the DOM only after a click is less reliable to retrieve. It's safer to keep important content present in the HTML.
If our content is not getting through, should we move to SSG?: SSR and SSG are strong options because they make it easier to include content in the initial HTML. You don't need to change every page at once — checking the rendering approach page by page and prioritizing the pages where content isn't getting through is a practical way to proceed. Re-verify with curl and URL Inspection after any change.
What does Netsujo SIGNAL do in this area?: Based on a check of your public information, we diagnose whether your content is present in the initial HTML, and turn the findings into deliverables covering HTML structure, structured data, and measurement. Production implementation can be handled in-house, by an existing agency, or by a partner engineer of your choosing. It does not guarantee search rankings or AI citation.