Question 1

What is Google's two-pass index?

Accepted Answer

Google indexes JavaScript apps in two passes. The first pass reads the initial HTML response from the server and discovers links and metadata. The second pass executes JavaScript on a render budget and re-indexes whatever the rendered DOM contains. Pages that exceed the budget — slow JS, hydration errors, large bundles — never get their second-pass content indexed and rank only on whatever the first-pass HTML happened to contain.

Question 2

What is the render budget and how do I measure it?

Accepted Answer

The render budget is the time Googlebot allocates to executing JavaScript before giving up on a page. It is not a publicly fixed number; it is a function of resource priority, crawl health, and historical render success. In practice, pages whose hydration finishes in under two to three seconds are reliably indexed; pages that take longer are at material risk. Our JavaScript SEO scanner measures the gap between first contentful paint and DOM settlement to flag at-risk routes.

Question 3

Is server-side rendering always better than client-side rendering for SEO?

Accepted Answer

For content pages, yes. SSR or static generation produces real HTML on the first pass, so Google indexes the content without depending on the render budget. CSR works for authenticated apps where SEO does not matter — dashboards, internal tools, single-customer portals — but is a structural liability for any page meant to rank. The audit tells you which routes need to migrate to SSR or SSG most urgently.

Question 4

What is the difference between SSR, SSG, and ISR?

Accepted Answer

SSR (server-side rendering) generates HTML per request on the server, so every page load runs through the framework's render path with fresh data. SSG (static site generation) generates HTML at build time, so requests are served from cache or CDN. ISR (incremental static regeneration) is a Next.js hybrid: pages are statically generated but revalidated on a schedule. All three produce real HTML on the first pass. The right choice depends on data freshness needs and traffic patterns.

Question 5

Does Googlebot run all JavaScript?

Accepted Answer

Yes, but on the second-pass schedule and with constraints. Googlebot uses a recent Chromium that supports modern JavaScript features. Network requests, fetch calls, and dynamic imports all run. The catches are timing — render budget can cut execution short — and certain APIs that are unavailable or behave differently from a standard browser session, including some autoplay, user-gesture-gated APIs, and certain storage APIs.

Question 6

What is hydration and why does it affect SEO?

Accepted Answer

Hydration is the process where a JavaScript framework attaches event handlers and state to server-rendered HTML, turning a static page into an interactive app. It matters for SEO because hydration mismatches — where the server-rendered HTML differs from the client render — can cause the framework to replace the server output. Google may have already cached the server version. The result: snippets and indexed content show fallback values that no longer match the live page.

Question 7

How do I know if my JavaScript app is being indexed correctly?

Accepted Answer

Three signals. Search Console's URL Inspection tool shows the indexed snapshot — compare it to the live rendered DOM. Search Console's Coverage report flags discovered-not-indexed and rendered-no-content pages. The DeepAudit AI real browser SEO audit reproduces both passes locally and gives you the diff in 60 seconds, including which routes are at render-budget risk and which are CSR-only.

Question 8

What about Core Web Vitals for JavaScript apps?

Accepted Answer

Core Web Vitals are tightly coupled with rendering strategy. SSR and SSG help LCP because real content paints before JavaScript executes. Hydration cost hurts INP because the page is unresponsive while React, Vue, or Angular is mounting. CLS suffers when images render without explicit dimensions and dynamic content shifts the layout. Every Core Web Vitals audit run by DeepAudit AI captures these signals under field conditions.

How Google actually indexes JavaScript

JavaScript SEO has its own physics