Optimize meta tags and content with Kiro
Optimizing meta tags and on-page content with Kiro means asking the agent in its IDE chat panel to have StoreSEO generate a meta title, description, tags, URL handle, FAQs and AI snippet for a Shopify resource, then applying the draft you approve.
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 or storefront project open, and the storeseo server defined in .kiro/settings/mcp.json or the user-level file. In the chat panel you type a request such as preview new meta for the product Linen Throw Blanket and show me the score change. Kiro calls storeseo_start, then storeseo_get_resource_seo, then storeseo_preview_resource_optimization. If you listed the read tools in autoApprove they run straight away; otherwise Kiro prompts for each. The preview is generated by StoreSEO on its own side, projects the new SEO score without saving, and spends AI Content Optimizer credit.
Kiro works in a plan-and-act style, so it often wants to break a request into steps. For this job, keep the steps small: one resource, one preview, one decision. When the draft appears, with a meta title, description, tags, FAQs, an AI snippet and sometimes a new URL handle, read the old and new address before you agree, since applying creates a redirect. A reply such as apply all of it but not the tags makes the agent call storeseo_apply_resource_optimization with the axes you chose, and the result shows the recomputed score and what still fails.
Kiro's per-server settings are useful here. The autoApprove list can cover the read tools, and disabledTools can hide the apply and settings tools from the agent while you are only experimenting with drafts. StoreSEO tells the agent to wait for your yes before applying, but that is an instruction the agent follows, so the autoApprove list is where you decide whether Kiro itself adds a second prompt for the write.
-
You: Preview new meta for Linen Throw Blanket and show me the score change.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
- storeseo_preview_resource_optimization preview
-
Kiro: The draft has a new meta title and description, three tags and two FAQs, and the score would go from 31 to 78. The handle is unchanged. Do you want me to apply it?
-
You: Apply everything but the tags.
- storeseo_apply_resource_optimization needs approval
What to ask Kiro
Use StoreSEO to preview new meta for my lowest-scoring product. Show the draft and the projected score and wait for my answer before applying.
Preview a meta title, description and FAQ for my Shipping Policy page and keep the handle.
Apply that preview except the tags, then show me the new score and the checklist that remains.
- 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 Kiro 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 Kiro
autoApprove with a wildcard would let Kiro run every StoreSEO tool without asking, which includes storeseo_apply_resource_optimization and the preview tool that spends credit. List individual read tools such as storeseo_get_resource_seo instead, so Kiro's prompt remains a second check on the write. A workspace file at .kiro/settings/mcp.json also overrides a user-level storeseo entry, so if the wrong store answers, check which file defines it.
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
Should I put the preview tool in Kiro's autoApprove list?
Only if you are comfortable spending AI Content Optimizer credit without a prompt. A preview generates content and writes nothing to the store, but it costs credit each time. Keep the apply and settings tools out of autoApprove so Kiro still prompts for writes.
Can Kiro hide the apply tool while I only review drafts?
Yes. The disabledTools list on the storeseo server hides tools from the agent, so adding storeseo_apply_resource_optimization there lets you generate and read previews without any way to apply them until you remove it.
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 Kiro guides