Store SEO audit Audit your store's SEO with Claude Code
Auditing your store's SEO with Claude Code means asking Anthropic's terminal agent which products, collections, pages and posts score worst in StoreSEO, and letting it read each one's checklist so you get a ranked worklist without opening the Shopify admin.
Last updated: October 2026
Set up Claude Code for StoreSEO
Skip this if Claude Code is already connected. The full guide, with the alternatives, is on the Claude Code page.
- 1
Add StoreSEO to Claude Code
Run this in any terminal. The user scope makes StoreSEO available in every project on your machine.
Terminalclaude mcp add --transport http --scope user storeseo https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Start Claude Code, run /mcp, choose storeseo and follow the browser window: pick your Shopify store and approve access.
Prompt/mcp
How does this work in Claude Code?
You start Claude Code in whatever folder you work from, often the theme repository, and type a plain request such as which twenty products score worst and why. Claude Code calls storeseo_start first, because every StoreSEO tool needs the conversation id it returns, and that first call already hands it a snapshot of the store: how many products, collections, pages and articles are optimized, need improvement or are not optimized, how many images still need work, and which features are set up. It then calls storeseo_list_resources sorted by score, lowest first, and storeseo_get_resource_seo for each candidate. You watch each call scroll past in the terminal, and every one of them is a read.
What comes back is a table you can act on. For each product Claude Code names the failing criteria by their visible titles, such as a meta description that is too short, a focus keyword missing from the title or images with no alt text, and it separates what a StoreSEO tool can fix from what only you can change, such as the focus keyword itself or the product title. Products also carry a GEO score for AI readiness, so the same pass tells you which listings AI shopping agents will struggle to understand. Because Claude Code keeps the whole session in context, you can follow up with show me only the ones where the meta is the main problem, or save the list to a file in the repository and work through it over several days.
Large catalogs are where the terminal pays off. Claude Code pages through the listing rather than loading everything at once, and you can ask it to stop at a score threshold, a product type or a collection. Nothing in an audit changes your store, so you can run it as often as you like and use it as the baseline before an optimization run.
-
You: Audit my products. Which ten score worst, and what is wrong with them?
- storeseo_start read-only
- storeseo_list_resources read-only
- storeseo_get_resource_seo read-only
-
Claude Code: StoreSEO found 214 products that need work. The ten lowest score between 18 and 34. Most are missing a meta description and image alt text; three have no focus keyword, which you set in the StoreSEO app.
-
You: Which of those can StoreSEO fix right now?
-
Claude Code: Meta, FAQs, AI snippet and alt text on all ten. The focus keywords on three need you first. Want me to preview the meta for the other seven?
What to ask Claude Code
Use StoreSEO to list my twenty lowest-scoring products and the main failing criterion on each. Read only, change nothing.
Audit my collections and pages, worst first, and split the fixes into ones StoreSEO can do and ones I have to do in the app.
Which products have the weakest GEO score? Save the list with their issues to seo-audit.md in this folder.
- 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.
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 Claude Code 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 Claude Code
Claude Code warns when a single tool result passes 10,000 tokens, and a full product listing with every criterion can get there on a big store. Ask for pages of twenty or fifty, or filter to not optimized products, instead of the whole catalog in one call. If you allowed the StoreSEO tools in your Claude Code permissions to stop the prompts, remember that the allow rule also covers the apply and generate tools, so scope it to the read tools if you only meant to speed up audits.
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
Does a Claude Code SEO audit change anything in my Shopify store?
No. The audit uses storeseo_start, storeseo_list_resources and storeseo_get_resource_seo, which are all read-only. Your store only changes when you later ask for a preview and approve applying it.
Can Claude Code save the audit results to a file?
Yes. Claude Code works in the folder you started it in, so you can ask it to write the worklist to a Markdown or CSV file there and pick it up in a later session.
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.
Keep going
Store SEO audit with other agents
More Claude Code guides