Is Your Website Blocking the Bots That Recommend Businesses Like Yours?

Published October 18, 2026

By Aaron Roberts · 6 min read

Last week a homeowner in Horseheads asked the AI assistant on her phone instead of searching. "Who can replace a water heater today?" It gave her three companies with phone numbers, and she called one. The whole conversation took about eight seconds, and no search results page ever showed up.

If your business wasn't one of the three, you didn't lose a click. You lost the call. There's no ranking report for it. No bounce record. Nothing to optimize. It just doesn't show up in any dashboard you look at.

That's the same shape as the handoff problem I wrote about two weeks ago: the number that costs you jobs is the one nobody counts.

This one has a twist, though. Some businesses are invisible to those assistants for a reason sitting in a file that took thirty seconds to create, and that nobody on the team has read since.

A real example from the last few weeks

The people who run websites for a living have started checking this on purpose. One person working with client sites said he read a guide on showing up in AI results, ran its checklist, and worked through three client websites. One of the three was blocking OpenAI's crawler, GPTBot, because a security plugin's default setting blocked AI bots when the plugin went in. Nobody on the agency side had set it on purpose. The business was paying to get found in one tab and blocking the new front door in another, and the only reason anybody noticed was a manual read of one text file.

That's not rare. A lot of the security plugins and hosting panels that local businesses run added a "block AI bots" switch over the past two years. Some ship with it on. Cloudflare has a one-click block for AI crawlers too. A business that never wanted any of it can still be running it.

The two checks to run this week

Both are free. Together they take about twenty minutes.

First, read your own robots.txt. Open yourwebsite.com/robots.txt in a browser. That file tells crawlers what they may read. Look for lines that block any of these names:

• GPTBot (OpenAI)
• OAI-SearchBot (ChatGPT's search)
• ChatGPT-User (ChatGPT reading a site on request)
• PerplexityBot (Perplexity)
• ClaudeBot (Anthropic)
• Google-Extended (Gemini)
• Applebot (Apple)

If you find a Disallow covering any of them, that assistant can't read your website at all. While you're in there, check your WordPress plugins and hosting dashboards for anything with the words "AI bots" or "crawler" in the settings.

Second, run the question test. Write down five questions a real customer would say out loud. For trade businesses it looks like this:

• Who can fix a burst pipe on a Sunday in Corning?
• Best price on a whole-home generator in Elmira?
• Who installs EV chargers in Horseheads?

Ask each one in ChatGPT, Gemini, and Perplexity. Screenshot the answers with the date. Then look for your name. If it never comes up, this is your starting line, not a report you need to buy.

"For a small local business, I'd start with a manual check before buying a broad tracking package. Pick a handful of questions customers actually ask, specify the service and area, and save the completions."

That advice is from a Reddit thread on exactly this subject. The same thread's other takeaway: this industry is new, and the tooling is priced like it. Early-technology pricing is how smaller shops get squeezed out. Some owners will buy a dashboard before they ever run a free twenty-minute test.

Even unblocked, why assistants skip some businesses

Blocking is only the front gate. If the bots can read you and you still never get named, it's usually one of these:

• Your services live in a brochure PDF, a phone tree, or a form. Assistants quote plain text. If the answer isn't written down in normal sentences, they can't say what you do.
• Your service area isn't on the page in plain text. "Proudly serving the community" tells an assistant nothing. Cities and towns in normal sentences tell it everything.
• Your phone number is only reachable through a form. An assistant that can't hand someone a phone number or hours will usually recommend the competitor it can.
• Your reviews live somewhere the assistants can't see them. Reviews feed every one of these answers. If yours are locked into one platform, or your Google Business Profile has been sitting stale for eight months, that shows up too.

None of this is a design job. It's a writing job, and a business owner can sit down with a coffee and do most of it in one pass.

What not to do

• Don't buy a GEO package the same week you find the problem. Run the free checks first.
• Don't keyword-stuff your services page. These systems read like people, not like 2009.
• Don't block the bots out of spite because you think they stole your content. That argument can be handled somewhere else. Blocking just guarantees you're absent from every future recommendation.

The shortlist

• Read robots.txt. Twenty seconds.
• Check plugin and hosting panel AI-bot switches. Five minutes.
• Run the question test in three assistants. Ten minutes. Save the screenshots.
• Write the plain-text basics: what you do, the towns, hours, phone, real service descriptions.
• Repeat the question test monthly and watch for movement.

The recommendation side of AI is moving faster than the search page ever did, and it doesn't announce itself. You hear about it when a customer says "the assistant gave me your number." Most of the time you never hear at all.

We run this exact check as part of our $1,000 AI Assessment, because half the time the fix is a setting, not a rebuild. If you want the short version of this done for you, that's the place to start. If you'd rather just talk about your phones, the assessment covers that too.