Search Console and Analytics reports

Read Search Console and Analytics with Codex

Reading Google reports with Codex means asking OpenAI's coding agent, in the terminal or the IDE extension, for Search Console and GA4 numbers through StoreSEO and getting a comparison with the previous period back in the session.

Jump to the prompts Connect Codex

Last updated: October 2026

Set up Codex for StoreSEO

Skip this if Codex is already connected. The full guide, with the alternatives, is on the Codex page.

1
Add StoreSEO to Codex

Run this in any terminal. It writes a [mcp_servers.storeseo] table to ~/.codex/config.toml, which the Codex CLI, the IDE extension and the ChatGPT desktop app all read.
Terminal

codex mcp add storeseo --url https://mcp.storeseo.com/mcp
2
Sign in to your store

Run the login command. Your browser opens: pick your Shopify store and approve access. Then run codex mcp list, or type /mcp inside Codex, to confirm storeseo is there.
Terminal

codex mcp login storeseo codex mcp list

How does this work in Codex?

You start Codex in a theme repository, with StoreSEO already added to config.toml and signed in with codex mcp login, and ask for a report such as which countries and devices send the most clicks. Codex calls storeseo_start to open the session, then storeseo_get_search_console_insights once for the country dimension and again for device, and you see each call in the transcript. Each response has range totals, the top rows by clicks and the per-metric change against the previous equal-length period.

For visitor data Codex calls storeseo_get_analytics_report, choosing demographics for country, traffic_source for channels or key_events for conversions. Because Codex works in your repository, it can write the results to a file, diff them against an earlier pull, or tie a page from the report to the template in the repo that produces it. The same config.toml is shared by the CLI, the IDE extension and the desktop app, so a report started in one place uses the same server settings as another.

The approval mode on the storeseo server decides what you see while this runs. The Google tools are read-only, so with the writes mode Codex should run them without a prompt and still stop for anything that is not marked read-only, which is the setting to keep for the jobs that follow a report, such as applying new meta, where you want the prompt. If a pull is large, ask Codex to split it by dimension and keep the result in a file.

Codex + StoreSEO Illustrative session

You: Which countries and devices bring the most Google clicks? Compare with last period.
storeseo_start read-only
storeseo_get_search_console_insights read-only
storeseo_get_search_console_insights read-only
Codex: Illustrative result: most clicks come from one country, and mobile is the larger device share. Clicks rose against the previous 28 days on both. Want the GA4 key events by traffic source too?
You: Yes.
storeseo_get_analytics_report read-only

What to ask Codex

Prompt 1

Use StoreSEO to get Search Console clicks by country and by device for the last 28 days and compare with the previous period.

Prompt 2

Pull my top 25 queries from Search Console and write them with position changes to reports/queries.csv.

Prompt 3

Get the GA4 search_traffic report for the last three months and tell me which month was strongest.

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.

storeseo_get_search_console_insightsstoreseo_get_analytics_report

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 Codex 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 Codex

Codex waits 60 seconds for a tool call by default, and a Search Console pull with a wide date range and a large top_n on a busy store can run long. If a report times out, raise tool_timeout_sec for the storeseo server in config.toml or ask for a narrower range or one dimension at a time. Keep the server's default_tools_approval_mode on writes or prompt, not approve, so the read tools run and the tools that change your store still stop for a decision.

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 does a Codex Search Console report time out?

Codex waits 60 seconds for a tool to finish by default. A large pull can take longer, so raise tool_timeout_sec for the storeseo server in config.toml, or ask for a smaller top_n, a shorter range or a single dimension.

Does the Codex CLI use the same StoreSEO setup as the IDE extension?

Yes. The CLI, the IDE extension and the desktop app share config.toml, so the storeseo server entry and its approval settings apply in all of them. A project-level file only loads in trusted projects, so the user file is simpler.

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.