Yeah, Google still *can* render JavaScript, but in the real world it’s not something I’d trust for important SEO content.
I’ve seen this a bunch on affiliate sites and content projects: pages look fine in the browser, but the indexed version is missing chunks of text, internal links, or even product copy. Usually it’s not that Google “can’t” render it — it’s more like it **delays rendering**, **doesn’t bother rendering everything**, or hits issues with scripts, timeouts, blocked resources, or weak crawl budget.
### My take on your questions:
#### 1) Does Google still have problems rendering JavaScript-heavy pages?
Yes, sometimes. Especially when:
– content loads late
– data comes from API calls after page load
– important links are injected by JS
– the page depends on user interaction
– there are hydration issues / blank states
– scripts are blocked or slow
Google is better than it used to be, but I still see JS-heavy pages lose content in indexing. For money pages, I wouldn’t gamble on it.
#### 2) Is SSR better than CSR for SEO?
100% yes, if the content matters.
If the page is important for rankings, **SSR or pre-rendering is safer** than pure CSR.
CSR can work, but it’s more fragile. I’ve had far fewer indexing headaches with:
– Next.js SSR
– static generation
– pre-rendered HTML
– hybrid setups
Basically: if the page needs to rank, make sure the core content is in the HTML response.
#### 3) How can I test whether Google actually sees my content?
Best ways I use:
– **Google Search Console → URL Inspection**
– check the rendered HTML
– compare it to the live version
– **View source vs rendered DOM**
– if content only exists after JS, that’s a warning sign
– **Fetch as Google / live test in GSC**
– **Rich Results Test**
– not just for schema — it shows rendered output too
– **Log files / server logs**
– see if Googlebot is hitting the page and how often
– **Cache / indexed snippet checks**
– search exact text from the page and see if Google picked it up
If the text doesn’t appear in the rendered HTML inside Search Console, I’d treat it as risky.
#### 4) Are React and Next