Where do I put the llms.txt file?

Upload llms.txt to the root of your domain so it's reachable at yourdomain.com/llms.txt — the same location as robots.txt. On most platforms this is the top-level public folder of your site; it cannot live in a subfolder.

My llms.txt shows a 404 — what's wrong?

A 404 means the file isn't in your domain root. Check it's named exactly llms.txt (lowercase, no .txt.txt double extension), sits at the top level of your public folder, and that your site has redeployed since you added it. If your browser shows an HTML page instead of plain text, your platform is serving an error page — same fix.

Do I need a separate llms.txt for each subdomain?

Yes — like robots.txt, an llms.txt applies only to the exact host it's served from. If you run blog.example.com separately from example.com, each needs its own file at its own root.

Does llms.txt actually improve AI visibility?

Not measurably yet — large 2026 studies found AI crawlers rarely fetch the file, and our own CDN log testing across five country-level brand sites matched that finding. Treat it as cheap insurance: minutes to add, no risk, positioned for future adoption.

Install Guide

How to install your llms.txt

Three steps, about five minutes. If you don't have a file yet, generate one free here — AI drafts it from your website.

Upload the file to your domain root so it's reachable at yourdomain.com/llms.txt — the exact same place robots.txt lives. It must be at the top level: a subfolder won't work.

Verify it's live. Open yourdomain.com/llms.txt in a browser. You should see your file as plain text. A 404 or an HTML page means it's not in the root — see the troubleshooting below.

Keep it current. Update the file when key pages change — new products, major content, rebrands. Re-generating takes 30 seconds whenever you need a refresh.

Where the root is, by platform

Cloudflare Pages, Netlify, Vercel

Put llms.txt in your project's root, public/ or static/ folder (wherever your favicon and robots.txt live), commit, and redeploy. Done.

WordPress

Upload via your hosting control panel's file manager (or SFTP) into the public_html folder — the same directory as wp-config.php. Some SEO plugins can also serve custom root files.

Shopify

Shopify doesn't serve arbitrary root files from Settings → Files. You'll need the theme code editor to add a template that responds at /llms.txt, or ask your developer — it's a ten-minute job for them.

Webflow

Webflow can't host root text files directly on most plans. Options: a reverse proxy (e.g. via Cloudflare) serving the file, or hosting the file on your CDN. If that sounds like too much, this is the honest moment to say the effort may exceed the current benefit — see the note below.

Custom-built site

Forward this page to whoever deploys your site. The instruction is one line: "serve this file at /llms.txt from the domain root."

Troubleshooting

404: the file isn't at the root, or the site hasn't redeployed since you added it.
You see an HTML page instead of text: your platform is serving its error page for the missing path — same fix as the 404.
Filename gotchas: exactly llms.txt, lowercase. Watch for a hidden double extension (llms.txt.txt) if you saved from a text editor.
Subdomains: like robots.txt, the file only covers the exact host it's on. blog.example.com needs its own copy.

Set your expectations honestly: llms.txt is cheap insurance, not a ranking lever. Our own CDN log testing across five country-level brand sites found AI crawlers rarely fetch the file — matching the large public studies. It's worth having because it costs minutes and carries no risk. But the things that actually move AI visibility are brand mentions, answer-first content and E-E-A-T signals. Full evidence in our llms.txt guide.

llms.txt is step one. Visibility is the game.

Visibly checks whether ChatGPT, Gemini, Perplexity and Claude actually recommend your brand — and tells you exactly what to fix. Free brand scan launching soon.

Get early access →