An expandable list of questions and answers. Obelisk automatically emits the right structured data for SEO.
Use an FAQ block to answer the recurring questions visitors ask before they convert — pricing, shipping, compatibility, cancellation terms. Collapsing the answers keeps the page scannable while still giving search engines the full text through the automatic FAQPage markup.
Because Google can show FAQ rich results directly in the search listing, this is one of the more effective ways to win extra space on a results page without extra SEO work — you just write the questions and answers.
Typical placement: at the bottom of a pricing or product page, or as a standalone /faq/ page built with the Pages feature.
What belongs in an FAQ
On a webshop, the strongest FAQ content covers shipping times, return policy and payment methods — the questions that most often stop a visitor from checking out. On a portfolio or agency site, it tends to cover process and timeline questions: how long a project takes, how revisions work, what's included in the price. On a professional services site, it's the natural place for pricing structure, engagement terms or eligibility questions that would otherwise need a phone call to answer. The common thread is that every entry should be a question a real visitor actually asks before converting, not filler content invented to pad the page.
A common mistake is duplicating information that's already covered elsewhere on the same page — if the pricing table already states the cancellation policy clearly, repeating it verbatim in the FAQ adds length without adding value. Another is writing answers so short they don't actually resolve the question ("It depends" is not an answer); since the FAQPage structured data surfaces this text directly in search results, a thin answer undersells the page in Google as much as it does for a visitor. Keep individual FAQ blocks focused — a long list of thirty questions is harder to scan than several shorter, page-specific FAQ sections placed where they're relevant.
An FAQ combines well with a Cta placed directly below it: once objections are addressed, the visitor is in the best position to act. For answers that need more than a sentence or two — step-by-step instructions, for example — nest a RichText block inside the answer rather than cramming everything into plain text.
Because the accordion is built on native disclosure behaviour, it opens and closes correctly with keyboard navigation and is announced properly by screen readers without any extra markup — you only need to write clear questions and complete answers.
<Faq> <FaqItem question='What is Obelisk?'>A headless CMS.</FaqItem> </Faq>