If AI assistants aren't recommending your business, no single tool will tell you why. The cause usually falls into one of four buckets, and each bucket has its own diagnostic: site audits (is your content clear and structured?), crawler checks (can AI bots reach it at all?), prompt-testing trackers (what do assistants actually say today?), and entity checkers (does the web agree on who you are?). Run them in that order, and you can usually name the main blocker in an afternoon.
This guide covers what each category can and can't explain, what to look for when choosing, and a simple workflow for combining them. No jargon required, and no need to buy everything at once.
Why "AI doesn't recommend me" is really four different problems
When someone asks ChatGPT, Claude, or Perplexity for "the best accountant for freelancers in Denver," the assistant has to do several things before it names you:
- Reach your content (or know about you from training data or search results).
- Understand what you do, who you serve, and where.
- Trust you, based on mentions and signals from other places.
- Choose you over other options for that specific question.
A failure at any step produces the same symptom: you don't show up. But the fixes are completely different. Blocked crawlers need a robots.txt edit. Vague pages need rewriting. A thin reputation needs third-party mentions. That's why a diagnostic tool that only measures one step can send you off fixing the wrong thing.
Category 1: Site audits (can the content be understood?)
What they do: Scan your pages for the things answer engines tend to rely on: clear page titles and descriptions, structured data (schema markup), question-and-answer formatting, headings that match real questions, author and business information, and basic technical health.
What they can explain:
- Pages that never state plainly what you do or who it's for
- Missing or broken structured data (for example, no Organization or LocalBusiness markup)
- Content buried in images, PDFs, or scripts that don't render as text
- Thin pages with no specific facts, prices, locations, or proof
- No FAQ-style content that mirrors how people phrase questions to assistants
What they can't explain:
- Whether an AI assistant actually mentions you (they audit your site, not the assistant)
- Whether competitors have stronger reputations elsewhere
- Whether bots are being blocked at the server level
What to look for when choosing one:
- Checks specific to answer engines, not just classic SEO scores
- Plain-language findings with a "fix this" instruction, not only a score
- Page-level results, so you can see which pages are weak
- Coverage of structured data validity, not just presence
Good first move: Start with a free audit. AEO Juice's free 26-check AEO report is built for this stage. It looks at the on-site signals answer engines lean on and tells you what's missing in plain English, which is usually enough to find the cheap wins.
Category 2: Crawler checks (can AI bots get in?)
What they do: Test whether the bots that feed AI products can access your site. These include crawlers associated with OpenAI, Anthropic, Perplexity, Google, and others. They examine your robots.txt, server responses, firewall or CDN rules, and sometimes your log files.
What they can explain:
- A robots.txt that disallows AI user agents (sometimes inherited from a template or a plugin default)
- A CDN or security setting that challenges or blocks unfamiliar bots with errors like 403 or 429
- Pages that require JavaScript to display any content, leaving bots an empty shell
- Missing or broken sitemaps
- Login walls or cookie interstitials hiding the real content
- Accidental
noindextags on important pages
What they can't explain:
- Why a fully accessible site still isn't recommended
- Whether being crawled leads to being cited (access is necessary, not sufficient)
- How training-data presence differs from live retrieval
A practical note on the two kinds of AI bots: Some crawlers collect data for model training; others fetch pages in real time to answer a specific question. You might intentionally block one type and allow the other. A good crawler check distinguishes them, so you don't accidentally shut out the bots that power live answers when you only meant to opt out of training.
How to check without a paid tool:
- Open
yourdomain.com/robots.txtand look forDisallowrules under user agents or a blanketUser-agent: *block. - View your page source (or use "view as text") and confirm your main content appears in the raw HTML.
- Check your CDN or security dashboard for bot-blocking rules and recent blocked requests.
- Confirm your sitemap loads and lists your key pages.
If the crawler check finds a block, fix it first. Nothing else in this guide matters if the doors are locked.
Category 3: Prompt-testing trackers (what do assistants say today?)
What they do: Run a set of realistic questions through AI assistants on a schedule and record whether your business is mentioned, cited, or ignored, and who gets named instead.
What they can explain:
- Which questions you appear in and which you don't
- Which competitors show up repeatedly for your category
- Which sources assistants cite (useful for finding where to earn mentions)
- Whether you're described accurately (right services, right city, right pricing)
- Whether your visibility is improving after changes
What they can't explain:
- Why you're missing. They show the symptom precisely, not the cause
- Anything with certainty, since answers vary by session, wording, location, and model version
That last point matters. AI answers are probabilistic. Ask the same question ten times and you may get different lists. Treat a single response as an anecdote. Treat a pattern across many runs as data.
What to look for when choosing one:
- Multiple assistants. ChatGPT, Claude, and Perplexity can behave differently.
- Repeated runs per prompt, so you see frequency rather than a one-off.
- Prompts you can customize, written the way your customers talk.
- Citation capture, showing which URLs the assistant relied on.
- History over time, so trends are visible week to week.
How to build a good prompt set (about 15–25 prompts):
- Category questions: "What's the best [service] in [city]?"
- Problem questions: "How do I fix [problem your business solves]?"
- Comparison-intent questions: "Which [service] is best for [specific customer type]?"
- Branded questions: "Is [your business] any good?" and "What does [your business] do?"
Branded questions are a revealing diagnostic. If the assistant can't describe you accurately when you're named outright, you have an entity or content problem. If it describes you well but never volunteers you for category questions, you have an authority or relevance problem.
Manual version: You can do this by hand with a spreadsheet. Run each prompt three times in a fresh chat on each assistant, log mentions and cited sources, and repeat monthly. It's tedious but free. Tools earn their keep by doing it weekly and at scale. AEO Juice's paid tiers include weekly LLM-visibility tracking for exactly this reason: trends are only visible if someone is checking consistently.
Category 4: Entity checkers (does the web agree on who you are?)
What they do: Examine how consistently and prominently your business is represented across the web: your name, address, category, description, founders, and links across directories, review sites, social profiles, knowledge sources, and press.
What they can explain:
- Inconsistent business names, addresses, or phone numbers across listings
- Missing profiles on the sites assistants frequently draw from (major review platforms, industry directories, Wikipedia or Wikidata where eligible, LinkedIn, Google Business Profile)
- A thin or contradictory description of what you do
- Few or no independent mentions (articles, lists, podcasts, community discussions)
- Confusion with a similarly named company
What they can't explain:
- On-site content problems
- Technical crawl blocks
- Whether a particular assistant will weigh these signals the way you expect
Why this category matters so much: Assistants lean heavily on corroboration. A business whose own site says "we're great" is a weaker signal than one that's also described consistently in a local chamber listing, a review site, a roundup article, and a few forum threads. If you're invisible in those places, a flawless website may still not be enough.
Manual version:
- Search your exact business name in quotes. Do the first two pages show consistent information?
- List every profile you control. Does each use the same name, description, and category?
- Search for "best [your category] in [your city]" and note which lists and directories appear. Are you on them?
- Ask an assistant "Who is [your business]?" and compare its answer with reality.
What each tool category can and can't tell you
| Question | Site audit | Crawler check | Prompt tracker | Entity checker |
|---|---|---|---|---|
| Is my content clear and structured? | Yes | No | No | No |
| Can AI bots access my pages? | Partly | Yes | No | No |
| Am I mentioned today? | No | No | Yes | No |
| Who gets recommended instead? | No | No | Yes | Partly |
| Is my reputation consistent across the web? | No | No | Partly | Yes |
| Why am I missing? | Partly | Partly | No | Partly |
No column answers "why" alone. That's the point of combining them.
A simple diagnosis workflow
Run these in order. Each step either finds the blocker or clears you to move on.
Step 1: Check access (30 minutes)
Run a crawler check. If bots are blocked or your content doesn't render without JavaScript, stop and fix it. Everything else is moot until this is resolved.
Step 2: Baseline your visibility (1–2 hours)
Run your prompt set across ChatGPT, Claude, and Perplexity, multiple times each. Record:
- Mention rate (how often you appear)
- Which competitors appear
- Which sources get cited
- Whether descriptions of you are accurate
Step 3: Audit your site (1 hour)
Run a site audit, such as the free 26-check AEO report. Compare the findings with your baseline. If assistants describe you vaguely and your audit shows vague pages, you've found a likely cause.
Step 4: Check your entity footprint (1–2 hours)
Compare your listings and mentions with those of the competitors that appear in your tracker results. Look at the sources assistants cited for them. Those are your targets.
Step 5: Read the pattern
| What you see | Likely cause | First fix |
|---|---|---|
| Bots blocked or empty HTML | Access | Update robots.txt, CDN rules, or rendering |
| Accurate branded answers, no category mentions | Authority or relevance | Create focused pages for target questions; earn third-party mentions |
| Inaccurate or vague branded answers | Content or entity clarity | Rewrite core pages; fix listings; add schema |
| Mentioned on one assistant but not others | Source differences | Look at which sources each cites and fill gaps |
| Competitors cited from sites you're absent from | Entity footprint | Get listed or featured on those sources |
| Everything looks fine, still absent | Competition or time | Publish consistently; track trends over weeks |
Step 6: Fix one thing, then re-test
Change one category of issue at a time and re-run the same prompts after a few weeks. Otherwise you won't know what worked. Changes to AI answers can lag, since some assistants rely on search indexes that update on their own schedule, and others on training data that updates far less often.
Common mistakes when diagnosing
- Trusting a single answer. One chat is an anecdote. Look for frequency.
- Buying a tracker before checking access. Tracking tells you you're missing; it can't unblock a bot.
- Only testing branded prompts. Being found by name is easy. Category prompts are where new customers come from.
- Ignoring local and customer-type specifics. Assistants respond to specificity. "Best bookkeeper for Etsy sellers in Ohio" is more winnable than "best bookkeeper."
- Expecting overnight results. Fixes compound over weeks, not hours.
Do you need all four tools?
Not necessarily. A reasonable path for a small business:
- Start free: a free site audit, a manual robots.txt check, and a hand-built prompt spreadsheet.
- Add tracking when you're making changes: consistent weekly data is what proves progress.
- Automate the ongoing work: diagnosis is a starting line. The real gains come from steadily publishing, fixing, and re-checking. AEO Juice's Pro and Prime tiers handle much of that with an automated content calendar, AI-generated fixes, and weekly tracking, so you aren't running this workflow by hand every month.
FAQ
Why doesn't ChatGPT recommend my business even though my website ranks on Google?
Ranking in search and being recommended by an assistant overlap but aren't identical. Assistants favor clear, specific answers and corroboration from other sources. Your site may rank for its name yet lack content that answers category questions, or lack third-party mentions that back it up.
Can I check whether AI crawlers are blocked for free?
Yes. Read your robots.txt file, confirm your content appears in the page's raw HTML, and review CDN or firewall bot rules. A dedicated crawler check is faster, but these manual steps catch the most common problems.
How often should I run prompt tests?
Weekly is ideal for spotting trends; monthly is the minimum. Run each prompt multiple times, since answers vary between runs.
Will fixing my site guarantee AI recommendations?
No. Nobody can guarantee placement in AI answers. Fixing access, clarity, and reputation removes obstacles and improves your odds, but results depend on competition and on how each assistant sources information.
What's the single most useful first step?
Run a free audit and a robots.txt check on the same day. Between them, you'll catch the most common and most fixable blockers before spending anything.
How long until I see changes after fixing issues?
It varies. Assistants that retrieve live web results can reflect changes within days or weeks. Those relying more on training data may take much longer. Track trends over at least four to eight weeks before judging.
The takeaway
Think of diagnosis like checking why a peach tree isn't bearing fruit: is it getting sun (access), is it healthy (content), do the neighboring orchards vouch for it (entity), and what does the harvest look like (tracking)? Check all four and the answer usually becomes obvious.
Ready for the quick version? Start with AEO Juice's free 26-check AEO report at aeojuice.com and see which bucket your blockers fall into.