Get products ready for AI search with OpenCode
Getting products ready for AI search with OpenCode means working in the terminal session you already have open, where the agent reads a product's GEO score in StoreSEO, previews the fixes, and rewrites a thin description once you have answered its questions.
Last updated: October 2026
Set up OpenCode for StoreSEO
Skip this if OpenCode is already connected. The full guide, with the alternatives, is on the OpenCode page.
- 1
Add StoreSEO to OpenCode
Run this from the project that should use StoreSEO, or add --global to make it available in every project. OpenCode writes a remote server entry to its configuration; the equivalent hand-written entry is shown in the next step.
Terminalopencode mcp add storeseo --url https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Remote servers use OAuth by default. Run the auth command, then pick your Shopify store in the browser and approve access. Inside OpenCode, /mcps does the same: select storeseo and sign in. opencode mcp list should then show it as connected.
Terminalopencode mcp auth storeseo opencode mcp list
How does this work in OpenCode?
You run OpenCode in your theme project and ask for what you want in plain words: which products are weakest for AI shopping agents, and what would fix the worst one. OpenCode calls storeseo_start first, then storeseo_list_resources by score and storeseo_get_resource_seo for the product you name. The GEO block comes back with the score and every criterion that passes or fails, and OpenCode summarizes it in the terminal. These are reads, and OpenCode lists them as tool calls as they run.
To fix a product, OpenCode checks storeseo_get_schema_settings and, if product schema is off, tells you that enabling it is a store-wide switch before it calls storeseo_update_schema_settings. It then calls storeseo_preview_resource_optimization for FAQs and an AI snippet, which spends AI credit and saves nothing, and shows the projected score. After your yes, storeseo_apply_resource_optimization applies what you accepted. If you decide not to apply the rest, the schema it turned on for this flow should be turned back off. Descriptions go through storeseo_scan_product_description, with StoreSEO's questions asked in order in the terminal and your answers typed back.
Because OpenCode is a terminal tool you can keep the evidence in the repository: ask it to write the before and after GEO checklists, or the previous description returned by the write, to a Markdown file next to your theme. Tool names appear with the server name in front, so a deny rule for the storeseo server can hide a tool you do not want the agent to reach.
-
You: Is product schema on? If not, turn it on for the AI readiness work.
- storeseo_start read-only
- storeseo_get_schema_settings read-only
-
OpenCode: Product schema is off. It is a store-wide setting, so turning it on clears that GEO criterion for every product. Do you want me to enable it?
-
You: Yes, enable it.
- storeseo_update_schema_settings needs approval
-
OpenCode: Product schema is now on. Next I can preview FAQs and an AI snippet for Merino Beanie, which spends AI credit and saves nothing.
What to ask OpenCode
Use StoreSEO to list my five lowest GEO-scoring products and what each is missing. Read only.
Make Merino Beanie ready for AI search. Check product schema first, then preview FAQs and an AI snippet and wait for my yes.
Scan the description of Ceramic Pour Over for AI agents, ask me the questions, and save the old description to old-description.html in this folder before writing.
- 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 OpenCode 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 OpenCode
OpenCode's documentation describes deny rules for MCP tools but no ask-before-running mode, so the pause before storeseo_write_product_description comes from StoreSEO's instruction to the agent and from you reading the terminal. That tool saves at once with no undo. If you want a client-side stop, deny the write tools by name until you are ready to use them, and remember that opencode mcp add only writes to the current project unless you pass --global.
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 I stop OpenCode from rewriting descriptions at all?
Yes. OpenCode documents deny rules for MCP tools, so you can hide storeseo_write_product_description and run only previews and reads until you decide otherwise. Tool names carry the server name in front.
What if I enabled product schema and then change my mind?
Tell OpenCode to turn it back off. Schema is a shop-wide setting, so the job's rule is that the agent only switches off the schema it enabled for this flow, never one you already had on.
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 OpenCode guides