Optimize meta tags and content with Kimi Code
Optimizing meta tags in Kimi Code means asking Moonshot AI's terminal agent to have StoreSEO generate a meta title, description, tags, URL handle and FAQs for one resource, reading the draft in the terminal and applying only what you approve.
Last updated: October 2026
Set up Kimi Code for StoreSEO
Skip this if Kimi Code is already connected. The full guide, with the alternatives, is on the Kimi Code page.
- 1
Add StoreSEO to Kimi Code
Create or edit ~/.kimi-code/mcp.json so every project on your machine can use StoreSEO. For one repository only, use .kimi-code/mcp.json inside it. You can also run /mcp-config in Kimi Code and have it add the server for you.
json config{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Start a new Kimi Code session (a server added mid-session registers in the next one), run this command, then follow the browser window: pick your Shopify store and approve access.
new message to Kimi Code/mcp-config login storeseo
Step-by-step guide in the docs: How to connect StoreSEO MCP to Kimi Code
How does this work in Kimi Code?
You work in the kimi prompt and name one resource to begin with, for example rewrite the meta for my linen shirt product. Kimi Code reads the current state with storeseo_get_resource_seo, then calls storeseo_preview_resource_optimization. StoreSEO writes the copy on its own servers, so the wording comes from StoreSEO rather than from the Kimi model, and the response carries a draft id and a projected score change. The preview spends AI Content Optimizer credit and saves nothing, which is why starting with one product before a larger batch is the sensible pattern.
Reading the draft is easier in a terminal than it sounds. Ask Kimi Code to print the old and new title and description as a short before and after block, and to show the old and new URL when the handle changes, because applying a handle creates a redirect from the old address. You then reply with which fields you accept. storeseo_apply_resource_optimization takes a subset, so you can approve the title and description and skip the handle, and the draft stays usable for an hour if you want the rest later.
Kimi Code can also compare the draft against the theme. If a template builds the title tag from a metafield or appends a store name, ask it to check the Liquid before you apply so the final title does not repeat the brand. For a larger run, ask for previews in batches of five and apply after each batch. Each preview costs credit whether or not you apply it, so keep the scope tight.
-
You: Improve the meta on my Linen Shirt product with StoreSEO.
- storeseo_start read-only
- storeseo_get_resource_seo read-only
-
Kimi Code: The meta description is empty. A preview spends AI Content Optimizer credit and saves nothing. Should I generate one?
-
You: Yes, go ahead.
- storeseo_preview_resource_optimization preview
-
Kimi Code: Illustrative draft: new title and description, score projected from 41 to 78, and a handle change from /linen-shirt to /mens-linen-shirt that adds a redirect. Apply the title and description and skip the handle?
-
You: Yes, apply those two.
- storeseo_apply_resource_optimization needs approval
What to ask Kimi Code
Tap a prompt to copy it, then paste it into Kimi Code.
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 Kimi Code 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 Kimi Code
Kimi Code's Approve for this session button is the one to watch here. Choosing it on storeseo_apply_resource_optimization lets every later apply in that session go through without a panel, so a batch of ten products becomes ten silent writes. Approve the first apply once, read what comes back, and keep a permanent rule in config.toml only for tools you are comfortable running unattended. Preview calls spend credit, so they deserve the same care even though they write nothing.
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
Does the Kimi model write the meta text?
No. StoreSEO generates the meta title, description, tags, handle and FAQs on its own servers when Kimi Code calls the preview tool. Kimi Code reads, presents and applies the draft, and any extra edits you want go through your own instructions.
What happens if I apply a URL handle change from Kimi Code?
StoreSEO updates the live URL and creates a redirect from the old address. The agent should show you the old and new URL before the apply call, and you can skip the handle while still applying the title and description.
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 Kimi Code guides