Learn to monitor your brand in ChatGPT, Perplexity, Gemini, and Google AI Overviews. Build a prompt panel, measure share of voice, and close visibility gaps.

Unlike a search result page ranking, there is no fixed position to hold in AI search. If you run the same buying prompt twice in the same hour you can get different brands, different citations, different framing back. API-served models reproduce their own outputs in only 22.1% of tests, so it's most important to track frequency, not rank. That means a fixed panel of buyer prompts, run repeatedly across ChatGPT, Perplexity, Gemini, and Google AI Overviews, logged by hand first and automated only once you know what you're measuring.
Here's how to build that panel and turn it into a number leadership can actually track.
A rank tracker checks a stable artifact because Google crawls, indexes, and ranks, and the position it reports today is roughly the position every searcher in that market sees.
An AI engine generates its answer at request time, per session, with no persistent index of results to poll. Re-run the same prompts weeks later and the citations behind the answers routinely shift, on some engines more than others.
Instead of asking what position you hold for a keyword, you're asking what share of answers you appear in, how you're described, and which sources put you there. Your existing rank tools can't answer any of that. They track keyword positions on SERPs, and there's no SERP to track here. Queries are conversational prompts with no fixed universe, and answers vary run to run, so measurement means sampling the same prompts repeatedly over time.
Each of the four major surfaces selects sources differently, so a mention on one tells you almost nothing about the others. Only a small fraction of the top sources cited across ChatGPT, Perplexity, and Google AI Overviews actually overlap.
Track all four separately from day one. A blended view can hide the platform where performance is weakest.
Once you know where to look, the next job is deciding exactly what to ask. Write prompts in buyer language, as full questions with use cases and constraints. Then freeze the set. Week-over-week numbers only mean something if the inputs don't move, and one widely used measurement framework recommends a frozen prompt set of 30 to 60 prompts per topic cluster, re-run weekly. Start with 20 to 30 per product line across five prompt types:
Pull the phrasing from sales call transcripts and support tickets where you can. A panel built from marketer vocabulary measures a conversation buyers aren't having.
We push every team we work with to run this by hand first, before any tool. The manual pass teaches you what the dashboards will later summarize, and a spreadsheet is all you need to start.
Every logged run tells you whether you appeared, how much of the conversation you own, how you were framed, and who the answer cited.
Mention frequency is the share of prompt runs where your brand appears at all. AI share of voice compares you against competitors. A simple formula is "(number of my brand mentions / total number of all brand mentions) × 100," counting each brand once per response even if it's named twice.
Worked example. 25 prompts run 4 times each is 100 responses. Your brand appears in 18, Competitor A in 30, Competitor B in 12. Total mentions come to 60, and your AI share of voice is 30%.
Report it per platform. A blended number can hide that you own Perplexity and are invisible in AI Overviews, and frankly, that's the kind of gap that costs you the board's confidence once someone else notices it first. Since no industry-standard formula exists and vendors weight position and topic volume differently, state your formula in the report once and never change it mid-trend.
Log a positive, neutral, or negative call plus the exact clause around your brand name, because "a budget option for small teams" and "the standard for enterprise" are both mentions, and they're different assets. One study of 102 brands across 102,025 responses found presence flipped only 6.8% between measurements while sentiment framing flipped 45.5% of the time. Counting mentions without reading framing understates your risk by an order of magnitude.
Log every domain each answer cites, and log citations separately from mentions, because the two diverge sharply. One citation study found ChatGPT rarely names a brand outright but links to its domain in most of the responses where it does appear. Gemini runs the opposite way. It mentions brands generously in prose but attaches a source link only a small fraction of the time.
One analysis of 6.8 million citations found brand-controlled sources drive 86% of citations, with first-party websites accounting for 44% and listings for 42%. Your site and listings are the base you control directly. The third-party remainder, the review sites and publications the engines keep citing in your category, becomes the lever list in your citation log, and your PR or partnerships team uses it to close mention gaps from outside.
You've been logging your own numbers on this panel. Turn it on your competitors next by running the identical panel with competitor names substituted into the branded prompts. The comparison and alternatives prompts already capture most of it, so this is largely a second read of data you've logged. Compute each competitor's share of voice with the same formula.
If your share of voice and Competitor A's both drop 10 points in a month, the model's behavior changed. If only yours drops, you have a problem. And log which domains get competitors cited. Competitor-only citation domains become named, addressable outreach targets instead of vague "do more PR" line items.
Visibility numbers matter most once they connect to what the business already tracks. Track crawler activity in your server logs and human referrals in GA4. In server logs, hits from OAI-SearchBot, which surfaces websites in ChatGPT search results, and PerplexityBot confirm the engines are fetching your pages at all.
In GA4, know the blind spots first. The built-in AI Assistants channel excludes AI Overviews and AI Mode, which GA4 keeps under Organic Search because they run on Googlebot with no separate referrer. GA4 cannot distinguish the largest AI search surface from ordinary organic clicks. ChatGPT's mobile app passes no referrer either, so GA4 classifies that traffic as Direct.
Blind spots to label in the report:
For what GA4 can see, build a custom channel group. Go to Admin → Data display → Channel groups, add a channel with the condition Source matches regex, and move it above Referral so the sequential waterfall catches it. A ready-made regex covers the major sources:
^https:\/\/(www\.meta\.ai|www\.perplexity\.ai|chat\.openai\.com|claude\.ai|chat\.mistral\.ai|gemini\.google\.com|bard\.google\.com|chatgpt\.com|copilot\.microsoft\.com)(\/.*)?$Expect small volume and outsized quality. One ecommerce dataset shows ChatGPT referrals converting at 11.4% versus 5.3% for organic search. GA4 referral counts undercount the effect too. Users who get an AI recommendation are 2.5 times more likely to visit the brand's site within seven days, and over half of those visits arrive through branded search, not a direct AI referral. Put branded search volume on the same report as AI share of voice to catch the lift GA4 misses.
Manual logging teaches the method. At some point, though, the panel outgrows a spreadsheet, and a tool earns its fee by doing what you can't do by hand. It runs the panel daily at sample sizes that smooth out non-determinism, computes share of voice, extracts every citation, and keeps trend history. It does not pick your prompts, judge whether "cheap option" is acceptable framing, or produce the content that closes a gap. That work stays with your team.
Keep your manual spreadsheet running for the first month after adopting any tool. Comparing its numbers to your own logs shows you how its sampling differs from a real buyer session, and where to trust it.
Whether you're running this by hand or through a tool, someone still has to own the rhythm. Assign one owner. In most teams that's the content or demand gen lead who built the panel. Split the rhythm into three loops.
Weekly: The owner runs the panel (or reviews the tool dashboard), updates per-platform share of voice, flags sentiment flips with the quoted framing, and notes new or lost citation domains. Budget 30 to 60 minutes with tooling, or a few hours without it.
Monthly, for leadership: One page. Share of voice trend per platform against your top two competitors, a sentiment summary with two or three quoted framings, citation domain movement, AI referral sessions and conversions from the GA4 channel group, and actions taken plus actions planned. Never report a single week's swing as a win or a crisis. Use four-week trends at minimum, given how much answers churn.
Quarterly: Refresh the panel for new competitors, products, and buying language. Version the change and annotate the trendline so nobody compares pre-refresh and post-refresh numbers blindly.
We've watched this exact bottleneck stall more than one otherwise-good tracking program. If the weekly run starts crowding out the content work it's supposed to inform, have the owner consolidate the tracking, content, and SEO workflows into a single system rather than running them separately.
Tracking tells you where you stand. Closing the gap is the work we spend most of our time on with clients, and it starts with earned third-party mentions. A 75,000-brand study found brand web mentions correlate with AI Overview visibility at 0.664, well ahead of Domain Rating (0.326) and total backlinks (0.218), and brands in the top quartile of web mentions receive up to 10× more AI Overview mentions than the next quartile. A follow-up piece in Search Engine Journal covered the same brand-mention correlation. Point your digital PR at the citation log you built. The review sites and industry publications each engine already cites in your category are named there, and YouTube channels count too when they show up in the log.
Use the citation log as a work queue:
On your own site, the moves with the strongest evidence:
Hallucinated mentions, where an engine states something false about your product, will also show up in your logs. The major platforms don't document a dedicated factual-correction workflow for brands. Perplexity accepts reports through the flag icon or support@perplexity.ai, routed through Perplexity support with the query URL, a description of the error, and the expected result. Google offers a Report a problem link beneath each AI Overview. OpenAI's trademark dispute form covers infringement only, not factual errors. File the reports, then treat the durable fix the same as the visibility fix. Publish accurate, structured pages the engines can crawl, and get the correct version echoed on the third-party domains they cite.
That same discipline, publish once and let the citations follow, is what turns a monitoring habit into an actual visibility program. GrowthOS runs the loop end to end. Insights tracks your citations and share of voice across the same engines you're already logging by hand, and feeds each gap straight into Creation so the content that closes it gets made next. If your tracking spreadsheet needs a system behind it, book a demo. Engagements start from $6,000/mo.

How to improve your brand's visibility in AI search
Get cited in ChatGPT, Perplexity, and Gemini. Brand recognition sets your floor. On-page structure earns the citation. Here are the levers that actually move the odds.
Read
How AI Search Engines Select and Cite Sources
Learn how AI search engines retrieve, rank, and cite sources. Discover the signals that win citations and how to improve your brand's AI visibility.
Read
What Answer Engine Optimization Is and How to Earn AI Citations
Answer engine optimization earns citations inside AI-generated answers. Learn how to structure content for ChatGPT, Perplexity, and Google AI Overviews.
Read
How to Generate llms.txt Files for AI Visibility
Generate llms.txt files with web tools or CLI. Learn format, placement, and whether it improves AI search visibility across ChatGPT, Perplexity, and Claude.
ReadWe use cookies and similar technologies to improve your experience and measure site performance. Cookie Policy