Read Search Console and Analytics with Cursor
Reading Google reports in Cursor means asking the editor's agent for Search Console and GA4 numbers through StoreSEO while your theme project is open, so the queries and pages it finds sit next to the files that render them.
Last updated: October 2026
Set up Cursor for StoreSEO
Skip this if Cursor is already connected. The full guide, with the alternatives, is on the Cursor page.
- 1
Add StoreSEO to mcp.json
Put this in ~/.cursor/mcp.json to use StoreSEO in every project, or in .cursor/mcp.json inside one theme project. In the StoreSEO app's setup guide the same JSON goes into Settings, Tools and MCP, New MCP server.
JSON{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Open Cursor's MCP settings (the Customize page in current versions), find storeseo and sign in when Cursor asks. A browser window opens: pick your Shopify store and approve access.
PromptUse StoreSEO to show me my store's SEO score breakdown.
- 3
Switch off four StoreSEO tools
StoreSEO has 44 tools and Cursor stops at about 40 active ones across all servers. In the storeseo entry in Cursor's MCP settings, turn off at least four you do not need. The four rank and competitor lookups are a good first choice if you are not on Pro.
Promptstoreseo_list_rank_locations storeseo_list_rank_languages storeseo_add_competitors storeseo_delete_competitor
How does this work in Cursor?
You have a Shopify theme open in Cursor and you ask the agent chat, in plain words, which pages get impressions but few clicks. The agent calls storeseo_start and then storeseo_get_search_console_insights with the page dimension, and Cursor shows each MCP call in the chat with its arguments, so you can read the date range and top_n the agent chose. The response carries range totals, the top rows ranked by clicks and the change against the previous equal-length period.
The editor is the point. Once the agent has a page URL or a product handle from the report, it can search the project for the template, section or snippet that renders it and tell you what that page contains: its title tag logic, its schema blocks, its image tags. For visitor behavior it calls storeseo_get_analytics_report with page_performance or traffic_source, and it can put the two reports side by side in a file in the repository if you want to keep them with the project.
Both Google tools are read-only. Cursor by default asks before an MCP tool runs, so expect a confirmation on the first calls unless you have changed the run mode, and approve the read tools to let a report flow. Keep that approval to reads, and leave the apply and generate tools on their prompt for the optimization jobs that come after the report.
-
You: Which pages in Search Console have lots of impressions but a weak CTR? Check which template renders each.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
-
Cursor: Illustrative result: three product pages show the most impressions with a low CTR. All three use templates/product.json with the same title tag logic in the meta snippet. Want GA4 page performance for them too?
-
You: Yes.
- storeseo_get_analytics_report read-only
What to ask Cursor
Use StoreSEO to pull Search Console by page for the last 28 days and tell me which templates in this theme render the top five.
Which queries have lost clicks compared with the previous period? Read only, and write the top 20 to notes/queries.md.
Get GA4 page_performance for last month and list the pages with the most views but the lowest engagement.
- 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 Cursor 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 Cursor
StoreSEO exposes 44 tools and Cursor allows about 40 active tools across all your servers, so you have to switch some off, and a Google report fails quietly if the tool you switched off was one of the two it needs. If the agent says it cannot read Search Console, open Cursor's MCP settings and check that storeseo_get_search_console_insights and storeseo_get_analytics_report are still enabled, and disable tools for jobs you do not use instead. A server in .cursor/mcp.json belongs to that project only, so use ~/.cursor/mcp.json to keep it everywhere.
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 can Cursor not find the Search Console tool?
Most often because the tool was switched off to stay under Cursor's cap of about 40 active tools. StoreSEO has 44 tools, so open the MCP settings, turn the Search Console and Analytics report tools back on and turn off tools for jobs you do not run.
Does Cursor need Google connected to read these reports?
Google has to be connected in the StoreSEO app, on a paid plan, with a GA4 property selected for Analytics. Cursor cannot do that step. If it is missing, the tool returns a message pointing you to the app.
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 Cursor guides