Fix JavaScript Rendering for SEO

If your important content only appears after JavaScript runs, you are gambling on a render queue that Google may delay for days and that AI crawlers skip entirely. This guide shows you how to detect JavaScript rendering gaps, choose between SSR and CSR, and ship content that Google and AI assistants can actually read.

5 min read7 sectionsJune 22, 2026

Kostadin Stamboliev

Founder and Imaginator

LinkedIn

Founder and Imaginator at Pineido. Practitioner across IT consulting, app and web development, technical SEO, and AI / automation. Ships production code in 30-day sprints with fixed scope and clear ownership.

Why JavaScript rendering breaks SEO

When you build a site as a single-page app (React, Vue, Angular) with client-side rendering, the server sends a near-empty HTML shell: one div and a script tag. The browser then downloads JavaScript, runs it, and paints the content. A human with a fast device never notices. Crawlers do.

Google processes pages in stages: crawl, render, index. Critically, it does not run your JavaScript in the same pass that it reads your HTML. The raw HTML is read first, and anything that exists only after JavaScript runs (product copy, article body, internal links, structured data) goes into a separate rendering queue. Until that queue clears, Google is indexing your empty shell. That delay is the whole problem, and it gets worse the deeper a page sits in your site.

SSR vs CSR vs static: what each one means for crawlers

There are four practical rendering strategies, and they are not equal for SEO.

Client-side rendering (CSR): the browser builds everything. Weakest for SEO. Next.js's own docs say CSR is not recommended when you need a page indexed. Fine for dashboards and logged-in views you never want in search.

Server-side rendering (SSR): the server builds full HTML on each request. Excellent for SEO because content arrives complete on the first crawl, no render queue required.

Static site generation (SSG): full HTML is built once at deploy time and served from a CDN. Excellent for SEO and the fastest to load. Best for marketing pages, docs, and blogs that change rarely.

Incremental static regeneration (ISR): static pages that quietly rebuild on a schedule. A good middle ground for content that updates often but not every second.

The modern pattern is hybrid: pick the right strategy per route rather than one mode for the whole app. React Server Components in the Next.js App Router make server-rendered HTML the default and let you opt into client interactivity only where a component truly needs it.

AI crawlers do not render JavaScript at all

Here is the part that surprises teams in 2026. Google will eventually render your JavaScript. The AI crawlers feeding ChatGPT, Claude, and Perplexity will not.

A widely cited Vercel and MERJ study tracked over 500 million GPTBot fetches and found zero evidence of JavaScript execution. GPTBot downloads JavaScript files some of the time, and ClaudeBot fetches them more often, but downloading a file is not the same as running it. They read JavaScript as text, they do not execute it. The same holds for OAI-SearchBot, Claude-SearchBot, PerplexityBot, and Meta's crawler.

The practical effect is binary. If your content lives in the initial HTML, AI assistants can quote it. If it only appears after JavaScript runs, you are invisible to them, no partial credit. The one exception is Google-Extended, which inherits Google's headless-Chromium pipeline and can render. So a pure-CSR page can rank on page one of Google and still be a blank shell to ChatGPT, Claude, and Perplexity at the same moment.

How to detect a JavaScript rendering gap in 10 minutes

You do not need to be a developer to find the gap. Run these three checks on any important page.

  1. View the raw source. Press Ctrl+U (or use view-source: in the address bar). Use Ctrl+F to search for a sentence of your real body copy, your H1, or a product name. If it is missing and you only see empty divs and script tags, your content is JavaScript-dependent.
  2. Disable JavaScript. In Chrome DevTools, open the Command Menu (Ctrl+Shift+P), type Disable JavaScript, then reload. Anything that vanishes is at risk in the rendering gap and is invisible to AI crawlers.
  3. Use Search Console URL Inspection. Run Test Live URL, then open View Crawled Page and the HTML tab to see the DOM after Googlebot rendered your JavaScript. Search it for your key content. Also check the Page Resources tab for blocked or failed files and the JavaScript console messages for errors. A blank rendered screenshot means the render failed outright, usually a script error or a blocked resource.

Common failure modes worth checking

Most rendering problems come from a short list of culprits:

Content that loads only on interaction. If text appears only after a click, a hover menu, or a Load More button, crawlers will not trigger it. Put it in the initial DOM and hide it with CSS instead.

Blocked JS or CSS in robots.txt. If Google cannot fetch the files, it cannot build the page.

