Manage sitemaps and indexing with Kimi Code
Managing sitemaps and indexing in Kimi Code means asking Moonshot AI's terminal agent to list the sitemap, noindex and nofollow flags StoreSEO holds for each resource, change them one at a time, and set up an HTML sitemap for your Shopify store.
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 ask something like which products are excluded from my sitemap or marked noindex. Kimi Code calls storeseo_list_resource_sitemaps for a resource type, product, collection, page or article, and can filter by sitemap, noindex or nofollow state. Each row carries the flags and a resource id, which the write tool takes. The list is a read, so in Always Ask mode it runs without a panel and you can page through a large catalog quickly.
Changes are one resource per call. storeseo_update_resource_sitemap sets sitemap_disabled, no_index or no_follow for a single product, collection, page or article, writing the matching Shopify metafields. A noindex flag removes a page from search results, so the agent should name the resource and wait for your yes, and after the write it should list the flags again in the same turn rather than assume the change took. In a terminal that makes a neat loop: change, re-list, report the current state.
The HTML sitemap has its own pair of tools. Kimi Code reads the current state with storeseo_get_html_sitemap_settings, generates it with storeseo_update_html_sitemap, and fetches your navigation menus with storeseo_list_sitemap_menus. Adding the link to a menu is a step you do in Shopify admin, because no tool does it, so the agent hands you the edit URL and the sitemap address and then marks setup complete once you tell it the link is in. If you only want a page out of the XML sitemap and not out of search, say so, because sitemap exclusion and noindex are separate flags and the agent should set only the one you name.
-
You: Which pages are marked noindex right now?
- storeseo_start read-only
- storeseo_list_resource_sitemaps read-only
-
Kimi Code: Illustrative result: the Summer Sale page and the Returns page are both noindex. The Summer Sale page is expired, so that looks right. Shall I set the Returns page back to indexable?
-
You: Yes, change the Returns page only.
- storeseo_update_resource_sitemap needs approval
- storeseo_list_resource_sitemaps read-only
-
Kimi Code: Re-listed: the Returns page is now indexable and still in the sitemap.
What to ask Kimi Code
Tap a prompt to copy it, then paste it into Kimi Code.
What StoreSEO does: sitemaps and indexing
StoreSEO controls two things here: per-resource sitemap flags (left out of the XML sitemap, noindex, nofollow) and an HTML sitemap page. The agent lists flags, changes them one resource at a time and walks you through the HTML sitemap setup.
- 1
List the flags
The agent lists products, collections, pages or articles with their sitemap, noindex and nofollow flags, filtered as you ask.
- 2
Change one resource
After your yes it sets the flags on one resource, which writes the matching Shopify metafields.
- 3
Re-read before reporting
Flags can also change in the StoreSEO app, so the agent re-lists before telling you the current state.
- 4
Create the HTML sitemap
It reads the HTML sitemap settings, then generates and enables the page.
- 5
Add it to a menu
It lists your navigation menus with their edit links; you add the sitemap link to a menu in Shopify admin, then the agent marks setup complete.
Sitemaps and indexing reference
| Flags per resource | Excluded from sitemap, noindex, nofollow |
|---|---|
| Resource types | Products, collections, pages and articles |
| Where flags live | Shopify metafields on the resource |
| HTML sitemap steps | Generate and enable, add the link to a menu yourself, mark complete |
| HTML sitemap settings | Replaced wholesale on update; read first |
| Menus | Listed with edit links; the menu you choose is not stored |
| Plan | Every active plan |
Rules Kimi Code follows
- A noindex flag removes a page from search results, so the agent names the resource and waits for your yes.
- The agent re-lists flags in the same turn before telling you their current state.
- Adding the sitemap link to a menu is a step you do in Shopify admin; no tool does it.
- HTML sitemap settings are read before every update, because an update replaces them.
In Kimi Code
Sitemap flags are single-resource writes with search consequences, and a long catalog tempts you toward Approve for this session. In Kimi Code that choice turns a careful one-page change into a loop that can flip many flags without a panel, and a wrong noindex only shows up weeks later in search traffic. Approve each write on its own, or keep a rule that leaves storeseo_update_resource_sitemap on ask while the list tools run freely.
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 Kimi Code add the HTML sitemap link to my menu?
No. Adding the link is a step you do in Shopify admin. Kimi Code can fetch your menus and their edit links with StoreSEO, give you the sitemap address, and mark setup complete after you tell it the link is in place.
Why does Kimi Code re-list flags after changing one?
StoreSEO tells the agent to re-read the flags in the same turn before reporting their state, so what you hear back is what the store now holds, not what the agent expected the write to do.
What is the difference between excluding a page from the sitemap and noindex?
Excluding a resource leaves it out of your XML sitemap, so crawlers are not pointed at it. Noindex tells search engines not to show the page in results even if they find it. StoreSEO sets each flag separately per resource.
Can the agent add the HTML sitemap to my menu?
No. The agent generates the HTML sitemap and lists your menus with their edit links, and you add the sitemap link to a menu in Shopify admin. Then the agent can mark setup complete.
Do sitemap tools need a paid plan?
No. The sitemap tools work on every active StoreSEO plan.
Why does the agent check the flags again before answering?
Sitemap flags can also be changed in the StoreSEO app outside the conversation, so an earlier listing may be stale. Re-reading in the same turn keeps the answer accurate.
Keep going
Sitemaps and indexing with other agents
More Kimi Code guides