Install your Agentic Kit on BigCommerce
BigCommerce doesn't let you write arbitrary files to the root of your domain. The reliable install path is the same as on Shopify: upload the three files to Storefront Files (which BigCommerce calls Files in WebDAV / the Storage Manager), then create 301 Redirects from the canonical root paths to the file URLs.
You'll be done in under 10 minutes.
⚠️ Don't upload via Web Pages. BigCommerce's "Web Pages" surface renders content as HTML, which mangles the JSON in
agents.jsonand breaks AI agent parsing. The install must go through Storage / Files + 301 Redirects so the original content-type is preserved.
Step 1 — Upload the three files
You have two options for uploading; pick whichever your store config already supports.
Option A — Storage Manager (no plugins required)
- In BigCommerce admin, go to Storage → Storage Manager (newer accounts) or Storefront → Files depending on your plan's UI.
- Click Upload and add the three files from your kit ZIP:
agents.jsonllms.txtagent-instructions.md
- Right-click each row and copy its public URL. They look like:
https://store-12345.mybigcommerce.com/content/agents.json - Save all three URLs in a notepad — you need them in Step 2.
Option B — WebDAV (advanced)
- In BigCommerce admin, go to Server Settings → File Access (WebDAV).
- Use the WebDAV credentials there with a client like Cyberduck or Transmit.
- Connect, navigate to
/content/, and upload all three files. - The public URL is
https://yourdomain.com/content/<filename>.
Step 2 — Add 301 redirects
- In BigCommerce admin, go to Storefront → My Themes and click Customize on your active theme.
- Open Theme Editor → Theme Files and locate
301-redirects.jsonif your theme uses one, OR fall back to the global redirect manager. - For the global manager, go to Channel Manager → Storefront → URL Manager → URL Redirects (path may vary slightly per plan).
- Add three redirects:
| From | To | Type |
|---|---|---|
/agents.json | the file URL for agents.json | 301 |
/llms.txt | the file URL for llms.txt | 301 |
/agent-instructions.md | the file URL for agent-instructions.md | 301 |
- Save each.
Step 3 — Verify
Open each URL in a new tab:
https://yourdomain.com/agents.jsonhttps://yourdomain.com/llms.txthttps://yourdomain.com/agent-instructions.md
Each should serve the file content (BigCommerce performs a 301 redirect to the storage URL behind the scenes — agents follow redirects fine).
Step 4 (recommended) — Add the auto-discovery snippet
Tell AI bots where to find these files directly from your <head>.
- Go to Storefront → My Themes → Customize.
- Open Edit HTML/CSS → Templates → layout → base.html (or
theme.liquid-equivalent for your theme). - Find the closing
</head>tag and paste this immediately before it:
<link rel="alternate" type="application/json" title="Agent Action Map" href="/agents.json">
<link rel="alternate" type="text/plain" title="LLM Context" href="/llms.txt">
<link rel="alternate" type="text/markdown" title="Agent Runbook" href="/agent-instructions.md">
- Save and click Publish.
Alternative: a Cloudflare proxy (advanced)
If you front your BigCommerce domain with Cloudflare, you can serve the three files directly from a Cloudflare Worker or R2 bucket — no BigCommerce redirects needed. Use this only if Cloudflare already sits in front of your domain.
Troubleshooting
Redirect loop.
Make sure the destination URL is the full
https://store-xxxxx.mybigcommerce.com/content/... URL — not a
relative path.
File downloads instead of displaying inline.
BigCommerce's storage serves some extensions with
Content-Disposition: attachment. This is harmless — AI agents read
the bytes either way. Inline display would need a proxy.
Storage Manager doesn't let me upload .md files.
Older BigCommerce themes restrict uploads by extension. Rename
agent-instructions.md → agent-instructions.md.txt and use that as
the redirect target. The canonical /agent-instructions.md URL still
works because agents follow the redirect.
Related reading
- What is llms.txt? → — what the file you just installed actually does.
- What is agents.json? → — the action-manifest spec the JSON file follows.
- How the kit maps to Lighthouse Agentic Browsing → — audit-by-audit, what passes and why.
- Kit format changelog → — the
_metablock inagents.jsonand the footer lines in the other two files are version-tagged generator metadata; safe to leave in place.
Need a hand? Reply to your purchase receipt and we'll help directly.