Read Search Console and Analytics with Claude Cowork
Getting Google reports from Claude Cowork means delegating the Search Console and GA4 read to Anthropic's task agent, which uses the StoreSEO connector to pull the numbers and hand you a written summary, once or on a schedule.
Last updated: October 2026
Set up Claude Cowork for StoreSEO
Skip this if Claude Cowork is already connected. The full guide, with the alternatives, is on the Claude Cowork page.
- 1
Add StoreSEO as a custom connector
In Cowork, open Customize, then Connectors, choose + Add and then Add custom connector. If you already added StoreSEO to your Claude account, look for it in that list first. Use this URL.
URLhttps://mcp.storeseo.com/mcp
- 2
Approve your store and check it
Sign in when the browser opens: pick your Shopify store and approve access. Then start a task and ask this first, so you know the connector works before you delegate real work.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Claude Cowork?
In Cowork you do not run the report step by step. You describe the result you want, for example a summary of last week's clicks, impressions and organic visitors with the biggest movers named, and Cowork works through it using the StoreSEO connector you added under Customize, Connectors. It opens the session with storeseo_start, reads storeseo_get_search_console_insights for the query and page dimensions, reads storeseo_get_analytics_report for the GA4 side, and returns a finished write-up for you to review instead of a conversation.
This job suits Cowork better than most because both Google tools are read-only. A weekly task has to run without you in the conversation, and a task that only reads can do that safely: it pulls the previous equal-length period for the comparison, notes which queries and pages changed most and lists the traffic sources that grew or shrank. You choose the cadence, and Anthropic's documentation says scheduled tasks run remotely even when your computer is asleep, on plans that include them.
The summary is where the follow-up work starts. If it flags a page with a falling CTR, you can open a normal Cowork conversation and ask for a preview of new meta, where you are present to give your yes. Keeping the scheduled task to reads and the fixes to a conversation you attend is the clean split between the two.
-
You: Every Monday, summarize my Search Console and GA4 changes. Read only.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
- storeseo_get_analytics_report read-only
-
Claude Cowork: Illustrative summary: clicks rose against the previous 28 days, organic sessions in GA4 rose less, and two product pages lost position. I will repeat this each Monday and apply nothing.
What to ask Claude Cowork
Use StoreSEO to write me a one-page summary of last week's Search Console clicks, impressions, CTR and position, and the five queries that moved most.
Every Monday, read Search Console by page and GA4 traffic sources for the last 28 days and summarize what changed. Do not apply, generate, publish or delete anything.
Compare this month's GA4 organic search traffic with last month's and list the pages that drove the difference.
- 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 Claude Cowork 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 Claude Cowork
A scheduled Cowork task runs while you are not in the conversation, so it cannot wait for a yes. Word the task as report-only and say in plain words that it must not apply, generate, publish or delete anything, because the Google tools are reads but the task could otherwise reach other StoreSEO tools. Scheduled tasks and Cowork itself depend on your plan and, on Team and Enterprise, on an admin toggle. If StoreSEO is missing inside Cowork, add it under Customize, Connectors there rather than assuming another surface carried it over.
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
Can Claude Cowork send me a weekly Search Console report?
Yes, as a scheduled task, on the plans where Anthropic offers them. Describe the report, tell it to use StoreSEO for Search Console and GA4, and keep it read-only. Cowork produces the summary for you to review.
Is it safe to schedule a StoreSEO task in Cowork?
A report-only task is a reasonable use because the two Google tools only read. The task cannot ask you a question mid-run, so say explicitly that it must not apply, generate, publish or delete anything, and do those jobs in a conversation you are present for.
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 Claude Cowork guides