How to track AI search visibility for a small SaaS
No single dashboard tells you how often AI assistants recommend your product. What a small team can do is put together a cheap weekly picture from a few sources: a prompt log you keep by hand, your server logs, your analytics, and two free webmaster tools. Each one sees a different slice, and none of them sees everything. This guide sets up that routine and is plain about the gaps.
The routine at a glance
| Signal | Where it comes from | What it can tell you |
|---|---|---|
| Prompt log | You, by hand | Whether you're named, who else is, which pages are cited |
| AI bot requests | Server or CDN logs | Whether AI crawlers can reach your pages, and do |
| AI referrals | Your analytics | Visits from people who clicked through |
| Google AI features | Search Console | Included in normal Web search data |
| Copilot and Bing citations | Bing Webmaster Tools | Sampled counts of your pages being cited |
| Off-site mentions | The third-party pages answers cite | Whether roundups and directories list you |
1. Keep the prompt log, every week
Use the method in our guide on checking whether ChatGPT mentions your brand: a fixed set of 5 to 10 customer-style prompts, the same unpersonalized setup every time, several runs per prompt, and one row per run.
For a SaaS product, two additions make a weekly log more useful:
- Add a "what we shipped" column. Note launches, pricing changes, new comparison pages, or a new directory listing. Later you can line changes in the log up against them. That shows timing, not cause.
- Compare a four-week rate, not single weeks. Answers vary a lot from run to run, so one week's result is noise. The guide above covers why.
2. Read your server logs for AI bots
The three assistant makers most small SaaS sites care about each publish their user agents, and each separates search, training, and user-triggered fetches:
| Provider | Search | Training | Fetches when a user asks |
|---|---|---|---|
| OpenAI | OAI-SearchBot | GPTBot | ChatGPT-User |
| Perplexity | PerplexityBot | (none listed) | Perplexity-User |
| Anthropic | Claude-SearchBot | ClaudeBot | Claude-User |
Sources: OpenAI, Perplexity, Anthropic.
Each week, check three things:
- Do the search bots get normal responses on your key pages? Pricing, features, docs, and comparison pages. A 403 or a challenge page means the bot read the block, not your page.
- Do user-triggered agents show up? OpenAI says ChatGPT may visit a page with the ChatGPT-User agent when someone asks a question. Perplexity and Anthropic describe Perplexity-User and Claude-User the same way. A request from one of them means an assistant fetched that page while answering someone. It isn't a count of people or of mentions.
- Are the requests real? Anyone can copy a user-agent string. OpenAI and Perplexity publish IP ranges for each bot, and Perplexity recommends checking the user agent and the IP address together.
If you're on Cloudflare, check two settings. Cloudflare's AI Crawler and Agent access policies let you allow or block search, agent, and training traffic separately. For new domains all three default to allow, but they can be changed (Cloudflare). Perplexity also warns that Cloudflare's Bot Fight Mode can't be skipped with WAF custom rules and can still challenge its bots (Perplexity).
3. Look for AI referrals in analytics
Referrals count only the people who clicked a link in an answer. We couldn't open a current OpenAI page that documents how ChatGPT labels the links it sends, so we won't repeat secondhand claims about it. Instead, check what your analytics actually records: filter sources and landing URLs for the assistants' own domains, such as chatgpt.com, and save that view so you can compare month to month. Treat the number as a floor, not a measure of visibility.
4. Check Google Search Console
Google says that when your site appears in AI Overviews or AI Mode, that traffic is included in your overall Search Console data, in the Performance report under the "Web" search type (Google Search Central). Its help center explains how it's counted (Search Console Help):
- A click on a link in an AI Overview or in AI Mode counts as a click.
- An AI Overview takes one position, and every link in it gets that position.
- A follow-up question in AI Mode counts as a new query.
- Search Labs experiments aren't included.
Neither page describes a filter that isolates AI Overviews or AI Mode. So Search Console tells you how your Google traffic is moving overall, AI features included, but not how much came from AI features.
5. Check Bing Webmaster Tools
Bing Webmaster Tools has an AI Performance report covering Microsoft Copilot, AI-generated summaries in Bing, and "select partner AI integrations" (Bing Webmaster Tools Help). It shows total citations, which of your pages were cited, and "grounding queries", which Bing describes as grouped phrases, not users' full questions.
Read it with Bing's own caveats: the data is sampled, a citation "does not represent traffic, clicks, or user engagement", and trends "cannot be attributed to a specific cause or event". It doesn't name ChatGPT, Claude, or Perplexity among the surfaces it covers.
6. Watch the pages that get cited
Your prompt log's "cited sources" column is the most useful list you have. Pick the third-party pages that keep coming up, such as review roundups, directories, and comparison posts, and check once a month whether you're listed and described correctly. Why this matters, and what to do about gaps, is covered in why AI answers cite your competitor instead of you.
What you can't measure
- How often assistants name you overall. None of the OpenAI, Anthropic, or Perplexity pages above offers site owners data on brand mentions. Bing reports citations of your pages, not mentions of your name.
- People who read an answer and never click. Analytics can't see them. Bing's citation counts come closest, and only for Microsoft's own surfaces and partners.
- Why something changed. Bing says this outright about its own report, and it applies to every signal here.
- Everyone's answers. Your prompt log is a small sample from one setup.
Put the signals side by side and look for agreement over several weeks, not a single number.
Where CiteLens fits: the CiteLens free audit checks on-page readiness for one public page: robots.txt rules for documented AI crawlers, llms.txt, sitemaps, structured data, title and H1, static text, FAQ coverage, and Open Graph. CiteLens Monitor, which saves URLs and shows diffs between runs, is in invite-only beta and not on sale. Weekly re-checks and alerts are coming soon. CiteLens doesn't track whether any assistant mentions your brand.
Disclosure: Born Bots builds CiteLens.
Check a page now with the free audit.
Sources
- OpenAI, "Overview of OpenAI Crawlers": https://platform.openai.com/docs/bots (opened 17 Nov 2026)
- Perplexity, "Perplexity Crawlers": https://docs.perplexity.ai/guides/bots (opened 17 Nov 2026)
- Anthropic (Claude Help Center), "Does Anthropic crawl data from the web, and how can site owners block the crawler?": https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler (opened 17 Nov 2026)
- Cloudflare, "AI Crawler and Agent access policies": https://developers.cloudflare.com/bots/additional-configurations/block-ai-bots/ (opened 17 Nov 2026)
- Google Search Central, "AI features and your website" (last updated 10 Dec 2025): https://developers.google.com/search/docs/appearance/ai-features (opened 17 Nov 2026)
- Search Console Help, "What are impressions, position, and clicks?": https://support.google.com/webmasters/answer/7042828 (opened 17 Nov 2026)
- Bing Webmaster Tools Help, "AI Performance": https://www.bing.com/webmasters/help/ai-performance-9f8e7d6c (opened 17 Nov 2026)
Last reviewed: 17 Nov 2026.