The AI Search Hub

AI search, in 35 guides — tracked, measured, and joined to revenue.

AI search is the cluster of surfaces — ChatGPT, Perplexity, Claude, Gemini, Copilot, AI Overviews — that answer queries by synthesizing from sources instead of just listing them. It is also the cluster that quietly broke your analytics: most of the traffic it sends shows up as “Direct” in GA4 because the referrer gets stripped or the navigation gets sandboxed. The 35 guides on this page cover how each engine works, how to track its traffic cleanly, and how to prove the revenue is real.

The 3-layer AI traffic problem

Layer 1 — detection. Did this visit come from an AI engine? The referrer is the primary signal but is often stripped; user-agent, UTM parameters, and landing-page patterns are the fallback layers. The dark-ai-traffic-ga4 piece walks through why GA4 misses ~70% of ChatGPT referrals by default.

Layer 2 — classification. Which AI engine? ChatGPT, Perplexity, Claude, Gemini, AI Overviews, Copilot all leave distinct fingerprints once you know what to look for. The per-engine guides in section 2 cover each one.

Layer 3 — revenue join. Did this visit convert? The server-side join from a classified AI session to a Stripe payment is the layer most tools never reach. Until you close that loop, every AI traffic conversation stays vibes-based.

What AI search is — and why it broke your analytics

AI search is the cluster of surfaces — ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, Copilot — that answer queries by synthesizing from sources instead of just listing them. From a tracking perspective, it broke your analytics. AI engines often strip referrers, sandbox the navigation, or send visits in patterns GA4's default channel groups misclassify as Direct. These four pieces cover the foundation: what AI search actually is, why your traffic numbers lie, and whether it is worth optimizing for at all.

Per-engine guides — ChatGPT, Perplexity, Claude, Gemini, Copilot

Each AI engine sends traffic with different referrer shapes, different conversion rates, and different attribution failure modes. These guides are the per-engine detection + tracking playbooks. Start with ChatGPT (highest volume, hardest attribution) and add the others as your audience picks them up.

GA4 setup — get AI traffic out of the Direct bucket

If you are still using GA4 as your primary analytics, these are the exact setup steps to stop losing AI traffic to Direct. Both pieces below are step-by-step — the first is the multi-engine umbrella, the second is the deep ChatGPT-specific walkthrough with the 30% capture-ceiling discussion most setup guides skip.

AI crawlers and agents — the bots before the humans

Before a human ever clicks an AI link, AI crawlers visit your site to gather content for both training and live retrieval. Understanding which bots visit, what they do, and how to distinguish them from spoofed traffic is the precursor to clean AI analytics. These pieces also cover the new agent surface — AI buying on behalf of humans — that broke a lot of classic attribution assumptions.

Measurement — conversion rates, RPV, attribution

Numbers from the 200-site Stripe-connected cohort and the Attrifast measurement architecture. If you only ever cite one piece on AI traffic ROI to your CFO, it's the 2026 revenue benchmark below.

Visibility — getting cited in the first place

The measurement layer is half the AI search problem. The other half is making sure your content gets cited at all. These pieces cover visibility metrics, the multi-engine rank-tracker category, and the corpus-effect signals (Reddit, Wikipedia) that disproportionately move citation rates.

Prompt tracking vs rank tracking

The category renaming SEO is going through is significant. "Rank tracking" used to mean keyword position; in the AI-search era, the equivalent is "prompt tracking" — monitoring whether you appear in answers to specific prompts on specific engines. These pieces define the new category.

AI shopping — recommendation attribution

When ChatGPT or Perplexity recommends a product directly in an answer, the attribution stack most e-commerce stores have falls over. These two pieces cover per-engine shopping attribution — what gets recommended, how to detect the visit, and how to join it to a Stripe payment.

AI traffic attribution tools

The honest tool landscape — which platforms do prompt tracking (Profound, Peec, SEOcrawl, Loamly), which do revenue attribution (Attrifast, Loamly, HubSpot), which fake it through GA4, and which do not address AI traffic at all.

Frequently asked questions

What counts as "AI search" in 2026?

