Just published CMS FAQ Accordion, free.

An FAQ whose schema is built from the same CMS rows it renders. Your client adds a question, the schema follows.

The usual way is to paste JSON into the page's Custom Code, where it can't see your CMS. It's a copy. Someone adds four questions, the page shows twelve, the schema still says eight, and nothing warns you.

One thing I want to be straight about: Google removed FAQ rich results in May 2026, so no component can promise you that dropdown any more. The schema is still valid, still read by Bing and by the answer engines, and it's a switch you can turn off.

The trigger is a real button, so the keyboard works without anything extra. And if you don't want a CMS at all, switch Source to List and type the questions in the panel. Same markup either way.

Just published CMS FAQ Accordion, free.

An FAQ whose schema is built from the same CMS rows it renders. Your client adds a question, the schema follows.

The usual way is to paste JSON into the page's Custom Code, where it can't see your CMS. It's a copy. Someone adds four questions, the page shows twelve, the schema still says eight, and nothing warns you.

One thing I want to be straight about: Google removed FAQ rich results in May 2026, so no component can promise you that dropdown any more. The schema is still valid, still read by Bing and by the answer engines, and it's a switch you can turn off.

The trigger is a real button, so the keyboard works without anything extra. And if you don't want a CMS at all, switch Source to List and type the questions in the panel. Same markup either way.