Server Rendering
0 articles tagged with Server Rendering
Server rendering is the practice of generating HTML on the server and sending it to the browser (and to crawlers) fully formed, rather than sending a minimal HTML shell and building the page with JavaScript. It is one of the most critical technical factors for AI visibility.
[ Coming soon ]
Articles with this tag are in progress. Follow @MattQR on X to be notified when they publish.
Most AI crawlers do not execute JavaScript. When a crawler requests a page from a React, Vue, or Angular app that uses client-side rendering (CSR), it receives an HTML file with no content: just a root div and script tags. The actual content is never rendered because the crawler does not execute the JavaScript. The result is that the page is indexed as empty or near-empty, and its content is invisible to AI citation. Server-side rendering (SSR) with frameworks like Next.js, or static site generation (SSG), solves this by ensuring the HTML response contains the actual content regardless of JavaScript execution. Every site that wants AI visibility must use SSR or SSG.
Common questions
Why does server rendering matter for AI visibility?
AI crawlers do not execute JavaScript. A page built with client-side rendering (React, Vue, Angular CSR) returns empty HTML to AI crawlers because the content is only added after JavaScript runs. Server-rendered or statically generated pages return full HTML to crawlers, making the content visible and indexable for AI citation.
How do I know if my site uses client-side rendering?
View the page source (Ctrl+U in browser) and check if the content is present in the HTML or if you only see a div with an id like "root" or "app" with no text content. If the content is absent in page source but visible in the browser, the site uses client-side rendering and will be invisible to AI crawlers.
All tags
Related resources