AI mention research report
See where a named brand or product appears in a provider-indexed set of AI answers, which domains are cited and whether returned questions overlap with searches already associated with your site. The report keeps indexed research separate from live prompt checks.
Install and run the report
Install the CLI once, then run seo start to connect your site and Google data. After setup you can run this report yourself or ask your agent to run it.
Install the SEO CLI globally.
npm i -g seoRun setup after installation.
seo startResearch one target in a limited provider-indexed AI dataset.
seo reports run ai-mention-research --params '{"target":{"label":"Example Analytics"},"surface":"google-ai-overview","countryCode":"GB","languageCode":"en","location":{"code":2826}}' --jsonWhat you get from this report
Compare provider-indexed AI mentions, cited domains and question samples with optional Search Console evidence for one exact surface and market.
- Best for
- You need mention and citation evidence beyond referral traffic or technical eligibility.
- Needs
- Provider-indexed AI mention data
- You get
- Compare provider-indexed AI mentions, cited domains and question samples with optional Search Console evidence for one exact surface and market.
- Use next
- Turn SEO queries into AI prompts
Every report follows the same rules for missing data and outside estimates.See how report data works.
What you need before you run it
The report uses the information below. Optional sources are only used when you ask for them.
Provider-indexed AI mention data
Provides target metrics, cited source domains, question samples, observation dates, model names, and the exact surface and market.
Optional Search Console query rows
Adds limited Search Console query and landing-page evidence for a property you own.
Explicit target and comparison set
Defines one named target, its aliases, and at most five named competitors measured in the same provider request.
Use a different report for these jobs
These jobs need a different report or a manual review.
You need the current answer for a fixed prompt rather than an indexed research dataset.
Run AI prompt observations. Keep the prompt, surface, requested and effective model, market label, settings, time, answer, and citations together so a later compatible observation can be compared.
You need measured visits from known AI products.
Run AI referrals. It reads Google Analytics referral sessions and landing pages instead of inferring traffic from mention records.
You only need technical crawl, index, or snippet eligibility evidence.
Run AI search readiness. It checks technical controls without claiming that an AI product mentioned or cited the site.
Use the report with an agent or in code
The command above is enough for most work. These options let an agent, script or application run the same report with explicit input and structured output.
CLI
Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the report with the validated parameters.
Check the current input before the agent or script runs the report.
seo reports describe ai-mention-research --jsonOnce the input is valid, run the report through the report catalog.
seo reports run ai-mention-research --params '{"target":{"label":"Example Analytics","aliases":["Example"]},"competitors":[{"label":"Competitor Cloud"}],"domain":"example.com","surface":"google-ai-overview","countryCode":"GB","languageCode":"en","location":{"code":2826},"site":"sc-domain:example.com","sampleLimit":10}' --jsonMCP
An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the report.
Ask the MCP server for the current report input.
{
"id": "ai-mention-research"
}Run the report after the agent has checked and filled the input.
{
"id": "ai-mention-research",
"params": {
"target": {
"label": "Example Analytics",
"aliases": [
"Example"
]
},
"competitors": [
{
"label": "Competitor Cloud"
}
],
"domain": "example.com",
"surface": "google-ai-overview",
"countryCode": "GB",
"languageCode": "en",
"location": {
"code": 2826
},
"site": "sc-domain:example.com",
"sampleLimit": 10
}
}TypeScript
Install the package in a Node 22 project when your application needs to run the report directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server.
Add the SEO package to your project.
npm install seoRun the report from your TypeScript application.
import { executeReport } from 'seo/mcp'
const result = await executeReport(
'ai-mention-research',
{
"target": {
"label": "Example Analytics",
"aliases": [
"Example"
]
},
"competitors": [
{
"label": "Competitor Cloud"
}
],
"domain": "example.com",
"surface": "google-ai-overview",
"countryCode": "GB",
"languageCode": "en",
"location": {
"code": 2826
},
"site": "sc-domain:example.com",
"sampleLimit": 10
},
)
console.log(result)What to do next
Inspect the exact market, cited pages and returned questions before acting on a mention difference. Check your existing pages, then use a fixed prompt observation only for the small question set where a current answer would change the decision.
- 01Inspect cited pages and current results for the questions that would change a decision.
- 02Use ai-prompt-observations for a small stable question set before making claims about current answers.
- 03Check existing pages, source rights, useful variation, and representative records before expanding a programmatic template.
Related reports
Turn real Search Console queries into repeatable AI monitoring prompts so assistant answers can be checked against demand your site already sees.
Check fixed prompts against exact current AI models, retain answer and citation evidence locally, and compare only compatible observations over time.
Find visits from known AI assistants in Google Analytics, see which landing pages received them and keep missing referrers separate from confirmed traffic.
Research ways to expand an existing programmatic page system with Search Console, keyword ideas, current results and competitor pages before building more.
Build a content brief from one page, its Search Console queries and the headings or topics already present. Keep every suggestion tied to demand.
Sources used by this report
These primary sources define the provider data or search controls used by the result.