Yes. Google renders JavaScript and indexes content that only appears after execution. The question is worth asking anyway, because “can” and “reliably does” are different, and the gap between them is where sites lose pages.
How it works
Processing happens in two passes rather than one.
- Crawl. The URL is fetched and the initial HTML is read. Links found here are queued immediately.
- Render. The page is placed in a queue, executed in a browser environment, and the resulting DOM is indexed.
The delay between the two is the whole issue. Server-rendered content is available at step one; JavaScript-dependent content waits for step two, which may be minutes or considerably longer.
What this means in practice
- JavaScript sites can rank. Plenty do.
- They are indexed more slowly, which matters for news, stock and anything time-sensitive.
- Discovery is slower, because links that only exist after rendering are found in the second pass.
- Failures are silent. If rendering does not complete, there is no error — the content simply is not there.
Where rendering does not save you
- Content requiring an interaction. Rendering executes scripts; it does not click, scroll or type. See JavaScript content not indexed.
- Links that are not anchors. A click handler is not followed regardless of rendering. See JavaScript links.
- Blocked resources. If the scripts are disallowed in robots.txt, rendering cannot complete.
- Slow or failing requests. Rendering does not wait indefinitely for a chain of API calls.
Other search engines
Rendering capability varies, and several handle JavaScript far less completely than Google. If traffic from other engines matters to you, or if AI answer engines are becoming a source, server-rendered HTML is the safer position — it works everywhere without depending on anyone’s render queue.
The practical conclusion
Do not avoid JavaScript. Do make sure anything you need indexed exists in the initial HTML, and that navigation is built from real anchors.
That combination gives you the framework you want and removes the entire class of rendering risk. See server-side vs client-side rendering.
Frequently asked questions
How long does rendering take?
There is no published figure and it varies. Treat it as an unpredictable delay rather than a fixed cost.
Does rendering use an old browser?
No — it uses a current evergreen Chromium. Modern syntax is not the problem it once was.
How do I check what was rendered?
URL Inspection in Search Console shows the rendered HTML Google produced, which is the authoritative view. See rendered HTML SEO audit.
Is server-side rendering always better?
For content that must be indexed, it removes risk. For interactive functionality after load, client-side is fine.
Consulting CTA
If your JavaScript application is not being indexed as expected, book an SEO consultation. See also JavaScript SEO.