Optimize meta tags and content with Zed
Optimizing meta tags and on-page content with Zed means asking the Agent Panel to have StoreSEO generate a meta title, description, tags, URL handle, FAQs and AI snippet for a Shopify resource, then approving the draft in the panel and at Zed's tool prompt.
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 in the window where your theme is loaded and, with a green dot beside storeseo under Settings, AI, MCP Servers, type a request such as preview the meta for my lowest-scoring product. Zed's default setting is confirm, so the panel asks before each tool action, including the reads. Expect a prompt for storeseo_start, another for storeseo_get_resource_seo, and another for storeseo_preview_resource_optimization. That last one generates the draft on StoreSEO's side, projects the new score without saving anything, and spends AI Content Optimizer credit when you allow it.
The generated meta title, description, tags, FAQs and AI snippet are shown in the panel, and a proposed URL handle comes with the old and new address because applying creates a redirect. This is where Zed gives you two separate checks. First StoreSEO tells the agent to wait for your yes in the conversation. Then, when the agent calls storeseo_apply_resource_optimization, Zed's own prompt appears and you allow or reject that single call. If you reply apply the meta and skip the FAQ, the call carries only those axes and the skipped parts stay available from the draft for an hour.
Several prompts in a row can feel slow when you work through a handful of products. Rather than setting the default to allow, give the read tools their own permission with keys of the form mcp:storeseo:tool_name, and leave the preview and apply tools on confirm. The preview prompt is a good moment to remember the credit cost, and the apply prompt is the last point where you can stop a handle change that would create a redirect.
-
You: Preview new meta for my lowest-scoring product.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Zed: The draft for Linen Throw Blanket has a new meta title and description, three tags and two FAQs. The projected score is 31 to 78 and the handle stays. Should I apply it?
-
You: Yes, apply it.
- storeseo_apply_resource_optimization needs approval
What to ask Zed
Use StoreSEO to preview new meta for my lowest-scoring product. Show me the draft and score change and apply nothing yet.
Preview a meta title, description and FAQ for the collection Summer Dresses and keep the current URL handle.
Apply the meta from that preview and skip the FAQ.
- 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 Zed 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 Zed
Zed asks before every tool action by default, reads included, and each preview prompt is a point where credit is about to be spent. Setting agent.tool_permissions.default to allow removes Zed's check, so the confirmation StoreSEO asks the agent for in the panel becomes the only one before storeseo_apply_resource_optimization writes. Allow individual read tools with per-tool keys and leave the preview, apply and settings tools on confirm.
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 for every StoreSEO call?
Zed's agent.tool_permissions.default is confirm, which asks before a tool action runs. You can allow only the read tools with per-tool keys such as mcp:storeseo:storeseo_get_resource_seo and keep the preview and apply tools on confirm.
Do I approve the apply twice in Zed?
Effectively yes. StoreSEO tells the agent to ask for your yes in the panel before it applies, and Zed then shows its own tool prompt for that call. The Zed prompt is the hard stop, and the in-panel confirmation is an instruction the agent follows.
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 Zed guides