Search Console and Analytics reports Read Search Console and Analytics with Claude Code
Reading Google reports with Claude Code means asking Anthropic's terminal agent for Search Console and GA4 numbers through StoreSEO while you work in your theme repository, so the data lands beside the code you are about to change.
Last updated: October 2026
Set up Claude Code for StoreSEO
Skip this if Claude Code is already connected. The full guide, with the alternatives, is on the Claude Code page.
- 1
Add StoreSEO to Claude Code
Run this in any terminal. The user scope makes StoreSEO available in every project on your machine.
Terminalclaude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Start Claude Code, run /mcp, choose storeseo and follow the browser window: pick your Shopify store and approve access.
Prompt/mcp
How does this work in Claude Code?
You are in a terminal with Claude Code started in a theme folder, and you type a request such as which queries lost clicks this month and which pages gained impressions. Claude Code calls storeseo_start, then storeseo_get_search_console_insights once per dimension it needs, usually query and then page, and each call prints as it runs. The results include range totals for clicks, impressions, CTR and average position and the change against the previous equal-length period, so you read a comparison rather than a raw dump.
Because Claude Code can read and write files in the working folder, the report does not have to stay on screen. Ask it to write the top queries and their position changes to a Markdown or CSV file, or to keep a dated reports folder, and a later session can compare a new pull with the saved one. For visitor data it calls storeseo_get_analytics_report with a report type like page_performance or traffic_source, and it can cross-reference those pages with the Liquid templates and content in the repository that produce them.
That cross-referencing is the reason to do this job in a terminal. A page with many impressions and a weak CTR is a candidate for new meta, and Claude Code can tell you which template or product handle it belongs to before you move on to the optimization job, where it asks for your yes before applying anything. The two Google tools themselves are reads and run straight away.
-
You: Pull my top pages from Search Console for the last 28 days and save them to reports/pages.md.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
-
Claude Code: Illustrative result: I wrote 25 pages to reports/pages.md with clicks, impressions, CTR and position, plus the change from the previous 28 days. Three product pages have strong impressions and a low CTR. Want the GA4 page performance for those three?
-
You: Yes, pull it.
- storeseo_get_analytics_report read-only
What to ask Claude Code
Use StoreSEO to pull Search Console by query for the last 28 days, compare with the previous period, and save the top 25 to reports/queries.md.
Which product pages have high impressions and a low CTR? Pull the page dimension, then tell me which templates in this repo render them.
Get the GA4 traffic_source report for last month and summarize which channels grew. Read only, change nothing.
- Which queries brought the most clicks from Google in the last 28 days, and how does that compare with the month before?
- Which product pages have high impressions but a CTR under two percent?
- Show organic search traffic from GA4 for the last three months.
- Which countries send the most visitors, and on which devices?
- Which traffic sources led to purchases last month?
What StoreSEO does: search console and analytics reports
StoreSEO connects to your Google Search Console and Google Analytics 4 property. The agent reads Search Console performance by date, query, page, country, device or search appearance, and curated GA4 reports, each compared with the previous period by default.
Requires: A paid StoreSEO plan with Google connected in the app, and a GA4 property selected for Analytics reports.
- 1
Pick the question
Search Console answers how you appear in Google: clicks, impressions, CTR and average position. GA4 answers what visitors do: users, engagement, pages, sources and key events.
- 2
Read the report
The agent reads the last 28 days by default, or the range you name, broken down by the dimension that fits the question.
- 3
Compare periods
Both reports include the previous period of the same length and the change per metric unless you ask otherwise.
- 4
Turn it into actions
The agent can link what it finds to the other jobs, for example pages with impressions but a low CTR are candidates for new meta.
Search Console and Analytics reports reference
| Search Console metrics | Clicks, impressions, CTR, average position |
|---|---|
| Search Console dimensions | Date, query, page, country, device, search appearance |
| GA4 reports | Search traffic, user activity, demographics, page performance, traffic source, key events |
| Default range | Last 28 days |
| Comparison | Previous equal-length period with per-metric change, on by default |
| What it writes | Nothing. Both tools are read-only and never connect or configure Google |
| Plan | Paid plan with Google connected; GA4 property selected for Analytics |
Rules Claude Code follows
- Both tools are reads and run straight away.
- Connecting Google or choosing the GA4 property is done in the StoreSEO app; the agent hands you the link when it is missing.
- Numbers are reported as Google returns them; the agent does not project outcomes from them.
In Claude Code
Claude Code warns when a single tool result is larger than 10,000 tokens, and a Search Console pull by query or page with a large top_n can reach that on a busy store. Ask for the top twenty or fifty rows, or one narrow dimension at a time, instead of the longest list the tool will return. Also check which scope you added the server with: without the user scope StoreSEO is available only in the project folder where you added it, so a report started from another directory will not find the Google tools.
What runs without asking. Reads such as SEO scores, store listings, settings and Google reports run straight away. Generating a preview spends AI credit but writes nothing, and StoreSEO tells the agent to say what a generation will cost before it runs one. Applying content, optimizing images, changing settings, publishing llms.txt or agents.md, writing a product description and deleting anything wait for your yes in the conversation. That yes is an instruction the agent follows, not a lock on the server, so your client's own tool-approval setting is the hard stop.
Questions
Can Claude Code save my Search Console data to a file?
Yes. Claude Code works in the folder you started it in, so it can write the report it reads from StoreSEO to a Markdown or CSV file there. StoreSEO does not store the file for you, and a later session can pull fresh numbers and compare them with the saved ones.
Will Claude Code ask before running the Google report tools?
That depends on your Claude Code permission settings. The tools are reads, but Claude Code can still prompt before an MCP tool runs unless you have allowed it. If you allow the StoreSEO tools, scope the rule to the read tools.
Can the agent connect my Google account?
No. Connecting Search Console and Google Analytics, and choosing the GA4 property, is done in the StoreSEO app. If Google is not connected, the tool returns a link telling you what to set up.
Can these reports change anything?
No. Both Google tools are read-only. They never connect, configure or write anything in Google or in your store.
Which plan includes Google reports over MCP?
A paid StoreSEO plan with Google connected. Analytics reports also need a GA4 property selected in the app.
How far back can the agent look?
You can name any date range the report supports. When you do not, both tools default to the last 28 days and compare it with the 28 days before.
Keep going
Search Console and Analytics reports with other agents
More Claude Code guides