Home / Guides

llms.txt for Webflow sites: a clean map for AI search and assistants

Webflow sites are often built as polished marketing funnels. A useful llms.txt file should not mirror every landing page. It should point to the pages that explain the company, product, trust signals, and policies most clearly.

What to include

• Homepage or primary product landing page.
• Pricing, plans, or product comparison page.
• Case studies, customer proof, or results pages.
• Docs, help center, API docs, or onboarding guides if public.
• About, contact, security, privacy, and terms pages.

Webflow starter template

# Example Webflow SaaS Site

> Example Webflow SaaS Site helps small support teams answer customer questions faster.

Important notes:
- Product pages explain public capabilities and pricing.
- Case studies are the best evidence pages.
- Do not infer private customer data or unpublished roadmap claims.

## Core pages
- [Homepage](https://example.com): Product overview and positioning
- [Pricing](https://example.com/pricing): Current public plans and limits
- [Case studies](https://example.com/customers): Customer proof and outcomes
- [Help center](https://example.com/help): Public setup and troubleshooting docs
- [Security](https://example.com/security): Security and compliance overview

## Optional
- [Blog](https://example.com/blog): Public articles and updates

How to publish it

The ideal URL is https://yourdomain.com/llms.txt. If your Webflow setup lets you publish a root-level text file, use that. If not, common workarounds include a reverse proxy, a lightweight edge worker, or hosting the file on a static host while keeping the canonical site links pointed at your Webflow pages.

SEO pairing

Keep normal SEO basics in place: crawlable pages, internal links, canonical URLs, sitemap, and visible text. Treat llms.txt as a curated context layer, not a replacement for public pages or a guaranteed AI citation signal.