Read Search Console and Analytics with NanoClaw
Reading Google reports with NanoClaw means asking your self-hosted agent in a chat for Search Console and Google Analytics 4 figures through StoreSEO, and getting a short written summary, which also makes it the safest job to schedule.
Last updated: October 2026
Set up NanoClaw for StoreSEO
Skip this if NanoClaw is already connected. The full guide, with the alternatives, is on the NanoClaw page.
- 1
Create a StoreSEO access token
In the StoreSEO app open Settings, AI Toolkit and generate a personal access token. Keep it out of chat messages and out of Git.
new message to NanoClawSettings → AI Toolkit → create a token
- 2
Add StoreSEO to your agent's container
Run this on the machine that hosts NanoClaw, using your agent group's ID from ncl groups list. The header goes in as a JSON object. NanoClaw may ask an admin to approve the change.
terminalncl groups config add-mcp-server --id <group-id> --name storeseo \ --url https://mcp.storeseo.com/mcp \ --headers '{"Authorization":"Bearer YOUR_TOKEN"}' - 3
Restart the agent's container
The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask for your store's SEO score.
terminalncl groups restart --id <group-id>
Step-by-step guide in the docs: How to connect StoreSEO MCP to NanoClaw
How does this work in NanoClaw?
Both Google tools only read, so this job asks the least of your approval settings. In your chat app you message @Andy something plain, such as which queries bring the most clicks and which pages sit between positions eight and twenty. The agent calls storeseo_start, then storeseo_get_search_console_insights with the dimension that fits, which can be date, query, page, country, device or search appearance, and storeseo_get_analytics_report for GA4 views such as traffic source or page performance. Both default to the last 28 days and compare with the previous period.
Chat is a good size for the answer. Ask for the top five rows and the change, not the whole table, and follow up with a second message to dig into one query. A finding can lead straight into another job: a page with many impressions and a low average position becomes a candidate for a meta preview in a later thread. The agent reports the figures as returned and should not project outcomes from them.
The natural automation is a NanoClaw scheduled task. Create it with ncl tasks create, a Monday cron recurrence, and a prompt that reads both reports, names the three biggest gains and drops and sends the summary to a named chat. Because these tools only read, an unattended run changes nothing in your store. The setup lives in the StoreSEO app: a paid plan, Google connected, and a GA4 property selected for the Analytics report. If any of that is missing, the agent cannot fix it from chat and should tell you where to go.
-
You: @Andy use StoreSEO to show which queries bring clicks and where we are close to page one.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
- storeseo_get_analytics_report read-only
-
NanoClaw: Illustrative result: the top query brought the most clicks, and three queries sit near positions 9 to 14. I can send you this every Monday as a read only summary. Want that set up?
-
You: Yes, send it to this chat.
What to ask NanoClaw
Tap a prompt to copy it, then paste it into NanoClaw.
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 NanoClaw 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 NanoClaw
These reports need a paid StoreSEO plan with Google connected, and the Analytics report also needs a GA4 property chosen in the StoreSEO app. A weekly NanoClaw task without that setup will only message you an error each Monday, so ask the same question in a chat first. Also give the task a destination, since a scheduled run has no chat attached and may otherwise have nowhere to send the summary.
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 my NanoClaw agent connect my Google account?
No. Connecting Google and choosing the GA4 property happen in the StoreSEO app. After that the agent only reads the reports, and if the connection is missing it should tell you to finish it there.
Is it safe to leave a NanoClaw Google report task running weekly?
Both report tools are read only, so a task that calls just those changes nothing in your store. Keep write tools out of that task's prompt and use a separate chat for any fixes.
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 NanoClaw guides