Yes — Google *can* render JavaScript, but in practice I still treat JS-heavy sites as “crawl-risky” unless I’ve verified otherwise.
A few thoughts from running this on real projects:
### 1) Does Google still have problems rendering JavaScript-heavy pages?
Yes, sometimes. Not because Google “can’t” render JS, but because rendering is not guaranteed to happen immediately or consistently at scale.
What I’ve seen in the wild:
– Content loads in the browser fine, but Google indexes only the initial HTML
– Important text is injected late, after interaction, or behind state changes
– Internal links added via JS are missed or discovered slowly
– Infinite scroll / lazy-loaded content gets partially crawled
– Canonicals, meta tags, and structured data sometimes render inconsistently if they depend on client-side execution
So the issue is less “Google ignores JavaScript” and more “Google may not fully process it the way you expect.”
### 2) Is SSR better than CSR for SEO?
In most cases, yes.
If the content matters for rankings, I prefer:
– **SSR** for core page content
– **Pre-rendering / static generation** where possible
– **CSR only for enhancements**, not for the primary content
My rule of thumb: if a page can rank without JavaScript, that’s usually safer.
CSR can work, but it adds failure points:
– render delay
– hydration issues
– content hidden until JS loads
– bot-specific behavior differences
– crawl budget waste on large sites
For affiliate sites, niche sites, or content-heavy sites, I’d rather have the main text in the HTML response.
### 3) How can I test whether Google actually sees my content?
A few practical checks:
#### Google Search Console
– **URL Inspection**
– Check the **Crawled page** / rendered HTML
– Compare rendered output with what you expect
– Look at screenshots if available
#### View source vs rendered DOM
– If the important content is missing from “view source” but present after JS execution, that’s a warning sign
– Use browser dev tools and compare:
– initial HTML
– rendered DOM
– network requests
#### Fetch as Google-style tools
– Rich Results Test
– Mobile-Friendly Test
– Rendering inspection tools like:
– Screaming Frog with JavaScript rendering
– Sitebulb
– Chrome headless / Pupp