Get products ready for AI search with Cursor
Getting products ready for AI search with Cursor means using the agent chat inside your theme project to read StoreSEO's GEO score for a product, preview FAQs and an AI snippet, and apply them once you approve, with the right tools left switched on.
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 sit in Cursor's editor with the theme project open and the agent chat beside your files. You type: the Merino Beanie looks thin to AI shopping agents, check its GEO score and fix what StoreSEO can. The agent calls storeseo_start, then storeseo_get_resource_seo, and Cursor shows each tool call in the chat with its arguments so you can read them. The result's geo block lists which AI-readiness criteria pass and which fail, and the agent splits them into things a tool can fix, such as FAQs, AI snippet, alt text and product schema, and things only you can change, such as the product title or category.
The first thing that can go wrong in Cursor is not StoreSEO at all. Cursor allows about 40 active tools across all your servers and StoreSEO has 44, so you have already switched some off in the MCP settings. If the agent says it has no tool to preview or apply, open the settings and check that storeseo_preview_resource_optimization and storeseo_apply_resource_optimization are on. This job also uses storeseo_get_resource_seo, storeseo_update_schema_settings, storeseo_scan_product_description and storeseo_write_product_description, so keep those six plus storeseo_start enabled and switch off tools for jobs you are not doing today.
Because the agent works in your project, you can ask it to cross-check the theme's own JSON-LD before enabling StoreSEO's product schema, and to keep the preview drafts in a scratch file while you decide. The preview generates the FAQs and snippet, projects the new SEO and GEO scores, and spends AI credit without saving. After your yes in the chat, the agent applies it and reports the re-analysed checklist, so you see which criteria now pass.
-
You: Check the Merino Beanie's GEO score and fix what StoreSEO can.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
-
Cursor: GEO is 41: no FAQs, no AI snippet. The title and category are yours to change in the app. The preview spends AI credit and saves nothing. Run it?
-
You: Go ahead.
- storeseo_preview_resource_optimization preview
-
Cursor: Projected GEO is 66 with five FAQs and a snippet. Apply both to the Merino Beanie?
-
You: Yes, apply.
- storeseo_apply_resource_optimization needs approval
What to ask Cursor
Use StoreSEO to check the GEO score of the Merino Beanie and list what an AI shopping agent cannot find. Read only.
Preview FAQs and an AI snippet for the Merino Beanie, show the projected GEO score, and wait for me before applying.
Which StoreSEO tools do you have right now? List the ones for AI search readiness and tell me if any are missing.
- Which of my products have the lowest GEO score, and what is missing for AI shopping agents?
- Make the product Merino Beanie ready for AI search: FAQs, AI snippet and product schema. Preview first.
- Scan the description of my best seller for AI agents and ask me the questions it needs.
- Rewrite the description of Ceramic Pour Over from my answers. Keep a copy of the old one for me.
- Is product JSON-LD schema enabled on my store? If not, explain what turning it on changes.
What StoreSEO does: ai search readiness
GEO is StoreSEO's AI readiness score for products. The agent reads which GEO criteria fail, fixes the ones a tool can fix (FAQs, AI snippet, alt text, product schema), and can rewrite a thin description from your own answers to StoreSEO's questions.
Requires: FAQs, AI snippets and descriptions spend AI Content Optimizer credit. The product needs a focus keyword, set in the StoreSEO app, before a description scan or rewrite.
- 1
Read the GEO checklist
The agent reads the product's GEO block: the score and every AI-readiness criterion that passes or fails.
- 2
Turn on product schema if it is off
Product JSON-LD is a shop-wide setting, so enabling it clears that criterion for every product at once. If you then decide not to apply the rest, the agent switches back off only the schema it turned on.
- 3
Preview FAQs and the AI snippet
The preview generates FAQs and an AI snippet (summary, benefits, best for) and projects the new SEO and GEO scores without saving.
- 4
Scan the description
For a thin or missing description, StoreSEO scores it on seven pillars (identity, materials, dimensions, features, use cases, what is included, care) and returns questions. The agent asks you each one, word for word.
- 5
Write and apply
With your answers, StoreSEO writes the description and saves it immediately; the response holds the only copy of the old text. The previewed FAQs and snippet are applied after your yes.
AI search readiness reference
| Scope | Products only; collections, pages and articles have no GEO score |
|---|---|
| Fixable by tools | FAQs, AI snippet, image alt text, product schema, description |
| Fixed only in the app or admin | Product title, category, product type, image count, inventory, variant barcode, SKU, price, image |
| Description pillars | Identity, materials, dimensions, features, use cases, what is included, care |
| Description write | Saved immediately to Shopify and StoreSEO; no undo and no revision history |
| Old description | Returned once in the write response, the only remaining copy |
| Product schema | Shop-wide toggle; credits the schema criterion on every product |
| Prerequisite | A focus keyword on the product, set in the StoreSEO app |
Rules Cursor follows
- The scan's questions go to you word for word and in order; the agent does not answer them for you.
- A description is only written without questions when you decline to answer or authorize a bulk run without them.
- Writing a description replaces the current one at once with no undo, so the agent asks first and keeps the old text the response returns.
- If the agent enabled product schema for this flow and you stop before applying, it turns that schema back off; it never disables a schema you already had on.
- Criteria only you can fix get one link to the product's fix page, not a link per criterion.
In Cursor
StoreSEO has 44 tools and Cursor allows about 40 active tools across all your servers, so you must turn some off in Cursor's MCP settings. For this job, make sure storeseo_get_resource_seo, storeseo_preview_resource_optimization and storeseo_apply_resource_optimization stay on, and if you want schema or a description rewrite, storeseo_update_schema_settings and the scan and write tools as well. If you set a StoreSEO tool to run without asking, the confirmation StoreSEO asks for in chat is the only check left, so keep the apply and write tools on ask.
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 can Cursor not find the StoreSEO tool for AI search readiness?
Cursor allows about 40 active tools across all servers and StoreSEO has 44, so one you need may be switched off. Open Cursor's MCP settings, find the storeseo server and turn on the preview, apply and get SEO tools, switching off tools for other jobs.
Does a .cursor/mcp.json entry make StoreSEO available in every project?
No. A server in .cursor/mcp.json belongs to that project only. Put it in ~/.cursor/mcp.json if you want StoreSEO's AI-readiness tools in every project you open.
What is a GEO score in StoreSEO?
GEO is StoreSEO's AI readiness score for products. It measures how well a product can be understood by AI shopping agents and generative search, using criteria such as FAQs, an AI snippet, image alt text, product schema and the quality of the description.
Can I undo a rewritten product description?
Not inside StoreSEO. The new description is saved immediately and StoreSEO keeps no revision history. The response returns the previous description once, so ask the agent to keep it for you before it writes.
Why does the agent ask me questions before writing a description?
StoreSEO scans the description on seven pillars and returns questions for the facts it cannot infer, such as materials or what is in the box. Your answers become stated facts in the new copy instead of guesses.
Does enabling product schema affect every product?
Yes. Product JSON-LD is a shop-wide setting, so turning it on clears that criterion for every product at once, and turning it off removes it everywhere.
Keep going
AI search readiness with other agents
More Cursor guides