Building FAQ Pages That Rank: Using the Accordion Block With Schema.org

An FAQ at the bottom of a landing page does three jobs at once: it answers real user questions, it’s a natural home for long-tail keywords, and — if you emit the right structured data — it earns rich snippets in Google that push your listing down the page with expandable Q&A pairs.

DesignSetGo’s Accordion block is purpose-built for this. Here’s how to make it actually rank.

The basic setup

The Accordion block holds Accordion Item children. Each item has a title (the question) and inner blocks (the answer). Two patterns that work:

• Single-open accordion: clicking an item closes the others. Good for deep FAQs where cognitive load matters.
• Multi-open accordion: items open independently. Good when users compare answers side-by-side.

Pick one behavior per page. Mixing is disorienting.

Content rules that move the needle

• Ask real questions. “What is DesignSetGo?” is a content-farm question. “Does DesignSetGo work with Twenty Twenty-Five?” is what users actually type into Google.
• Answer in the first 2-3 sentences. Both users and Google’s snippet algorithm prefer front-loaded answers. Elaborate after.
• Aim for 40-80 words per answer. Short enough to skim, long enough to signal depth.
• 5-10 questions per page. Fewer feels thin; more feels padded. If you have 20 real questions, split into topic-specific FAQ pages.
• Use natural language in questions. Include the full phrasing, not just keywords. Voice search rewards this.

The structured data piece

Google used to show FAQ rich snippets generously. They tightened eligibility in 2023 (now mostly reserved for authoritative sites and well-known brands), but the schema still helps: it clarifies content structure for search, it powers voice answers on Google Assistant, and it’s read by AI search tools like Perplexity and ChatGPT Search.

You have two options for emitting FAQPage schema on DesignSetGo accordions:

Option 1: let Yoast or RankMath handle it

If you’re already running Yoast SEO or RankMath, they both have FAQ block schema generators. The tradeoff: they require you to use their FAQ block, not the Accordion block. You lose the accordion UX.

Option 2: emit schema yourself

Add a Custom HTML block to the page containing the FAQ, with a JSON-LD script:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does DesignSetGo work with Twenty Twenty-Five?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes — DesignSetGo is built for FSE themes and tested against Twenty Twenty-Five. All blocks respect theme.json typography, color, and spacing presets."
      }
    },
    {
      "@type": "Question",
      "name": "Can I use DesignSetGo alongside GenerateBlocks?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. DesignSetGo namespaces its blocks under designsetgo/ and scopes its CSS, so there are no conflicts with other block plugins."
      }
    }
  ]
}
</script>

Match the name and text fields exactly to what’s visible on the page. Google cross-checks them, and a mismatch disqualifies the page from rich snippets.

Bonus: let an LLM keep it in sync

The hardest part of FAQ schema is keeping the JSON-LD in sync with the visible accordion as you edit. If you’ve wired up the DesignSetGo Abilities API, you can hand this to your LLM:

“Read the accordion on post {ID}, then regenerate the FAQPage JSON-LD in the custom HTML block immediately after it. Match every question and answer verbatim.”

One prompt, zero drift. Add it to your pre-publish checklist.

What to measure

Give it two weeks, then check Search Console for the FAQ pages. Look for:

• Impressions on the exact question phrasings (a sign your schema is being parsed).
• Long-tail queries that don’t appear in your H2s (a sign users are finding answers via the accordion content).
• Average position on question-style queries (“does X work with Y”, “how do I X”).

Well-structured FAQ content is one of the last remaining SEO wins that’s both cheap to implement and still meaningful for discovery. An Accordion block, tight answers, matching schema — that’s the whole playbook.