Read Search Console and Analytics with Kimi Code
Reading Google reports in Kimi Code means asking Moonshot AI's terminal agent for Search Console and GA4 numbers through StoreSEO, comparing them with the previous period, and turning queries and pages into a prioritized list of fixes.
Last updated: October 2026
Set up Kimi Code for StoreSEO
Skip this if Kimi Code is already connected. The full guide, with the alternatives, is on the Kimi Code page.
- 1
Add StoreSEO to Kimi Code
Create or edit ~/.kimi-code/mcp.json so every project on your machine can use StoreSEO. For one repository only, use .kimi-code/mcp.json inside it. You can also run /mcp-config in Kimi Code and have it add the server for you.
json config{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Start a new Kimi Code session (a server added mid-session registers in the next one), run this command, then follow the browser window: pick your Shopify store and approve access.
new message to Kimi Code/mcp-config login storeseo
Step-by-step guide in the docs: How to connect StoreSEO MCP to Kimi Code
How does this work in Kimi Code?
You ask a question the data can answer, such as which queries rank between positions eight and twenty, or which pages lost clicks this month. Kimi Code calls storeseo_get_search_console_insights with a dimension, query, page, country, device or date, and gets clicks, impressions, click-through rate and average position, plus the previous equal-length period and the change in each. For traffic questions it calls storeseo_get_analytics_report with a report type such as search_traffic, page_performance or traffic_source. The default range is the last 28 days.
Both tools are reads, so in Kimi Code's default mode the whole analysis runs without an approval panel. What the terminal adds is a place to keep the work. Ask the agent to save the table of near-page-one queries to a file, and to map each query to a product or collection in your theme repository by searching the templates and content. The agent reports numbers as Google returns them and does not project outcomes from them.
These reports have prerequisites that come up before the first answer. Google reports need a paid StoreSEO plan with Google connected in the app, and Analytics reports need a GA4 property selected. If either is missing, Kimi Code should give you the link into the StoreSEO app and stop. A good habit is to pair each report with a follow-up: take the low-click, high-impression pages and hand them back to the optimize job as candidates for new meta.
-
You: Which queries are close to page one for my store?
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
- storeseo_get_analytics_report read-only
-
Kimi Code: Illustrative result: six queries sit between positions 8 and 20, and the biggest by impressions is linen shirt men. Its page also lost organic sessions against the previous 28 days. Want me to preview new meta for that page?
What to ask Kimi Code
Tap a prompt to copy it, then paste it into Kimi Code.
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 Kimi 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 Kimi Code
A report can be large, and Kimi Code carries whatever a tool returns into its context for the rest of the session. Ask for a narrow dimension and a modest top row count, and write the result to a file you can reopen, instead of pulling queries, pages and countries all at once. If the tools answer that Google is not connected or no GA4 property is selected, that is a setting in the StoreSEO app, not something to fix with a different command.
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
Does reading Google reports in Kimi Code need an approval?
The two tools, storeseo_get_search_console_insights and storeseo_get_analytics_report, only read, and Kimi Code runs read-only calls without a prompt in its default mode. Nothing is written to your store or to Google.
Why does Kimi Code say Google is not connected?
Search Console and Analytics reports need a paid StoreSEO plan with Google connected in the app, and GA4 reports also need a property selected. Connect Google or pick the property in StoreSEO, then ask again in a new request.
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 Kimi Code guides