Runtime-injected noindex or canonical tags. JavaScript that sets these after load is risky; Google reads the initial tags first.

Soft 404s. With client-side routing, a missing URL often still returns HTTP 200. Google's December 2025 documentation update clarified that pages returning non-200 status codes may skip JavaScript rendering entirely, so make sure real 404s return a 404.

Slow or broken hydration. WRS uses a render budget measured in seconds; design for content to be present within about 5 seconds. An uncaught JavaScript error can freeze the page in a half-rendered state, and Google may index it exactly as broken.

How to fix it: choose the right strategy, skip the old workarounds

The durable fix is to put real content in the initial HTML response.

For a new build, use a framework with first-class server rendering: Next.js, Nuxt for Vue, SvelteKit, or Astro for content-heavy sites that ship near-zero JavaScript by default. Server-render or statically generate every page you want found, and reserve CSR for genuinely private, interactive views.

For a legacy SPA you cannot rewrite yet, prerendering is the pragmatic bridge. Note that Google's old Rendertron was archived back in 2022, and Google now treats dynamic rendering (serving bots a different prerendered version) as a workaround, not a long-term solution, because you end up maintaining two versions of the site. Managed services like Prerender.io still work and start around $49/month for roughly 25,000 renders, and build-time tools like react-snap generate static HTML for content that does not change between deploys. These buy you time, but the real answer is a real server-rendered architecture.

Where Pineido fits

If your view-source is empty, your traffic is soft, and you are starting to disappear from AI answers, this is exactly the kind of scoped, measurable problem we fix on a fixed-price 30-day sprint. A JS-rendering cleanup sprint audits every key template for the rendering gap, moves your indexable content into the initial HTML through SSR or static generation, repairs status codes and blocked resources, and verifies the result in Search Console and against raw-HTML AI-crawler checks. You get a clear before-and-after on what Google and AI assistants can actually read, with no open-ended retainer.

Get operations insights weekly

Join service-business operators who get one actionable insight on ops, automation, and growth every week.

Checking that you're human. You can send in a moment.

No spam. Unsubscribe anytime.

You’re subscribed! Look for our next issue in your inbox.

Frequently asked questions

Does Google render JavaScript for SEO?

Yes, but on a delay. Google crawls your raw HTML first, then queues the page for a separate rendering pass using a headless Chromium service. That gap can be seconds, hours, or days, and during it Google only sees what was in your initial HTML. Server-side rendering or static generation removes the wait by delivering full content on the first crawl.

Can ChatGPT, Claude, and Perplexity read JavaScript-rendered content?

No. Research tracking hundreds of millions of crawler fetches found no evidence that GPTBot, ClaudeBot, or PerplexityBot execute JavaScript. They read your raw HTML only. If your content appears after JavaScript runs, it is invisible to these AI assistants. Google-Extended is the exception because it uses Google's rendering pipeline.

What is the difference between SSR and CSR for SEO?

With server-side rendering (SSR) the server sends complete HTML, so crawlers see your content immediately. With client-side rendering (CSR) the browser builds the page from JavaScript, so crawlers initially see an empty shell. SSR (and static generation) is strongly preferred for any page you want indexed or quoted by AI; CSR is fine only for private or non-indexed views.

How do I check what Google actually sees on my page?

Use three quick checks. Press Ctrl+U to view raw source and search for your real content. Disable JavaScript in Chrome DevTools and reload to see what vanishes. Then run the Search Console URL Inspection tool, use Test Live URL, and open the HTML tab to see the rendered DOM plus any blocked resources or console errors.

Is dynamic rendering still recommended for SEO?

No. Google treats dynamic rendering (serving crawlers a separate prerendered version) as a workaround, not a long-term solution, and its own Rendertron tool was archived in 2022. It forces you to maintain two versions of the site. Use true server-side rendering or static generation instead. Managed prerendering like Prerender.io is acceptable only as a temporary bridge for legacy SPAs.

My pages rank on Google but get no AI traffic. Why?

This is the classic JavaScript rendering gap. Google renders your JavaScript and ranks the page, but AI crawlers do not run JavaScript, so the same page is a blank shell to ChatGPT, Claude, and Perplexity. Moving your content into the initial HTML through SSR or static generation makes it visible to both at once.

Ready to ship?

Tell us where you are stuck. We will review it and send a focused recommendation within one business day.