Legible can work with multiple kinds of knowledge, and each one plays a different role. Some content belongs on the public website, some works best as a structured FAQ, and some belongs in uploaded documents that strengthen chat context without changing the site.
This guide helps customers decide which source to use for each type of information.
The Simple Decision Rule
- Use website content for material that should be public, discoverable, and part of the normal site experience.
- Use FAQs for short, high-value answers that need to be available quickly and clearly to AI systems and chat assistants.
- Use uploaded documents for deeper reference material that improves context but does not belong on the public website.
Website Content
Website content is the foundation of Legible. These are your normal pages, articles, docs, guides, product pages, and other public content. Legible turns that content into AI-readable formats and retrieval-ready material without requiring you to duplicate it elsewhere.
- Best for public-facing content that should be discoverable and citable.
- Best when the content already lives in your CMS and should stay there.
- Best when you want both human visitors and AI systems to access the same source material.
FAQ Items
FAQs are best when you need a short, direct answer that AI systems and chatbots can use immediately. They are especially helpful when the answer is important but not yet represented clearly enough on the public site.
- Best for repeated customer questions.
- Best for concise policy or support answers.
- Best when content should be available to the AI layer before the website is updated.
- Best when you want that content to strengthen chat and AI-facing indexes without a CMS deployment.
Uploaded Documents
Uploaded documents are best for long-form context, background material, implementation notes, manuals, PDFs, and internal-style reference content that improves answers but may not belong in your site navigation.
- Best for PDFs, DOCX files, Markdown files, and text notes.
- Best for richer background context that helps assistant quality.
- Best when the content improves retrieval but is not intended as a normal public page.
Comparison Snapshot
Website content
- Public: yes
- Good for llms.txt and AI discovery: yes
- Good for chat: yes
- Best for: canonical public source material
FAQs
- Public: optional
- Good for llms.txt and AI discovery: yes
- Good for chat: yes
- Best for: short, high-priority answers
Uploaded documents
- Public: not necessarily
- Good for llms.txt and AI discovery: primarily as part of Legible's AI knowledge layer
- Good for chat: yes
- Best for: supplementary context and reference materialHow Teams Usually Combine Them
- Keep canonical public information on the website.
- Add FAQs for direct answers the assistant should know immediately.
- Upload documents for reference material that improves answer quality behind the scenes.
- Let Legible unify all three into one retrieval-ready knowledge layer.
What Legible handles for you
- Teams do not need separate knowledge systems for public pages, FAQs, and supporting files.
- The same product layer can serve AI discovery and chatbot retrieval.
- Customers can choose the right source format without losing consistency in the underlying AI-ready content pipeline.
