Implementation Guide

Add llms.txt to Your Site

Step-by-step instructions for 13 hosting providers. Some have built-in support — others need a file drop or a quick config change.

File Format

llms.txt uses a simple markdown structure defined at llmstxt.org.

OrderElementSyntaxDetails
1Title (H1)# Site NameProject or site name
2Blockquote> Summary textOne or two sentence description
3DetailsFree-form markdownOptional additional context
4Section headings## SectionOrganize links by category
5Link list- [Title](url): DescOne entry per resource

Example

# Example Company

> Cloud-based project management for teams of all sizes.

## Docs

- [Getting Started](https://example.com/docs/start): Quick start guide
- [API Reference](https://example.com/docs/api): Full API documentation

## Blog

- [Announcing v2.0](https://example.com/blog/v2): Major release notes
- [Best Practices](https://example.com/blog/tips): Tips for teams

Provider Instructions

Select a hosting provider to see step-by-step setup instructions.

Built-in Support

These providers have native llms.txt support — enable it from their dashboard.

Easy Setup

Drop the file into your project and deploy. Minimal or no configuration.

Moderate Setup

Requires server configuration or CLI commands beyond dropping a file.

Workaround Required

No native file hosting at the domain root. Use a redirect, proxy, or app.

Quick Reference

Where to place llms.txt on each provider at a glance.

ProviderSupportFile LocationNotes
WebflowBuilt-inProject Settings > SEONative support since July 2025
WixBuilt-inAuto-generatedSEO Dashboard > Tools & Settings
WordPressBuilt-inPlugin or site rootYoast SEO, Rank Math, or manual upload
GitHub PagesManualRepository rootAdd to Jekyll include list if needed
NetlifyManualPublish directoryOptional netlify.toml for headers
VercelManual/public folderOr Route Handler for dynamic generation
Cloudflare PagesManualBuild output rootUse _headers file for Content-Type
ApacheManual/var/www/html/ or public_html/Optional .htaccess for MIME type
AWS S3 + CloudFrontManualS3 bucket rootSet Content-Type on upload; invalidate cache
NGINXManualWeb rootAdd location block; reload with nginx -s reload
IISManualC:\inetpub\wwwroot\Optional web.config for MIME mapping
SquarespaceManualExternal (redirect/proxy)URL redirect or Cloudflare Worker
ShopifyManualApp or Liquid templateMultiple apps available; or DIY with Liquid

Best Practices

Guidelines for an effective llms.txt file.

Content

  • Start with a clear H1 title matching your brand or site name
  • Write a concise blockquote summary — one or two sentences
  • Organize links under descriptive H2 headings
  • Use the format: - [Title](URL): Description
  • Prioritize high-value content first; skip low-quality pages
  • Keep descriptions factual — avoid marketing language

Common Mistakes

  • Listing every page instead of key resources
  • Forgetting to update after adding or removing important pages
  • Using HTML instead of standard markdown
  • Including broken or redirecting links
  • Serving with wrong Content-Type (use text/plain or text/markdown)
  • Keyword stuffing or promotional copy

Technical

  • Serve as text/plain or text/markdown — never text/html
  • Ensure accessible at /llms.txt (optionally /llms-full.txt for extended content)
  • Use UTF-8 encoding
  • Keep the file under 100 KB
  • Set cache headers between 1–24 hours
  • Verify with: curl -I https://yourdomain.com/llms.txt

Maintenance

  • Update when you publish significant new content
  • Automate generation from your CMS or build pipeline where possible
  • Remove links to deprecated or retired pages promptly
  • Test periodically to confirm correct Content-Type and encoding