A growing number of your potential customers no longer start with Google. They ask ChatGPT, Claude or Perplexity "who can do this near me?" and act on the answer. Which raises a question almost no business owner has thought to ask: when one of those assistants visits your website, can it actually read it? For a surprising number of small-business sites, the answer is no — not a single word.
The unsettling part is that nothing tells you. Your site looks perfect to you, loads fine on your phone, might even sit near the top of Google — and is still a blank page to the tools more and more people now trust to make the shortlist.
Why an AI assistant might see nothing
A web page arrives in two stages. First your browser downloads the HTML — the raw text of the page. Then, on a lot of modern sites, JavaScript runs and builds the content you actually see. Your browser does both in a blink, so you never notice the join.
The automated crawlers that feed ChatGPT, Claude and Perplexity mostly do only the first step. They download the HTML and stop. They do not run the JavaScript. So if your site was built so that its words only appear after the JavaScript runs — which is exactly how many app-style "single-page" builds and some Wix and Squarespace setups work — then the version an assistant downloads can be nearly empty. A title, perhaps a line of description, and a blank space where all your content should be.
Here's the trap that hides it: Google's crawler is the exception. It does run JavaScript. So your site can look completely healthy in Google Search while being invisible to every AI assistant — and you'd have no reason to suspect a thing. This isn't a fringe theory, either; Anthropic's own documentation states plainly that its web fetch tool "does not support websites dynamically rendered via JavaScript."
The 30-second test you can run yourself
Two ways — pick whichever you're comfortable with.
The no-terminal way. Open your website, right-click anywhere on the page and choose View Page Source (on a Mac it may be under View → Developer → View Source). A window of raw code opens — don't worry about reading it. Press Cmd-F (or Ctrl-F) and search for a sentence you know is on the page: your tagline, a service you offer, your phone number. If it's there, good. If the search comes up empty, that text isn't in your HTML — and an AI assistant won't find it either.
The technical way, if a terminal doesn't scare you:
curl -s https://yourwebsite.com | grep -c "a phrase from your page"Swap in your address and a real phrase from the page. If it prints 0, that phrase isn't in the raw HTML.
Either way, you're now seeing your website the way GPTBot, ClaudeBot and PerplexityBot see it — before a line of JavaScript has run.
What it means if you failed the test
Don't panic. It doesn't mean your website is bad, and it's fixable. It means your site is built to assemble itself in the visitor's browser rather than arriving ready-made. For someone on a modern phone, that's usually fine. For AI assistants, search previews and older devices, it's a wall.
The fix is to have each page arrive as complete HTML — the text already present in the very first response, before any JavaScript. The industry calls this "server-side rendering," "static generation" or "pre-rendering." The label doesn't matter; the result does. Your words are in the page from the first byte. It's a decision about how the site is built, not how it looks, and on most platforms it's very achievable.
Why this is worth caring about right now
Two reasons.
First, the people who arrive through an AI recommendation are the good ones. They convert far better than a cold click off a Google results page, because the assistant has already done the shortlisting for them — it has, in effect, vouched for you. A handful of pre-qualified visitors beats a flood of browsers.
Second, almost nobody has checked. Run that View Source test on a few of your competitors. If theirs comes up empty too — and plenty will — then the first local business to fix it is the one the assistants can actually start naming.
The honest caveat
Being readable is the price of entry, not a guarantee. Getting an AI to recommend you is a bigger job: consistent details about your business across the web, real reviews, and genuinely being the best answer to the question. But none of that counts for anything if the assistant can't read your site in the first place. That's step one — and it's the cheapest step you'll ever take.
If you'd like to know how your own site does, I offer a fixed-price AI & agent readiness audit — or if you want one built to be readable from the first byte, have a look at how I work.