Setup & site building · Guide
How to Add an FAQ Section in WordPress (With or Without a Plugin)

Short answer
To add an FAQ in WordPress without a plugin, insert a Details block for each question, type the question as its summary and the answer inside, so visitors can click to expand it. You can also use plain headings and paragraphs, an SEO plugin's FAQ block, or a page builder's accordion widget. Keep answers short, accurate and visible to search engines.
Key takeaways
- The core Details block creates collapsible questions and answers without a plugin.
- Plain headings and paragraphs are the simplest, most readable FAQ format.
- SEO plugins offer FAQ blocks that can add FAQ structured data automatically.
- Google now shows FAQ rich results only for a narrow set of authoritative sites.
- Write questions your visitors really ask, with short, direct answers.
Why add a questions and answers section?
An FAQ section answers common questions in one place, reduces repeated support emails, helps visitors decide faster and gives search engines and AI tools clear, quotable answers.
Good FAQ sections come from real questions. Look at support emails, sales calls, live chat logs and comments to find what people actually ask.
FAQs work well on product pages, service pages, pricing pages and at the end of long guides. A short FAQ near a buying decision often removes the last doubt.
Avoid stuffing FAQs with marketing claims. Visitors can tell when answers dodge the question, and it damages trust.
A good test is whether a real customer would nod at the answer. If it reads like an advert, rewrite it as a plain, honest reply.
How do you add questions with the Details block?
In the block editor, add a Details block, type the question in the summary line, then add the answer inside the block; visitors click the question to show or hide the answer.
- Open the page in the block editor
- Click the plus button and search for Details
- Type your question in the summary line
- Click inside the block and type the answer
- Repeat for each question
- Group the blocks under an FAQ heading
The WordPress documentation for the Details block shows the block's settings, including whether it opens by default.
The Details block uses the HTML details and summary elements, which browsers support natively. MDN's reference for the details element explains how it works.
Should you use collapsible questions or open text?
Open headings and paragraphs are easiest to read and scan, while collapsible questions save space on long lists; choose open text for short FAQs and collapsible blocks for longer ones.
Collapsed answers hide content, so visitors who skim may miss important information. If an answer matters to most people, consider leaving it open.
For open FAQs, use an H2 for the FAQ section and H3 headings for each question. That structure helps screen readers and search engines understand the page.
Search engines can read collapsed content in the page code, but key information is still better placed in visible text.
How do you add a Q&A block with an SEO plugin?
Most major SEO plugins include an FAQ block for the block editor; add the block, enter each question and answer, and the plugin outputs the FAQ and can add FAQ structured data.
This is convenient if you already use an SEO plugin. You get a consistent layout and structured data without writing code.
Check how the block looks with your theme. Some plugin FAQ blocks have minimal styling, so you may need a little CSS or theme styling to match your design.
Avoid adding the same FAQ twice, once with a plugin block and again with another method, as that duplicates content and structured data.
How do you add a Q&A accordion with a page builder?
Page builders such as Elementor include accordion or toggle widgets; add the widget, enter each question as a title and the answer as content, and style it in the widget settings.
Some builders offer an option to output FAQ structured data from the accordion. Turn it on only if no other plugin adds FAQ schema to the same page.
Our guide on how to use Elementor in WordPress covers adding and styling widgets.
Does question and answer structured data still matter?
FAQ structured data still helps machines understand your questions and answers, but Google limited FAQ rich results in 2023 to well-known, authoritative government and health websites.
Google explained the change in its post on changes to HowTo and FAQ rich results. Most sites no longer see expanded FAQ answers in search results.
That does not make FAQs useless. Clear questions and answers can still appear in featured snippets, AI answers and voice results because the content itself is useful.
If you do add schema, follow Google's FAQPage structured data guidelines, and only mark up questions and answers visible on the page. Our guide on adding FAQ schema in WordPress shows the methods.
How do you write good questions and answers?
Use the words customers use, start each answer with a direct one-sentence reply, add one or two supporting details, and keep each answer under about 80 words.
Write questions as complete questions, such as How long does delivery take, rather than single words like Delivery. Full questions match how people search and ask AI tools.
Put the most common questions first. Visitors rarely read to the end of a long list, so the order matters as much as the wording.
Link to a full guide when an answer needs more detail. The FAQ should point people in the right direction, not replace a whole page.
How do you find the right questions to answer?
Collect questions from support emails, sales calls, chat logs, reviews and search tools, then pick the ones that come up most often or block people from buying.
Search Console can show queries that already bring visitors to the page. Questions in those queries are strong candidates, because people are actively searching for them.
The People also ask boxes in search results and the questions people type into AI assistants are useful too. Rewrite them in your own words and answer them honestly for your situation.
Review the list every few months. New products, policy changes and seasonal questions mean the best questions shift over time.
How many questions should the section have?
Most pages need four to eight focused questions; a dedicated help page can have more, organised into clear categories with headings.
A long, unsorted list is hard to use. If you have more than ten questions, group them by topic, such as Orders, Delivery and Returns.
On a dedicated FAQ page, add a short table of contents or jump links at the top so visitors can reach the right section quickly.
How do you make question accordions accessible?
Use real buttons or the native details element, make sure questions can be opened with a keyboard, keep a visible focus outline and avoid hiding essential information.
The W3C's accordion pattern describes how accessible accordions should behave with keyboards and screen readers.
The core Details block is accessible by default because browsers handle the behaviour. Custom accordion scripts in themes or plugins vary in quality, so test them with a keyboard.
Where should the questions go on a page?
Place FAQs near the end of a page, after the main content and before the final call to action, or next to the part of the page they relate to, such as pricing.
On product pages, an FAQ under the description answers questions about sizing, delivery or compatibility right when shoppers need it.
On long guides, a short FAQ at the end catches the related questions readers still have after the main sections.
How do you keep answers up to date?
Review your questions whenever prices, policies, products or processes change, date-stamp important answers where helpful, and remove questions nobody asks any more.
Outdated answers do more harm than missing ones, because visitors trust what they read on your own site. A wrong delivery time or old price creates support tickets and erodes trust.
Assign an owner for each page's questions, such as the support lead for delivery and returns. Clear ownership means updates actually happen when something changes.
How do you reuse the same questions on several pages?
Save the FAQ as a synced pattern, then insert it on each page; editing the pattern once updates every page that uses it.
This suits shared questions such as delivery times or refund policies. Our guide on creating synced patterns explains how to set them up.
Be careful with structured data on repeated FAQs. The same questions marked up on many pages add little value and can look like duplicate content.
Frequently asked questions
Can I add an FAQ in WordPress without a plugin?
Yes. Use the core Details block for collapsible questions, or headings and paragraphs for an open FAQ. Both work in the block editor without installing anything.
Does Google still show FAQ rich results?
Only for a small set of well-known, authoritative government and health sites since 2023. Most sites no longer get expanded FAQ results, but clear answers can still appear in other search features.
Should FAQ answers be collapsed or visible?
Short FAQs read best fully visible. Collapsible questions save space on long lists. If an answer matters to most visitors, consider leaving it open so nobody misses it.
How long should FAQ answers be?
Aim for a direct one-sentence answer followed by a short detail or two, usually under about 80 words. Link to a full guide when the topic needs a longer explanation.
Can I use the same FAQ on multiple pages?
Yes. Save it as a synced pattern so one edit updates every copy. Avoid adding FAQ structured data to the same questions on many pages.
Sources
- Details block WordPress.org Documentation
- Changes to HowTo and FAQ rich results Google Search Central Blog
- FAQPage structured data Google Search Central
- The details element MDN Web Docs
- Accordion Pattern W3C WAI-ARIA Authoring Practices
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


