By the AEO GEO Marketing team · Updated
- Some AI crawlers fetch HTML without fully executing JavaScript.
- Content that only appears after scripts run may be missed or delayed.
- Server-side rendering or static generation makes content reliably visible.
- Test pages with JavaScript disabled and with crawler tools.
- Prioritise rendering fixes for pages you want cited.
Why rendering matters for AI visibility
Modern websites often rely on JavaScript frameworks to build pages in the browser. The server sends a mostly empty HTML shell, then scripts fetch data and render the content. Browsers handle this smoothly, so humans see a complete page.
Crawlers are different. Googlebot can render JavaScript, though rendering may happen later than the initial crawl. Many other crawlers, including several used by AI companies, fetch the raw HTML and may not execute JavaScript fully or at all. If your key content only exists after scripts run, those crawlers may see a page with little or no text, and your content cannot be cited.
Which content is most at risk
Content is most at risk when it is:
- Loaded from an API after page load, such as product details, prices or reviews.
- Rendered inside single-page applications without server-side rendering.
- Hidden behind interactions, such as tabs, accordions or “load more” buttons that fetch content on click.
- Injected by third-party widgets, such as review or FAQ widgets.
- Displayed in images or canvas elements instead of text.
Navigation links built only with JavaScript can also prevent crawlers from discovering pages.
How to check what crawlers see
There are several quick tests:
- View the page source (not the inspected DOM) in your browser. If the main text is missing from the raw HTML, crawlers that do not render may miss it.
- Disable JavaScript in your browser and reload the page. What remains is roughly what non-rendering crawlers see.
- Use Google Search Console’s URL Inspection to see the rendered HTML and screenshot Googlebot captured.
- Fetch the page with a command-line tool using an AI crawler’s user agent to see the raw response.
- Ask an AI assistant to summarise a specific URL and see whether it reports the main content correctly.
Server-side rendering
Server-side rendering (SSR) generates the full HTML on the server for each request, so crawlers receive complete content immediately. Frameworks such as Next.js, Nuxt, SvelteKit and Remix support SSR. The page can still become interactive in the browser after loading. SSR is a good fit for dynamic content that changes frequently, such as prices or availability.
Static site generation
Static site generation (SSG) builds HTML pages in advance, at deploy time. Every crawler receives a complete page, and pages load very quickly. Static generation suits marketing sites, documentation, blogs and many service businesses. Content can be regenerated when it changes. Our own website is statically generated for this reason: every page, including all city and service guides, is plain HTML.
Hybrid approaches
Many sites combine approaches: static generation for most pages, server-side rendering for dynamic ones, and client-side rendering for interactive features that do not need to be indexed, such as account dashboards. Incremental static regeneration rebuilds static pages periodically. The key principle is simple: content you want indexed and cited should be present in the initial HTML.
Dynamic rendering is a workaround, not a solution
Dynamic rendering serves pre-rendered HTML to bots and the client-side version to users. Google has described it as a workaround rather than a long-term solution. It adds complexity, can drift out of sync with the user-facing version and requires accurate bot detection. Prefer SSR or SSG when possible.
Tabs, accordions and “read more”
Interactive elements are not a problem in themselves. If the content inside tabs or accordions is present in the HTML and simply hidden with CSS until clicked, crawlers can still read it. Problems arise when content is fetched only on click. Check that hidden content exists in the page source. Consider showing the most important answers openly rather than hiding them.
Internal links that crawlers can follow
Crawlers discover pages by following links. Use standard anchor elements with href attributes for navigation and internal links. Links triggered only by JavaScript events, such as click handlers on div elements, may not be followed. Make sure menus, pagination and related-content links are crawlable, and provide an XML sitemap as a backup.
Structured data and rendering
Structured data injected by JavaScript may be processed by Google after rendering, but other systems may not see it. Include JSON-LD directly in the server-delivered HTML where possible. Validate it with Google’s Rich Results Test and the Schema Markup Validator, and check that it matches visible content.
Performance is part of the picture
Heavy JavaScript slows pages down, which affects user experience, Core Web Vitals and crawl efficiency. Reduce unused scripts, defer non-essential code, lazy-load below-the-fold media and split bundles. Faster pages are crawled more efficiently and are more pleasant for the visitors AI engines send you.
Third-party widgets
Review widgets, chat tools, FAQ plugins and embedded content often load via JavaScript from other domains. Their content may not be visible to crawlers and is not attributed to your site. Where content matters for AI visibility, such as reviews or FAQs, render it in your own HTML or use solutions that output server-side markup.
A worked example: an e-commerce store on a JavaScript framework
An online store built as a single-page application notices that AI assistants describe its products vaguely and rarely cite its pages. Viewing the page source shows product descriptions, specifications and reviews are loaded by API calls after page load. The team moves product and category pages to server-side rendering, includes JSON-LD in the server response and renders reviews in HTML. After the change, AI assistants begin quoting product details accurately, and Search Console shows faster indexing of new products.
Prioritising fixes
Rendering changes can require significant development work. Prioritise:
- Pages that drive revenue: services, products, pricing, locations.
- Pages you want cited for important questions: guides and FAQs.
- Navigation and internal links that help discovery.
- Lower-priority content later.
Even moving a small set of key pages to SSR or static HTML can make a big difference.
Checklist
- Main content visible in page source.
- Navigation uses crawlable links.
- Structured data in the initial HTML.
- No important content loaded only on click.
- Reviews and FAQs rendered in HTML.
- XML sitemap submitted.
- Core Web Vitals acceptable on mobile.
- AI crawlers allowed in robots.txt and firewall.
Single-page applications and routing
Single-page applications often change the URL with JavaScript without loading a new HTML document. If each “page” does not have its own server-rendered URL, crawlers may see only the initial shell. Make sure every important view has a unique URL that returns full HTML when requested directly, with its own title, description and canonical tag. Test by opening each URL in a fresh browser tab with JavaScript disabled.
Lazy loading done right
Lazy loading images and below-the-fold content improves speed, but text that matters should not depend on scrolling to load. Use native lazy loading for images and keep text content in the HTML. Infinite scroll should be backed by paginated URLs that crawlers can follow, so products or articles further down the list are discoverable.
Content management systems and page builders
Some page builders and headless CMS setups render content client-side by default. Check your CMS output: does the published HTML contain the text? Many modern frameworks offer server rendering or static export options; enabling them is often a configuration change rather than a rebuild. Ask your developers or platform support which rendering mode your site uses.
Meta tags and canonical tags in the HTML
Titles, meta descriptions, canonical tags and robots directives should be present in the server response, not added later by scripts. Crawlers that do not render JavaScript rely on these tags to understand the page. Check them in the page source, and make sure client-side code does not change them in ways that conflict with the server version.
Monitoring after changes
Rendering changes can break things silently. After deploying, check page source for key pages, run a crawl with a tool that compares raw and rendered HTML, re-test structured data and watch Search Console for indexing changes. Keep monitoring periodically, because new features or plugins can reintroduce client-side rendering without anyone noticing.
Key terms in this guide
- Schema markup: Code, usually JSON-LD, that describes a page’s content in a standard vocabulary from Schema.org, helping engines understand businesses, services, people, FAQs and more.
- JSON-LD: JavaScript Object Notation for Linked Data: the format Google recommends for adding schema markup to web pages.
- robots.txt: A file that tells crawlers which parts of a website they may access. It can allow or block specific AI crawlers such as GPTBot, ClaudeBot and PerplexityBot.
- Core Web Vitals: Google’s user-experience metrics: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
- Rendering: How a crawler turns code into a viewable page. Content that only appears after JavaScript runs may be missed by some AI crawlers.
How AEO GEO Marketing can help
If you would rather have specialists handle this, these services cover the work described in this guide:
AI SEO & Generative Engine Optimization
Get cited in Google AI Overviews, ChatGPT & Perplexity. The new search visibility standard. It includes geo / aeo full audit, ai overview citation strategy, entity authority building and more, from $800/mo.
Web Design & Development
Performance-first websites built for conversion, speed and AI search visibility. It includes ux & visual design, core web vitals engineering, schema-ready architecture and more, from $1,500/mo.
AI Visibility Audit
A full report on how AI engines see your brand, with a prioritised 90-day action plan. It includes prompt testing, competitor benchmark, technical ai readiness and more, from $750 one-off.
Not sure where to start? The free 48-hour AI snapshot shows where AI engines cite you today.
Frequently asked questions
Does Google render JavaScript?
Yes, Googlebot renders JavaScript, but rendering can be delayed and resource-limited. Other crawlers vary.
Do AI crawlers run JavaScript?
Some do partially; many rely primarily on the raw HTML. Assume content must be in the HTML to be reliably seen.
Is React bad for SEO?
No. React and similar frameworks work well with server-side rendering or static generation.
How do I know if my site has a rendering problem?
Compare page source with the rendered page, test with JavaScript disabled, and check Search Console’s URL Inspection.
Related guides and services
Continue with these guides:
- The schema markup guide for AI search: FAQPage, Organization, Article, HowTo and LocalBusiness — what to deploy and why.
- What is llms.txt and does your website need one?: A plain-English guide to llms.txt: what it is, what it can and cannot do, and how to write one in under an hour.
- GPTBot, ClaudeBot, PerplexityBot: which AI crawlers should you allow?: A practical guide to AI crawlers, what each one does, and how to configure robots.txt and your firewall without losing AI visibility.
- Site architecture and topic clusters for AI search: How to organise your website into clear topics so search and AI engines understand your expertise and find the right page for every question.
Or see how we put this into practice:
- AI SEO & Generative Engine Optimization: Get cited in Google AI Overviews, ChatGPT & Perplexity. The new search visibility standard.
- Web Design & Development: Performance-first websites built for conversion, speed and AI search visibility.
- AI Visibility Audit: A full report on how AI engines see your brand, with a prioritised 90-day action plan.
Get a free 48-hour GEO audit that shows exactly where AI engines cite you — and where they cite your competitors.