Question t08 tail implement decision anchor
How can I test whether our content work changed what AI assistants recommend?
On 29 October 2026, ChatGPT recommended Search Console; Claude recommended three brands, starting with Ahrefs Brand Radar; Gemini recommended five brands, starting with Geoptie, without searching the web; Perplexity recommended Search Console. No brand was recommended by all four.
Asked once of each AI on 29 October 2026, with its own web search on and no location sent. Answers are shown verbatim. How we read them: one grand master model marked each brand, and a brand counts only if its name is in the answer word for word. The method.
ChatGPT
gpt-6-luna
Treat it as an experiment, not a before-and-after screenshot. AI answers vary across runs and over time, so repeated, consistent measurements matter. (arxiv.org)
A practical test
- Define what “recommend” means.
Don’t count every brand mention as a recommendation. For each answer, record whether you were:
- recommended as an option;
- named but not recommended;
- cited or linked as a source;
- absent—or described inaccurately.
- Build a fixed set of real buyer questions.
Include non-branded prompts like “What’s a good…?”, “Compare…”, and “Alternatives to…”. Keep the wording, language, location, and intent consistent; don’t test only prompts that already name your company.
- Create a comparison group.
Select similar topics or pages that won’t receive the new content work yet. Measure both the pages you update and the untreated group before and after. If the treated group improves more than the control group, that’s stronger evidence of an effect than a simple before/after increase. If all your content is changed at once, you can still track outcomes—but it’s harder to attribute the change specifically to that work.
- Run the same tests repeatedly.
Ask the prompts across the assistants that matter to your audience, several times at baseline and after the content is live and has had time to be discovered. Record the date, assistant, model if visible, prompt, full answer, and cited URLs. Compare rates across runs, not one-off answers.
- Track a small set of outcome metrics.
For example:
- Recommendation rate: answers that recommend you ÷ answers that returned a relevant recommendation.
- Citation rate: answers citing your site ÷ relevant answers.
- Position and competitor share: whether you’re a leading option and which competitors appear.
- Qualified visits and conversions: where referral data is available.
- Interpret the result cautiously.
Look at the change for treated pages versus controls, and check whether it holds across prompts and assistants. Note other changes during the test—PR, product launches, site changes, or model updates—that could also explain a shift.
For Google Search’s AI features, use Search Console alongside your prompt tests. Google now documents a generative-AI performance report for AI Overviews and AI Mode, with impressions by page and date; that measures visibility in Google Search, not whether assistants generally recommend you. (support.google.com)
Minimum viable setup: a spreadsheet, a fixed prompt set, treated and control topics, repeated runs, and a rubric that separates “mentioned,” “recommended,” and “cited.”
What it searched
- measure effect content SEO on AI assistant recommendations methodology randomized experiment
- AI answer engine visibility measurement recommendations brand mentions methodology study
- Google Search Central AI features website traffic measurement AI Overviews documentation
Sites it found
- support.google.comGenerative AI performance report (Search) - Search Console Helpcited
- arxiv.orgDon't Measure Once: Measuring Visibility in AI Search (GEO)cited
and 39 more found but not cited
- axios.com
- developers.google.com
- openseo.now
- generaldataworks.com
- blog.google
- pointvisible.com
- robotvisible.com
- ai-visibility-index.semrush.com
- ansedd.com
- knowledge.3bl.com
- emperorbrains.com
- sofindable.com
- arxiv.org
- medicodigital.com
- arxiv.org
- arxiv.org
- substack-post-media.s3.us-east-1.amazonaws.com
- nature.com
- scratchmm.com
- aivisibilityresearch.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- reddit.com
- techradar.com
- techradar.com
- techradar.com
- techradar.com
- en.wikipedia.org
- apnews.com
- en.wikipedia.org
Claude
claude-haiku-5-5
You can answer this with a before-and-after test: run a fixed set of prompts through the assistants before and after your changes, then compare the results, accounting for the fact that AI answers vary from run to run.
1. Set a baseline before you change anything
- Pick 20 to 50 high-value commercial prompts. One source suggests starting manually with that many, then moving to a dedicated tool once prompt volume becomes unmanageable. Pick 20 to 50 high-value commercial prompts, run them across LLMs of choice, and calculate your visibility score as brand mentions divided by total answers tested, multiplied by 100. Move to a dedicated tool once the prompt volume becomes unmanageable.
- Include a mix of informational, comparative, and transactional prompts, since they influence perception and choice differently. What types of queries (informational, comparative, transactional) influence perception and choice?
- Record the date, the assistant, the model version, and whether you used a logged-in or logged-out session for every run.
2. Sample repeatedly, not once
- Answers are not deterministic. One tracker notes that tools differ on whether they scrape the chat interface or the API, models change constantly, and personalization means the same prompt can return different answers. Run each prompt several times per assistant, using fresh sessions, and use the same method at both baseline and follow-up.
- Metrics are estimates from repeated prompt sampling. Track them over time and per model, never from a single answer.
3. Score the answers, not just whether your name appears
- Mention rate: how often your brand appears at all.
- Recommendation rate: how often the answer actively suggests you. A neutral list entry differs from a recommendation. Calculate it as the number of answers that contain an explicit recommendation for your brand by the total prompts tested.
- Share of voice: how often you appear compared with named competitors in the same answers.
- Sources cited: which pages the assistant draws on. This matters most for your test, because it shows whether your new content is being used at all. Trace the data citations behind responses.
- Accuracy and sentiment: whether the description of your brand is correct and favorable.
4. Separate your effect from background noise
- Keep a control group of relevant prompts that your content work did not target. If the targeted prompts move and the control group does not, the change is more likely your work. If both move, the cause may be model updates or market shifts.
- Compare the change against your run-to-run variation. A 5-point move may be noise if repeated runs routinely differ by that much.
- Allow time for effects. Content may take weeks to be crawled, indexed, and picked up, so check at several intervals, not just once.
5. Connect it to business outcomes (optional)
- Track AI-referred traffic, branded search, and sales inquiries alongside visibility scores. Treat these as supporting evidence, since the causal link is weaker than in your prompt tests.
Tools: You can start with a spreadsheet. Dedicated trackers such as Ahrefs' Brand Radar, Amplitude's AI visibility product, or Meltwater's GenAI Lens automate the sampling. Check how each one collects answers (interface scraping versus API), because that affects comparability with your manual results. Free audits also exist, but they are one-off snapshots rather than longitudinal tests.
Caveat: A single-session check or one tool's score can mislead. The most convincing evidence is a consistent, repeated, controlled comparison across several assistants over time.
What it searched
- measure brand visibility in AI assistant recommendations tracking
Sites it found
- meltwater.comAI Visibility: How to Track Your Brand Across Generative AIcited
- position.digitalHow to Monitor Brand Visibility in AI Searchcited
- visiblie.comAI Visibility Metrics & Score: What to Track (2026)cited
and 6 more found but not cited
- amplitude.comAI Visibility Platform
- martechseries.comAI Visibility Launches Free Tool to Measure Whether AI Assistants Recommend Your Brand
- visiblie.comWhat Is AI Visibility? Definition & Metrics - Visiblie
- venturemagazine.netHow to Monitor Brand Mentions Across AI Assistants - Venture
- ahrefs.comThe conference for marketers ready to win in 2026
- zenodo.orgPublished September 7, 2025 | Version 1.0
Gemini
gemini-3.1-flash-lite
Testing whether your content updates have changed AI assistant recommendations requires shifting from traditional "rank tracking" to Answer Engine Optimization (AEO). Because AI answers are generated dynamically and vary by prompt and model, you cannot rely on a single, static position.
Instead, use the following framework to measure your impact over time.
1. Build a Fixed "Prompt Set"
To see if your content changes are actually working, you must test them consistently against a "ground truth" set of questions.
- Define Your Prompts: Create 20–40 prompts that your ideal customers actually ask (e.g., "What are the best tools for [Your Category]?", "How to solve [Specific Problem]?", or "Compare [Your Brand] vs. [Competitor]").
- Establish a Schedule: Run this same set of prompts across major platforms (ChatGPT, Perplexity, Gemini, Google AI Overviews, and Claude) on a fixed cadence—weekly or bi-weekly.
- Track Trends, Not Anecdotes: A single check is meaningless because AI responses are inconsistent. Record whether your brand is:
- Mentioned: Simply named in the response.
- Recommended: Positively framed or suggested as a solution.
- Cited: Linked as a source (the gold standard for traffic and authority).
2. Use "Directional" Monitoring
Since there is no "AI tab" in Google Search Console, you must assemble a view from multiple sources to track the impact of your work.
- Manual Tracking (Free): Use a spreadsheet to log your prompt results over time. This is the most defensible method because it forces you to look at the qualitative shift in how the AI "talks" about your brand.
- Server Log Analysis: Check your server logs for "live retrieval fetches." Unlike bulk training crawls, these occur when an AI system is actively reading your page to answer a user’s live question. A spike in these specific fetches is a high-confidence signal that your content is being chosen as relevant.
- AEO Monitoring Tools: If you have the budget, tools like Geoptie, Profound, Ahrefs Brand Radar, or Conductor can automate the tracking of brand mentions, citation rates, and competitive share-of-voice across multiple AI engines.
3. Measure Business Outcomes
Visibility is a vanity metric if it doesn't lead to action. Connect your AI visibility efforts to business KPIs:
- AI Referral Traffic: Use Google Analytics 4 (or your preferred analytics platform) to isolate traffic from AI-driven domains (e.g.,
chatgpt.com,perplexity.ai). - Branded Search Spikes: Monitor if your direct traffic or branded keyword volume increases when your content begins to earn more citations in AI summaries.
- Conversion Rates: Track if visitors arriving from these AI-engine referrers are higher quality (e.g., longer time on site, higher conversion rates) compared to traditional search traffic.
Summary Checklist for Your Team
| Step | Action | Why? |
|---|---|---|
| 1. Baseline | Run 20+ core questions through 3–5 AIs before publishing. | You need to know your starting point. |
| 2. Audit | Check if the AI cites your site or a competitor’s. | Identifies your direct "AI competitors." |
| 3. Optimize | Update content to answer the "missing" parts of the AI answer. | AI often prioritizes concise, structured, and authoritative answers. |
| 4. Monitor | Re-run the same 20+ prompts every 2 weeks. | Tracks if the "fix" actually changed the AI's behavior. |
Important Note: Avoid looking for a "ranking" number. Instead, look for consistency. If your brand was absent from your "category" prompt but starts appearing in 3 out of 10 runs after your content update, you are moving the needle.
What it searched
No web search run. It answered without searching.
Sites it found
None.
Perplexity
perplexity/sonar
Treat it like a before-and-after experiment, not a one-off “ask an AI and see” check.
- Define what “changed the recommendation” means. Track separately whether an assistant:
- mentions your brand,
- recommends it (not just names it),
- links to or cites your specific content,
- recommends competitors instead,
- describes your offering accurately.
- Choose a fixed prompt set. Use real questions from customers, sales calls, support, and search queries. Include discovery, comparison, and purchase-intent prompts. Keep the wording and market context consistent.
- Record a baseline before changing content. Run each prompt on the assistants and platforms that matter to your audience. Save the date, prompt, full answer, brands named, recommendation, and cited URLs. Use fresh chats and repeat each prompt several times—answers can vary between runs. A practical starting point is three to five runs per prompt per assistant. 915
- Make the content change and keep a change log. Note the page, what changed, publication date, and the prompt groups you expect it to affect.
- Rerun the same test. After the content has had time to be found and reflected in results, use the same prompts, assistants, settings, and number of repetitions. Compare rates, not isolated answers:
- Recommendation rate = runs that recommend you ÷ total runs
- Citation rate = runs citing your page ÷ total runs
- Mention rate = runs mentioning you ÷ total runs
Break results down by assistant and prompt category, and track competitor mentions or citations too. 810
- Check business outcomes separately. Monitor visits and conversions from AI-referred traffic, alongside ordinary organic clicks and conversions. For Google’s AI search features, Search Console documentation currently describes reporting on impressions and pages shown; use analytics for visits and conversions. 23
Be cautious about causality. AI answers vary, and platforms, retrieval systems, and competitors change over time. A better test is to update some comparable pages or topic groups while leaving others unchanged, then compare how both groups shift. Keep the observation window and measurement method the same, and report the sample size and dates. A rise in recommendations after an edit is evidence of a possible effect—not proof by itself. 810
What it searched
- measure AI search visibility recommendations content changes methodology 2026
- AI assistants citation tracking prompt testing content marketing measurement
- Google AI Overviews reporting search console AI traffic measurement 2026
Sites it found
- support.google.comGenerative AI performance report (Search)cited
- developers.google.comAI Features and Your Website | Google Search Centralcited
- genezio.comProve and Defend AI Visibility Numbers to Leadership - Geneziocited
- blog.hubspot.comAnswer engine visibility: The playbook for marketers - HubSpot Blogcited
- blog.hubspot.comHow to identify content gaps for AI visibilitycited
- supermetrics.comHow to measure and report AI search visibility in 2026cited
and 9 more found but not cited
- developers.google.comIntroducing Search Generative AI performance reports in ...
- windsor.aiHow to Track AI Overviews for Your Keywords
- falia.coGoogle AI Overviews: what does Search Console measure?
- blog.hubspot.comHow often to run AEO prompt tracking: A cadence guide
- searchengineland.comWhat 9 months of AI Overview data and 51,000+ tracked events reveal
- keywordseverywhere.comGoogle AI Overviews Tracker 2026: Changes, Statistics & ...
- targetinternet.comHow to measure AI search visibility in GA4 and Search Console
- wppoland.comAI-citation monitoring: what to track and how often (2026)
- searchengineland.comContent strategy in 2026: What actually changed (and what ...
AI search visibility tools: what AI recommends, November 2026 Every answer as CSV or JSON