AI Visibility Report · 2026
What AI Actually Sees
Four organizations. One AI visibility study. An agency, a nonprofit, an art gallery, and a SaaS startup.
Regional marketing agency
Southeast US
Regional nonprofit
Southeast US
Contemporary art gallery
Southeast US
B2B SaaS startup
West Coast US
Overview
About the Pilot Testing Program
Earlier in 2026 as part of an introductory pilot program for my consulting business, I tracked how four organizations showed up in AI answers. The four organizations do not intersect other than three of them existing in the same region. They work in different fields. They serve different people. They produce different content.
All four had the same problems. Citations came from one or two topics only. Other topics got zero citations. Perplexity bots were blocked for most every client. Claude's live assistant was partly blocked for all four. Almost all citations pointed to just one or two pages.
AI visibility challenges are multi-facted. It is about your site's structure and content, but also about the popularity of your industry. Crawler access and content format decide whether AI cites you and having more content does not automatically fix the problem.
| Client | Type | Region | Queries | Citations | Mention rate |
|---|---|---|---|---|---|
| A | Regional marketing agency | Southeast US | 12,764 | 456 | 3.57% |
| B | Regional nonprofit | Southeast US | 8,847 | 362 | 4.09% |
| C | Contemporary art gallery | Southeast US | 5,218 | 90 | 1.72% |
| D | B2B SaaS startup | West Coast US | 9,640 | 563 | 5.84% |
| Combined | 36,469 | 1,471 | 4.03% | ||
Question 1
Where are citations actually coming from?
ChatGPT had 74.1% of all 1,471 citations. That is not because ChatGPT is the best platform. It is because ChatGPT was the only platform all four clients could be read by. Perplexity was blocked. Claude's live assistant was partly blocked. Three of four clients had nearly all citations go to one platform.
| Platform | Client A | Client B | Client C | Client D | Total | Share |
|---|---|---|---|---|---|---|
| ChatGPT | 339 | 271 | 82 | 398 | 1,090 | 74.1% |
| Gemini | 98 | 74 | 7 | 142 | 321 | 21.8% |
| Claude | 19 | 17 | 1 | 0 | 37 | 2.5% |
| Perplexity | 0 | 0 | 0 | 23 | 23 | 1.6% |
| Total | 456 | 362 | 90 | 563 | 1,471 | 100% |
Claude's 2.5% share is a result of access failures regardless of model. Gemini has 21.8% of citations.Client D was the only client to get any Perplexity citations off the bat, the other three companies had Perplexity blocked entirely as a result of normal bot filtration parameters on their servers.
Question 2
Why the Perplexity window matters and what we can learn from it
AI crawlers do not all work the same way. Training crawlers index your content for future model updates while live assistant fetchers read your content in real-time when a user asks a question.. People are starting to understand that difference. What gets less attention is that these crawlers also return on very different schedules. That matters a lot when access is either blocked, broken, or limited to protect server load.
| Crawler | Type | Re-index cycle | Error recovery time |
|---|---|---|---|
| ChatGPT-User / Claude-User | Live assistant fetcher | Real-time, triggered by user query | Immediate once resolved |
| GPTBot / ClaudeBot | Training crawler | 7–21 days | 1–2 cycles (~14–42 days) |
| PerplexityBot | Live + training hybrid | 45–90 days (observed from logs) | 1 to 3 cycles, up to 270 days |
| Googlebot | Training / index | 3–30 days (authority-dependent) | 1–2 cycles |
Client A's logs showed this clearly. PerplexityBot got access for a short window in late February 2026. It read a few pages before it was blocked again on a schedule. From March 1 through the end of the study, every Perplexity visit went only to robots.txt. Each visit got a 403 error and stopped. The crawler came back every 3 to 5 days. Every time, it found the same block.
Question 3
How AI agents see your site and what you should let them read
Most sites add block rules when a crawler causes a problem and may not be as nuanced when block as to which bots to allow from a souce and which to bar. Protecting yourself from massive bot traffic is standard, but AI creates a new problem of how to open access, when, and to which bots. Client A's bot logs showed 36 different AI crawlers during the study. Several large crawler categories were blocked across the whole site the entire time.
| Crawler | Type | Visits | Success rate | Status |
|---|---|---|---|---|
| ChatGPT-User | Live assistant fetcher | 4,260 | 98.2% | Healthy |
| OAI-SearchBot | AI indexing crawler | 6,175 | 82.7% | Healthy |
| DuckAssistBot | AI assistant fetcher | 136 | 80.9% | Healthy |
| Applebot | AI indexing + assistant | 2,073 | 58.9% | Partial |
| ClaudeBot | Training crawler | 17,423 | 35.4% | Partial (training only) |
| Claude-User | Live assistant fetcher | 49 | 42.9% | Partially blocked |
| DeepSeek | AI assistant | 126 | 7.1% | Mostly blocked |
| PerplexityBot | Live + training hybrid | 101 | 6.9% | 93% blocked, robots.txt only |
| GPTBot | Training crawler (OpenAI) | 2,229 | 0.0% | Fully blocked |
| meta-externalagent | Training crawler (Meta) | 30,995 | 0.0% | Fully blocked |
| Amazonbot | Training + indexing | 24,190 | 0.0% | Fully blocked |
Source: Client A bot traffic logs, monitoring period 2025–2026. Success rate = HTTP 200 responses only.
ChatGPT-User is the live assistant. When a real user asks a question, it reads your site. It got in 98.2% of the time. GPTBot is OpenAI's training crawler. It builds the model's base knowledge of the world. It made 2,229 visits. It was blocked every time. The site was open to live queries but invisible to training data. These are two different bots with two different rules on the same server.
Crawler access framework
| Category | Examples | Recommendation |
|---|---|---|
| Live assistant fetchers | ChatGPT-User, Claude-User, PerplexityBot, DuckAssistBot, DeepSeek, Gemini-Fetch | Always allow. These generate real-time citations. Permit them in robots.txt before any general block rule. |
| Training crawlers | GPTBot, ClaudeBot, meta-externalagent, Amazonbot, TikTokSpider | Allow selectively. Blocking removes you from future training data. It does not affect live citations directly. |
| AI indexing crawlers | OAI-SearchBot, bingbot, Googlebot, Applebot, YouBot | Allow. These feed the retrieval indexes AI platforms draw from at answer time. |
| Unknown / catch-all | User-agent: * and unrecognized agents | Review before blocking. A blanket disallow catches live fetchers too. |
Question 4
How much traffic is coming from AI, and how fast is that changing?
| Traffic source | Start of period | End of period | Change | Notes |
|---|---|---|---|---|
| Google organic (avg.) | 61.4% | 57.8% | −3.6pp | Share declining; absolute volume stable |
| Direct / dark traffic | 18.2% | 17.9% | −0.3pp | Largely stable |
| Social / paid / email | 14.1% | 13.6% | −0.5pp | Flat to slightly declining |
| AI bot traffic (all crawlers) | 3.1% | 6.8% | +3.7pp | More than doubled across the period |
| AI-referred user traffic | 0.4% | 1.1% | +0.7pp | Fastest-growing referral source; Client D led at 2.3% |
Percentage point changes reflect share of total traffic, not absolute volume. Estimates across all four clients.
Your AI referral traffic is an industry signal, not just an individual site success signal
Most brands see low AI referral numbers and think the site is the problem. It is not always the site. Your AI referral traffic shows how ready your whole industry is for AI citation.
Low numbers mean the whole category lacks AI-ready content. AI has nothing good to cite in your space. As more brands build structured content, citation rates rise for all of them.
The 50% threshold
As of March 2026, 48% of all Google queries trigger AI Overviews (BrightEdge, Digital Applied). Above that line, most discovery queries end with an AI summary. Users do not click through. Brands that fix access and structure now will get cited when that line is crossed.
Part I
Client A: Regional Marketing Agency
Southeast US · Moderate regional recognition · 3.57% overall mention rate
The agency showed up in 456 of 12,764 queries. 86.6% of citations came from two verticals. The rate fell from 5.2% to 3.2% over the study because the query set grew to include verticals where the client had no content.
| Vertical | Queries | Citations | Rate |
|---|---|---|---|
| Outdoor / Active Lifestyle | ~1,200 | 201 | 43.9% |
| Creative Agency Services | ~1,500 | 194 | 8.8% |
| AEC | ~3,200 | 0 | 0.0% |
| Nonprofit | ~2,800 | 0 | 0.0% |
| Rebranding | ~2,891 | 0 | 0.0% |
Every query that produced a citation had a location term in it. A content audit tested 43 topic pieces, and twenty-two scored 0 for AI visibility. Only one piece scored 4, a year-in-review article that named the agency directly.
Part II
Client B: Regional Nonprofit
Southeast US · Moderate regional recognition · 4.09% overall mention rate
The nonprofit showed up in 362 of 8,847 queries. 80.1% of citations came from two topics. Fundraising and Advocacy got zero citations across 7,579 queries. Fundraising content is written for donors. It tells stories. AI needs facts it can extract. A mission statement does not produce a citation.
| Vertical | Queries | Citations | Rate |
|---|---|---|---|
| Environmental Education / Coastal Conservation | ~1,100 | 180 | 47.2% |
| Volunteer & Community Engagement | ~1,168 | 110 | 12.4% |
| Major Gifts & Fundraising | ~2,100 | 0 | 0.0% |
| Corporate Partnership / CSR | ~2,800 | 0 | 0.0% |
| Advocacy & Policy | ~2,679 | 0 | 0.0% |
Part III
Client C: Contemporary Art Gallery
Southeast US · Local / emerging recognition · 1.72% overall mention rate
The gallery showed up in 90 of 5,218 queries. That is the lowest rate of all four clients. 87 of those 90 citations came from named entity queries. The gallery's name or a specific artist's name had to be in the query. 97% of all citations pointed to the homepage alone.
Geography had to be very specific. Broad regional terms did not work. A city name or neighborhood name was needed. Smaller brands need tighter geographic anchors than well-known brands.
| Vertical | Queries | Citations | Rate |
|---|---|---|---|
| Gallery Discovery / Exhibition Listings | ~820 | 58 | 14.1% |
| Artist & Work Research (named artists in inventory) | ~650 | 29 | 7.1% |
| Art Investment & Secondary Market Guidance | ~1,100 | 2 | 0.2% |
| Art Fair & Event Coverage | ~1,200 | 1 | 0.1% |
| Collector Services & Acquisition Consulting | ~1,448 | 0 | 0.0% |
Part IV
Client D: B2B SaaS Startup
West Coast US · Early-stage / growing recognition · 5.84% overall mention rate
The SaaS client had the highest mention rate. Product pages have structure AI can read. Feature lists and pricing tables are easy to extract. Competitor comparison queries still got zero citations. AI cited the client's competitors instead. The client had no content that compared itself to anyone.
| Vertical | Queries | Citations | Rate |
|---|---|---|---|
| Core product category / primary use case | ~1,800 | 304 | 33.8% |
| SMB / team-scale use cases | ~1,500 | 153 | 10.2% |
| Integration ecosystem & API use cases | ~2,100 | 74 | 3.5% |
| Enterprise / procurement queries | ~2,200 | 32 | 1.5% |
| Competitor comparison queries | ~2,040 | 0 | 0.0% |
Client D was the only client to get any Perplexity citations. It earned 23. Every one included a third-party source. Perplexity requires external proof before citing a brand. ChatGPT will cite your own pages directly. Perplexity will not.
| Vertical | Perplexity citations | Avg. position | Primary source cited |
|---|---|---|---|
| Core product category | 14 | 7th–9th | Third-party review platforms |
| SMB / team use cases | 6 | 9th–11th | Integration partner docs and blog coverage |
| Integration ecosystem | 3 | 11th+ | API documentation pages |
| Enterprise / procurement | 0 | — | No third-party procurement coverage indexed |
| Competitor comparison | 0 | — | Competitors cited instead |
Cross-client
Takeaways
Content structure impacted mention rate better than brand size or industry. Client D's product pages not only have built-in structure but the structure is a universal standard across SaaS products. Client C's content is mostly storytelling with little data. That is why it scored lowest. Citation rates fell consistantly for all companies throughout the course of the 90 day test as more verticals were revealed through fanout queries.
| Pattern | Client A | Client B | Client C | Client D |
|---|---|---|---|---|
| Overall mention rate | 3.57% | 4.09% | 1.72% | 5.84% |
| Rate drift (start → end) | 5.2% → 3.2% | 6.3% → 3.7% | 2.8% → 1.4% | 7.1% → 5.2% |
| Citation-producing verticals | 2 of 5 | 2 of 5 | 2 of 5 | 4 of 5 |
| Zero-citation verticals | 3 of 5 | 3 of 5 | 3 of 5 | 1 of 5 |
| Perplexity access | 93% blocked | 94% blocked | 95% blocked | 66% blocked / 23 citations |
| Claude-User effective rate | 42.9% | ~39% | ~42% | ~61% |
| ChatGPT-User success rate | 98.2% | 97.2% | 96.3% | 99.1% |
| GPTBot (training crawler) | 100% blocked | ~blocked | ~blocked | ~blocked |
| Citation page concentration | ~95% on 2 pages | ~92% on 2 pages | ~97% on homepage | ~71% on 3 pages |
| Geographic requirement | 100% regional | 100% regional | 100% neighborhood-level | 60% geo / 40% category |
| Most commercially significant zero | AEC + Rebranding | Fundraising + Advocacy | Art investment + Collector services | Competitor comparison |
Framework
Content gap framework
Zero-citation verticals do not all have the same problem or the same solution.
| Gap type | Signal | Fix |
|---|---|---|
| Missing | Competitors may get cited on queries where you never appear. If AI already has a source for the topic then recency and region area a way to overtake competitors in citations. | Write new content for these topics. Put the direct answer first. Add a FAQ block. Include location terms. |
| Weak | You rank in search but AI does not cite you. The answer may be buried, i.e. there is no direct answer in the first 150 words. | Rewrite the intro as a direct answer. Add numbered steps. Change every H2 into a question. |
| Outdated | AI cites a newer version of the same topic from a competitor. Your version is more than 18 months old. | Add a last-verified date. Refresh every stat with its source and year. |
Content structure that earns citations particularly for physical or SaaS products
| Element | Why it earns citations | What to avoid |
|---|---|---|
| Direct answer within first 150 words | AI takes the first clean answer it finds. Everything after that is secondary. | "In today's digital landscape..." and any opener that delays the answer. |
| Question-phrased H2 headings | Matches the question the user asked. "How does X work?" works. "Background" does not. | Vague section titles, noun phrases, internal jargon. |
| Single-sentence declarative claims | Long sentences are hard for AI to pull from. Short factual statements get cited more. | Hedged language: "many studies suggest that, in most cases..." |
| Inline source attribution | "Source: Gartner, 2025 (n=1,200)" raises AI credibility scoring. | Footnotes, "research shows", and undated stats. |
Query Research
Human vs. bot query divergence
This was probably the most interesting observation during the course of testing. For the project 3 researchers were hired and they used Scribe to record search conversations and interactions with AI. They were instructed to test in their regular preferred browser, with ingognito, and using a VPN at various locations. A human using a local browser got drastically different results than automated tools like Profound, or even custom listening tools using API calls via AppScript. How you phrase a query matters but where you are matters more. Bot traffic that runs through these AI tools is also very different than human user traffic. Because AI is highly subjected to individual user environments and geo-locations, data gathered via bot queries was different. Automated tools give you a starting point, and in a future of agentic search that data is important, but user data should be gathered separately for an accurate picture.
| Query | Type | Result | Key observation |
|---|---|---|---|
| "best marketing agencies for environmental nonprofits" | Evaluator, no geo | National / generic agency list | No location term returns national category leaders. Regional fit does not matter to AI without it. |
| "best marketing agencies for environmental nonprofits in the Carolinas" | Evaluator, geo-anchored | Localized agency list | The location term changed the entire result set. Client A was absent even though it operates in that market. |
| "nonprofit digital marketing strategy" | Naive, no geo | General strategy content | No agency citations at all. Broad queries produce educational content, not vendor lists. |
| "What content helps conservation nonprofits in the Carolinas appear in AI answers?" | Long-tail, geo-anchored | Specific local keyword recommendations | AI returned very specific local terms like estuary names and local species. Those are the terms your content needs to contain. |
Source: Human-researcher query session, Client A engagement. Queries run from regional browser, not neutral datacenter IPs.
Adding a location term changed the entire result set. National names dropped out. Regional providers appeared. Client A was not on that list. Its content does not name its region clearly or often enough.
When asked what helps a regional nonprofit get cited, AI named very specific local terms. Named waterways. Local species. Event names. Your content needs those exact terms at that level of detail.
Commercial context
The paid AI layer
Organic citations come first. Paid ads in AI platforms are largely in beta, paid ads on Google do not help a brand AI cannot otherwise find in terms of citations or authority. We do know that there is a 91% higher paid CTR when a brand is cited organically next to its ad (Seer Interactive, BrightEdge, March 2026). But this doesn't automatically translate to AI platform ranking or citations.
| Platform | Format | Status | Key number |
|---|---|---|---|
| Google AI Overviews / AI Mode | Auto-eligible via Performance Max. Ads show inside AI summaries. | Live globally | 25.5% of AI Overview results include ads, up 394% year over year. |
| ChatGPT | Sidebar ads labeled Sponsored. Self-serve, no minimum spend. | Live Feb 9, 2026 | $60 CPM via agencies. Matched to conversation intent, not keyword. |
| Microsoft Copilot | Showroom Ads via Performance Max. Interactive product comparisons. | Live April 2025 | 73% higher CTR than traditional search. 16% higher conversion rate. |
| Perplexity | Tested Nov 2024. Paused Oct 2025. Dropped Feb 2026. | Pulled | Moved to subscriptions and enterprise revenue instead. |
| Claude / Anthropic | No ads by stated policy. | No ads | Highest conversion rate at 16.8% (Fahlout, March 2026). No ads is part of the trust positioning. |
What's next
Agentic commerce
AI agents are already completing purchases for users. The standard marketing funnel has multiple steps which an agent collapses into a single prompt or task.
In the 2025 holiday season, AI drove 20% of all retail sales, $262 billion (Salesforce Commerce Cloud, US Chamber of Commerce, February 2026). That is double what AI drove in 2024. Gartner projects 33% of all web content will be built for AI search by 2026.
In B2B, agents are starting to buy from other agents. Google's Universal Commerce Protocol (UCP) is a system where brands pay to be in AI agents' shortlists. Etsy, Wayfair, Shopify, Target, and Walmart were early adopters.
This means a few things, particularly when we look at the citation and ranking differences between bot and human-user queriesa across regions. If agentic search and agentic purchasing overtake the market, then monitoring AI bot citaiton levvels becomes more important. However there are other oncoming regional avenues as well where the human-user data is more valuable, (car navigation ads, etc.)
| Format | How it works | What brands must do |
|---|---|---|
| Google UCP | Brands pay to appear in agents' consideration sets when AI completes purchases on users' behalf. | Match UCP feed standards. Keep product and service data structured and current. |
| B2B agent-to-agent procurement | Buyer-side AI agents evaluate vendors and start purchases with no human needed for routine orders. | Write clear service descriptions. Use structured pricing. Make your content readable by machines. |
| Conversational commerce agents | A user asks an agent to find and buy something. The agent handles the whole process in one session. | Keep brand data consistent across all feeds. Reviews and availability need to be indexed and accurate. |
Action
Recommendations
In order of impact.
-
1Fix crawler access first
Let all live assistant fetchers through. That includes Claude-User and PerplexityBot. Check that blanket bot-block rules are not also catching GPTBot. Perplexity takes 45 to 90 days to re-index.
-
2Audit robots.txt, CDN settings, and WAF rules
A robots.txt audit alone misses CDN and WAF rules. Whitelist live fetcher user agents in robots.txt before any general block rule. Then check CDN allow/deny settings. Then check WAF rate limits for crawler traffic. All three can block crawlers independently.
-
3Map your zero-citation verticals
Every client had at least one commercially important vertical with zero citations. Find yours. Run queries your buyers actually use. Note which verticals never produce your brand. Those are your priority content gaps.
-
4Reformat for AI extraction
Put a direct one-sentence answer in the first 150 words of every key page. Change H2 headings to questions. Replace hedged claims with single declarative sentences. Cite sources inline.
-
5Add geographic specificity
Regional brands need explicit location terms in their content. City names, neighborhood names, named local landmarks. Every citation in this study that came from a location query required the location to be named in the content.
-
6Build external citation presence for Perplexity
Perplexity does not cite brand pages directly. It cites third-party sources. Get coverage in review platforms, industry directories, and partner documentation. Client D's 23 citations all came through third-party sources.
-
7Start tracking AI referral traffic now
Set up UTM source tracking for AI platforms in your analytics. Segment bot traffic from user traffic. Establish a baseline before you make changes. You cannot measure improvement without a starting number.