Adding llms.txt by Platform

The file itself is trivial — the friction is platform-specific. Here's how to get /llms.txt live on each major setup, plus how to verify it worked:

WordPress

• Easiest: a snippet plugin (e.g. WPCode) with a rewrite rule serving static content at /llms.txt.
• Classic: upload via FTP/SFTP to the web root (public_html/) alongside .htaccess. Works unless caching layers interfere.
• Verify: visit yoursite.com/llms.txt — you should see raw Markdown, not a 404 or the theme's 404 page.

Shopify

• Shopify doesn't allow arbitrary root files. Workaround: create a page/redirect. Settings → URL Redirects won't serve text/plain reliably; use an app or proxy route instead.
• Alternative that works today: put the content behind /pages/llms and reference it from robots.txt Sitemap field context — imperfect, but readable by crawlers that fetch HTML too.
• Verify: fetch the URL with curl -I and check the status code.

Webflow

• Site settings → Custom Code → you can't add root files directly; publish a CMS item with slug "llms.txt" and strip styling via a blank layout page. Content-type will be text/html — acceptable to most readers, not ideal.
• Verify: confirm the slug resolves publicly.

Static hosts / Vercel / Netlify

• Drop llms.txt into the deploy root. Done. This is the zero-friction case.

Universal verification (30 seconds)

Run our free audit after any change — it checks all six surfaces including llms.txt reachability and content type, so you know immediately whether the platform mangled something.