FAQs
Purpose
FAQs are a structured list of question/answer pairs. They surface on:
- The public FAQ page (
/faqs). - Inline FAQ blocks placed on relevant pages.
- The AI Help Chat, which uses them as one of its knowledge sources.
- AEO (Answer Engine Optimisation) — auto-published as schema.org FAQ markup for search engines.
When to use this
When the same question comes in by email three times, write an FAQ entry. Saves you answering it a fourth.
Key fields
- Question — the question as a visitor would phrase it.
- Answer — the answer. Markdown supported. Aim for 2-4 short paragraphs.
- Category — pick from Blog Categories (or repurpose) to group FAQs.
- Order — sort order within a category.
- Status — Draft / Published.
Common tasks
Add an FAQ
- Content > FAQs, Create New.
- Question, Answer.
- Category, Order.
- Status = Published, Save.
Embed an FAQ block on a page
- Edit a Page or Post.
- Add an FAQ block.
- Pick the FAQs to show (or filter by category).
- The block renders an accordion.
Auto-extracted FAQs
The AEO indexer scans your Posts for ## headings phrased as questions and proposes them as FAQs. Review and Publish the ones you want — they're created as Drafts. See Content > FAQs for any pending suggestions.
Gotchas
- The AI Help Chat reads FAQs as a knowledge source — write them clearly. "What time does the bar open?" beats "Bar hours".
- Schema markup — published FAQs are emitted as JSON-LD on their host page, helping Google show them directly in search results. Avoid putting promotional/marketing copy in answers; treat them as honest factual replies.
- Don't bury answers — link to the relevant page where appropriate, but answer the question in the FAQ itself. Members shouldn't have to chase a link.
- Auto-extracted FAQs can be noisy — clean them up regularly to avoid surfacing internal-jargon questions to visitors.
Related
Still need help? Open the chat assistant in the corner, or send us a message.
