Store SEO audit

Audit your store's SEO with Gemini CLI

Auditing your Shopify store's SEO with Gemini CLI means asking Google's terminal agent, connected to the StoreSEO MCP server, which products, collections, pages and posts score worst, and letting it read each checklist to produce a ranked worklist.

Jump to the prompts Connect Gemini CLI

Last updated: October 2026

Set up Gemini CLI for StoreSEO

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

1
Add StoreSEO to Gemini CLI

Run this in any terminal. The user scope writes the server to ~/.gemini/settings.json so every project sees it. Without --scope user the command writes to the current project's .gemini/settings.json.
Terminal

gemini mcp add --scope user --transport http storeseo https://mcp.storeseo.com/mcp
2
Sign in to your store

Start gemini. The first time it calls StoreSEO it opens your browser: pick your Shopify store and approve access. If the window does not open, type /mcp auth storeseo inside Gemini CLI. Then gemini mcp list should show storeseo as connected.
Prompt

/mcp auth storeseo

How does this work in Gemini CLI?

You open Gemini CLI in your project folder and ask the audit question in plain words. The first time it calls a StoreSEO tool, Gemini CLI opens your browser for the sign-in, you pick your Shopify store and approve, and it stores the tokens, so the audit then runs without further setup. It calls storeseo_start to open the session, then storeseo_list_resources sorted by score with the lowest first, then storeseo_get_resource_seo for each product it reports on. All three are reads, and Gemini CLI lists them as tool calls in the terminal as it goes.

What you get is a worklist you can use straight away. Gemini CLI names the failing criteria by their visible titles, and groups them: the ones a StoreSEO tool can fix, such as meta, FAQs and image alt text, and the ones you have to change yourself, such as the focus keyword and the product title. Products also carry a GEO score for AI readiness, so you can ask which listings AI shopping agents will struggle with. Ask it to save the result to a file in the folder and you have a baseline to compare with after you fix things.

Gemini CLI asks for confirmation on tool calls unless you tell it not to, and that default suits this job well. Reads are quick to approve, and the later steps, a preview and an apply, are where you want the prompt to stay. Keep that in mind before you reach for any option that skips confirmations.

Gemini CLI + StoreSEO Illustrative session

You: Audit my store's SEO. Which products are weakest?
storeseo_start read-only
storeseo_list_resources read-only
storeseo_get_resource_seo read-only
Gemini CLI: Your weakest product scores 14 and the tenth weakest 29. Most lack a meta description or alt text, and four have a low GEO score because there are no FAQs.
You: Save that to seo-audit.md.
Gemini CLI: Saved. Want me to preview StoreSEO's meta and FAQs for the weakest four?

What to ask Gemini CLI

Prompt 1

Use StoreSEO to list my twenty lowest-scoring products with the main issue on each. Read only.

Prompt 2

Audit my collections, pages and blog posts, worst first, and save the worklist to seo-audit.md in this folder.

Prompt 3

Which products have the weakest GEO score for AI shopping agents, and what is missing on each?

Show me my ten lowest-scoring products and the top issue on each.
Which collections are not optimized yet, and what is failing on them?
Give me an SEO audit of my blog posts, worst first.
Which products have the weakest GEO score for AI shopping agents, and why?
Summarize my store's SEO: how many products, collections, pages and posts are optimized?
For the product Linen Shirt, list every failing SEO criterion and say which ones StoreSEO can fix.

What StoreSEO does: store seo audit

StoreSEO scores every product, collection, page and blog post against its SEO checklist, and scores products for AI readiness (GEO) as well. An agent opens a session, lists the weakest resources first and reads the per-criterion analysis for each, so you get a ranked worklist instead of a dashboard to click through.

1

Open a StoreSEO session

The agent calls the start tool first. It returns a conversation id every later call needs, plus a snapshot of your store: how many resources are optimized, need improvement or are not optimized, image status, rank tracking and which features are set up.
2

List the weakest resources

It lists products, collections, pages or articles sorted by score, lowest first, or filtered to the ones marked not optimized. Products also carry a GEO score and their AI-readiness issues.
3

Read the checklist for each one

For each candidate it reads the full SEO record: current meta fields, focus keyword, score, every criterion that passes or fails, image status, FAQs and AI snippet.
4

Sort fixes by who can make them

It separates what a StoreSEO tool can fix (meta, handle, FAQs, AI snippet, image alt text, schema) from what only you can change in the app or in Shopify admin (the focus keyword, the product title, category, inventory).
5

Report a worklist

You get the resources in order, with the failing criteria in plain words and one suggested next fix. Nothing is written during an audit.

storeseo_startstoreseo_list_resourcesstoreseo_get_resource_seo

Store SEO audit reference

Resource types	Products, collections, pages and blog articles
Scores	An SEO score for every resource, plus a GEO (AI readiness) score for products
Status labels	Optimized, needs improvement, not optimized; GEO adds not analysed
Sorting	By score, lowest first, or filtered to not optimized
Session	Every call carries the conversation id from the start tool; calls without it fail
What it writes	Nothing. Every audit tool is read-only
Fixed only in the app	Focus keyword choice, product title wording, Shopify category, product type, inventory, variant data
Plan	Any active StoreSEO plan, including the free plan

Rules Gemini CLI follows

Every audit call is a read and runs straight away; nothing in this job changes your store.
The agent describes criteria by their visible title, never by internal identifiers or raw status values.
Criteria no tool can fix, such as choosing the focus keyword, are handed to you with a link into the StoreSEO app rather than guessed.
The agent should offer one next fix at a time, tied to what it just found, instead of dumping the whole list as a checklist.

In Gemini CLI

The browser sign-in needs a browser on the same machine, so an audit started over SSH or in a headless session will stall at authentication. On such a machine, create a personal access token in StoreSEO under Settings, AI Toolkit and add it as a header. Also, gemini mcp add defaults to project scope, so a server added without --scope user is found only in that project, and an audit run from another folder will not have the StoreSEO tools. Do not set trust on the server just to speed up the audit.

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 did Gemini CLI open a browser during my StoreSEO audit?

The first call to the server starts the OAuth sign-in. Pick your Shopify store, approve access, and Gemini CLI stores the tokens so later audits run without another prompt.

Can I run the audit from a server with no browser?

Yes, with a personal access token. Create one in StoreSEO under Settings, AI Toolkit and add it to the server entry as a header, because the browser sign-in needs a browser on the same machine.

Does an SEO audit change anything in my store?

No. The audit uses read-only tools: the session start, the resource list and the per-resource SEO record. Your store is only changed later, by a separate step you agree to.

What is the difference between the SEO score and the GEO score?

The SEO score measures a resource against StoreSEO's on-page checklist for search engines. The GEO score applies to products only and measures how ready the product is for AI shopping agents and generative search, using criteria such as FAQs, an AI snippet, alt text and product schema.

Can the agent choose my focus keyword?

No tool can set the focus keyword. The agent can tell you when the keyword is missing or looks wrong and give you a link to set it in the StoreSEO app, and several fixes such as keyword clusters and description writing need it set first.

How many products can the agent audit at once?

The listing is paginated, so the agent can walk your whole catalog page by page. In practice it is more useful to ask for the lowest scores first and work down from there.