Read Search Console and Analytics with Paperclip
Reading Search Console and Analytics from Paperclip means scheduling an agent to pull your clicks, impressions, queries and traffic sources through StoreSEO each week and post the movers on a task you can skim.
Last updated: October 2026
Set up Paperclip for StoreSEO
Skip this if Paperclip is already connected. The full guide, with the alternatives, is on the Paperclip page.
- 1
Add StoreSEO to the agent Paperclip runs
Run this on the machine that hosts the agent, as the same OS user the Paperclip heartbeat runs as, from the agent's working directory. It is the claude_local adapter path, and user scope makes StoreSEO available to every Claude Code agent that user runs.
terminalclaude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp
- 2
Sign in once, then let Paperclip run headless
Start claude interactively as that same user, run /mcp, choose storeseo and finish the browser sign-in: pick your Shopify store and approve. Claude Code keeps the credentials, so later Paperclip runs need no browser. Check with claude mcp get storeseo.
new message to Paperclip/mcp
Step-by-step guide in the docs: How to connect StoreSEO MCP to Paperclip
How does this work in Paperclip?
This is the cleanest job to hand to an unattended agent, because both tools write nothing. A Paperclip routine fires on its cron schedule, which Paperclip evaluates in the browser's timezone, creates a task and wakes the agent. The agent calls storeseo_get_search_console_insights for the last 28 days, broken down by query, page, country, device or search appearance, and storeseo_get_analytics_report for a GA4 bundle such as search_traffic, traffic_source or page_performance. Both compare against the previous equal-length period by default, so the comment arrives with the change per metric already worked out.
The useful asks are the ones with a threshold: queries ranking between positions eight and twenty, pages with impressions but a low click rate, a traffic source that fell. Report the numbers as Google returns them and do not let the agent project outcomes from them. Where a finding points at a fix, such as a page with weak CTR needing new meta, the agent can open a follow-up task rather than doing it, which keeps the report run harmless.
Setup is not something the routine can do. Connecting Google and choosing the GA4 property happen in the StoreSEO app, and a paid plan is required, so when the tool returns a link saying what to set up, the agent should post that link on the task for you. A good weekly note also keeps its length in check: five movers per report, each with its before and after, is easier to act on than a dump of every query.
-
You: Routine task: weekly Google report. Read only. Post movers on this task.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
- storeseo_get_analytics_report read-only
-
Paperclip: Posted the report: clicks rose against the previous 28 days, and three queries sit between positions 8 and 20. Linen Shirt has many impressions and a weak CTR, so its meta is the likely fix.
-
You: Open a follow-up task for the Linen Shirt meta, unassigned.
-
Paperclip: Created the follow-up task and assigned it to nobody. No preview or apply was run.
What to ask Paperclip
Tap a prompt to copy it, then paste it into Paperclip.
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 Paperclip 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 Paperclip
A routine can only report what Google data StoreSEO can reach, and the setup is outside the agent's reach. If Google is not connected, or no GA4 property is selected, the tool returns a link to fix it in the StoreSEO app and every weekly run will repeat that message until you do. Also remember the agent itself is not limited to reads: with the Claude Code adapter's default of skipping permission prompts, keep the routine's instructions read only.
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
Is a Search Console report safe to schedule in Paperclip?
Yes, as far as StoreSEO goes: both Google tools are read-only and never connect or configure Google. Still word the routine as read only, since the agent running it could call other StoreSEO tools if the instructions allow it.
Which StoreSEO plan does a Paperclip Google report need?
A paid StoreSEO plan with Google connected in the app. Analytics reports also need a GA4 property selected. Paperclip itself is open source and self-hosted, so the plan question is only about StoreSEO.
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 Paperclip guides