Get products ready for AI search with Zed
Getting products ready for AI search with Zed means asking the Agent Panel to read a product's GEO score in StoreSEO, preview FAQs and an AI snippet, and rewrite a thin description from your answers, with Zed's own prompts as a second check on every tool call.
Last updated: October 2026
Set up Zed for StoreSEO
Skip this if Zed is already connected. The full guide, with the alternatives, is on the Zed page.
- 1
Add StoreSEO as a remote server
Open Settings, then AI, then MCP Servers and add a remote server, or add this to settings.json yourself. Leave out headers so Zed can sign you in.
JSON{ "context_servers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in and check the dot
Because the entry has no Authorization header, Zed prompts you to authenticate. Pick your Shopify store and approve in the browser. In Settings, AI, MCP Servers a green dot next to storeseo means the server is active. Then ask this in the Agent Panel.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Zed?
You open the Agent Panel next to your theme files and type something like make Merino Beanie ready for AI search, preview first. The agent calls storeseo_start, then storeseo_get_resource_seo for the product, and Zed shows each call in the thread. By default Zed asks for approval before running any tool action, reads included, so the first pass is a handful of confirmations: start, list, get. The GEO block that comes back gives the score and each AI readiness criterion, which the agent turns into a short list of what is missing.
The fixing steps then pass through two gates. StoreSEO tells the agent to say what a preview costs in AI credit and to wait for your yes before storeseo_preview_resource_optimization, then to show the drafted FAQs, the AI snippet and the projected score before storeseo_apply_resource_optimization. Zed adds its own confirm prompt on each call, so you approve the same step twice in different places: once in the chat, once in the dialog. For a description, the agent runs storeseo_scan_product_description and asks you StoreSEO's questions in the thread, and you type the answers in the panel before storeseo_write_product_description runs.
You can tune the friction. Zed's tool permissions accept per-tool keys in the form mcp:storeseo:storeseo_list_resources, so you can allow the read tools and leave the preview, apply, schema and write tools on confirm. That keeps a catalog scan quick without removing the check on the steps that cost credit or change the store.
-
You: Make Ceramic Pour Over ready for AI search. Start with its description.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
-
Zed: Its GEO score is 29 and the description is one line. I can scan it, which spends AI credit and writes nothing, and then ask you StoreSEO's questions. Shall I scan?
-
You: Yes, go ahead.
- storeseo_scan_product_description preview
-
Zed: StoreSEO has seven questions. First, word for word: what materials is this product made from?
What to ask Zed
Use StoreSEO to list my five lowest GEO-scoring products and what each is missing for AI shopping agents. Read only.
Is product schema turned on for my store? If not, tell me what enabling it changes before you touch it.
Scan the description of Ceramic Pour Over for AI agents and ask me StoreSEO's questions one at a time. Do not write until I say so.
- 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 Zed 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 Zed
Zed asks before every tool action by default, so an AI readiness pass over several products means many prompts. Allow only the read tools with per-tool keys such as mcp:storeseo:storeseo_get_resource_seo and keep storeseo_scan_product_description, storeseo_write_product_description and the apply and schema tools on confirm, because they spend credit or change the store. If you set the default to allow, Zed's check disappears and StoreSEO's own request to wait for your yes is the only pause before a description is replaced.
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 does Zed prompt me even for reading GEO scores?
Zed's default tool permission is confirm, which prompts before any tool action. You can allow specific read tools with per-tool keys and leave writes on confirm.
Do I approve a description rewrite in Zed or in the chat?
Both. StoreSEO tells the agent to ask in the chat and wait for your yes, and Zed's own confirm prompt appears on the call unless you allowed that tool. The write replaces the live description with no undo.
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 Zed guides