How to make a JavaScript site render for search and AI

Executive summary

Search engines can render JavaScript but do it on a delay and imperfectly, and most AI answer crawlers do not run JavaScript at all. The safe answer for content you need indexed and cited is to deliver it in the initial HTML through server-side rendering or pre-rendering, so no execution is required to read it.

What this helps you decide

Which rendering strategy guarantees your important content is present in the HTML a crawler receives.

Business problem

Single-page applications often serve an empty shell to crawlers and inject content only after JavaScript runs. Search engines may render it late or not at all, and many AI crawlers do not execute JavaScript, so the content is effectively invisible.

Step-by-step process

1. 1
   See what the crawler sees

   View the rendered HTML in URL Inspection and fetch the raw HTML with JavaScript disabled to compare what exists before and after execution.

2. 2
   Identify content that must be in the HTML

   List the main copy, headings, links and metadata that need indexing, and confirm whether each is present without JavaScript.

3. 3
   Choose a rendering strategy

   Prefer server-side rendering or static pre-rendering for content pages so the important markup ships in the initial response.

4. 4
   Ensure links are real anchors

   Render navigation and internal links as standard href anchors in the HTML, not JavaScript-only handlers, so crawlers can discover pages.

5. 5
   Render metadata server-side

   Output titles, meta descriptions, canonicals and structured data in the initial HTML rather than injecting them client-side after load.

6. 6
   Avoid interaction-gated content

   Do not hide primary content behind clicks, tabs or scroll events a crawler will not trigger.

7. 7
   Validate across crawlers

   Confirm the content appears for search engines and test that non-JavaScript AI crawlers receive it too, since many never execute scripts.

Worked example

Checklist

• Compare rendered versus raw HTML for key templates
• List the content that must appear without JavaScript
• Adopt server-side rendering or pre-rendering for content pages
• Render internal links as real href anchors
• Output metadata and structured data in the initial HTML
• Verify both search and non-JavaScript AI crawlers see the content

Common mistakes

• Assuming crawlers render JavaScript as reliably and quickly as a browser
• Injecting titles, canonicals or content only after client-side execution
• Hiding primary content behind tabs, clicks or scroll events crawlers never trigger

30-minute experiment

KPIs to track

• Indexation rate of JavaScript-rendered templates
• Content present in raw HTML versus rendered HTML
• AI citations of pages that were previously client-rendered

FAQs