What Is JavaScript SEO? Rendering, Indexing and Common Fixes

How Google processes JavaScript pages

A traditional HTML page arrives with its content already in place. A JavaScript application often sends an almost empty HTML shell and builds the page in the browser. Google handles this in stages:

1. Crawling: Googlebot requests the URL, checks robots.txt and downloads the initial HTML.
2. Rendering: the page waits for Google's Web Rendering Service, which runs a recent version of Chromium to execute JavaScript and produce the final page.
3. Indexing: Google reads the rendered HTML, extracts content and links, and stores the page in its index.

Links discovered in the rendered HTML are added back to the crawl queue, so poorly rendered pages can also hide the rest of your site.

The rendering queue

Executing JavaScript costs far more computing resources than reading plain HTML, so Google does not always render a page the moment it is crawled. Pages are placed in a rendering queue and processed when resources are available. Google says the wait is often short, but it can be longer, and anything that exists only after rendering is unknown to Google until then.

Content, links, titles and canonical tags present in the initial HTML are available immediately. Content that depends on rendering is available only after the page leaves the queue, and only if the scripts run successfully.

For a small blog this delay rarely matters. For a large e-commerce or news site that publishes thousands of URLs, or changes prices and stock often, waiting for rendering can mean new pages and updates take longer to appear in search. Putting critical content in the server response removes that dependency.

Server-side rendering versus client-side rendering

Compare what Googlebot receives first in each case:

<!-- Client-side rendering: initial HTML -->
<body>
  <div id="root"></div>
  <script src="/app.js"></script>
</body>

<!-- Server-side rendering: initial HTML -->
<body>
  <div id="root">
    <h1>Cotton Kurtas for Men</h1>
    <p>Breathable handloom kurtas in 12 colours.</p>
    <a href="/kurtas/blue-cotton/">Blue cotton kurta</a>
  </div>
  <script src="/app.js"></script>
</body>

Frameworks such as Next.js, Nuxt, SvelteKit, Astro and Angular support SSR or SSG. If you are new to how scripts change a page, our JavaScript fundamentals guide explains the DOM and rendering basics.

Common JavaScript SEO problems

• Links without real URLs: Google follows <a href="/page/"> links. Buttons or elements that navigate with onclick handlers are not crawled as links.
• Fragment-based routes: URLs like /#/products are treated as one page. Use the History API to create clean paths.
• Content behind interactions: Googlebot does not click tabs or "load more" buttons, so content that loads only after a click may not be indexed.
• Blocked resources: disallowing JavaScript or CSS files in robots.txt stops Google from rendering the page properly.
• Soft 404 errors: single-page apps often return a 200 status for missing pages. Return a real 404, or add a noindex tag through JavaScript on error views.
• Missing metadata: titles, descriptions and canonical tags set late by scripts may be ignored or conflict with the initial HTML.

Testing what search engines see

1. Use the URL Inspection tool in Search Console and run a live test to see the rendered HTML and a screenshot.
2. Compare "View page source" (initial HTML) with the browser's Elements panel (rendered DOM).
3. Disable JavaScript in your browser and check whether main content and links still appear.
4. Crawl the site with a crawler in JavaScript rendering mode and compare results with a plain HTML crawl.

These tools are described in our overview of SEO software and testing tools.

Search engines other than Google

Bing also renders JavaScript, but rendering support varies widely among other crawlers. Many social media preview bots and several AI crawlers read only the initial HTML. Server-rendered content is the safest way to reach all of them.

Rendering checks form part of the technical modules in the SkillNewton online search engine optimization course, where learners audit real JavaScript sites.

Common mistakes

• Assuming that because Google can render JavaScript, every page will be rendered and indexed quickly.
• Blocking script or stylesheet folders in robots.txt.
• Navigating with click handlers instead of standard anchor links with href values.
• Returning a 200 status code for "page not found" views in a single-page app.
• Testing only in a normal browser and never checking the rendered HTML Google sees.

Frequently asked questions