Meta description filled by JavaScript: does Google read the right one?

In brief

Your meta description exists only in the JavaScript render, not in the raw HTML that Google reads first, so your optimized description may not feed the snippet. Impact is mostly on click-through, rarely on ranking. Render the meta description server-side.

InfoGEO recommendations

What is it?

The meta description exists only in the JavaScript render, not in the raw HTML.

Why it hurts SEO and AI

The Google snippet and AI reading are mostly based on the raw HTML: your optimized description is invisible there. CTR impact more than ranking.

When it is NOT a problem

  • A correct meta description is already present in the raw HTML and the JavaScript only duplicates or confirms it.
  • Google often rewrites the snippet from page content based on the query anyway: the stakes are moderate.
  • The page is not meant to be indexed (app interface, back office): no snippet to polish.
Before
<!-- Raw HTML returned by the server -->
<head>
  <title>Trail running shoes</title>
  <!-- meta description injected later by JS -->
</head>
After
<!-- Raw HTML returned by the server -->
<head>
  <title>Trail running shoes</title>
  <meta name="description" content="Our selection of trail running shoes, field-tested.">
</head>

On the left, the snippet depends on JavaScript; on the right, the description is already in the raw HTML that Google reads first.

How to fix it

  1. View the raw page source (Ctrl+U) and look for the meta name=description tag: if it is absent or empty, it is injected by JavaScript.
  2. Move meta description generation to server-side rendering (SSR/SSG) instead of a client-side add-on after load.
  3. Make sure it is unique and relevant per page, not a single generic global value.
  4. Re-crawl the page to confirm the description is now in the raw HTML.

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

Is this issue on your site?

Is your meta description in the source code, or only after JavaScript? Enter a URL: Seogard compares the raw HTML and the render and tells you what Google actually reads. Free, no credit card.

By clicking Scan, I certify that I own this site or have permission to crawl it.

  • No credit card
  • Result in ~30 s

What you get back

Your description is present in the raw HTML, so actually read by Google and AI systems.

Seogard catches this regression automatically — through its SSR checker.

Frequently asked questions

Does Google use a meta description added by JavaScript?

It may see it on its second rendering pass, but it often builds the snippet from the first crawl of the raw HTML. It is better to have it there from the start.

Is this a serious SEO problem?

No, the impact is mostly on click-through rate in results, not on ranking. It is a hygiene improvement, not a critical emergency.

Related rules

Content visible only after JavaScriptMost of the body text only exists after JavaScript runs (absent from the raw HTML). AI crawlers (ChatGPT, Perplexity, Claude) read the raw HTML and will probably never see this content. Title missing from raw HTML (JS-only)The <title> is missing from the raw HTML sent by your server but filled in after JavaScript loads. Google may see it with a delay and LLMs (ChatGPT, Perplexity, Claude) probably never see it — they mostly read the raw HTML. Fix: render the title server-side (SSR). 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 July 10, 2026