# Search Console API and AI Analysis with Claude and ChatGPT

> Analyse Search Console data with the API, exports and AI assistants like Claude and ChatGPT, with prompts, quotas and checks.

Source: https://mentionx.ai/learn/search-console/search-console-api-ai-analysis  
Author: Dipuck Jones, founder of MentionX  
Updated: 4 November 2026  
Level: Practitioner

**The Search Console API and AI assistants let you analyse more data, faster: pull it with the API or exports, then ask Claude or ChatGPT to find patterns.** The rule is simple: let AI suggest, then verify in Search Console.

*Checked 4 November 2026 (CET) against Search Console Help and Google Search Central documentation. Search Console reports and rollouts change often, and some features only appear for eligible properties, so confirm in your own property. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.*

> **Key takeaways**
>
> - The API offers Search Analytics, Sitemaps and URL Inspection.
> - Quotas limit load and request rates.
> - Exports plus AI assistants find patterns fast.
> - Always verify AI findings.
> - Remove personal data before uploading.

## API options

From Google's [Search Console API usage limits](https://developers.google.com/webmaster-tools/limits):

| API | Use | Limits |
|---|---|---|
| Search Analytics | Performance data beyond the UI | Load quotas (10-minute, daily) + QPS/QPM/QPD |
| URL Inspection | Index status at scale | Per-site and per-project quota |
| Sitemaps | List and submit sitemaps | Standard limits |

## AI analysis

