Z Search Console and Analytics reports

Read Search Console and Analytics with Zed

Reading Search Console and Analytics with Zed means asking the Agent Panel in your editor for clicks, impressions, queries, pages and traffic sources, which StoreSEO fetches from your Google accounts, with Zed's own tool prompt deciding when each call may run.

Jump to the prompts Connect Zed

Last updated: October 2026

Set up Zed for StoreSEO

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

1
Add StoreSEO as a remote server

Open Settings, then AI, then MCP Servers and add a remote server, or add this to settings.json yourself. Leave out headers so Zed can sign you in.
JSON

{ "context_servers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }
2
Sign in and check the dot

Because the entry has no Authorization header, Zed prompts you to authenticate. Pick your Shopify store and approve in the browser. In Settings, AI, MCP Servers a green dot next to storeseo means the server is active. Then ask this in the Agent Panel.
Prompt

Use StoreSEO to show me my store's SEO score breakdown.

How does this work in Zed?

You are in Zed with your theme project open and the Agent Panel showing. Settings, AI, MCP Servers has a green dot next to storeseo, so you type a question such as which queries brought the most clicks from Google this month. The agent calls storeseo_start and then storeseo_get_search_console_insights, and the result appears in the panel as ranked rows with the totals and the previous period of equal length. A second question about visitors uses storeseo_get_analytics_report, with a report type like search_traffic or traffic_source.

Zed behaves differently from most clients here because of agent.tool_permissions.default, which is confirm out of the box. That means the panel asks before it runs a tool action, and it does so for reads too. A report question can therefore show a prompt for storeseo_start, another for the Search Console call and another for the GA4 call. Nothing is wrong when that happens: it is Zed's own check, not StoreSEO, and you accept each one to let the report through.

If the prompts get in the way of a longer reporting session, give the read tools their own permission using keys of the form mcp:storeseo:tool_name, for example mcp:storeseo:storeseo_get_search_console_insights, and set them to allow. Leave the apply, generate and update tools on confirm. That way the figures arrive without a click while a later write, such as new meta for a page with a weak click-through rate, still stops at Zed's prompt as well as at StoreSEO's own request for your yes. The answers stay in the panel, and you can copy the table into a note beside the code.

Zed + StoreSEO Illustrative session

You: Which queries brought the most Google clicks in the last 28 days?
storeseo_start read-only
storeseo_get_search_console_insights read-only
Zed: The top query is linen shirt women, followed by two brand searches. Total clicks are up against the previous 28 days. Do you want the GA4 search traffic report for the same range?
You: Yes, that one too.
storeseo_get_analytics_report read-only
Zed: GA4 shows organic search clicks and impressions both rising, with average position near 14 on the weakest days.

What to ask Zed

Prompt 1

Use StoreSEO to show my top 15 Google queries by clicks for the last 28 days, with the change against the previous period.

Prompt 2

Which device type sends the most Search Console clicks, and which one grew fastest compared with the previous 28 days?

Prompt 3

Read the GA4 search_traffic report for the last three months and describe the trend in two sentences.

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

Zed's default is to ask before every tool action, reads included, so one report question can mean three prompts. Allow only the two Google report tools and storeseo_start with per-tool keys such as mcp:storeseo:storeseo_get_search_console_insights, and leave the write tools on confirm. Setting agent.tool_permissions.default to allow removes Zed's check altogether, so StoreSEO's request for your yes in the chat would be the only one left. Use it sparingly, even for a session that only reads.

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

Why does Zed ask me to approve a report that only reads data?

Zed's agent.tool_permissions.default is confirm by default, which covers every tool action, reads included. That prompt comes from Zed, not StoreSEO. You can allow individual read tools with keys of the form mcp:storeseo:tool_name and keep the write tools on confirm.

Does Zed need a Google sign-in for these reports?

No. Google is connected inside the StoreSEO app, under a paid plan, and Analytics also needs a GA4 property selected there. Zed only signs in to StoreSEO, and the report tools return a link if a Google step is missing.

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.