FAQ Section
A list of questions that expand to reveal their answers: one centred column of bordered rows, each with a square plus/minus button, matching the product and ingredients page design.
The questions can come from two places. You can type them straight into the section as FAQ Item blocks, or you can point the section at a reusable FAQ cluster so the same set of questions can be maintained once and shown on several pages. A cluster always wins: as soon as one is attached with questions in it, the blocks are ignored entirely.
The section also outputs FAQ structured data behind the scenes, which is what lets Google show the questions directly in search results and lets AI assistants quote the answers. That happens automatically — there’s nothing to switch on.
Settings
Section titled “Settings”| Setting | What it does |
|---|---|
| Section ID | Optional anchor, so a link elsewhere on the page can jump here. Must be unique on the page and written in handle format (section-id, not Section ID). |
| FAQ cluster | The reusable set of questions to show. Leave empty to use the FAQ Item blocks below instead. |
| Fallback FAQ cluster | Used only when FAQ cluster is empty. This is how the collection pages work — the cluster comes from the collection’s own settings, and this field supplies a general set for collections that don’t have one. |
| Padding top / bottom (mobile) | Space above and below the section on phones. Default 3rem each. |
| Padding top / bottom (tablet) | Space above and below the section at tablet width. Default 4rem each. |
| Padding top / bottom | Space above and below the section on desktop. Default 5rem each. |
There are no colour settings on this section — it inherits its text colour from the page.
Blocks
Section titled “Blocks”The heading
Section titled “The heading”The heading above the questions is a Title block, not a section setting. Select it in the customizer the way you would any other title to change the wording, heading level, or type style. Clear its text to run the section with no heading at all.
The FAQ cluster’s own title is not used here. A cluster is reused across several pages, so a title travelling with it meant the heading could change out from under the page it was placed on. Set the heading where you can see it instead.
Accepts FAQ Item blocks — but only as the fallback for when no FAQ cluster is attached.
| Setting | What it does |
|---|---|
| Question | The line shown in the closed state. Default “What stores carry our products?”. |
| Answer | The rich text revealed when the row is opened. Links and lists are fine. |
| Open by default | Starts the row expanded when the page loads. Off by default. |
Where it’s used
Section titled “Where it’s used”- Product pages and the Ingredients page — no cluster, questions written as blocks.
- Collection pages — FAQ cluster wired to the
collection’s own FAQ cluster setting and
frequently-asked-questionsas the fallback. Each collection can therefore carry its own questions, and any collection that doesn’t gets the general set.
- Use a cluster for anything repeated. Shipping, returns and ingredient questions that belong on more than one page should live in a cluster, so the answer is corrected in one place rather than three.
- Write answers as complete sentences. They’re pulled out and handed to search engines and AI assistants stripped of formatting, so an answer that only makes sense next to the question above it reads badly out of context.
- Leave every row closed. Opening one by default pushes everything below it down the page, and on mobile the second question can end up off-screen. Use Open by default only when the section holds a single question.
- Order by how often the question gets asked, not by topic. Most people read the first two or three rows and stop.
- Keep it to eight questions or fewer per section. A long accordion is a wall of near-identical rows to scan. If you have more, split them across two sections with their own headings.
- Set the heading on each section. The heading is a Title block inside the section, so it is set per page. A cluster’s own title is ignored — the same cluster can appear under a different heading wherever it is reused.