Read Search Console and Analytics with Manus
Reading Search Console and Analytics with Manus means asking a task agent to pull your clicks, impressions, queries, pages and traffic sources through StoreSEO and write up what moved, without you opening Google or the StoreSEO app.
Last updated: October 2026
Set up Manus for StoreSEO
Skip this if Manus is already connected. The full guide, with the alternatives, is on the Manus page.
- 1
Create an access token in StoreSEO
In the StoreSEO app, open Settings, then AI Toolkit, and generate a named personal access token. Copy it now and keep it out of any chat.
new message to ManusStoreSEO → Settings → AI Toolkit → generate a token
- 2
Add StoreSEO as a custom MCP server
In Manus, open Settings, then Integrations, then Custom MCP Servers, and choose Add Server. Give it a name, paste this URL as the server URL and enter your token as the authentication, as a Bearer token.
server URLhttps://mcp.storeseo.com/mcp
- 3
Check it and use it
Manus verifies it can reach the server and read its tools. Then start a task that names StoreSEO, so Manus uses the connector.
new message to ManusUse StoreSEO to show me my store's SEO score breakdown.
Step-by-step guide in the docs: How to connect StoreSEO MCP to Manus
How does this work in Manus?
These reports need a paid StoreSEO plan with Google connected in the app, and a GA4 property selected for Analytics, so check that before you blame the agent. In a Manus task that names StoreSEO, a request such as which queries brought the most clicks over the last 28 days and how does that compare with the month before makes Manus call storeseo_start and then storeseo_get_search_console_insights. It picks the dimension that fits the question, whether query, page, country, device or search appearance, and the report returns the totals plus the previous period and the change per metric.
For visitor behavior it calls storeseo_get_analytics_report with the report type that matches, for example traffic source or page performance. Both tools read only and never connect or configure Google, so if Google is missing the answer is a link into the app, not something Manus can fix. The strength of Manus here is combining the two reports into one brief, for instance pages that earn impressions in Search Console but a weak click rate, next to what visitors do once they arrive.
This is the clearest fit for a scheduled task. A Monday task can read the last 28 days against the period before, name the five biggest movers and write a short brief to read with coffee. The numbers are reported as Google returns them and the task should not project outcomes from them. When a brief points at a page with low click-through, the follow-up, new meta for that page, is a different job and belongs in a task where you can approve the preview.
-
You: Use StoreSEO to tell me which queries and pages gained or lost clicks in the last 28 days.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
- storeseo_get_analytics_report read-only
-
Manus: Illustrative result: clicks are up on the linen collection and down on two older blog posts. Search impressions rose, but the average position slipped. Want a weekly version of this brief?
-
You: Yes, weekly, read only.
What to ask Manus
Tap a prompt to copy it, then paste it into Manus.
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 Manus 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 Manus
Because every tool in this job reads, a scheduled Manus task is safe, but only for as long as the prompt stays that narrow. Do not extend a recurring brief to add apply new meta to low-CTR pages. The skip confirmations setting lets a scheduled task send, publish or post without asking each time, so leave it off for any task that touches StoreSEO. If Google is not connected or no GA4 property is selected, the tool returns a link to set that up in the app, and the schedule will keep returning the same gap until you do.
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 a scheduled Manus task read Search Console for me every week?
Yes. Manus documents scheduled tasks that use your connected apps and run unattended, and both Google tools only read. Write the prompt as a read-and-summarize task and leave the skip confirmations setting off.
Why does Manus say Google is not connected?
Connecting Search Console and Analytics, and choosing the GA4 property, is done in the StoreSEO app and needs a paid plan. Manus cannot do it, and the tool returns a link to the setting that 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.
Keep going
Search Console and Analytics reports with other agents
More Manus guides