Get products ready for AI search with Kiro
Getting products ready for AI search with Kiro means asking its agent, from the chat panel in your IDE, to read a product's GEO score in StoreSEO, preview the fixes and rewrite a thin description, with an autoApprove list you control deciding which calls run unprompted.
Last updated: October 2026
Set up Kiro for StoreSEO
Skip this if Kiro is already connected. The full guide, with the alternatives, is on the Kiro page.
- 1
Add StoreSEO to your Kiro MCP config
Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows and Linux), search for MCP and open the workspace config (.kiro/settings/mcp.json) or the user config (~/.kiro/settings/mcp.json). Paste this and save. Kiro applies the change on save, and the first connection opens a browser sign-in: pick your Shopify store and approve.
JSON{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }
How does this work in Kiro?
You work in Kiro with your theme project open and ask in the chat panel which products AI shopping agents will find hardest to read. The agent calls storeseo_start, then storeseo_list_resources sorted by score and storeseo_get_resource_seo for the weakest ones. The GEO score and the failing criteria come back, and the agent reports them in the chat: missing FAQs, no AI snippet, image alt text gaps, a one-line description. A sensible autoApprove list covers exactly these read tools, so the audit runs without a prompt on each call.
The write side stays outside that list. The agent calls storeseo_preview_resource_optimization to draft FAQs and an AI snippet and to project the new GEO score, after telling you it spends AI credit; Kiro should prompt for it, since you have not listed it, and that prompt is a useful moment to check the cost. You review the draft in the chat, say yes, and storeseo_apply_resource_optimization applies what you accepted. For a thin description the agent runs storeseo_scan_product_description, asks you StoreSEO's questions in order, and passes your answers to storeseo_write_product_description once you have agreed that it replaces the live text.
Because Kiro supports both a workspace file at .kiro/settings/mcp.json and a user file at ~/.kiro/settings/mcp.json, you can keep a read-only autoApprove list in the shared workspace config and a different one personally. If the sign-in points at the wrong store, check which of the two files defines storeseo, since the workspace entry wins on a name clash.
-
You: Which products are weakest for AI search, and how do I fix the worst one?
- storeseo_start read-only
- storeseo_list_resources read-only
- storeseo_get_resource_seo read-only
-
Kiro: Merino Beanie scores 38 on GEO: no FAQs, no AI snippet and no alt text on two images. A preview spends AI credit and writes nothing. Do you want me to run it?
-
You: Yes, preview it.
- storeseo_preview_resource_optimization preview
What to ask Kiro
Use StoreSEO to list my five lowest GEO-scoring products and what each is missing for AI shopping agents. Read only.
Preview FAQs and an AI snippet for Merino Beanie, tell me the AI credit cost first, and apply nothing until I confirm.
Scan the description of Ceramic Pour Over for AI agents and ask me every question StoreSEO returns, in order.
- 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 Kiro 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 Kiro
Keep storeseo_scan_product_description, storeseo_write_product_description, storeseo_update_schema_settings and storeseo_apply_resource_optimization out of Kiro's autoApprove list. The scan spends AI credit, the write replaces the live description with no undo, and the schema switch is store-wide. A wildcard in autoApprove would run every StoreSEO tool without Kiro asking, so list individual read tools such as storeseo_start and storeseo_get_resource_seo and leave the rest for Kiro's own prompt.
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 should I put in Kiro's autoApprove for this job?
Only reads, such as storeseo_start, storeseo_list_resources and storeseo_get_resource_seo. Leave the scan, preview, apply, schema and description write tools out so Kiro still prompts for them.
Does Kiro need a focus keyword on the product before a description rewrite?
Yes. StoreSEO's scan and write require a focus keyword on the product, which you set in the StoreSEO app. Kiro cannot set one with any tool.
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 Kiro guides