AI Search And Product Discovery: How To See If It Is Affecting Your Traffic

Product discovery used to leave footprints. A buyer searched, clicked, compared and came back, analytics saw every step, and your marketing team could rebuild the journey from the logs.

AI search broke that trail. Now a buyer asks ChatGPT or Gemini which tools solve their problem, reads a synthesized shortlist, and maybe interrogates it for ten minutes. If they reach your site at all, they arrive as a "direct" visitor your analytics has never seen before. The discovery happened, the consideration happened, and sometimes even the shortlist happened. Nothing in your stack recorded any of it, so the buyer's first measurable touch now lands halfway through their journey.

So how do you find out whether AI engines are already discovering your product for buyers? You want that answer from your own data, this week, rather than in theory. There are seven signals, and none of them needs new tooling for the first check. Together they turn "probably, maybe?" into a defensible read on how much of your funnel has already moved upstream of your instrumentation.

Signal one: the referral strings you already have

Start with the direct evidence by filtering your analytics referral report for the known AI sources:

Any nonzero row confirms that AI answers are putting your links in front of buyers, and that some of those buyers click.

Read those rows with two rules in mind. The first is to expect undercounting. App contexts and privacy settings strip referrers, so a real slice of AI-referred visits lands in direct or unassigned, and the rows you can see are a floor rather than the total.

The second rule is to ignore the small absolute numbers and read the slope and the landing pages instead. AI referrals characteristically arrive deep, on pricing, docs and comparison pages rather than the homepage, because the engine already answered the early questions. A handful of weekly sessions landing straight on pricing isn't noise. It's the visible tip of a discovery process running upstream.

If you use GA4, build the segment once as a custom channel group or exploration filter that matches the referrer strings above, plus session source containing "openai" or "perplexity". Five minutes of configuration turns every future check into a glance, and your historical data is already sitting there waiting to be segmented.

Signal two: prompt-shaped queries in Search Console

Open GSC, sort your queries by length, and look for strings that read like sentences. They're constraint-stacked, question-formed and oddly specific, phrasings nobody would have typed into 2019 Google. When they appear and grow, your market has started searching conversationally, and Google's AI machinery is fanning those conversations into sub-queries your pages get retrieved against.

The field guide to reading GSC's AI data covers the full method. For this audit, you only need to know whether the prompt-shaped share of your impressions is growing quarter over quarter. If it is, discovery behavior in your market has already shifted, whatever your referral report says.

While you're in Search Console, turn on the AI performance report if you haven't already. It shows impressions on Google's AI surfaces with real limits (no clicks, no query strings), but it gives you a direct answer to "does Google's answer layer show my pages at all."

RANKCONTROL

Know exactly what AI says about your competitors.

RankControl's Recon Agent monitors competitor citations across ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode. See where they show up and you don't.

See how it works→

Signals three and four: the shadows in your own data

Signal three is branded search growth without a campaign behind it. When an engine recommends you, the buyer often doesn't click anything. They finish the conversation and then search your name, so pull two years of branded query volume and look for growth that no launch, ad flight or PR moment explains.

Unexplained branded lift is the classic shadow of answer-layer exposure, and it's often the largest AI-discovery signal a company has. It hides in a report nobody reads because it "only" contains people who already knew the name. That's exactly backwards, since it contains people who just learned the name somewhere you couldn't see.

Signal four is direct traffic holding firm on deep pages. Direct visits to your homepage are bookmarks and habit. Direct visits to a specific comparison page or integration doc come from people who were handed the URL, and AI answers now do a lot of that handing. Segment your direct traffic by landing-page depth. A rising share of deep-page direct entries, especially to money pages, is discovery traffic in disguise.

Signal five: the bots in your logs

Your server logs hold the supply-side evidence. One niche-site owner described the moment well in r/Agentic_SEO. Unexpected ChatGPT referrals to a six-month-old site prompted him to build a dashboard tracking which AI crawlers visit, what they fetch and how often they return, and the resulting feed runs around the clock.

You don't need a custom dashboard for your first pass, just one grep. Search a month of access logs for the retrieval-time fetchers, meaning ChatGPT-User, PerplexityBot and Google's on-demand fetches, as distinct from training crawlers like GPTBot. A retrieval hit means a live answer pulled your page while a human waited. That's the closest thing your logs offer to watching your product get discovered in real time.

Note which pages get fetched repeatedly, since those are the pages the engines consider quotable. How much they overlap with the pages you consider important, or fail to, is a finding of its own.

Signals six and seven: the outside view

For signal six, ask the engines yourself. Run your ten most valuable buying queries, the "best X for Y" phrasings your deals actually start from, across ChatGPT, Perplexity, Gemini and Google's AI Mode. Log whether you're named, how you're described and who gets named instead.

Thirty minutes, once, gives you the discovery answer directly. Either the engines already recommend you, or you're watching competitors get discovered in your place, query by query. Teams that run this as a weekly tracked set turn the one-off snapshot into a trend line that catches shifts early.

Signal seven means interrogating your own signups. Add one field to your signup flow or your first sales call: how did you hear about us? "ChatGPT told me" answers have gone from novelty to routine across B2B in the past year. Self-reported attribution, for all its fuzziness, is the only instrument that sees the conversations analytics never will. If even a few percent of new signups name an AI assistant unprompted, scale that by everyone who didn't say, and you have your answer about whether discovery moved.

RANKCONTROL

26 content formats. Published on your domain. Matched to your brand.

Guides, comparisons, listicles, case studies, and more. RankControl generates content that gets cited by ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode.

Start free→

A worked afternoon, for shape

Here's the audit run end to end on an illustrative mid-market SaaS, a project management tool with decent organic traffic and no AI strategy yet. This is what each check turned up:

That discontinued-plan answer is somebody's corroboration problem, and it's also an opportunity.

It's tempting to skip the signup survey on a first pass, because it's the slowest signal to yield data. That would be a mistake. The survey is the only signal on the list that captures conversations no instrument sees, so skipping it structurally biases your whole audit toward "nothing is happening." Start it first, precisely because it needs lead time.

The verdict for this fictional team is posture two, happening but dark, with the eleven referral sessions as the visible tip. What they need next is the weekly query run and an extraction pass on the two pages the bots already favor, rather than another round of measurement.

Reading the seven together

Run all seven and you'll land in one of three postures.

The first is confirmed and visible: referrals exist, bots fetch your pages and the engines name you. Discovery is happening and partly measurable, so instrument it properly and start optimizing your citation share.

In the second, happening but dark, referrals sit near zero while branded search grows, deep-page direct traffic rises and the engines name you when asked. Discovery is happening upstream and your analytics simply can't see it. That's a measurement gap, and you should never read it as evidence of absence.

The third posture is genuinely absent. The engines don't name you, bots barely visit and there are no shadows in the data. Your market may still be early, or your content isn't retrievable, and the fix starts with extraction-ready structure on your money pages rather than with measurement.

The mistake to avoid is the one the broken trail invites: concluding from a quiet referral report that AI discovery isn't relevant to you yet. The defining feature of this shift is that the most important discovery events leave the faintest tracks. Companies that figure that out early get a quarter or two of uncontested answers while their competitors wait for a dashboard to tell them what already happened.

An afternoon on the seven signals settles the question with your own data. The standing version, one segment and one weekly query run, keeps it settled from then on.

Your competitors are getting cited by AI. You're not.

Every day without citation tracking is a day your competitors pull ahead in ChatGPT, Perplexity, and Claude.

Show me who's getting cited→2-minute overview · real case-study numbers