FAQ Structuring Best Practices
Group multiple FAQs into a single article
Knowledge Management retrieves content at the article level. We recommend you do not create one article per FAQ question, because it creates unnecessary maintenance overhead and fragments content in ways that can reduce search accuracy.
Instead, we recommend you group related questions into a single topic-based article. For example, all questions related to life insurance products and coverage should live in one article titled something like "Life Insurance — Frequently Asked Questions."
A good FAQ article typically contains between 5 and 15 questions. Fewer than 5 questions may not justify a standalone article; more than 15 is a signal the topic can and should be split, for easier parsing by both people and machines.
Recommended article structure
Title
Use a clear, descriptive title that signals the topic and the FAQ format.
Examples:
- Life Insurance — Frequently Asked Questions
- Claims Process FAQs
- Billing and Payments — Common Questions
Avoid vague titles like "General FAQs" or "Miscellaneous Questions." These are difficult for users and AI to interpret.
Summary
Always complete the page summary field. Knowledge Management uses this field in search ranking. A strong description briefly lists the types of questions covered, to help users and AI confirm they have found the right article before they click through.
Example: "Answers to common questions about life insurance coverage, beneficiaries, policy changes, premium payments, and lapses."
Individual Q&A pairs
Format each question and answer pair as follows:
- Use a heading for the question. Knowledge Management indexes headings heavily, which allows AI to surface the specific question within a search result.
- Write the question in natural language, the way a user would phrase it.
- Place the direct answer in the first sentence immediately below the heading.
- Follow with supporting detail or context if needed.
- Keep most answers between 2 and 5 sentences.
- Link to deeper documentation, instead of embedding procedures inline.
Do not bury the answer. If the key information is not in the first sentence of the answer block, it may be missed by AI retrieval systems that chunk content.
When to split an FAQ into separate articles
A single topic-cluster article works well in most cases. Split the page into multiple articles when any of the following apply:
- The audience is meaningfully different. For example, agent-facing FAQs vs. policyholder-facing FAQs on the same topic.
- Alternately, use conditional content blocks to distinguish audiences.
- The article has grown beyond 15 questions.
- The questions fall naturally into sub-topics.
- Analytics or user feedback shows that people consistently cannot find answers within the combined article.
When splitting, cross-link related articles so users can navigate between them easily.
FAQs vs. procedural documentation
FAQ articles answer what and why. Step-by-step procedures answer how. Keep these content types separate.
Mixing FAQs and procedures in the same article degrades both the user experience and AI retrieval accuracy. If an FAQ answer naturally leads into a process (for example, "How do I file a claim?"), provide a brief answer and then link to the dedicated procedure article, rather than embedding the full steps.
Reference: FAQ article checklist
- The title uses topic name + FAQ signal (for example, "Life Insurance — Frequently Asked Questions").
- The Page Summary field is completed and lists the types of questions covered.
- Each question is formatted as a heading.
- Each answer leads with a direct response in the first sentence.
- The article contains between 5 and 15 questions.
- Procedural content is linked, not embedded.
- Related FAQ articles are cross-linked if the topic has been split.
Pro tip: Prompt the Enhanced Editor AI to quickly format your FAQs.