BridgeToAgentGet the kit — $49
All install guides
Webflow~7 minIntermediate

Install your Agentic Kit on Webflow

Webflow does not let you upload arbitrary files at the root of your domain directly. You have two clean options: route the files through Custom Code & Redirects (works on every plan), or — if your site is on a paid Webflow Hosting plan with 301 Redirects plus Site Assets — host the files in Webflow Assets and redirect the root paths to the asset URLs.

This guide covers the second approach because it's the most reliable across Webflow plans. You'll be done in 7 minutes.

Step 1 — Upload the three files to Webflow Assets

  1. In the Webflow Designer, open the left sidebar and click the Assets panel.
  2. Click Upload and drag the three files from the kit ZIP:
    • agents.json
    • llms.txt
    • agent-instructions.md
  3. After upload, click each asset row to reveal its CDN URL. They look like: https://uploads-ssl.webflow.com/abc123.../agents.json
  4. Copy all three URLs to a notepad — you need them in Step 2.

⚠️ If Webflow rejects the file types Webflow Assets sometimes blocks unfamiliar extensions. Workaround: rename agents.json → agents.json.txt, agent-instructions.md → agent-instructions.md.txt, upload, then use the redirect target with the .txt suffix. Agents follow the redirect either way; the root-served URL keeps the canonical name.

Step 2 — Add 301 redirects

  1. In Webflow, go to Site Settings → Publishing → 301 Redirects.
  2. Add three redirects:
Old pathRedirect to
/agents.jsonthe Webflow Assets URL for agents.json
/llms.txtthe Webflow Assets URL for llms.txt
/agent-instructions.mdthe Webflow Assets URL for agent-instructions.md
  1. Click Save Changes.
  2. Click Publish in the top-right and publish to your live domain.

Step 3 — Verify

Open each URL in a new tab:

  • https://yourdomain.com/agents.json
  • https://yourdomain.com/llms.txt
  • https://yourdomain.com/agent-instructions.md

Each should serve the file content (Webflow performs a 301 redirect to the Assets CDN 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>.

  1. In Webflow, go to Site Settings → Custom Code → Head Code.
  2. Paste this block and click Save Changes:
<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">
  1. Publish.

Alternative: Cloudflare proxy (advanced)

If you front your Webflow site with Cloudflare, you can serve the three files directly from a Cloudflare Worker or R2 bucket — no Webflow redirects needed. This gives true root-served files. Use this only if Cloudflare already sits in front of your domain.

Troubleshooting

The redirect returns 404 even after publishing. Webflow caches the published site. Try a hard refresh (Cmd-Shift-R or Ctrl-F5) and confirm you published to the live domain, not just the staging webflow.io subdomain.

Webflow rejects the .json file extension on upload. See the warning in Step 1 — rename to .json.txt and target that extension in the redirect.

File downloads instead of displaying in the browser. Webflow Assets serves them with Content-Disposition: attachment on some plans. This is fine for AI agents — they read the bytes either way. Inline display would need a Worker-based proxy.

Need a hand? Reply to your purchase receipt and we'll help directly.