Publish llms.txt and agents.md with OpenClaw
Publishing llms.txt and agents.md with OpenClaw means using your own always-on agent runtime, reached from a chat app or the CLI, to check which AI discovery files your store serves and to have StoreSEO regenerate them when you say so.
Last updated: October 2026
Set up OpenClaw for StoreSEO
Skip this if OpenClaw is already connected. The full guide, with the alternatives, is on the OpenClaw page.
- 1
Add StoreSEO to OpenClaw
Run this on the installation that owns the connector. The --auth oauth flag marks the server as an OAuth server, which is what openclaw mcp login needs.
Terminalopenclaw mcp add storeseo \ --url https://mcp.storeseo.com/mcp \ --transport streamable-http \ --auth oauth
- 2
Sign in to your store
The login prints an authorization URL. Open it in a browser, pick your Shopify store and approve access. OpenClaw captures the redirect and saves the credentials.
Terminalopenclaw mcp login storeseo
- 3
Check the connection
The probe opens a live connection and reports the tools the server offers. A saved server entry proves nothing until the probe passes.
Terminalopenclaw mcp doctor storeseo --probe
How does this work in OpenClaw?
OpenClaw runs on your machine or server and you talk to it from WhatsApp, Telegram, Slack, Discord, the Control UI or the CLI. Once storeseo is added with openclaw mcp add and signed in with openclaw mcp login, you message it the way you would a colleague: is my llms.txt current. OpenClaw opens a StoreSEO session with storeseo_start and reads storeseo_get_llms_txt_status and storeseo_get_agents_md_status. The reply lands in the same chat, naming the active version, whether a rebuild is due and whether /agents.md is custom or Shopify's default.
The status checks suit OpenClaw's scheduler, which is the real difference here. An automation created with openclaw automations create can run every Monday in an isolated session, read both statuses and announce the result in a channel. Keep that job to reads. A scheduled run has nobody to say yes, and storeseo_generate_llms_txt writes into your live theme while storeseo_generate_agents_md publishes at once and spends credit. If the Monday report says a rebuild is due, reply in the chat. OpenClaw then asks you to confirm, runs the generation after your yes and polls until it finishes.
OpenClaw also has its own per-server approval setting, configured with openclaw mcp configure storeseo --approval and one of approve, prompt or auto. For this job, prompt is the sensible choice for the write tools, because it adds a client-side stop on top of the confirmation StoreSEO asks the agent for. You can narrow the 44 tools with openclaw mcp tools include and exclude options, for example to expose only the status and version tools to a reporting agent and keep generation, activation, deletion and reset for a separate one.
-
You: The Monday report said a rebuild is due. Regenerate my llms.txt.
- storeseo_start read-only
- storeseo_get_llms_txt_status read-only
-
OpenClaw: Confirmed: settings changed after version 6. Generating writes llms.txt into your live theme and uploads a copy to Shopify Files in one run, and takes a minute or two. Run it?
-
You: Yes, run it.
- storeseo_generate_llms_txt needs approval
- storeseo_get_llms_txt_status read-only
-
OpenClaw: Done. The new version is active at your /llms.txt. I will keep next Monday's report read-only.
What to ask OpenClaw
Use StoreSEO to check my llms.txt and agents.md status and tell me if a rebuild is due. Read only.
Every Monday at 8am, send me which llms.txt version is live and whether agents.md is custom or default. Do not generate anything.
A rebuild is due. Tell me what generating llms.txt writes to my theme and then wait for my yes.
- Is my llms.txt up to date, and which version is live right now?
- Generate a new llms.txt that includes products and collections but not blog posts. Warn me before it goes live.
- Show me my llms.txt versions and switch back to the one from last week.
- Does my store serve a custom agents.md or Shopify's default?
- Write an agents.md for my store and publish it. Tell me what it costs first.
- Reset agents.md to Shopify's default.
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 OpenClaw 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 OpenClaw
A scheduled OpenClaw automation cannot wait for a yes, so keep the weekly llms.txt and agents.md job report-only and tell it in the prompt not to generate, activate, delete or reset anything. Do the writes in a message you can answer. If you set openclaw mcp configure storeseo --approval to auto, nothing in OpenClaw stops a generation, so StoreSEO's own request to confirm is then the only check. Also run the mcp commands on the installation that owns the connector, or the report will fail to find storeseo.
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 OpenClaw regenerate my llms.txt on a schedule?
StoreSEO can regenerate llms.txt on a schedule saved in its own settings, which an agent can set through storeseo_generate_llms_txt. An OpenClaw automation is better used for a read-only weekly status report, because a scheduled run cannot give the yes that a live theme write needs.
Where does the OpenClaw report about llms.txt appear?
In the channel you give the automation with the announce, channel and to options, such as a Telegram chat. Past runs are listed with openclaw automations runs followed by the job ID.
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 OpenClaw guides