Store SEO audit Audit your store's SEO with Claude Cowork
Auditing your Shopify store's SEO with Claude Cowork means giving Cowork a task that reads StoreSEO's scores for your products, collections, pages and posts and returns a ranked worklist, either right now or on a schedule you set up once.
Last updated: October 2026
Set up Claude Cowork for StoreSEO
Skip this if Claude Cowork is already connected. The full guide, with the alternatives, is on the Claude Cowork page.
- 1
Add StoreSEO as a custom connector
In Cowork, open Customize, then Connectors, choose + Add and then Add custom connector. If you already added StoreSEO to your Claude account, look for it in that list first. Use this URL.
URLhttps://mcp.storeseo.com/mcp
- 2
Approve your store and check it
Sign in when the browser opens: pick your Shopify store and approve access. Then start a task and ask this first, so you know the connector works before you delegate real work.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Claude Cowork?
You start from the Cowork tab in the Claude desktop app and describe the audit as a task rather than a question. Cowork works through it by calling storeseo_start to open a StoreSEO session, storeseo_list_resources sorted by score with the lowest first, and storeseo_get_resource_seo for each product it needs to explain. You can watch it work, and when it finishes it hands back the worklist, or writes it into a file if you asked for one. Every tool in the audit is a read, so you can run it freely against a live store.
An audit is the best job to schedule in Cowork, because the whole point is a recurring picture rather than a one-off answer. A weekly task can read the score breakdown, list the ten lowest-scoring products and write a short summary of what moved since last time, which gives you a standing worklist without opening Shopify. Cowork runs scheduled tasks without you in the conversation, so write the task as report only, and say in plain words that it must not apply, generate, publish or delete anything.
When you do want to act on what the audit found, switch to an interactive session in the same place. Ask for a preview of a specific resource, read it, and say yes to the apply there, where you are present to approve it. The split keeps the scheduled task safe and keeps the decisions with you.
-
You: Audit my store's SEO and save a worklist I can reuse next week.
- storeseo_start read-only
- storeseo_list_resources read-only
- storeseo_get_resource_seo read-only
-
Claude Cowork: I saved a worklist of the ten lowest products. The common gaps are missing meta descriptions and image alt text, and two need a focus keyword from you in the StoreSEO app.
-
You: Schedule this every Monday morning, report only.
-
Claude Cowork: I set up a weekly task that reads scores and writes the summary, and it is told not to apply or publish anything. Want me to preview fixes for the top product now?
What to ask Claude Cowork
Use StoreSEO to audit my store: list my ten lowest-scoring products with the main issue on each, and save the result as a worklist file.
Every Monday, read my StoreSEO score breakdown and lowest-scoring products and summarize what changed. Do not apply, generate, publish or delete anything.
Compare this week's weakest products with last week's worklist and tell me which ones are still on it.
- 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 Cowork 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 Cowork
A scheduled Cowork task runs while you are away, so nobody can say yes to a StoreSEO confirmation. Keep a scheduled audit to the read tools and word the task to forbid apply, generate, publish and delete, because that wording is an instruction the agent follows rather than a lock. If the connector is missing inside Cowork, add it under Customize, Connectors there instead of assuming one added in a regular chat carried over, and on Team and Enterprise plans an admin may need to turn Cowork on first.
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
Can Claude Cowork run my StoreSEO audit every week?
Yes. Cowork documents scheduled tasks that run on a cadence and can use your connected apps. Word the task as a report that only reads scores and lowest-scoring products, since you are not there to approve any change.
Where does the audit result end up in Cowork?
It comes back in the Cowork task, and you can ask it to write the worklist to a file or a document so you can compare it with the next run.
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 Cowork guides