This integration adds questions and answers as their own content type, with their own categories.
Questions live as separate entries instead of as text inside one page, so you can reuse them, reorder them, and show a different set on different pages.
#One core, a different look in every theme
The integration is split in two.
The shared half is everything structural: the faq content type, the categories, the filter behavior, the accordion markup, the placement options and the structured data. That half is identical wherever the integration runs, so a question you wrote on one site behaves the same way on the next one.
The other half belongs to the theme. Each of our themes ships its own FAQ page template and its own styling for the accordion, the toggle and the filter pills, so the same questions look like part of the theme they run in. A theme can also replace any individual part of the output with its own.
The screenshots in one theme's documentation are not what you will see in another.
The behavior is the same everywhere, and the drawing is not. That is deliberate: an FAQ block that looked identical across twelve themes would look out of place in eleven of them.
#Placing them
There are three ways: the Elementor widget, the editor block, and the shortcode [jkd_faq]. All three render the same listing underneath, so the choice only depends on where you are working.
The shortcode is the route when questions have to go somewhere that has neither blocks nor Elementor.
There is also a dedicated FAQ page template. A page using it renders every question as an accordion, with category filter pills and a closing "still need help" call to action. Both of those are toggles on the page itself, so you can turn either off.
Create the questions
Each one is an entry with the question as its title and the answer as its content.
Sort them into categories
Categories are what let a given page show a subset instead of everything.
Create the FAQ page
Make a page and assign the theme's FAQ page template under Page AttributesTemplate.
Point the theme at that page
Set it as the FAQ page in the theme's settings. Until you do, links that should reach the FAQ page fall back to the site root.
Individual questions do not get their own URL.
A single FAQ entry redirects to the FAQ page and jumps to itself there, because one question on a page of its own is a thin page that competes with the real one. There is no category archive either: the filter pills work in the browser instead of loading a new URL.
#The structured data
The listing emits FAQPage structured data in JSON-LD, so a search engine reads actual questions and answers instead of a collapsed block of text with something hidden inside it.
That helps a search engine understand the page, and it no longer buys what it used to. In August 2023 Google narrowed FAQ rich results to well known authoritative government and health sites, so an ordinary business site will almost certainly not get expandable questions under its search listing, however correct the markup is. The markup is still emitted: it is machine readable, and other search engines and AI assistants read it.
You can confirm what your page emits with the Google Rich Results Test.
If a page holds more than one listing, the first one is the one described in the structured data.
The schema prints once per page, which is correct, so put the listing that represents the page first, before any small side list.
#Keeping a page useful
The short route: create the questions, sort them into categories, put a list on a page, and choose the category that list shows.
One page should not display every question on the site.
Categories exist so the shipping page carries shipping questions. A page with forty unrelated questions helps nobody and dilutes the structured data it emits.
This integration is licensed with the theme, not on its own.
Integrations are premium functionality for customers running a Pro license of one of our themes. They are written against our themes and expect them, and we cannot support or take responsibility for what one does inside somebody else's theme. See how theme integrations work.
#Common questions
Can the same question appear on two pages?
Yes. That is why questions are separate entries: page text would have to be kept in step by hand.
Why does my FAQ look different from the one in the documentation?
Because the appearance belongs to the theme, not to the integration. The questions, the categories, the filtering and the markup are shared; the accordion, the toggle icon and the pills are drawn by whichever theme you are running. Check your own theme's documentation for what it looks like there.
Do I have to use categories?
No, a listing with no category shows every question. That stops working as the list grows, because categories are how each page keeps the questions that belong to it.
Will Google show my FAQ in search results?
Almost certainly not as an expandable rich result, and that has nothing to do with your markup. Google restricted FAQ rich results to well known government and health sites in August 2023. The structured data is still emitted and still correct, and other search engines and AI assistants still read it.
Can I style the accordion?
It follows the theme, which is the point of it. What you control is placement and which category a given list shows. Beyond that you are into custom CSS, which is yours to maintain.
The questions do not show up on the page
Check that the questions are published, and that the category the block or widget is set to actually contains some of them. A listing left on all categories shows every published question.
If the questions exist and the page is still empty, clear any page cache before looking further.
Links to the FAQ page go to the home page instead
The theme has not been told which page is the FAQ page yet. Set it in the theme's settings, and the links resolve.
#Still stuck
Open a support ticket and say what you tried and where it stopped. Your product, your domain, a screenshot and the exact message you saw are usually enough to settle it in one reply.
Last updated
