How to Build an FAQ in Joomla 5 and Joomla 6
Learn how to build an accessible FAQ in Joomla 5 and 6, organize questions and answers, choose between Articles and manual content, and add structured data responsibly.
An FAQ can make support, product and service information easier to scan when visitors repeatedly ask the same questions. The useful part is not the accordion effect itself; it is the clear question-and-answer structure.
This guide explains how to build an accessible FAQ in Joomla 5 and Joomla 6, when to use Joomla Articles or manual content, and how to treat structured data without turning every accordion into an FAQ.

Start with real questions
An FAQ should contain genuine questions that visitors are likely to ask.
Good examples:
How long do updates and support last?
Can I use the extension on multiple websites?
Where can I download my purchased extensions?
Avoid turning ordinary section headings into fake questions simply to make the page look like an FAQ.
Keep each answer focused
Most FAQ answers should solve one question directly.
If an answer becomes very long, consider:
- a short FAQ answer;
- a link to a full Guide or Documentation page;
- a separate troubleshooting article.
This keeps the FAQ useful as a scanning interface while preserving detailed information elsewhere.
Choose the content source
There are two common content models for a Joomla FAQ.
Manual FAQ items
Use manual items when the questions belong only to this FAQ block.
This is useful for:
- product FAQs;
- service questions;
- small landing-page FAQs;
- short support collections.
Joomla Articles
Use Joomla Articles when each answer is meaningful content in its own right or should also exist elsewhere on the site.
Articles make sense when:
- answers are long;
- the same content is reused elsewhere;
- you need normal Article URLs;
- the content is maintained as part of a larger knowledge base.
Build an FAQ with ES Content Display
ES Content Display includes a dedicated FAQ layout.
The basic workflow is:
- Create an ES Content Display module.
- Choose Manual Items or Joomla Articles as the source.
- Add or select the question-and-answer content.
- Set Display Layout to FAQ.
- Choose whether one or several answers may stay open.
- Choose the initial open state.
- Publish the module.
Use the Title as the question
Each item needs a meaningful Title that acts as the question.
The visible Intro and/or Body provides the answer.
For example:
Title:
Can I use the extension on multiple websites?
Body:
Yes. ExtensionSpot extensions can be used on multiple websites...
Single-open vs multiple-open FAQs
Single-open
Opening one answer closes the previous answer.
This keeps long FAQs compact and works well when visitors normally read one item at a time.
Multiple-open
Several answers can remain expanded.
This is useful when visitors may compare answers or need to keep several instructions visible.
Choose the initial open state carefully
An FAQ can start with:
- all answers closed; or
- the first answer open.
For long FAQs, all-closed usually produces a cleaner first view. For a short FAQ, opening the first important answer can provide immediate context.
Accessibility is part of the FAQ interaction
A FAQ should not be implemented as plain clickable text with hidden content.
A good implementation needs:
- real button controls;
aria-expandedstate;aria-controlsrelationships;- meaningful heading structure;
- keyboard navigation.
ES Content Display uses these patterns in its FAQ renderer.
Link directly to a specific FAQ question
Deep links are useful when you want to send a visitor directly to one answer.
For example, a support reply can link to the exact FAQ question instead of asking the visitor to scan the entire page.
ES Content Display supports module-scoped Deep Links and opens the matching FAQ item when a valid item hash is loaded.
FAQ structured data: use it for semantics, not as a shortcut
ES Content Display can output optional FAQPage structured data for genuine FAQ content.
The structured data should only describe questions and answers that are visibly present to the visitor.
Do not enable FAQ structured data on ordinary accordion content that is not actually an FAQ.
Important: Google no longer shows FAQ rich results
Google retired FAQ rich results from Search in 2026. That means valid FAQ structured data should not be added with the expectation of receiving the old expanded FAQ search result.
Schema can still describe the meaning of the page for systems that use Schema.org, but the content itself should be useful even without a special Google result.
FAQ vs accordion
The difference is semantic:
- Accordion describes the interaction pattern.
- FAQ describes question-and-answer content.
An FAQ may use an accordion interface, but not every accordion is an FAQ.
For non-question content, see How to Create an Accordion in Joomla.
Use the FAQ as a hub, not a dead end
When an answer needs more detail, link to the relevant Guide, Documentation page or product page.
For example:
FAQ answer
↓
Full Guide
↓
Product / Documentation
This creates a useful path instead of placing all information inside one giant FAQ.
Frequently asked questions
Can I build a Joomla FAQ without separate Articles?
Yes. Manual Items are useful when the questions and answers belong only to the FAQ module.
Can Joomla Articles be used as FAQ items?
Yes. ES Content Display can use Joomla Articles as the source when the answers are maintained as normal Articles.
Should I add FAQ schema to every accordion?
No. Use FAQ structured data only when the visible content is genuinely a collection of questions and answers.
Will FAQ schema produce a Google FAQ rich result?
No. Google discontinued FAQ rich results in 2026, so the schema should not be added for that purpose.
Summary
A good Joomla FAQ starts with real questions, direct answers and accessible interaction. Choose Manual Items for FAQ-specific content or Joomla Articles for reusable long-form content, and use structured data only when it accurately describes what visitors can see.
See the ES Content Display documentation for FAQ Mode, structured data, accessibility and Deep Links.