Search Console and Analytics reports Read Search Console and Analytics with Gemini CLI
Reading Google reports with Gemini CLI means asking Google's command-line agent for Search Console and GA4 numbers through the StoreSEO MCP server and reading the comparison with the previous period in your terminal.
Last updated: October 2026
Set up Gemini CLI for StoreSEO
Skip this if Gemini CLI is already connected. The full guide, with the alternatives, is on the Gemini CLI page.
- 1
Add StoreSEO to Gemini CLI
Run this in any terminal. The user scope writes the server to ~/.gemini/settings.json so every project sees it. Without --scope user the command writes to the current project's .gemini/settings.json.
Terminalgemini mcp add --scope user --transport http storeseo https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Start gemini. The first time it calls StoreSEO it opens your browser: pick your Shopify store and approve access. If the window does not open, type /mcp auth storeseo inside Gemini CLI. Then gemini mcp list should show storeseo as connected.
Prompt/mcp auth storeseo
How does this work in Gemini CLI?
You run Gemini CLI in a folder, with StoreSEO added under mcpServers or through gemini mcp add, and ask for the report in a sentence, such as which search appearances and devices drive my clicks. The model sees the tools as mcp_storeseo_ names and calls storeseo_start, then storeseo_get_search_console_insights with the dimension you asked for. Gemini CLI prints the call and asks for confirmation before running it unless the server is trusted, which is the default behavior you should leave in place.
What returns is the range summary for clicks, impressions, CTR and average position, the top rows ranked by clicks, and the change against the previous equal-length period. For visitors Gemini CLI calls storeseo_get_analytics_report, for example with the traffic_source or user_activity report type, and you can follow up with a narrower range or a different dimension in the same session. Because the CLI reads the folder it was started in, it can also save a report to a file there or compare a new pull with an earlier one.
Two details are particular to this client. Each confirmation you give covers a read, so a report session is a short run of approvals rather than a risk, and you can allow the Google tools for the session if you do not want to repeat them. And if you want the model to see fewer StoreSEO tools, an includeTools list on the server can limit it to the two Google tools plus storeseo_start.
-
You: Show Search Console clicks by device for the last 28 days.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
-
Gemini CLI: Illustrative result: mobile brings most clicks and its CTR is slightly lower than desktop. Both rose against the previous 28 days. Want the GA4 traffic sources for the same range?
-
You: Yes.
- storeseo_get_analytics_report read-only
What to ask Gemini CLI
Use StoreSEO to show Search Console clicks by search appearance and by device for the last 28 days, compared with the previous period.
Get the top 20 queries from Search Console and save them with position changes to reports/queries.md.
Pull the GA4 traffic_source report for last month and tell me which channel grew the most.
- 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 Gemini CLI 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 Gemini CLI
Do not set trust: true or --trust on the storeseo server to avoid the confirmations during a report session. Trust skips every tool confirmation for that server, including the tools that apply content or change settings, and then the confirmation StoreSEO asks for in the chat is the only check. Allow the two Google read tools for the session instead, or use an includeTools list. If the browser sign-in cannot open because you work over SSH or in a headless session, use a personal access token from Settings, AI Toolkit as a header.
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
Should I trust the StoreSEO server in Gemini CLI to speed up reports?
No. Trust skips confirmations for every tool on that server, not only the two Google report tools. Approve the read tools for the session, or limit the server with includeTools, and keep confirmations on for tools that write.
Why does Gemini CLI not show a Google report tool?
Check that the server connected and that an includeTools or excludeTools list did not remove the Search Console or Analytics tool. Also confirm that Google is connected in the StoreSEO app on a paid plan.
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 Gemini CLI guides