Read Search Console and Analytics with Muse
Reading Google reports with Muse means asking Meta's personal AI agent a question about search clicks, queries, pages or site traffic, and letting StoreSEO pull the Search Console and Google Analytics numbers behind the answer, compared with the previous period.
Last updated: October 2026
Set up Muse for StoreSEO
Skip this if Muse is already connected. The full guide, with the alternatives, is on the Muse page.
- 1
Send this message to Muse
Paste it into a new chat with Muse in the app, on muse.ai or in WhatsApp. Muse is rolling out in the US first, so you need access to it before this works.
new message to MuseAdd a custom connector for my Shopify SEO app StoreSEO: https://mcp.storeseo.com/mcp - It is an MCP server over HTTP and it signs in with OAuth. Send me the sign-in link and I will approve it. - Once it is connected, show me my store's SEO score breakdown.
- 2
Approve the sign-in for your store
Open the sign-in link Muse sends back, pick your Shopify store in the browser and approve access. Meta does not review custom connectors, so only approve this one if you started it.
server URLhttps://mcp.storeseo.com/mcp
Step-by-step guide in the docs: How to connect StoreSEO MCP to Muse
How does this work in Muse?
This is the lightest job to run from a phone, because both tools are reads and the answer is a short list of numbers. You ask which queries brought the most Google clicks in the last 28 days, and Muse calls storeseo_start and storeseo_get_search_console_insights with a dimension: query, page, country, device, search appearance or date. The result carries clicks, impressions, click-through rate and average position, plus the previous equal-length period and per-metric changes unless you turn the comparison off. The default window is 28 days, and you can name another.
For visitors rather than searches, Muse calls storeseo_get_analytics_report with a report type: search traffic, user activity, demographics, page performance, traffic source or key events. Time series come back as rows by date and the rest as paginated lists with totals. Both tools need a paid StoreSEO plan with Google connected, and GA4 also needs a property selected. Connecting Google and choosing the property happen in the StoreSEO app, and Muse hands you the link when either is missing instead of guessing a result.
The format that works in Muse is one question, one table, one follow-up. Ask for the top ten queries, then ask which of them rank between positions 8 and 20, or which product pages have high impressions and low click-through. Muse reports numbers as Google returns them and should not project outcomes from them. Because Muse also runs in WhatsApp, you can ask the same question on the move and compare this month with the last without opening a dashboard.
-
You: Use StoreSEO to show my top Google queries from the last 28 days.
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
-
Muse: Illustrative result: your top query is linen shirts for men with 410 clicks, up 12 percent on the previous 28 days. Two product pages show many impressions and a low click-through rate. Want the analytics view of those pages too?
-
You: Yes, page performance.
- storeseo_get_analytics_report read-only
-
Muse: Illustrative result: both pages show low engagement time. I can compare them with your best-performing page if you like.
What to ask Muse
Tap a prompt to copy it, then paste it into Muse.
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 Muse 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 Muse
Because both reports are reads, the risk here is not damage but wrong inferences from a small screen. Tables on a phone get trimmed, so ask Muse to state the date range, the dimension and the totals line at the top of each answer, and do not rely on a trimmed list when you compare two periods. Google data also lags, so a very recent window can look thin. If Muse says Google is not connected, that is a StoreSEO app setting, not something to approve in the thread.
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
Do I need a paid StoreSEO plan for Google reports in Muse?
Yes. Both the Search Console and GA4 tools need a paid StoreSEO plan with Google connected, and Analytics also needs a GA4 property selected in the StoreSEO app.
Can Muse change my Google settings or submit pages to Google?
No. The two Google tools only read reports. Connecting Google and choosing the GA4 property are done in the StoreSEO 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 Muse guides