The site looks great in a browser, but the page source is an empty div and a couple of scripts. Google then has to run the JavaScript before it can see any text, and it doesn't always do that, not straight away and not completely. We find what Google can't see and set up rendering so it sees everything.
On a traditional site the server sends finished HTML with the text in it. On an application built with React, Vue or Angular the server often sends an empty page, and the content is assembled in the browser. Users don't notice the difference. Google does.
Google can run JavaScript, but it first puts the page in a rendering queue. That's usually quick, sometimes slower, and if rendering fails Google sees an empty page. Most AI tools that read websites don't run JavaScript at all, and other search engines don't do it as well as Google.
02
The most common mistakes
links built as buttons with onClick instead of real a href links, so Google can't follow them
the same title and meta description on every page, because the app only changes them after loading
URLs with # in them, which Google treats as a single page
content that only loads when the user scrolls or clicks a tab
a page returning status 200 for a URL that doesn't exist, with "not found" shown only on screen
API calls that are slow or blocked in robots.txt, so Google gets a page without data
03
SSR, SSG or rendering in the browser
With server-side rendering (SSR) the server sends a finished page with content for every request, and JavaScript then takes over the interaction. With static generation (SSG) pages are built in advance, when content is published. Google reads both without trouble. Next.js and Nuxt support both.
Rendering only in the browser is fine for areas behind a login, such as a user account or admin panel. For pages that need to appear in search, we almost always recommend SSR or SSG.
04
How we check
We compare three things: the HTML the server returns, the page after JavaScript runs, and what Google shows in the URL Inspection tool in Search Console. The difference between them shows what Google can't see.
Then we crawl the whole site with and without JavaScript, and check that every page has its own title, description, canonical and status code, and that every important page can be reached through real links.
05
Part of technical SEO
JavaScript SEO is the part of technical SEO where SEO and programming overlap the most. "Introduce SSR" isn't much of a recommendation if nobody knows how to do it on an existing application without rewriting everything.
06
We fix it in the code
Because we build frontends in React, Vue and Next.js, we don't stop at a report. We add server-side rendering or prerendering, turn buttons into real links, set meta tags per page and return correct status codes.
If your own team develops the application, they get exact instructions per component and a check after every change.
FAQ
Questions about JavaScript SEO
Yes, but with more risk than plain HTML pages. If rendering fails, or content only loads after a click, Google doesn't see it, and on large sites some pages may stay unindexed.
Most tools that read websites for AI answers don't run JavaScript. If content only appears after rendering in the browser, the page practically doesn't exist for them. One more reason for server-side rendering.
Not always. On a smaller site, prerendering the pages that matter for search is sometimes enough. For online stores and content-heavy sites, SSR or static generation is the safer long-term choice.
In Search Console, open URL Inspection, run a live test and look at the rendered HTML. If text from the page isn't in that HTML, Google can't see it.
Is your site built with React, Vue or Angular?
Send us the URL. We'll check what Google can and can't see on your pages.