Validate the file
Paste your Framer site map into the validator to catch missing context, unsafe URLs, and vague claims.
Open validatorllms.txt for Framer sites: a practical map for AI search and assistants
Framer sites are often fast-moving marketing sites with landing pages, CMS collections, case studies, and help content. A useful llms.txt file should not mirror every page. It should point to the pages that best explain the company, product, proof, policies, and support paths.
Publishing note: the ideal URL is
https://yourdomain.com/llms.txt. If your Framer setup cannot publish a root-level text file directly, use a verified fallback such as a reverse proxy, edge worker, or static host while keeping canonical links pointed at the Framer pages.
Best Framer pages to include
- Homepage and primary product or service page.
- Pricing, comparison, or plan-limit pages.
- Case studies, customer stories, or proof pages.
- CMS collection hubs for blog, guides, resources, or changelog posts.
- Help center, docs, status, security, privacy, terms, and contact pages.
Pages to avoid
- Experiment pages, duplicate landing pages, and unpublished campaign variants.
- Internal prototype links, preview links, or password-protected pages.
- CMS tag archives with thin or overlapping content.
- Claims that are not visible on public Framer pages.
Framer starter template
# Example Framer SaaS Site > Example Framer SaaS Site helps support teams summarize customer conversations and find answers faster. Important notes: - Product and pricing pages are the source for public capabilities. - Case studies describe specific customer contexts and should not be treated as guarantees. - Private dashboards, demos, and customer portals are not part of this public map. ## Core pages - [Homepage](https://example.com): Product overview and positioning - [Pricing](https://example.com/pricing): Plans, limits, and billing terms - [Case Studies](https://example.com/customers): Public customer proof - [Resources](https://example.com/resources): Guides and educational content - [Help Center](https://example.com/help): Setup and troubleshooting articles - [Security](https://example.com/security): Security and compliance overview - [Contact](https://example.com/contact): Sales and support escalation ## Optional - [Changelog](https://example.com/changelog): Product updates and behavior changes
Normal SEO still matters
Treat llms.txt as a curated context file, not as a ranking shortcut. Keep important Framer pages crawlable, internally linked, descriptive, and visible as text. Use Search Console and server logs to confirm that the final domain, sitemap, and important pages can be crawled.
Launch checklist
- Publish the Framer site on the final custom domain.
- Confirm
/robots.txt,/sitemap.xml, and public pages return HTTP 200. - Publish or proxy
/llms.txtonly after testing the final URL. - Submit the sitemap in Search Console after DNS and HTTPS are stable.
- Validate the
llms.txtdraft and monitor crawler logs after launch.
Compare platform setup
Need another visual-site builder example? The Webflow guide uses the same conservative publishing principle.
Read Webflow guide