Read Search Console and Analytics with GitHub Copilot
Reading Google reports with GitHub Copilot means asking Copilot Chat in Agent mode, inside Visual Studio Code, for Search Console and GA4 numbers through StoreSEO while your theme workspace stays open.
Last updated: October 2026
Set up GitHub Copilot for StoreSEO
Skip this if GitHub Copilot is already connected. The full guide, with the alternatives, is on the GitHub Copilot page.
- 1
Add StoreSEO to .vscode/mcp.json
Create or open .vscode/mcp.json in your workspace and paste this. VS Code uses a top-level servers key, not mcpServers, and a remote server needs type http.
JSON{ "servers": { "storeseo": { "type": "http", "url": "https://mcp.storeseo.com/mcp" } } } - 2
Start the server and sign in
Run MCP: List Servers from the Command Palette, pick storeseo and start it. If it asks you to sign in, pick your Shopify store in the browser and approve access. Then open Copilot Chat in Agent mode, check the tools icon lists StoreSEO and ask this.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in GitHub Copilot?
You open Copilot Chat in VS Code, switch to Agent mode and ask for a report, for example which queries sent the most clicks last month. Copilot calls storeseo_start, then storeseo_get_search_console_insights with the query dimension, and VS Code shows the MCP tool call in the chat with a confirmation to continue, where you can inspect the arguments. Once it runs, the response carries range totals for clicks, impressions, CTR and average position, the top rows by clicks and the change against the previous equal-length period.
Questions about visitors go to storeseo_get_analytics_report. Copilot picks a report type such as search_traffic, page_performance or traffic_source and returns totals and rows, and it can put the Search Console and GA4 views into a Markdown file in the workspace so the numbers sit in the repository you are working on. Since Agent mode can read the files that render a page, it can also point from a page in the report to the template or section behind it.
VS Code gives you a granular choice on the confirmation prompt, such as allowing a tool for the session or the workspace. For this job it is reasonable to allow the two Google report tools, because they are reads. Keep the prompt on for the apply, generate and delete tools that follow a report, since StoreSEO asks for your yes in the chat but the editor's confirmation is the hard stop. Tool output also stays in the chat, so you can ask Copilot to turn a long report into a short list of pages worth checking.
-
You: Which queries brought the most clicks from Google last month?
- storeseo_start read-only
- storeseo_get_search_console_insights read-only
-
GitHub Copilot: Illustrative result: clicks are up on the previous period. The top query is a brand term and the next three are product phrases around positions 5 to 9. Want the GA4 page performance for the pages they land on?
-
You: Yes, pull it.
- storeseo_get_analytics_report read-only
What to ask GitHub Copilot
Use StoreSEO to get Search Console clicks and impressions by query for the last 28 days and compare with the previous period.
Pull my top pages from Search Console and write the top 20 with CTR and position to docs/search-pages.md in this workspace.
Get GA4 key_events for last month and show which traffic source led to the most events.
- 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 GitHub Copilot 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 GitHub Copilot
On Copilot Business and Enterprise an organization admin has to enable MCP servers in Copilot policy, or the StoreSEO tools will not appear in Agent mode, so a missing Google tool can be a policy issue rather than a StoreSEO one. The server also has to be under the servers key in .vscode/mcp.json, not mcpServers, which belongs to the portable .mcp.json file. If you commit .vscode/mcp.json, remember it is shared with your team, and keep any token out of it.
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
Why are the StoreSEO Google report tools missing in Copilot Agent mode?
Check that the server is listed under servers in .vscode/mcp.json and started, that you use VS Code 1.99 or later, and that on Business or Enterprise your admin enabled MCP servers in Copilot policy. Then confirm Google is connected in the StoreSEO app.
Can I allow the Google report tools without allowing the rest of StoreSEO?
Yes. VS Code confirms tools one at a time, so you can allow the Search Console and Analytics report tools, which are reads, and keep the confirmation on for the tools that apply content or change settings.
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 GitHub Copilot guides