JavaScript-loaded content: check what is missing from raw HTML

In brief

Identify text that appears after JavaScript but is missing from the HTTP response. Google can render JavaScript, so this difference does not automatically make your content invisible. Focus on the main content, loading errors and interactions required to reveal it.

WarningGEO recommendations

What is it?

The browser displays substantially more words after JavaScript than the text extracted from the HTTP response.

Why check this signal?

The content depends on scripts loading and running. Google can render JavaScript, but a blocked script, failed API request or required interaction may prevent access. A crawler that does not execute those scripts receives only the initial HTML.

When it is NOT a problem

  • The main content is in the HTML and only interactive or personalized elements are added after loading.
  • The page is a private application screen with no indexing objective.
  • The difference consists of a few words or interface elements. A word count is a clue, not a measurement of indexed content.
Before
<section id="description"></section>
<!-- The description then depends on fetch() and JavaScript. -->
After
<section id="description">
  <p>Compare server HTML with JavaScript rendering.</p>
</section>

This example illustrates where to serve content. The scanner's controlled test then measures word counts in both versions and the related recommendation before and after the fix.

How to fix it

  1. Compare the text in the page source with the loaded DOM. Identify useful blocks missing from the HTTP response.
  2. Check JavaScript errors, API requests and content that requires a click or login.
  3. If those blocks need to be available in the initial response, load their data during server-side rendering or static generation (SSR/SSG).
  4. Run the analysis again to confirm the intended content is present in the raw HTML and still correct after JavaScript.
  5. Check indexing separately in Search Console: a complete DOM or a resolved alert does not prove that Google indexed the text.

An example measured with the Seogard crawler: See the SSR test before and after

Sources and verification

This scan checks what is missing from the raw HTML but appears in the JavaScript render

Is this issue on your site?

Is your main content in the raw HTML or added after JavaScript? Check both versions with the SSR checker. Account required, 14-day trial with no credit card.

Create your account and try it free for 14 days. No credit card. By continuing, I confirm that I own this site or have permission to analyze it.

  • No credit card
  • Account required · 14-day trial

What you get back

Main content available in the server response, with fewer JavaScript dependencies for reading it. This does not guarantee indexing or citation.

Check this signal with Seogard's SSR checker.

Frequently asked questions

Can Google index JavaScript-loaded content?

Yes, if it can retrieve and render the required resources. Content behind an interaction, authentication or failed scripts may remain inaccessible. A local render does not prove indexing.

Do missing word counts measure my visibility in AI answers?

No. They compare text extracted from HTML with text in the rendered DOM. Access methods vary across services and crawlers; this measurement does not predict citations.

Related rules

Title missing from raw HTML (JS-only)The title tag is missing from the raw HTML but filled in after JavaScript executes. Description missing from raw HTML (JS-only)The meta description exists only in the JavaScript render, not in the raw HTML. Missing llms.txtNo /llms.txt file detected. Speculative convention: its use by major LLMs is not confirmed to date (a proposal not adopted by Google/OpenAI). Mainly useful for documentation and agents.

Updated September 8, 2026