Optimize meta tags and content with OpenCode
Optimizing meta tags and on-page content with OpenCode means asking the terminal agent to have StoreSEO generate a meta title, description, tags, URL handle, FAQs and AI snippet for one Shopify resource, then applying the draft you approve from the prompt.
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 start OpenCode in your theme project, check that opencode mcp list shows storeseo as connected, and type a request such as preview new meta for my lowest-scoring product and wait for me. The model sees the tools as storeseo_ plus the tool name and calls storeseo_start, then storeseo_get_resource_seo, then storeseo_preview_resource_optimization. StoreSEO writes the draft on its own side and projects the new SEO score, plus the GEO score for products, without saving anything. The preview spends AI Content Optimizer credit even if you never apply it.
The draft is printed in the terminal, which makes it easy to keep. Ask OpenCode to paste the title and description into a notes file in the project, or to compare the proposed URL handle with the product's current one before you decide. When the handle changes, you should see the old and new URL first, because applying creates a redirect. Say apply everything except the handle, and OpenCode calls storeseo_apply_resource_optimization with the skipped fields listed. The result returns the recomputed score and checklist, which OpenCode summarizes as what is fixed and what still needs you.
OpenCode's permission rules can match tool names with a pattern such as storeseo_*. The docs describe deny rules but no ask-first mode, so StoreSEO's own request for your yes in the chat is the main check on writes. If you want a client-side stop, deny storeseo_apply_resource_optimization and storeseo_update_ai_optimization_settings by name while you review drafts, and remove the rule when you are ready to apply.
-
You: Preview new meta for my lowest-scoring product and wait for me.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
OpenCode: Here is the draft for Linen Throw Blanket: new meta title and description, three tags and a shorter handle, which would create a redirect from the old URL. Projected score 31 to 78. Apply it all?
-
You: Apply all except the handle.
- storeseo_apply_resource_optimization needs approval
What to ask OpenCode
Use StoreSEO to preview new meta for my five lowest-scoring products. Show each draft and the score change, and do not apply anything.
Preview a meta title, description and FAQ for the page About Us, keep the handle, and save the draft text to meta-draft.md.
Apply the previewed meta but skip the tags and the URL handle.
- Optimize the meta title and description for my five lowest-scoring products. Show me the previews before you apply anything.
- Preview a new meta title, description and FAQ for the collection Summer Dresses, and keep the current URL handle.
- Apply the meta from that preview but skip the FAQ.
- Which of my pages have no meta description? Draft one for each and wait for my approval.
- What does StoreSEO optimize automatically for new products right now?
- Turn on automatic meta and alt text for new products only. Tell me what that will spend first.
What StoreSEO does: meta tags and on-page content
StoreSEO generates the content server-side: meta title and description, tags, a keyword-led URL handle, FAQs and an AI snippet. The agent shows you the draft and the projected score change before anything is saved, then applies all of it or only the parts you approve.
Requires: Generating a preview spends AI Content Optimizer credit; applying a preview is free.
- 1
Read the current state
The agent reads the resource's SEO record so it knows which fields exist, which fail and what the preview will add.
- 2
Generate a preview
StoreSEO writes the meta title, description, tags, URL handle, FAQs and AI snippet and projects the new SEO score, plus the GEO score for products. Nothing is saved yet. Preview spends credit whether or not you apply it.
- 3
Show you the draft
The agent presents the generated text and the score change. When the handle changes it shows the old and new URL and tells you a redirect will be created.
- 4
Apply what you approve
After your yes it applies everything, or only the parts you chose, for example the meta but not the FAQs. Skipped fields stay available from the same draft for an hour.
- 5
Report the new score
The apply call returns the recomputed score and the remaining checklist, so the agent tells you what changed and offers the next most useful fix.
Meta tags and on-page content reference
| Generated fields | Meta title, meta description, tags, URL handle, FAQs, AI snippet |
|---|---|
| Resource types | Products, collections, pages and articles (collections have no meta tags or tags axis in auto settings) |
| Who writes the copy | StoreSEO, server-side. The agent never authors meta, FAQs or handles itself |
| Cost | Preview spends AI Content Optimizer credit; apply is free; a new preview spends again |
| Draft lifetime | One hour after the preview |
| URL handle | Applying a new handle changes the live URL and creates a redirect from the old one; a handle already in use is dropped automatically |
| Partial apply | Apply a subset of axes, or skip individual fields such as the handle |
| Auto optimization | Optional settings that generate content for newly synced resources; only future syncs, nothing is backfilled |
| Auto settings plan | Configurable on any plan; switching an auto toggle on needs a paid plan and no active trial |
Rules OpenCode follows
- The agent previews first and applies only after you confirm the previewed content.
- When a handle changes, you see the old URL and the new URL before the apply call, because applying creates a redirect.
- A request like optimize my worst five products authorizes the previews; the agent should remind you that previews spend credit even if you do not apply them.
- Turning on auto optimization spends credit on every future sync, so the agent proposes the exact sections and waits for your yes.
- Product title, focus keyword and description body are not written by this job; the description has its own tool in the AI search job.
In OpenCode
OpenCode V2 expects servers under mcp.servers while older versions put the entry directly under mcp, so a config copied from a tutorial may leave storeseo missing and the model with no preview tool at all. Because the documented permission rules are deny rules and not an ask-first mode, a deny pattern on storeseo_* also blocks the read and preview tools, so deny only the apply and settings tools by name if you want drafts but no writes.
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 applying a draft while I review it?
Yes. Add a permission rule that denies storeseo_apply_resource_optimization by name. Previews and reads still run, and you remove the rule when you are ready to apply. A broad pattern that matches every StoreSEO tool would block the preview tool too.
Does OpenCode need the StoreSEO tools added in every project?
Only if you added the server without the global flag. opencode mcp add writes to the project configuration by default, so run it with the global flag to make StoreSEO available in every project.
Does previewing an optimization change my product?
No. A preview generates the content and projects the score without saving anything. It does spend AI Content Optimizer credit, and applying the draft afterwards is free.
What happens to the old URL when the handle changes?
Applying a new URL handle updates the live URL and StoreSEO creates a redirect from the old one, so existing links keep working. The agent should show you both URLs before it applies the change.
Can I apply only part of a preview?
Yes. The apply step takes the axes you approved, and individual content fields such as the URL handle can be skipped. Skipped parts stay available from the same draft for one hour.
Does auto optimization fix my existing products?
No. Auto optimization only acts on resources synced or updated after you turn it on. Existing products are fixed with the preview and apply steps in this job.
Will StoreSEO change my product title?
No. This job writes the SEO meta title, not the storefront product title. The product title is edited in Shopify admin.
Keep going
Meta tags and on-page content with other agents
More OpenCode guides