K Search Console and Analytics reports

Read Search Console and Analytics with Kiro

Reading Search Console and Analytics with Kiro means asking AWS's agentic IDE for your store's clicks, impressions, queries, pages and traffic sources, which StoreSEO reads from your connected Google accounts and Kiro lays out in the chat panel next to your project.

Jump to the prompts Connect Kiro

Last updated: October 2026

Set up Kiro for StoreSEO

Skip this if Kiro is already connected. The full guide, with the alternatives, is on the Kiro page.

1
Add StoreSEO to your Kiro MCP config

Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows and Linux), search for MCP and open the workspace config (.kiro/settings/mcp.json) or the user config (~/.kiro/settings/mcp.json). Paste this and save. Kiro applies the change on save, and the first connection opens a browser sign-in: pick your Shopify store and approve.
JSON

{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }

How does this work in Kiro?

You work in Kiro with the project open and the chat panel on the side. After storeseo is added to .kiro/settings/mcp.json or the user-level file and the browser sign-in is done, you ask a question like which queries earned the most clicks from Google last month. Kiro's agent calls storeseo_start and then storeseo_get_search_console_insights, and the reply lists the top rows ranked by clicks with the range totals and the previous period of equal length, including the change per metric.

Analytics works the same way through storeseo_get_analytics_report. Ask which channels drove users and it picks the traffic_source report, ask about engagement over time and it uses user_activity, and ask about key events for a purchase-related view. Each report is one read, and you can narrow by dimension, so the same Search Console data can be split by page, country, device or search appearance. Kiro tends to plan multi-step work, so a request such as audit my Google performance and list the next three pages to improve can run several reads in a row before it answers.

Kiro's autoApprove list is the useful lever for this job. Put storeseo_start, storeseo_get_search_console_insights and storeseo_get_analytics_report in it and a reporting session runs without a prompt for every call. Keep the apply, generate and update tools out of that list, so Kiro still stops before a write. A finding such as a page with plenty of impressions and a poor click-through rate can then lead into a preview in the same chat, and StoreSEO asks for your yes before anything is applied. The figures stay in the conversation, so you can ask Kiro to save them in a spec or notes file.

Kiro + StoreSEO Illustrative session

You: Give me my Google performance for the last 28 days: top queries first, then GA4 channels.
storeseo_start read-only
storeseo_get_search_console_insights read-only
storeseo_get_analytics_report read-only
Kiro: Clicks are up compared with the previous 28 days, led by linen shirt women. In GA4, organic search is the largest channel and direct is second. Do you want the weakest-CTR pages listed next?
You: Yes, and save the summary to notes/traffic.md.
Kiro: Saved the summary to notes/traffic.md, with the previous-period figures beside each metric.

What to ask Kiro

Prompt 1

Use StoreSEO to list my top queries by clicks for the last 28 days with the change from the previous 28 days.

Prompt 2

Show the Search Console pages report and flag the pages with high impressions and a CTR under two percent.

Prompt 3

Read GA4 traffic_source for last month and write a short summary of the channels into notes/traffic.md.

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.

storeseo_get_search_console_insightsstoreseo_get_analytics_report

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 Kiro 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 Kiro

A workspace .kiro/settings/mcp.json overrides a user-level entry with the same name, so if the sign-in points at the wrong store or the report tools look unavailable, check which file defines storeseo. When you fill in autoApprove, list the individual read tools. A wildcard would also approve the write tools, and then Kiro would stop asking before StoreSEO applies content, which leaves only StoreSEO's own request for your yes. Keep the two Google tools in the list and nothing more.

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

Which StoreSEO tools should I put in Kiro's autoApprove for reports?

storeseo_start, storeseo_get_search_console_insights and storeseo_get_analytics_report are all reads, so they are reasonable to list. Leave the apply, generate and update tools out so Kiro still prompts before a write.

Can Kiro compare this month's Search Console data with last month's?

Yes. Both report tools include the previous period of the same length and the change per metric by default, so a 28 day range is compared with the 28 days before it. You can also name your own date range.

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.