Manage sitemaps and indexing with NanoClaw
Managing sitemaps with NanoClaw means asking your self-hosted agent in a chat which Shopify resources StoreSEO leaves out of the sitemap or marks noindex, then changing those flags one resource at a time after you reply yes.
Last updated: October 2026
Set up NanoClaw for StoreSEO
Skip this if NanoClaw is already connected. The full guide, with the alternatives, is on the NanoClaw page.
- 1
Create a StoreSEO access token
In the StoreSEO app open Settings, AI Toolkit and generate a personal access token. Keep it out of chat messages and out of Git.
new message to NanoClawSettings → AI Toolkit → create a token
- 2
Add StoreSEO to your agent's container
Run this on the machine that hosts NanoClaw, using your agent group's ID from ncl groups list. The header goes in as a JSON object. NanoClaw may ask an admin to approve the change.
terminalncl groups config add-mcp-server --id <group-id> --name storeseo \ --url https://mcp.storeseo.com/mcp \ --headers '{"Authorization":"Bearer YOUR_TOKEN"}' - 3
Restart the agent's container
The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask for your store's SEO score.
terminalncl groups restart --id <group-id>
Step-by-step guide in the docs: How to connect StoreSEO MCP to NanoClaw
How does this work in NanoClaw?
One stray noindex flag can remove a page from search results, so this job is best done in a thread you can scroll back through. Message @Andy and ask what is hidden from search. The agent calls storeseo_start and then storeseo_list_resource_sitemaps for one resource type at a time, filtered on sitemap, noindex or nofollow. Each row shows the flags for a product, collection, page or article. Ask it to group the result, for instance every noindex page and every product left out of the sitemap, and reply with the ones that were intentional.
Changes go through storeseo_update_resource_sitemap, one resource per call, and it writes Shopify metafields on that resource. The agent should name the resource and the flag in the thread, wait for your yes, make the call, and then list the flags again to confirm the state. The HTML sitemap adds a manual step: storeseo_update_html_sitemap generates it, you add the link to a menu in Shopify admin using the edit URL from storeseo_list_sitemap_menus, and only then does the agent mark setup complete. The agent cannot add the menu link for you.
NanoClaw scheduled tasks work well on the read side. Create one that lists noindex and sitemap-excluded resources every Monday and tells you what is new since last time, which catches an accidental flag early. Keep it report only. Changing a flag from a scheduled run would hide a page from search with nobody watching, and your fork may or may not stop to ask before the tool runs, so the prompt itself has to forbid it.
-
You: @Andy use StoreSEO to show me which pages are hidden from search.
- storeseo_start read-only
- storeseo_list_resource_sitemaps read-only
-
NanoClaw: Illustrative result: two pages are noindex, and one of them is your Shipping Policy. Should I turn noindex off for the Shipping Policy page?
-
You: Yes, turn it off.
- storeseo_update_resource_sitemap needs approval
- storeseo_list_resource_sitemaps read-only
-
NanoClaw: Confirmed: the Shipping Policy page is no longer marked noindex.
What to ask NanoClaw
Tap a prompt to copy it, then paste it into NanoClaw.
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 NanoClaw 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 NanoClaw
Group chats are the risk here. In a shared Slack or Discord channel anyone who can message your agent with the trigger word can ask for a flag change, and the StoreSEO token behind it is yours. Add the StoreSEO server only to an agent group whose chat has just the people you trust with your store, and check how your fork restricts who may trigger the agent before allowing noindex changes.
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 a NanoClaw scheduled task flag pages as noindex for me?
It can if the prompt says so, but nobody is there to confirm, and a wrong flag hides a page from search. Keep scheduled tasks to listing flags and reporting what is new, and make changes in a chat.
Can NanoClaw add the HTML sitemap to my menu?
No. After it generates the sitemap, you add the link to a menu in Shopify admin yourself, using the edit link the agent sends you, and then the agent can mark setup complete.
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 NanoClaw guides