How to Add llms.txt to Your Webflow Site
Webflow gives you a beautiful visual builder but a deliberately locked-down hosting layer. There is no FTP and no root file manager, so adding a llms.txt file takes one extra step compared with a self-hosted site. This guide walks through the two approaches that actually work on Webflow and is honest about the trade-offs of each.
Start with a generated file
Whichever hosting workaround you choose, you first need the content itself. Our free generator reads your existing pages and produces a properly structured llms.txt in Markdown. Enter your Webflow domain, review the output, and download the file — then use one of the two delivery methods below to make it live at your root.
Generate your file first:
What the file should contain
The llms.txt format, proposed by Jeremy Howard and Answer.AI in 2024, is just Markdown: an H1 with your business name, a blockquote summary, and H2 sections of curated links with short descriptions. Keep it human-readable and point only to canonical, public URLs.
# Your Business Name > A one-sentence description of what your > Webflow site offers and who it serves. ## Services - [Design Services](https://yourdomain.com/services): What you do. - [Pricing](https://yourdomain.com/pricing): Plans and rates. ## Portfolio - [Case Studies](https://yourdomain.com/work): Selected projects. ## About - [About](https://yourdomain.com/about): Team and story. - [Contact](https://yourdomain.com/contact): How to reach you.
Save it as plain text named llms.txt (lowercase). You will host this exact content in whichever method you pick next.
Method 1: A 301 redirect to a hosted copy
Webflow's project settings include a 301 redirects panel under Publishing. Host your llms.txt somewhere you control raw responses — an object-storage bucket, a GitHub raw URL, or a small static host — then add a redirect:
Old path: /llms.txt Redirects to: https://files.example-host.com/llms.txt
This is the fastest path and needs no DNS changes. The honest caveat: a crawler hitting /llms.txt receives a redirect rather than the content directly. Reputable crawlers follow 301s, so this generally works, but a direct 200 response is technically cleaner. If you want that, use Method 2.
Method 2: A reverse proxy (Cloudflare)
For a true 200 response at your root, place your domain behind a proxy such as Cloudflare and intercept the single path. Point your domain's DNS at Cloudflare (keeping Webflow's hosting records proxied), then add a Cloudflare Worker or a Snippet/Rule that returns your Markdown for /llms.txt and passes everything else through to Webflow.
// Cloudflare Worker (sketch)
export default {
async fetch(request, env) {
const url = new URL(request.url);
if (url.pathname === "/llms.txt") {
return new Response(env.LLMS_TXT, {
headers: { "content-type": "text/plain; charset=utf-8" },
});
}
return fetch(request); // pass through to Webflow
},
};Store the file body in a Worker variable, KV, or environment binding. This yields a clean, cache-friendly text/plain response at the canonical URL and never touches the rest of your Webflow site.
Verify it works
Open the URL
Visit https://yourdomain.com/llms.txt. With Method 1 you should land on the hosted copy; with Method 2 you should see plain-text Markdown with no redirect.
Check the response
Use your browser dev tools or curl -I to confirm a 200 (Method 2) or a 301 that resolves to your file (Method 1), served as text/plain.
Confirm the links resolve
Every URL inside the file must return 200 on your live Webflow site. Broken links in llms.txt are worse than omitting them.
Run a visibility check
Use our AI Visibility tool to confirm the file is reachable and parseable from outside your network.
Frequently Asked Questions
Can I upload llms.txt directly to Webflow?
No. Webflow is a closed hosting environment with no FTP, file manager, or way to drop a raw .txt file at your domain root. Every published URL is generated from a page or asset in the Designer, and page slugs cannot contain a dot, so you cannot create a page literally named llms.txt. That constraint is why a workaround is required.
Does a 301 redirect to an external file still work for AI crawlers?
Most reputable crawlers follow redirects, so a 301 from /llms.txt to a hosted copy will usually resolve. That said, a direct 200 response at the canonical path is cleaner and removes any risk that a crawler declines to follow the hop. Treat the redirect as a pragmatic option, not a perfect one.
Will putting Webflow behind Cloudflare break my site?
It should not, as long as you keep Webflow's DNS and SSL requirements satisfied and proxy the correct records. A Cloudflare Worker or redirect rule can intercept /llms.txt and return your content directly, which is the closest thing to native root-file support Webflow allows.
Is llms.txt guaranteed to change how AI tools describe my business?
No. As of mid-2026 llms.txt is a proposed, advisory standard with no enforcement mechanism. Support varies across AI systems, and there is no guarantee any given model will fetch or use your file. It is a low-cost, best-practice signal, not a ranking lever.
Where does the file physically live in the reverse-proxy approach?
You host the Markdown content wherever you control raw responses — a Cloudflare Worker, an object-storage bucket, a small serverless endpoint, or another static host — and the proxy layer maps your domain's /llms.txt path to it. Webflow keeps serving your marketing pages; only that one path is intercepted.
Generate Your llms.txt for Webflow
Enter your Webflow domain and get a ready-to-host llms.txt file. Then wire it up with a redirect or a Cloudflare Worker.