How to build an FAQ accordion in Framer that clients can edit
Build a reusable FAQ accordion in Framer with open and closed variants, CMS-driven content and a mobile-friendly layout your client can maintain.

Almost every landing page we build ends with an FAQ. It answers the objections that stop people from buying, it cuts down on repetitive emails, and it gives search engines plain-language answers to real questions. Yet FAQ sections are often the most neglected part of a Framer site: a pile of hard-coded text blocks that only the designer can touch.
In this guide we will build an FAQ accordion in Framer the way we would hand it to a client: one reusable component with open and closed states, content that lives in the CMS, and a layout that holds up on mobile. If you follow along, your client can add, reorder or rewrite questions without opening the canvas or asking you for help.
Decide what the accordion has to do
Before you draw anything, agree on the behaviour. A few decisions shape the whole build:
- One open at a time, or many? Letting several items stay open is simpler to build and easier for people who want to compare answers. A single-open accordion feels tidier but needs a little extra logic.
- Closed by default, or first item open? Opening the first item shows visitors that the rows are interactive.
- How long are the answers? If some answers run to several paragraphs, plan for rich text instead of a single text layer.
- Who edits it? If the client will maintain it, the content belongs in the CMS, not on the canvas.
For most marketing sites, we recommend independent items (each opens on its own), all closed by default, with answers stored as rich text in a CMS collection.
Build the item as a component with two variants
Start with a single FAQ row. Create a frame with a vertical stack and two children: a header row and an answer block. The header row is a horizontal stack with the question text set to fill the width and an icon (a plus sign or chevron) on the right.
Turn the frame into a component and add a second variant. Name them clearly, for example Closed and Open. In the Closed variant, hide the answer block. In the Open variant, show it and rotate the icon 45 degrees for a plus, or 180 degrees for a chevron.
Two settings matter here. First, set the component's height to Fit so it grows with the answer. A fixed height is the most common reason an accordion clips text or leaves a gap. Second, keep the padding and gap identical across both variants so the header does not jump when the item opens.
Add the tap interaction and transition
Select the Closed variant and add an On Tap interaction that changes to Open. Then select Open and add an On Tap that changes back to Closed. Now each row toggles on its own.
For the transition, use a short spring or ease-out of around 0.2 to 0.3 seconds. Anything slower makes the page feel sluggish when someone scans several answers in a row. Avoid fading the whole row; animate the answer appearing and the icon rotating, and leave the question text still so it stays readable.
Test the interaction in preview with your longest answer. If the transition looks fine with two lines but stutters with ten, shorten the duration rather than adding more effects.
Move the content into the CMS
Hard-coded rows are fine for a quick prototype, but they lock the client out. Create a CMS collection called FAQ with these fields:
- Question as a plain text field.
- Answer as a formatted text field, so the client can add links, bold text and lists.
- Order as a number field, used to sort items.
- Page or Topic as an option field, if the same collection feeds FAQs on several pages.
Expose the question and answer as component properties on your FAQ item. Then add a Collection List to the page, point it at the FAQ collection, sort it by Order, and place your component inside. Connect the question property to the Question field and the answer property to the Answer field.
If you use a Topic field, filter the Collection List on each page. A pricing page can show billing questions while the homepage shows general ones, all from a single collection the client edits in one place.
Make it work on mobile and for keyboard users
An accordion that looks good on desktop can still fail on a phone. Check these points at your smallest breakpoint:
- The tap area covers the whole header row, not just the icon. People aim for the question text.
- The header row is at least 44 pixels tall so it is easy to hit with a thumb.
- Long questions wrap onto two lines without pushing the icon off the edge. Set the icon to a fixed size and the text to fill the remaining space.
- Body text in the answer is the same size as body text elsewhere on the site, not a smaller "fine print" style.
Keyboard and screen reader support is harder to control with variants alone. If accessibility is a firm requirement for the project, test with the Tab key in the published site. Where the built-in approach falls short, a well-reviewed accordion component from the Framer Marketplace or a small code component that uses proper button semantics is a safer choice than a custom workaround.
Write questions people actually ask
The best-built accordion is useless if the questions are vague. Pull them from real sources: sales calls, support emails, chat transcripts and objections your client hears before people buy. Phrase each question the way a customer would type it, and answer it in the first sentence before adding detail.
Keep the list short. Six to ten questions per page is usually enough. If you have thirty, group them by topic and split them across pages, or add simple headings above smaller accordions.
Check SEO and structured data
Text inside a collapsed accordion is still part of the page, so search engines can read it. That makes the FAQ a good place to answer specific, searchable questions in plain language.
You may be tempted to add FAQ structured data in the page's custom code. Since 2023, Google shows FAQ rich results only for a narrow set of well-known government and health websites, so for most client sites the markup will not change how the page looks in search. It does no harm, but do not promise clients a visual boost from it. Clear headings and direct answers matter more.
Hand it over properly
Before you ship, write a short note for the client that covers how to add a new question, how the Order field works, and which Topic value puts a question on which page. Add two or three sample entries that show good formatting. Then publish, open the live site on a phone, and tap through every item once.
A well-built FAQ accordion takes less than an hour in Framer, and it pays off for the life of the site. You build the component once, the content lives in the CMS, and the client keeps it current without waiting on you. That is the kind of handoff that leads to repeat work.

