If your website uses modern front-end frameworks like React, Vue, or Angular, and core content only appears after JavaScript executes, that content is effectively invisible to most AI crawlers. Your page may look information-rich in a browser, but what AI receives may be nothing more than an empty shell. In real projects, this is the single most common fatal GEO issue.<\/p>\n\n\n\n
A browser is a complete runtime environment: it downloads HTML, executes JavaScript, renders CSS, and ultimately displays a visually complete page. Every word you see on screen is the result of the browser running the full pipeline.<\/p>\n\n\n\n
AI crawling systems work differently. In many generative search scenarios, crawling systems first receive the initial HTML. They typically don’t execute JavaScript, don’t render CSS, and don’t wait for asynchronous loading \u2014 though specific implementations differ across systems.<\/p>\n\n\n\n
This means: if your core content is rendered via JavaScript in the browser (client-side rendering), that content simply isn’t present in the initial HTML when AI crawlers receive it.<\/p>\n\n\n\n
The fastest way to check whether you have this problem takes just ten seconds:<\/p>\n\n\n\n
On your core page, press Ctrl+U (Windows) or Cmd+Option+U (Mac) to view the page source. Search the source code for your most important product name or key conclusion.<\/p>\n\n\n\n
Found it<\/strong> = Content is in the initial HTML. AI can see it.<\/p>\n\n\n\n Can’t find it<\/strong> = Content is JavaScript-rendered and most likely invisible to AI. Needs fixing.<\/p>\n\n\n\n This test costs almost nothing but is highly accurate. Run it on your 5 most important pages.<\/p>\n\n\n\n Google Search Console URL Inspection.<\/strong> Enter the page URL, click “Test Live URL,” and compare Google’s rendered screenshot against the actual page. Large blank areas indicate a rendering problem.<\/p>\n\n\n\n Command-line curl test.<\/strong> Run The core principle is just one thing: ensure core content exists in the initial HTML without depending on JavaScript execution.<\/strong><\/p>\n\n\n\n WordPress users<\/strong> most likely don’t have this problem \u2014 WordPress renders server-side by default. But if you’ve installed numerous front-end optimization plugins (lazy loading, deferred rendering, etc.), it’s still worth running the ten-second test to verify.<\/p>\n\n\n\n React\/Vue\/Angular users<\/strong> need to ensure core content can render directly in the initial HTML. The most common solutions are SSR (Server-Side Rendering) or SSG (Static Site Generation) \u2014 Next.js users can use If you can’t change the technical architecture short-term,<\/strong> at minimum ensure the page’s H1 heading, Meta Description, and core conclusion paragraph exist as plain HTML in the initial server response.<\/p>\n\n\n\n WordPress renders server-side by default, so core content is usually in the initial HTML. But two scenarios require caution: lazy-loading or deferred-rendering plugins may cause some content to become JS-loaded; highly customized WordPress themes may introduce client-side rendering. Run the ten-second test to confirm.<\/p>\n\n\n\n Next.js supports multiple rendering modes, including SSR, SSG, and client-side rendering. Default settings vary by version and configuration. The key is confirming that your core content pages actually use SSR or SSG mode, rather than assuming “I use Next.js, so I’m fine.” The ten-second test is the most direct verification.<\/p>\n\n\n\n Product spec tables (especially those loaded dynamically via components), user review modules, FAQ accordion panels, and pricing information \u2014 these are frequently JavaScript-loaded, and also frequently the content AI most wants to extract. Check each one.<\/p>\n","protected":false},"excerpt":{"rendered":" If your website uses modern front-end frameworks like React, Vue, or Angular, and core content only appears after JavaScript executes, that content is effectively invisible to most AI crawlers. Your page may look information-rich in a browser, but what AI receives may be nothing more than an empty shell. In…<\/p>\n","protected":false},"author":1,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[106],"ht-kb-tag":[],"class_list":["post-48759","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-geo-tactics"],"_links":{"self":[{"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/ht-kb\/48759","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/comments?post=48759"}],"version-history":[{"count":0,"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/ht-kb\/48759\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/media?parent=48759"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/ht-kb-category?post=48759"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.geobok.com\/en\/wp-json\/wp\/v2\/ht-kb-tag?post=48759"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Two Additional Detection Methods<\/h3>\n\n\n\n
curl -s 'your-URL' | grep 'keyword'<\/code> in the terminal. No output means the keyword isn’t in the initial HTML.<\/p>\n\n\n\nHow to Fix It<\/h3>\n\n\n\n
getServerSideProps<\/code> or getStaticProps<\/code>; Nuxt.js has SSR support by default. Pre-rendering, hybrid rendering, and server-side output of critical content can also achieve similar results. The specific approach depends on your technical architecture, but the core principle stays the same: key content must not depend on client-side JavaScript to appear.<\/strong> This usually requires developer involvement \u2014 and it should come before any other GEO optimization work.<\/p>\n\n\n\nPractical Essentials<\/h2>\n\n\n\n
\n
FAQ<\/h2>\n\n\n\n
I use WordPress. Am I definitely fine?<\/h3>\n\n\n\n
Doesn’t Next.js support SSR by default?<\/h3>\n\n\n\n
Besides body content, what else commonly gets hidden behind JS rendering?<\/h3>\n\n\n\n