§ Webflow

llms.txt on Webflow

Webflow hosting does not serve arbitrary root files, so /llms.txt cannot be uploaded. The options that exist, ranked by how much they actually get you.

Webflow serves pages it generates and assets from its CDN. Root-level files are managed by the platform - robots.txt is exposed in site settings, others are not.

generate one from your site →

§ how to serve it

Serving /llms.txt from Webflow.

step 1

Know the constraint before you look for a setting

There is no file upload for root paths in Webflow. Assets go to uploads-ssl.webflow.com or the site CDN, and pages live at the slugs you give them. Webflow exposes robots.txt in Site settings → SEO because it built a feature for it; llms.txt has no such feature unless and until Webflow adds one. Time spent hunting the admin for it is time wasted.

step 2

Check whether Webflow has shipped support since

Worth thirty seconds before building a workaround. Fetch the path on your published site - a platform that adds root-file support does so without every customer hearing about it.

bash

curl -sI https://your-site.webflow.io/llms.txt | head -1
curl -sI https://your-custom-domain.com/llms.txt | head -1

step 3

Put a reverse proxy in front if the path matters

The only way to get a real file at /llms.txt on a Webflow-hosted domain is to answer the request before it reaches Webflow. If your domain is already behind Cloudflare, a Worker on that route returns the file in a few lines and leaves the rest of the site untouched.

Cloudflare Worker, routed on example.com/llms.txt

const FILE = `# Acme

> What Acme does, in one sentence.

## Pages

- [Product](https://acme.com/product): What it does and who it is for
`;

export default {
  fetch(request) {
    const { pathname } = new URL(request.url);
    if (pathname === '/llms.txt') {
      return new Response(FILE, {
        headers: { 'Content-Type': 'text/plain; charset=utf-8' },
      });
    }
    return fetch(request); // Everything else goes to Webflow untouched.
  },
};

step 4

Or accept a page, and stop pretending it is the file

A Webflow page at /llms is an HTML page. It is not an llms.txt and no client looking for the file will find it. It can still be a perfectly good human-readable index of your site - just do not let a tool or an agency tell you it satisfies the format.

§ what goes wrong here

What Webflow gets wrong.

The failures below are specific to Webflow. A generic llms.txt guide will not mention any of them.

Exporting the site does not help if Webflow hosts it

The Webflow-specific confusion. Code export gives you a zip you can host anywhere, and on your own host a root file is trivial. But if you are still publishing to Webflow hosting, the export changes nothing about what the live domain serves. Two different deployment targets, one of which you are not using.

Custom code in site settings cannot create a URL

Webflow's custom code fields inject markup into the head or body of your pages. They cannot create a new URL, cannot set a content type, and cannot respond to a request for a path that has no page. Whatever you put there, /llms.txt still 404s.

The .webflow.io staging domain behaving differently

Your staging domain is noindexed by Webflow and does not always behave identically to the custom domain, particularly once a proxy is in front of the latter. Test against the domain that is actually published.

§ related

Next to read.

Squarespacellms.txt on SquarespaceSquarespace does not expose the domain root, so there is no way to serve /llms.txt from a Squarespace-hosted site. What that leaves you, stated plainly.Shopifyllms.txt on ShopifyShopify does not let you put arbitrary files at the domain root, so /llms.txt is not directly writable. What you can actually do, and which workarounds are worth it.Next.jsllms.txt on Next.jsTwo ways to serve /llms.txt from Next.js - a static file in public/, or a route handler that generates it from your content. Plus the middleware and rewrite traps that make a correct file return HTML.toolllms.txt CheckerFetch your /llms.txt, validate it against the spec, and report what is missing.

→ What Is llms.txt? The Format, and What It Actually Does

§ faq

Questions, answered.

Can you add an llms.txt file to a Webflow site?

Not on Webflow hosting. There is no root-file upload, and custom code fields inject markup into existing pages rather than creating new URLs. The real options are a reverse proxy in front of your domain that answers /llms.txt itself, or hosting the exported site somewhere that lets you place files at the root.

Why can I edit robots.txt in Webflow but not llms.txt?

Because robots.txt is a feature Webflow built. The platform serves root-level files it knows about, and each one is a deliberate product decision, not a general "any file at the root" capability. If Webflow adds llms.txt support it will appear the same way - as a field in site settings.

Does a Webflow page at /llms work instead?

It is an HTML page at a different URL, so no client looking for /llms.txt will find it, and anything that does fetch it gets markup rather than markdown. It can still be a useful human-facing index; it just is not an llms.txt and should not be described as one.

Is a Cloudflare Worker worth it for one file?

Only if you have decided the exact path matters, and only if your domain is already behind Cloudflare. You are adding a piece of infrastructure in front of your whole site to serve a file whose real-world effect is currently unproven. That is a reasonable bet for some sites and clearly not worth it for others.

§ the part that matters

An llms.txt will not fix a site AI cannot read.

Before writing an index for AI clients, check that they can fetch your pages at all. LintPage runs 60 checks against a URL in about 30 seconds - free, no signup.

run a full scan →