SaaS SEO · Technical SEO
JavaScript SEO: what Google really sees of your SaaS
JavaScript SEO is the set of practices that let Google crawl, render and index a site whose content or navigation depends on JavaScript. Google can run JavaScript, but in three steps (crawling, rendering, indexing) and with rendering placed in a queue. On a SaaS built with React, Vue or Angular, the risk is not being ignored: it is that links, tags or whole pages only appear in a version Google processes later, or never.
Franck Gordi
· 9 min read
Crawling
Rendering
Indexing
Key takeaways
- Google processes a JavaScript app in three phases, crawling, rendering then indexing, and rendering may wait a few seconds or longer.
- Google only discovers links that are a elements with an href attribute: fragment-based # routing prevents that discovery.
- A noindex in the original HTML may stop Google from running the JavaScript, so removing it later by script is not reliable.
- Google calls dynamic rendering a workaround and recommends server-side rendering, static rendering or hydration instead.
- According to Google, not all bots can run JavaScript: server-side rendering remains advisable for speed and compatibility.
How does Google process a JavaScript app?
Google's JavaScript SEO basics documentation describes three phases. Googlebot first fetches the URL after checking robots.txt, then parses the HTML response for other links. Pages returning 200 are then placed in a render queue, where a headless Chromium runs the JavaScript. The rendered HTML is finally used for indexing and for discovering new links.
Google pipeline
Three phases, two versions of the same page
- Crawling
- Googlebot reads robots.txt, fetches the initial HTML and extracts URLs found in href attributes. Blocked files will not be rendered.
- Render queue
- Every 200 page enters it, with or without JavaScript. It may stay there a few seconds, sometimes longer, depending on Google's resources.
- Rendering
- A headless Chromium runs the JavaScript. Content, links and tags added at this stage only exist from that point on.
- Indexing
- Google indexes from the rendered HTML and adds the new links it finds there to the crawl queue.
The consequence for a SaaS is simple: anything that only exists in the rendered version depends on an extra step. A 404 page may never be rendered at all, since Google says rendering might be skipped for non-200 status codes.
Client-side, server-side or static rendering: which to choose?
Google does not penalise client-side rendering, but it notes that server-side or pre-rendering is still a great idea: the site is faster for users and crawlers, and not all bots can run JavaScript. For a SaaS, the healthiest split often separates pages meant to rank (marketing site, blog, documentation, integrations) from the logged-in app, which is not meant to be indexed.
Dynamic rendering, which serves a pre-rendered version to bots only, is no longer a target. Google's page on dynamic rendering calls it a workaround that is not recommended, and points to server-side rendering, static rendering or hydration.
JavaScript errors that hide your pages
Diagnosis
Four common errors on a JavaScript app
- # fragment routing
- Google only discovers a elements with href and asks you to use the History API. Content loaded from a fragment is not a page for Google.
- Soft 404 in single-page apps
- Client routing returns 200 for a missing page. Fix: redirect to a URL that returns 404, or add noindex to the error page.
- Canonical rewritten by script
- JavaScript must not change the canonical from the original HTML. Several conflicting canonical tags lead to unexpected results.
- Initial noindex removed later
- Google may not run the JavaScript of a noindex page. A page to be indexed must not carry noindex in its original code.
Links that are not links
A button with a click handler, a clickable div or navigation driven entirely by app state are not links for Google. The same mechanism breaks lists: it is detailed in our article on SEO pagination, where a pure JavaScript "Load more" button hides a whole library.
Tags changed after the fact
Title, meta description, canonical and robots can be managed with JavaScript, but Google advises setting them in the HTML when possible. The canonical case is covered in our guide to the canonical tag. On a multilingual app, the same logic applies to hreflang tags.
Caching and blocked resources
Google caches aggressively and may ignore caching headers: it recommends content fingerprinting in file names, such as main.2bb85551.js, so an outdated script is not used. A JavaScript file blocked by robots.txt will not be executed either.
How to check JavaScript SEO before release?
Google's checklist for fixing JavaScript issues always starts from the same tool: comparing what users see with the HTML Google renders.
- Rendered HTML: Search Console URL Inspection or the Rich Results Test shows the main content, links and tags.
- Links: every public page is reachable through an a element with href, with no # fragment.
- HTTP codes: a missing page returns 404, or carries noindex, instead of an empty 200.
- Tags: one canonical, identical between initial and rendered HTML, no initial noindex on a page to index.
- Resources: JavaScript files not blocked by robots.txt and versioned by fingerprint.
On a site generating many URLs, rendering also weighs on crawling: our article on crawl budget explains when this becomes a real issue. If the problem comes from the framework or template, a technical SEO project on crawling and indexing addresses the cause, and an SEO audit that prioritises bottlenecks tells you whether it comes first. Before a stack overhaul, the checks from SEO migration apply too.
Frequently asked questions about JavaScript SEO
Can Google read a JavaScript site?
Yes. Google runs JavaScript with an evergreen version of Chromium. Rendering goes through a queue, though: a page may stay there for a few seconds, or longer, before generated content is taken into account.
Is server-side rendering mandatory?
No, but Google still recommends it: server-side or pre-rendering makes the site faster for users and crawlers, and not all bots can run JavaScript.
Is dynamic rendering still a good solution?
Google describes it as a workaround and not a recommended solution, because it adds complexity and resource requirements. It recommends server-side rendering, static rendering or hydration instead.
Can the canonical tag be injected with JavaScript?
It is possible but not recommended. If the canonical is already in the original HTML, JavaScript must never change it to another value. An injected tag must be the only canonical tag on the page.
Can JavaScript remove a noindex tag?
Don't rely on it. When Google finds noindex in the original HTML, it may skip running the page's JavaScript. A page meant to be indexed should not contain noindex in its original code.
How can I see what Google renders of my page?
With the URL Inspection tool in Search Console or the Rich Results Test. Both show the rendered HTML: check that the expected content, links and tags are there.
Sources and scope
Documentation accessed October 6, 2026. This article relies on Google's public guidance; it presents no client case and no measured gain.
About the author

Franck Gordi
Independent SEO and GEO consultant for B2B SaaS. He helps software companies become visible on Google and cited by AI engines.
LinkedIn →