Can AI Read Your Website? Check Yours in a Minute

I've been building a tool called Voice Print. You paste your web address, it reads your site, and it hands back how your business actually sounds, in your own words, with real lines from your own pages as proof. The point is to fix a thing every owner runs into: ChatGPT will write you something competent and it won't sound remotely like you.

To test it I started feeding it real small business websites. Dozens of them.

A lot of them came back nearly empty.

Not because those businesses have nothing to say. Their sites are full of words, and I could read every one of them on screen. The machine couldn't. It was getting a fraction of what I was seeing, and on some sites it was getting almost nothing at all.

One design studio has Nike, Mattel and Crocs on its client list. What a machine gets from that homepage is the navigation menu and those client names. That's it. Everything else on the page, it never sees.

I went looking for why, and it turns out to be the same handful of causes over and over. So this guide is the detour: what a machine actually gets when it visits your site, how to check yours, and what to do if it comes back empty.

Why a machine sees something different

When you visit a website, two things happen. Your browser downloads a file, then it runs that file to draw the page. Photos appear, menus slide open, text fades in. It's so fast you've never noticed there were two steps.

Most AI crawlers only do the first one.

They grab the file, take whatever words are already sitting in it, and move on. They don't wait around for the page to finish drawing itself. Vercel and MERJ watched over 500 million visits from OpenAI's crawler and saw no sign it ever ran that second step. Anthropic says the same about how Claude fetches a page.

If your words are already in the file, you're fine. If your site sends an empty shell and fills it in afterward, the machine gets the shell.

I found a bakery with a lovely line on its homepage about baking everything from scratch. That sentence is technically in the file, folded up inside a block of code. No simple reader would ever call it a sentence.

Check yours right now

Run your own site through Voice Print, the tool I mentioned at the top. Paste your web address and it reads your site the way a crawler does, so you can see for yourself what comes back. It's free and it takes about a minute.

If it comes back full of your own words, you're in good shape. If it comes back thin, the rest of this guide is for you.

Where this hurts, and where it doesn't

There are scarier versions of this story going around than the facts support, so here are the edges of it.

Your Google ranking is a separate question. Google runs that second step, and has for years. If you rank well today, nothing here changes that.

Some AI tools find you anyway. A few answer from a search index instead of visiting your page, so you can still turn up that way.

It matters for the ones that read the raw file. When someone asks an AI what your business does, who you serve, or whether you're open Sundays, the answer comes from whatever the crawler could read. If that was close to empty, the AI either fills the gap with something else or skips you.

Nobody's site is invisible. Some are just harder to read than their owners think.

The fixes, easiest first

Take your words out of your pictures. This was the most common problem I found, and it has nothing to do with which website builder you use. Gorgeous homepages put the headline, the tagline, sometimes the whole menu, inside an image. It looks great and it reads as a blank. Retype those as real text. Every website builder has a text block for it.

Write down the things people ask you. A lot of homepages come up nearly empty for a boring reason: there aren't many words on them. One studio I checked has a single sentence on its homepage. The file was honest about that. If a stranger can't learn what you do, who you do it for, where you are and roughly what it costs, an AI can't either. An About page and an FAQ page in plain text will cover most of it. Use the questions customers actually ask you on the phone.

Put your menu and prices on the page, not only in a PDF. Keep the PDF if you like it. Add a text version underneath it.

If a developer built your site, ask them one question. "Does the server send finished pages, or does the browser build them?" They'll know what you mean, and they'll know the fix. On some sites it's a small job. On others it's real work, so get an honest quote before you agree to anything.

Sometimes the answer is to move. A few website builders give you no say in what goes in the file, and there's no setting that changes it. That's a real decision with real cost. Weigh it against how much of your business actually starts with someone searching. For a lot of local businesses that's not much, and staying put is the right call.

When you can skip all of this

Plenty of good businesses can ignore this entirely.

If your customers walk in, come from referrals, or find you through a marketplace, your homepage isn't your front door. If your Google Business Profile is complete and accurate, that's doing more work for local searches than your website is.

And if nobody's asking an AI about your line of work yet, this is a next-year problem, not a this-week one.

When they do start asking, the businesses with readable pages are the ones it has something to say about.

One more thing

Once your words are in the file, the next question is whether they sound like you. Generic copy reads as generic to an AI too. How to Train ChatGPT on Your Business's Voice covers that side of it.

Either way, go look. It's a strange feeling to see your own site the way a machine does, and it's usually a quick fix once you have.