Home / Guides

llms.txt for help centers: make support knowledge easier to find and trust

A help center or knowledge base can have hundreds of articles. A useful llms.txt file should not list all of them. It should point AI assistants, support teams, and search crawlers toward the canonical public pages that explain the product, policies, troubleshooting paths, and escalation options.

Best pages to include

• Help center home and top category landing pages.
• Getting started, account setup, billing, and troubleshooting hubs.
• Top FAQs that answer recurring pre-sale and support questions.
• Contact, escalation, status, refund, privacy, and terms pages.
• Product changelog or release notes if support answers depend on version changes.

Pages to avoid

• Private ticket URLs, customer portals, or logged-in article paths.
• Duplicated tag archives and search result pages.
• Outdated articles that contradict current support policy.
• Thin one-question pages when a better category hub exists.

Help center starter template

# Example Help Center

> Example Help Center explains setup, billing, troubleshooting, and support escalation for Example Product.

Important notes:
- Public support articles are general guidance, not customer-specific advice.
- Account-specific issues require the authenticated support portal.
- Status and changelog pages are the source for incidents and release changes.

## Core pages
- [Help Center Home](https://example.com/help): Main support hub and category index
- [Getting Started](https://example.com/help/getting-started): First setup path
- [Account and Billing](https://example.com/help/billing): Plans, invoices, refunds, and account access
- [Troubleshooting](https://example.com/help/troubleshooting): Common fixes and diagnostic steps
- [Contact Support](https://example.com/contact): Escalation and support channels
- [Status](https://status.example.com): Current incidents and uptime history
- [Privacy Policy](https://example.com/privacy): Data handling and privacy terms

## Optional
- [Changelog](https://example.com/changelog): Product releases and behavior changes

Pair it with normal SEO

A curated llms.txt file is only a map. Keep help articles crawlable, internally linked, dated when needed, and consistent with your visible support policy. Submit the sitemap after major help center migrations, and use server logs or Search Console to confirm Googlebot and other crawlers are reaching the pages you expect.

Measure whether it helps

• Search Console impressions for help-center queries.
• Referral visits from support/community answers.
• Bot hits to /robots.txt, /sitemap.xml, /llms.txt, and key help articles.
• Copy or audit events when support teams reuse the guidance.