Sites built in JavaScript that AI crawlers cannot read
Google renders JavaScript, so it can usually see content your site builds in the browser, though rendering can be delayed. OpenAI, Anthropic and Perplexity do not say in their crawler documentation that their crawlers run JavaScript, and Google itself notes that not all bots can. If your provider names, hours or services appear only after scripts run, assume some AI crawlers see a nearly empty page.
How Google handles JavaScript
Many modern websites send the browser a nearly empty page plus a bundle of JavaScript, and the script builds the visible content. Patients never notice, because their browser runs the script instantly. Crawlers are another matter.
Google describes a three stage process: crawling, rendering and indexing. Googlebot fetches the page, queues it for rendering, and a headless version of the Chromium browser runs the JavaScript so Google can index the result. Google notes that pages may stay in the rendering queue for a few seconds, or longer. In 2026 it updated its documentation to say it has been rendering JavaScript for years.
The same documentation adds a caveat that matters here: server side rendering or pre rendering is still a great idea, because it makes your site faster for users and crawlers, and not all bots can run JavaScript.
What AI crawlers document, and what they do not
OpenAI, Anthropic and Perplexity each publish pages describing their crawlers: their names, what they are for and how to control them with robots.txt. None of those pages says whether the crawlers run JavaScript.
That silence is the honest state of knowledge. It does not prove they cannot render scripts, and their behavior may change. But a crawler that reads only the HTML your server sends will miss anything your scripts add later, and you cannot confirm from their documentation that this is not happening.
There is one more category. Google's 2026 guide on generative AI features describes AI agents, browser based systems that complete tasks for people, and says they may gather data by analyzing screenshots, inspecting the page structure and interpreting the accessibility tree. Agents that work in a real browser will run your scripts. Crawlers that build search indexes may not. The safe design serves both.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
A five minute check you can do yourself
You do not need to be technical to see what a crawler that skips JavaScript would see.
- On a desktop computer, open a key page, such as a provider bio or your insurance page, in Chrome, Edge or Firefox.
- Open the page source. In most browsers you can right click the page and choose View page source.
- Use the browser's find command to search the source for something that should be there: your phone number, a provider's last name, an insurance plan, your hours.
- If you find the text, a crawler that reads only HTML can see it. If you find nothing, or only a short script reference, that content is built by JavaScript.
For Google's view, use the URL Inspection tool in Search Console. Test the live URL and you can view a screenshot of the page as Google renders it. Then compare what Google sees with what the source shows.
The parts of practice sites that often vanish
Even on sites that are otherwise plain HTML, certain features are commonly loaded by script from another service. Check these first:
- Provider directories and "find a doctor" tools that load from a database
- Insurance lists shown in an interactive widget or filtered search
- Location finders and embedded maps that carry the only copy of your addresses
- Hours shown by a widget that pulls from another system
- Review widgets that display ratings from third party sites
- Tabs and accordions that fetch their content only when clicked
- Booking tools, which often load entirely from the scheduling vendor
The booking widget is a fair exception: it does not need to be crawlable. But the facts around it, such as which visit types new patients can book online, should be written on the page in plain text.
Fixes, from simplest to biggest
- Write key facts as plain text on the page. Your phone, address, hours, providers and accepted insurance should appear in the page itself, not only inside a widget. This fixes most of the problem for a small cost.
- Use real links. Google can reliably crawl only standard anchor links with an href address. Menus and buttons that work only through script may hide whole sections. See internal links.
- Load less from third parties. Fewer scripts also helps speed; see chat widgets, plugins and third party scripts.
- Render on the server. Many modern frameworks can send fully built HTML to every visitor, through server side rendering or static generation, while keeping interactive features. This is a developer decision, but it is the complete fix.
Avoid putting important facts only in images or PDFs, which create the same problem by a different route.
Questions to ask your web developer
If you have someone who manages your site, these questions take five minutes and tell you where you stand:
- Is our site rendered on the server, statically generated, or built in the browser?
- If I disable JavaScript, can I still read our provider bios, locations, hours and insurance?
- Which parts of the site load from third party services?
- Are our menus and internal links standard links that a crawler can follow?
- Do any security or bot management settings block AI crawlers? See robots.txt and AI crawlers.
If you are choosing a new vendor, ask the first two before you sign. Our questions to ask a marketing agency include more.
Checklist
- Your phone, address and hours appear in the page source, not only after scripts run
- Provider names and credentials appear in the page source of each bio
- Accepted insurance is written as text on a page, not only in a widget
- Menus and internal links are standard links
- Search Console's live URL test shows Google rendering your key pages fully
- Key facts are not published only in images or PDFs
Frequently asked
My site looks fine in my browser. Why would crawlers see something different?
Your browser runs JavaScript, so it shows everything the scripts build. A crawler that reads only the HTML sent by your server sees the page before scripts run. If the content is added by scripts, that crawler may see little or nothing.
Is this a problem for Google too?
Less so. Google renders JavaScript with a version of Chromium, though rendering may be delayed. Google still recommends server side rendering or pre rendering because it is faster for users and crawlers and because not all bots can run JavaScript.
Are Wix, Squarespace and WordPress sites affected?
It depends on the theme, plugins and widgets, not just the platform. Many pages on these platforms include their main text in the HTML, but widgets for reviews, maps, insurance or providers may not. Run the page source check on your own key pages.
Sources
- Understand the JavaScript SEO basics, Google Search Central
- Latest documentation updates, Google Search Central
- Optimizing your website for generative AI features on Google Search, Google Search Central
- Overview of OpenAI crawlers, OpenAI
- Does Anthropic crawl data from the web, and how can site owners block the crawler?, Anthropic
- Perplexity crawlers, Perplexity
- SEO link best practices for Google, Google Search Central
- URL Inspection tool, Google Search Console Help
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.