Publish llms.txt and agents.md with Manus
Publishing llms.txt and agents.md with Manus means asking a task agent to check what your store serves to AI crawlers and shopping agents through StoreSEO, then generate or roll back those files once you have agreed what goes live.
Last updated: October 2026
Set up Manus for StoreSEO
Skip this if Manus is already connected. The full guide, with the alternatives, is on the Manus page.
- 1
Create an access token in StoreSEO
In the StoreSEO app, open Settings, then AI Toolkit, and generate a named personal access token. Copy it now and keep it out of any chat.
new message to ManusStoreSEO → Settings → AI Toolkit → generate a token
- 2
Add StoreSEO as a custom MCP server
In Manus, open Settings, then Integrations, then Custom MCP Servers, and choose Add Server. Give it a name, paste this URL as the server URL and enter your token as the authentication, as a Bearer token.
server URLhttps://mcp.storeseo.com/mcp
- 3
Check it and use it
Manus verifies it can reach the server and read its tools. Then start a task that names StoreSEO, so Manus uses the connector.
new message to ManusUse StoreSEO to show me my store's SEO score breakdown.
Step-by-step guide in the docs: How to connect StoreSEO MCP to Manus
How does this work in Manus?
Begin with a question rather than a command. A task that says use StoreSEO to tell me what my store serves at llms.txt and agents.md makes Manus call storeseo_start, storeseo_get_llms_txt_status and storeseo_get_agents_md_status, and storeseo_list_llms_txt_versions if you want the version history. You get the saved settings, the latest version, whether a rebuild is due, the public URLs and whether agents.md is a custom file or Shopify's default. All of these are reads, so this first answer needs no approval and costs no credit.
Generating is where a long task shape helps. storeseo_generate_llms_txt queues the run, and the same run writes a template into your live theme and uploads a copy to Shopify Files, so Manus should tell you that before it starts. The generation takes a minute or two and the status tool is the poll, which Manus can keep checking in the same task until generation_ongoing turns false. Then it can report the version that is now active. storeseo_generate_agents_md is different: it publishes live at once, spends credit and needs at least one published product.
Rolling back is separate. storeseo_activate_llms_txt_version makes an older version the live one, and the live file serves the active version, which is not always the newest. Deleting a version and resetting agents.md to Shopify's default are permanent, so Manus should name exactly what it will remove and which version will take over. Ask it to paste the generated text into the task before a reset, because there is no history to restore it from.
-
You: Use StoreSEO to check my llms.txt and then refresh it if it is stale.
- storeseo_start read-only
- storeseo_get_llms_txt_status read-only
-
Manus: Illustrative result: the latest version is nine weeks old and a rebuild is due. Generating writes a template into your live theme and uploads a copy to Shopify Files in the same run, with no separate publish step. Should I generate it?
-
You: Yes, generate it.
- storeseo_generate_llms_txt needs approval
- storeseo_get_llms_txt_status read-only
-
Manus: Generation finished and the new version is active. It includes products and collections.
What to ask Manus
Tap a prompt to copy it, then paste it into Manus.
What StoreSEO does: llms.txt and agents.md
llms.txt is a curated map of your store for AI crawlers, and agents.md tells AI shopping agents who you are and how to buy. StoreSEO generates both from your store data and publishes them to your live theme; the agent checks status, generates, switches llms.txt versions and resets agents.md to Shopify's default.
Requires: agents.md generation spends AI Content Optimizer credit and needs at least one published product.
- 1
Check what is live
The agent reads the llms.txt status (settings, latest version, whether a rebuild is due, public URL) and the agents.md status (custom file or Shopify's default, public URL).
- 2
Warn before publishing
Generating llms.txt writes a template to your live theme and uploads a copy to Shopify Files in the same run, with no separate publish step. Generating agents.md publishes it live at once and spends credit. The agent says so and waits for your yes.
- 3
Generate and wait
llms.txt generation takes a minute or two; the agent polls the status until it finishes. agents.md returns the published text and its URL straight away.
- 4
Manage versions
StoreSEO keeps the latest ten llms.txt versions. The live file serves the active version, which is not always the newest, and any version can be made active again.
- 5
Roll back
Deleting a version is permanent. Resetting agents.md drops the custom file so Shopify's default serves again, and there is no history to restore it from.
llms.txt and agents.md reference
| llms.txt | Generated from your products, collections, pages and posts; served at your store's /llms.txt |
|---|---|
| Where it is written | A template in the live theme plus a copy in Shopify Files, in the same run |
| Schedule | llms.txt can regenerate on a saved schedule; settings passed with a run are saved for scheduled runs |
| Versions kept | The latest ten; the live file serves the active one |
| Generation time | About one to two minutes for llms.txt |
| agents.md | AI-written from your brand profile, top products, collections and contact details; served at /agents.md |
| agents.md publish | Live immediately; replaces Shopify's native default |
| agents.md reset | Shopify's default serves again within seconds; the custom text is gone for good |
Rules Manus follows
- The agent tells you that llms.txt generation writes to your live theme before it starts.
- agents.md generation publishes live and spends credit, so the agent says both and waits for your yes.
- Deleting an llms.txt version and resetting agents.md cannot be undone; the agent confirms each one.
- Deleting the active llms.txt version promotes the next newest automatically, so the agent says which version will go live.
In Manus
This is the job where a scheduled Manus task is most tempting and most risky. A weekly task that reads the status and reports whether a rebuild is due is a good use of it. A weekly task that also generates would write to your live theme and publish agents.md with nobody there to agree, and the skip confirmations setting would remove the one pause Manus has. Leave that setting off, schedule the status check only, and run any generation as a normal task you are watching.
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 a Manus task have to stay open while llms.txt generates?
The generation runs in StoreSEO and takes a minute or two. Manus polls storeseo_get_llms_txt_status until generation_ongoing is false, so keep the task open until it reports the new version rather than assuming it finished.
Can a scheduled Manus task regenerate llms.txt for me?
You could write it that way, but you should not. Generating writes to your live theme, and a scheduled run cannot wait for your yes. Schedule a status check and generate in a task you start.
What is the difference between llms.txt and agents.md?
llms.txt is a curated map of your store for AI crawlers and answer engines, served at /llms.txt. agents.md is the file AI shopping agents read to understand your brand and how to shop with you, served at /agents.md. StoreSEO can generate both.
Does generating llms.txt change my theme?
Yes. The same run writes an llms.txt template into your live theme and uploads a copy to Shopify Files. There is no separate publish step, which is why the agent should warn you before it starts.
Can I go back to an older llms.txt?
Yes. StoreSEO keeps the latest ten versions, and any of them can be made the active one, which republishes it to your storefront. Deleting a version is permanent.
Can I undo a generated agents.md?
You can reset it, which makes Shopify's native default serve again within seconds. The custom text is discarded with no history, so keep a copy if you might want it back.
Keep going
llms.txt and agents.md with other agents
More Manus guides