Audit your store's SEO with Cursor
Auditing your Shopify store's SEO in Cursor means asking Cursor's agent chat, inside the editor where your theme code lives, which products, collections, pages and posts score worst in StoreSEO, and getting a ranked worklist you can keep as a file in the project.
Last updated: October 2026
Set up Cursor for StoreSEO
Skip this if Cursor is already connected. The full guide, with the alternatives, is on the Cursor page.
- 1
Add StoreSEO to mcp.json
Put this in ~/.cursor/mcp.json to use StoreSEO in every project, or in .cursor/mcp.json inside one theme project. In the StoreSEO app's setup guide the same JSON goes into Settings, Tools and MCP, New MCP server.
JSON{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Open Cursor's MCP settings (the Customize page in current versions), find storeseo and sign in when Cursor asks. A browser window opens: pick your Shopify store and approve access.
PromptUse StoreSEO to show me my store's SEO score breakdown.
- 3
Switch off four StoreSEO tools
StoreSEO has 44 tools and Cursor stops at about 40 active ones across all servers. In the storeseo entry in Cursor's MCP settings, turn off at least four you do not need. The four rank and competitor lookups are a good first choice if you are not on Pro.
Promptstoreseo_list_rank_locations storeseo_list_rank_languages storeseo_add_competitors storeseo_delete_competitor
How does this work in Cursor?
You are in Cursor with a theme or storefront project open, using the agent chat panel. You type the audit request in plain words. Cursor calls storeseo_start to open the session, then storeseo_list_resources sorted by score, then storeseo_get_resource_seo for each product it will describe, and each call appears in the chat as a tool step you can expand to see the arguments and the result. These are read tools, so the results are safe to expand and read.
The editor changes what you can do with the answer. Ask Cursor to write the worklist to a Markdown file in the repository, such as seo-audit.md, and it creates the file beside your code. Because the agent can also read your project, you can ask it to connect findings to the theme, for example which product template renders the page for a product with weak GEO data. It will still say that the focus keyword, the product title and the category are changed in the StoreSEO app or in Shopify admin, not by a StoreSEO tool.
Before the audit, check which StoreSEO tools are switched on. The three audit tools, storeseo_start, storeseo_list_resources and storeseo_get_resource_seo, must be among the tools active in Cursor, and the tool cap makes it likely that you disabled some StoreSEO tools. If the agent says it cannot find a listing tool, look there first.
-
You: Audit my store's SEO and put the worklist in seo-audit.md.
- storeseo_start read-only
- storeseo_list_resources read-only
- storeseo_get_resource_seo read-only
-
Cursor: I wrote seo-audit.md with the twenty lowest products, each with its score and failing criteria. Meta descriptions and alt text are the most common gaps.
-
You: Which of these needs me, not StoreSEO?
-
Cursor: Four products have no focus keyword, and that is set in the StoreSEO app. Do you want a preview of the meta for the rest?
What to ask Cursor
Using StoreSEO, list my twenty lowest-scoring products and the top failing criterion on each, then write the result to seo-audit.md.
Which products have the weakest GEO score? For each, say what would help AI shopping agents, and note which fixes are only possible in the StoreSEO app.
Audit my pages and blog posts, worst first, and add a short section to seo-audit.md for 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.
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 Cursor 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 Cursor
StoreSEO has 44 tools and Cursor allows about 40 active tools across all your servers, so you have to switch some off in Cursor's MCP settings, and the audit tools are the three you must keep on. If you switch off storeseo_list_resources by mistake, Cursor can open a session but cannot rank anything. Also, a server in .cursor/mcp.json belongs to that project only, so an audit started in another project will not see StoreSEO unless you added it to ~/.cursor/mcp.json.
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
Which StoreSEO tools does a Cursor audit need switched on?
storeseo_start, storeseo_list_resources and storeseo_get_resource_seo. With Cursor's cap of about 40 active tools you must turn some StoreSEO tools off, so turn off ones for jobs you are not doing and keep these three.
Can Cursor keep the audit results in my repository?
Yes. Ask the agent to write the worklist to a Markdown or CSV file in the project, and it creates it beside your code, where you can commit it or compare it with a later audit.
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 Cursor guides