---
title: "AI search query report | SEO Skill"
description: "Turn real Search Console queries into repeatable AI monitoring prompts so assistant answers can be checked against demand your site already sees."
canonical: "https://seoskill.dev/docs/reports/seo-to-ai-query"
language: "en"
---

# AI search query report

Build AI monitoring prompts from the searches already associated with your site. This gives the monitoring a demand signal without claiming that SEO queries and assistant prompts are identical.

## 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 seo
```

Run setup after installation.

```
seo start
```

Turn returned searches into repeatable AI monitoring prompts.

```
seo seo-to-ai-query --project example
```

## What you get from this report

Turn real Search Console queries into repeatable AI monitoring prompts so assistant answers can be checked against demand your site already sees.

Best for

You need a limited prompt corpus whose source queries and dates remain attached.

Needs

Returned Search Console queries

You get

Turn real Search Console queries into repeatable AI monitoring prompts so assistant answers can be checked against demand your site already sees.

Use next

Find AI referral traffic

Every report follows the same rules for missing data and outside estimates.[See how report data works](https://seoskill.dev/docs/reports#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.

### Returned Search Console queries

Provides the source wording, impressions, dates, and property scope behind each prompt.

### Prompt and source row limits

Bound the eligible query set and final monitoring corpus.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You want to know whether AI assistants already send visits recorded by your analytics property.

Run AI referrals. It reads captured Google Analytics referral traffic and reports the sources, landing pages, sessions, and available engagement evidence. Generated monitoring prompts contain no referral or visit data.

AI referral traffic report

](https://seoskill.dev/docs/reports/ai-referrals)[

### You need to know whether an assistant currently mentions, cites, or recommends the site for a prompt.

Run AI prompt observations for a small fixed subset. It keeps each answer, citation, exact model, settings, time, cache state, and cost beside the Search Console source evidence used to build the prompts.

AI prompt observation report

](https://seoskill.dev/docs/reports/ai-prompt-observations)

## 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 seo-to-ai-query --json
```

Once the input is valid, run the report through the report catalog.

```
seo reports run seo-to-ai-query --params '{"site":"sc-domain:example.com","days":90,"limit":20,"minImpressions":100,"maxRows":10000}' --json
```

### MCP

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": "seo-to-ai-query"
}
```

Run the report after the agent has checked and filled the input.

```
{
  "id": "seo-to-ai-query",
  "params": {
    "site": "sc-domain:example.com",
    "days": 90,
    "limit": 20,
    "minImpressions": 100,
    "maxRows": 10000
  }
}
```

### 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 seo
```

Run the report from your TypeScript application.

```
import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'seo-to-ai-query',
  {
  "site": "sc-domain:example.com",
  "days": 90,
  "limit": 20,
  "minImpressions": 100,
  "maxRows": 10000
},
)

console.log(result)
```

## What to do next

Review the generated prompts so they still represent the searches and topics you care about. Save a stable prompt set for external answer monitoring and keep any observed mentions separate from Search Console performance.

1.  01Choose representative variants and monitor them on a controlled schedule.
2.  02Use AI referrals separately for observed Google Analytics referral evidence.

## Related reports

[

Find visits from known AI assistants in Google Analytics, see which landing pages received them and keep missing referrers separate from confirmed traffic.

AI referral traffic report

](https://seoskill.dev/docs/reports/ai-referrals)[

Find Search Console queries with forum, review, comparison or discussion intent so your content can answer the format people are looking for.

Community intent report

](https://seoskill.dev/docs/reports/community-intent)[

Check whether crawlers can access and use important pages in AI search. Find technical blockers without inventing a visibility or citation score.

AI search readiness audit

](https://seoskill.dev/docs/reports/ai-readiness)

## Sources used by this report

These primary sources define the provider data or search controls used by the result.

-   [Search Console Search Analytics API guidance](https://developers.google.com/webmaster-tools/v1/how-tos/search_analytics)
-   [Google guidance for AI features and websites](https://developers.google.com/search/docs/appearance/ai-features)