Practically: ChatGPT (chat + search modes), Perplexity, Claude (chat + research), Gemini (chat + AI Mode), Microsoft Copilot, Google AI Overviews, plus the long tail of smaller engines (DeepSeek, Phind, You.com). They each answer queries by synthesizing across sources rather than listing them. From an attribution perspective, they all share the same fundamental problem — they often strip the referrer, send traffic in patterns GA4 misclassifies, and route the visit through architectures classic analytics was not designed for.

How do I track AI search traffic if GA4 buckets it as Direct?

You stop relying on the GA4 default channel groups and add a custom AI-engine classifier — either via GA4 Custom Channel Groups (Admin → Data display) or, more reliably, via server-side detection that inspects the referrer, user-agent, and landing-page pattern. The dark-ai-traffic-ga4 article in the overview section above is the diagnostic walkthrough, and the chatgpt-referral-analytics-guide is the deep-dive on the recovery path. Attrifast does this classification automatically on the server side; if you do not want to roll your own, that is the wedge.

Which AI engine sends the highest-value traffic?

In our 200-site Stripe-connected cohort, ChatGPT sends the highest absolute volume of paid conversions. Perplexity sends the highest conversion rate per visit but at lower volume. Claude is the smallest volume but with the highest order value in B2B-skewed properties. Gemini sits between Perplexity and ChatGPT on conversion rate. AI Overviews citations show up as Google referrals (not as a distinct AI engine) and convert similarly to other Google organic traffic. The chatgpt-vs-perplexity-vs-claude-traffic-quality article in the measurement section has the per-engine breakdown.

Does AI search traffic actually convert better than search traffic?

Yes, materially, in our 200-site cohort — AI-sourced traffic converted at roughly 3-4x the rate of generic search traffic on average, with significant variance by vertical. The honest interpretation: AI traffic skews toward higher-intent queries (the user has already had a conversation with the model and arrived with a specific question), and the population doing AI search trends toward early-adopter / higher-income segments. Some of the conversion lift is intent quality, some is demographic. Read the chatgpt-vs-google-traffic-quality piece for the full data and methodology caveats.

How do I optimize for AI search?

Two surfaces with two different lever sets. For the live-retrieval surface (ChatGPT search, browse mode, AI Overviews, Perplexity), the levers are structural — schema markup, FAQ blocks, direct-answer formatting at the top of the page, primary-source citations in the body, freshness signals. For the training-corpus surface (no-browse model answers, default model recommendations), the levers are authority-based and slow — Wikipedia presence, Reddit mentions, consistent entity data, third-party citations from authoritative publishers. The /aeo and /geo hubs cover the optimization playbooks; this hub focuses primarily on the tracking and measurement layer.

What is the difference between AI search optimization and traditional SEO?

Traditional SEO optimizes for blue-link rankings; AI search optimization additionally optimizes for being the source the model summarizes. A page can rank #2 in Google for a query and get cited in 80% of ChatGPT answers for that query — or rank #1 and be cited in 0%. The two states are correlated but not identical. The structural signals that earn AI citations (schema, direct-answer blocks, primary citations) overlap with classic on-page SEO but are not the same set. Most teams now run both as a unified practice.

Do AI engines obey llms.txt and robots.txt?

Mostly yes, with engine-specific quirks. GPTBot (ChatGPT training crawler) and OAI-SearchBot (ChatGPT live search) obey robots.txt directives. ClaudeBot (Anthropic training) obeys robots.txt. PerplexityBot historically had some gray-area incidents; current behavior is mostly compliant. Google-Extended is the directive for Gemini training opt-out. llms.txt is a newer, voluntary convention — adoption is low (~7% of public SaaS sites in Q1 2026) and not all crawlers consume it. The llms-txt-vs-robots-txt piece is the full reference.

The Direct bucket is eating your AI revenue. Take it back.

Attrifast detects, classifies, and joins ChatGPT, Perplexity, Claude, Gemini, AI Overviews, and Copilot traffic to Stripe revenue server-side. Two-minute install, $29/mo, no GA4 surgery required.

Start the 5-day free trial →

5-day free trial · $29/mo · cancel anytime