See [Claude CSV analysis of GA4 and Ads data](https://mentionx.ai/learn/claude/claude-csv-analysis-ga4-ads), [Claude MCP connectors for marketers](https://mentionx.ai/learn/claude/claude-mcp-connectors-marketers), [ChatGPT data analysis of marketing exports](https://mentionx.ai/learn/chatgpt/chatgpt-data-analysis-marketing-exports) and [Analysing GA4 exports with Claude and ChatGPT](https://mentionx.ai/learn/ga4/ga4-exports-ai-analysis-claude-chatgpt).

*Our view:* AI-powered configuration inside Search Console (lesson 4) is for setting up views; external assistants are for interpreting exports.

> **Pro move:** ask the assistant to output the regex it used to group queries, then paste it into Search Console to confirm.

## Prompts for analysing exports

| Task | Prompt pattern |
|---|---|
| Find decliners | "Here is a CSV of pages with clicks for two periods. List the 10 pages with the biggest absolute drop and suggest a likely reason based only on the query columns." |
| Cluster queries | "Group these queries by intent: informational, comparison, pricing, branded. Return a table." |
| Write a summary | "Write a 5-bullet summary for a marketing director. Don't invent numbers; use only the data provided." |
| Check regex | "Test this RE2 regex against these 20 queries and show which match." |

Always check AI output against the data. Assistants can misread columns or round numbers.

## Troubleshooting

| Problem | Cause | Fix |
|---|---|---|
| API quota errors | Load quota exceeded | Narrow date ranges, fewer dimensions, spread requests |
| API totals differ from UI | Row limits and anonymised queries | Compare trends |
| AI tool invents figures | Model filled gaps | Ask it to cite rows; verify |
| Sensitive data concerns | Exports contain URLs and queries | Remove personal data; follow company policy |

## Using the Search Analytics API without code

Google's [Search Analytics query reference](https://developers.google.com/webmaster-tools/v1/searchanalytics/query) documents every field, and you can try requests from Google's API documentation after signing in. A typical request body:

```json
{
  "startDate": "2026-08-01",
  "endDate": "2026-10-31",
  "dimensions": ["page", "query"],
  "rowLimit": 25000,
  "dimensionFilterGroups": [{
    "filters": [{"dimension": "page", "operator": "includingRegex", "expression": "/blog/"}]
  }]
}
```

Per the reference, `rowLimit` accepts 1 to 25,000 (default 1,000), and `startRow` pages through further rows. Operators include `contains`, `equals`, `notContains`, `notEquals`, `includingRegex` and `excludingRegex` (RE2). Dates are in Pacific Time. Set `dataState` to `all` to include fresh, incomplete data, and `type` to `discover`, `googleNews`, `news`, `image`, `video` or `web` (the default). The API returns top rows, not a guaranteed complete set. Spreadsheet add-ons and Data Studio also call the API for you.

## Reducing quota problems

- Request fewer dimensions at once; page and query together is the most expensive combination.
- Use shorter date ranges and loop over them.
- Cache results; don't re-request the same data daily.
- For big, ongoing needs, bulk export (lesson 18) avoids API quotas entirely.

## A prompt library for Search Console exports

| Goal | Prompt |
|---|---|
| Content gaps | "These are queries with many impressions and low CTR for our site. Group them into topics and suggest which topics need a dedicated page. Cite example queries for each topic." |
| Title rewrites | "For each page and its top 5 queries, suggest a title under 60 characters that matches the dominant intent. Don't invent features." |
| Cannibalisation | "Find queries where two or more of our URLs get impressions. List query, URLs and clicks for each." |
| Executive summary | "Summarise this month vs last month in 5 bullets for a marketing director. Use only these numbers and say when a change is small." |
| Regex builder | "Write an RE2 regex that matches these 10 queries but not these 10. Explain each part." |

## Verification rules

1. **Ask the assistant to cite rows** for every claim.
2. **Spot-check three claims** in Search Console.
3. **Check arithmetic** on any totals or percentages it reports.
4. **Don't let it guess causes** without evidence; treat suggested causes as hypotheses.
5. **Keep the prompt** and the export date so next month is comparable.

## Data handling

Search Console exports contain URLs and queries. Queries can occasionally include personal information people typed into Google. Remove any such rows, follow your company's policy for AI tools, and prefer workspace or enterprise accounts with data controls when your company provides them.

## Ledgerline walkthrough: a cannibalisation check

1. The SEO lead pulled page and query data for 3 months with the API Explorer, filtered to the blog.
2. They uploaded the CSV to ChatGPT and used the cannibalisation prompt.
3. ChatGPT listed queries where two blog posts competed. The lead verified three in Search Console with a query filter and the Pages tab.
4. Two posts covering "invoice approval workflow" were merged, with a redirect from the weaker one. The date was annotated.

## Questions practitioners ask

**Is the API data the same as the UI?** It uses the same data, but returns top rows and has row limits, so totals can differ slightly.

**Can I use the API for the generative AI report?** Check the current API reference; don't assume a report in the UI has an API endpoint.

**Should I use AI-powered configuration or an external assistant?** Use AI-powered configuration to set views inside Search Console; use an external assistant to analyse exported data.

## Paging through results

For large sites, loop with `startRow`, increasing it by your `rowLimit` until a response returns no rows. Keep dimensions minimal; each extra dimension multiplies rows.

## Analysis questions by goal

Paste exported, non-sensitive aggregate data and ask specific questions:

- "Here are 12 months of clicks by section. Which sections changed most, and which months?"
- "Group these queries into themes and list the top themes by impressions."
- "Compare these two date ranges and list pages with the biggest click drops and their impression change."

Check every claim against the data. Assistants can miscount or invent patterns.

## API errors and fixes

| Error | Likely cause | Fix |
|---|---|---|
| 403 | Account lacks access to the property | Add the user or service account in Search Console |
| Empty rows | Dates too recent with final data, or filters too strict | Use `dataState: all` or widen filters |
| Wrong property | URL-prefix vs Domain format | Use `sc-domain:example.com` for Domain properties |

## Where this fits in the monthly routine

Use the API when the UI limits get in the way: more rows, scheduled pulls into a sheet, or many properties. Keep the pull small and documented so someone else can run it.

## Quick checks before you move on

- You can run a query with a regex filter and paging.
- Credentials are stored securely and not shared in sheets or chat.
- Every assistant claim about the data has been checked against the export.

## Worked example: Ledgerline's AI analysis

*Ledgerline is a fictional accounts-payable software company. Details and numbers are illustrative.*

Ledgerline's SEO lead exported two months of page data and asked Claude for top decliners. Claude flagged the integrations section; checking Search Console confirmed it. One suggested cause was wrong, so the lead noted it and kept the prompt.

### Walkthrough

1. Export the Performance report for two periods (Pages tab, with Compare).
2. Remove any columns or rows containing personal data.
3. Upload the CSV to Claude or ChatGPT.
4. Ask for the top 10 decliners with likely reasons, citing rows.
5. Check three of the claims in Search Console yourself.
6. Save the prompt for next month.

## Try it yourself

Export one month vs the previous month by page, and ask an AI assistant to identify the top decliners and group them by section. Verify the result against Search Console.

## Quick quiz

**1. Does the Search Analytics API have quotas?**

*Answer:* Yes, load quotas over 10 minutes and a day, plus per-second, per-minute and per-day request limits.

**2. Does URL Inspection API share that quota?**

*Answer:* No. It has its own per-site and per-project quota.

**3. Should you trust AI summaries without checking?**

*Answer:* No.

**4. What should you remove before uploading exports?**

*Answer:* Personal data.

## What should you check before the next lesson?

- You know the API quotas.
- You tested one AI analysis prompt.
- You verified its findings.

Next: [Search Console and AI visibility beyond Google](https://mentionx.ai/learn/search-console/search-console-ai-visibility-connection). Or return to the [Search Console for Marketers track](https://mentionx.ai/learn/search-console/search-console-for-marketers).

## Common questions

**Do I need to code to use the API?** Not necessarily; connectors and add-ons exist, but code gives more control.

**Can Claude connect to Search Console directly?** Via MCP connectors where available; see the Claude track.

**Is it safe to upload exports?** Follow your company's data policy and remove personal data.

## Sources

- Google for Developers, [Search Console API: Usage limits](https://developers.google.com/webmaster-tools/limits)
- Search Console Help, [Performance report (Search results): Advanced filtering and comparison](https://support.google.com/webmasters/answer/17011165)
- All accessed 4 Nov 2026.

## Frequently asked questions

### Do I need to code to use the API?

Not necessarily; connectors and add-ons exist, but code gives more control.

### Can Claude connect to Search Console directly?

Via MCP connectors where available; see the Claude track.

### Is it safe to upload exports?

Follow your company's data policy and remove personal data.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/search-console/search-console-api-ai-analysis