How to Check If Your Site Appears in AI Search

Appearing in AI answers is one half of AI visibility; being readable by the crawlers behind them is the other.

"AI search" now means more than Google. People get answers from ChatGPT, Perplexity, Claude, Microsoft Copilot and Google's AI Overviews, and each decides independently whether to surface your site. Here's how to find out if you're showing up, using two complementary methods.

Method 1: Ask the AI engines directly

The quickest gut-check is to behave like your customers. Open each engine and run prompts where your site should be a natural answer:

• Brand prompt: "What is [your brand] and what do they do?"
• Category prompt: "What are the best tools for [your category]?"
• Problem prompt: "How do I [the problem your product solves]?"

Do this in ChatGPT (with web search on), Perplexity, and Google's AI Mode / AI Overviews. Note three things: does it mention you, does it cite your URL, and is what it says accurate? If you're absent or misrepresented, that's your gap. This method shows the outcome, but not why.

Method 2: Check whether engines can technically read you

If AI engines don't cite you, it's almost always because they can't properly crawl or parse your site. These are the technical signals that decide it:

• Crawler access, your robots.txt must allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Google-Extended. See how to allow GPTBot.
• Rendered HTML, your content must exist in the raw HTML, not only after JavaScript runs.
• Structured data, JSON-LD helps engines understand and quote you accurately.
• Freshness, visible and machine-readable update dates build trust.

Testing these by hand is covered step by step in how to check your website's AI visibility. To test them all at once, run an automated audit.

Where to check, engine by engine

Each engine sources answers differently, so "am I visible on AI" has a different answer depending on which one you ask. Check them separately:

• ChatGPT, turn on web search and ask your category question. Then paste your URL and ask it to summarize the page. If it can summarize the page but never volunteers you unprompted, your problem is authority, not crawlability. If it cannot read the page at all, you have a technical blocker.
• Perplexity, the most transparent of the group, because it lists its sources for every answer. Run your category question and read the citation list. If competitors are there and you are not, you can see exactly which pages beat you.
• Google AI Overviews and AI Mode, run the query logged out and in an incognito window, since personalization skews results. Overviews lean heavily on pages already ranking in the top ten for the query, so poor classic rankings usually mean no Overview presence.
• Claude, ask with web search enabled, and separately paste the URL. ClaudeBot access is a common gap because many sites only added GPTBot to robots.txt.
• Microsoft Copilot, draws on the Bing index, so confirm you are in Bing at all. Bing Webmaster Tools will tell you in a minute, and plenty of sites indexed in Google are missing from Bing entirely.

One caveat worth internalizing: AI answers are non-deterministic. The same prompt can return different sources on consecutive runs. Run each prompt three or four times before you conclude anything, and never read a single answer as a verdict.

The three ways an AI engine can find you

If you are absent, it helps to know which of these paths is broken, because the fixes are completely different:

• Training data, a snapshot of the web taken at some past date. You cannot influence this retroactively, and there is a long lag before new content lands here.
• Live retrieval, the engine runs a search at answer time and reads the results. This is where most citations come from today, and it is the path you can influence fastest.
• Direct fetch, a user hands the engine your URL. This is the purest test of whether your page is technically readable, stripped of any question about authority.

Test them in reverse order. If a direct fetch fails, fix the technical blocker first, because nothing else can work until it is resolved. If a direct fetch works but live retrieval never surfaces you, the gap is authority and content structure.

Why "in AI search" is different from "ranking on Google"

With 60% of Google searches now ending without a click, being the answer matters more than being a blue link. A page can rank #1 in classic search and still never be quoted by an AI engine if its content is locked behind JavaScript or missing the structure AI needs. That's why "do I rank?" and "do I appear in AI search?" are two different questions, and you need to check both.

The fastest way to check

Sona's free AI visibility checker probes your live site the way an AI engine would: it runs a real GPTBot crawl test, checks JS rendering, inspects your schema and content structure, and scores you 0–100 with a prioritized list of exactly what's keeping you out of AI answers. It takes about 30 seconds and needs no account.