Primary content only present after JS
If the main content of a page only appears after JavaScript runs, I am betting everything on Google rendering it correctly and quickly. When rendering fails or lags, the page can be indexed as effectively empty.
Main content is absent from raw HTML and only appears after JS executes.
Why it matters
Google renders JS, but render is deferred and not guaranteed in all conditions; content that depends entirely on client-side execution is at higher risk of being missed or delayed, and the AI-features guide stresses content must be crawlable and visible in the rendered HTML.
How to fix it
Server-render or statically generate primary content; confirm via URL Inspection’s rendered HTML.
How to find it on your site
- In Search Console URL Inspection, run a live test and read the rendered HTML, not just the source.
- Compare the raw view-source HTML against the rendered HTML for the main content.
- Disable JavaScript in the browser and reload to see what survives.
- Server-render or pre-render the primary content so it is present without JavaScript.
Cross-reference to ranking and citation factors
Google indexes the rendered HTML, but render is a second pass that can be delayed or skipped under load. Content present in the initial HTML is the safest path to being indexed and quoted.
Impact
High. Render-dependent content risks delayed/partial indexing; magnitude depends on the site. Direct mechanism; magnitude inferred.
Evidence
Google only indexes content visible in the rendered HTML; verify with URL Inspection. Google Search Central, Understand JavaScript SEO Basics; Google Search Central, In-Depth Guide to How Google Search Works; Google Search Central, Optimizing your website for generative AI features on Google Search
Sources