Best FAQ blocks 2026: 24 verified sections

A FAQ block is a list of questions that open, and its risk is duplicated content. The catalogue counts 24 from 6 registries, measured on 1 November 2026 on /api/blocks/category/faq; the table sorts by files and shows how little one takes.

The trouble is not the accordion, it is the copy

The FAQ section has a quirk no other block has: the same text ends up in the page twice, once visible and once inside the structured data. If the block opens a question with an animation and the structured text differs, the result is not a validation error but a page declaring things it does not show. Rich-result guidelines require the structured content to match what is visible.

The second problem is motion. An accordion that opens one item at a time and animates its height pushes the content below: someone reading the next answer loses their place. The third is semantics: when the question is a div with a click handler, the keyboard never reaches it and a screen reader does not announce that it expands.

What to look at inside the block

• Whether it uses the native details and summary elements, which work without JavaScript and print the answer on paper.
• Whether it opens one item at a time or leaves several answers open, the second often being the more useful choice.
• Whether the question is a button with aria-expanded, or a div with a click handler.
• Whether the answer text sits in the same node the structured data declares, with no hand-rewritten duplicate.
• The publisher licence, uniform here but still worth reading on the record.

The detail that marks a healthy block is the absence of JavaScript. With details and summary the browser handles opening, keyboard and in-page search, and the page stays readable when the script never arrives. An accordion built on a primitive library brings better animation and controlled state, which you only need if a deep link must open a specific item.

The limitation the block cannot see

None of the 24 blocks generates the structured data, and none checks that the visible text matches the declared text. That mismatch is the most common cause of lost rich results, and it almost always starts with an answer updated by hand in one place only. The second limitation is licensing: the block covers the markup, not the answers you put inside.

The rule that stops duplicated answers

If the section is static and lives on a marketing page, use native details and generate the structured data from the same list that draws the page. If users must open an item from a link or search across answers, you need a controlled accordion, and then the text must come from one source. Either way, five or six real questions beat fifteen padded out for volume.

The alternative is a separate help page with an index and search. For a site with many recurring questions it holds up: the page grows, gets updated and takes no room in the sales page. A block inside the page pays off when the questions are few and exist to remove the last doubt before a purchase or a contact.

There is little to improvise about question order. The useful sequence follows objections: price first, then cancellation, then personal data, then support. A block sorting alphabetically looks tidy and helps nobody. When there are more than six questions, an index at the top linking to each item is what makes the section usable, and no block in the table includes one: it has to be added.

curl "https://ui.eneawork.it/api/blocks/category/faq?limit=10"

The sections are in /blocks/category/faq, base accordions in /components/cat/accordion and toggle icons in /icons. For accessibility read the React component checklist and for the manual test testing with axe; the comparison between a ready block and a primitive is in copy-paste or headless.