Can Google see your JavaScript content? A rendering audit for AI search
Compare the server HTML, the page before interaction and Search Console’s live render to find where key content disappears.
To check whether Google can access a key fact on a JavaScript page, look for the same sentence in the server response, the rendered page before any interaction and the HTML from Search Console’s live URL test. The first place where the sentence disappears tells you which part of the delivery to investigate. Start with a public page and a fact worth quoting, such as a product’s eligibility condition or the scope of a study.
Google documents separate crawling, rendering and indexing stages. It can run JavaScript and use the rendered HTML for indexing. For AI Overviews and AI Mode, Google says a supporting page must be indexed and eligible to appear with a snippet in Search. This audit checks how the text reaches Google. Eligibility, selection as a source and citation are separate outcomes.
1. Pick one URL and two exact phrases
Open the public URL in a fresh browser session, signed out. Record the final URL and choose two short phrases: one from the answer and one from its supporting evidence. On a comparison page, you might choose a plan’s eligibility condition and the date when it was checked. In a multilingual site, run the same test on both language URLs with phrases specific to each language.
2. Compare the server response with the rendered page
- Open the browser’s Network panel and reload. Select the main document request and check its status, final URL and Response tab. Find each phrase and look at its surrounding markup. A match inside a script or serialized data tells you the browser received the words. Check separately whether they appear as page text.
- Before clicking or scrolling, look for the phrases in the page and in the Elements panel. Give the page time to finish its initial load. If a phrase appears at this stage only, note the script or request that supplies it. Check for errors or requests that depend on a cookie, session or API response.
- If a phrase appears only after opening a tab, choosing a filter or clicking ‘Load more’, record the interaction. An accordion can contain text in its HTML from the start. The case to investigate is an interaction that fetches or inserts the text for the first time.
3. Check what Google’s live test receives
In a verified Search Console property, inspect the exact URL and run the live test. Open the tested page’s HTML and search for the two phrases. Check the surrounding text and consult the loaded resources and JavaScript output if anything is missing. Google documents that Search does not interact with a page to reveal lazy-loaded content. Treat the live result as evidence of that fetch. Use the indexed report separately to check indexing status and Google’s selected canonical.
An example and a fix you can verify
Suppose a software comparison shows the sentence ‘Exports are available on annual plans’ only after someone clicks a pricing tab. The sentence is absent from the document response and the live test’s rendered HTML. In this example the tab makes a request after the click. Put the eligibility sentence in the public comparison section using static or server rendering, and keep the tab for the detailed pricing view. Then repeat the test on the deployed URL and verify that the sentence now appears in the document response, the page before interaction and the live test.
Keep a small record for each URL: date, exact phrase, response status, presence in the document body, presence before interaction, live-test result and next action. When all three checks show the phrase and its context, move on to indexing, snippet eligibility and the quality of the evidence on the page. Google’s test covers its own inspection system. Assess other answer engines using their documentation and observations specific to those engines.
- Audit the canonical URL when AI answers cite an older page
- Check whether the English and Spanish versions carry the same evidence
Documentation reviewed on 9 November 2026.