V1 Accordion FAQ Schema

  • Hello,

    With the advent of AI, the way search works is evolving, as is the way AI systems scan content to deliver results. FAQ schemas are making a comeback because AI systems particularly value them as simple Q&A formats that are easy to parse.

    Unfortunately, the GB teams decided that FAQ schemas weren’t the future, and the V2 accordion doesn’t support FAQ schemas. In my opinion, that was a bad decision. The team has made very few bad decisions in its history, so we can point out one when it happens without calling into question the quality of GB or the teams’ work in general.

    Anyway, the V1 version, which I continue to use for that purpose, does support FAQ schemas, but there’s still a problem.

    Ideally, for a FAQ to be interpreted perfectly, the expected format is :

    <H2> TITLE FAQ </H2>
    <H3> Question 1 </H3>
    <p> Answer </p>
    <H3> Question 2 </H3>
    <p> Answer </p>
    Etc.

    My issue is I don’t see a way in the V1 of the accordion to set the “Question” block to H3.

    Is there a solution?

    Thanks for your help,
    Samuel

    PS: Please reconsider your decision not to implement FAQ schema in the V2 accordion.

  • Hello,

    Of course, you have a point in your case about schema in v2 accordion and it’s on out radar. I would like to redirect you to David’s answer found here.

    Regarding you question about the accordion title, select the Accordion block and set ACCORDION TITLE TYPE to Container.

    Accordion title type to Container

    Thes, select the text below the accordion title block and set the tag accordingly.

    Set accordion title tag

  • Thanks for your reply,

    Your solution is half resolving the issue, but you loss all the button design, you loss the icon, you have to design it all over again, and the icon is not dynamic anymore (open and close icon), it’s really a half working solution, that demands lot’s of manual settings… when you have tons of FAQ blocks it’s quite frustrating.

    Regarding David’s answer, I think there is a misunderstanding, I’m not talking about how Google is using or not FAQ as rich result, it is now well known that Google has downgraded FAQ for classic SERPS. But here I’m talking about how AI robots are using FAQ (and so AI overviews/Google Gemini/potentially Google futur SERP mecanic based on Gemini)

  • Hi Samuel,

    Regarding David’s answer, I think there is a misunderstanding, I’m not talking about how Google is using or not FAQ as rich result, it is now well known that Google has downgraded FAQ for classic SERPS. But here I’m talking about how AI robots are using FAQ (and so AI overviews/Google Gemini/potentially Google futur SERP mecanic based on Gemini)

    Ok, I see!

    But I think, enabling the FAQ schema support outputs a valid JSON-LD block automatically, which is exactly what search engines and AI crawlers read. No heading manipulation needed.

    Regarding the <h3> approach: FAQ schema is JSON-LD and has no dependency on HTML heading tags whatsoever — the two are completely independent. Beyond that, wrapping the accordion’s <button> in an <h3> via a render_block filter creates real problems: the theme’s heading styles (font size, margin) break the accordion layout, and display:contents — the usual workaround — has inconsistent browser support when applied to heading elements. There’s also a risk that the accordion JS, which expects the button as a direct child of the accordion item container, fails to initialise correctly with an extra element in between.

    So the short answer is: enable the schema toggle in the v1 accordion settings, and you’re done. The JSON-LD is output correctly and the accordion works exactly as designed.

    Regarding FAQ schema in the v2 accordion — that’s noted and on our radar.

  • Thanks for your explainations

  • You are welcome!

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.