Raulji FAQ Accordion for Blog & Pages

Yes. FAQs are edited from a dedicated panel in the block editor's document sidebar, so they sit alongside your other post settings rather than on a separate screen. A classic meta box is used automatically if you are still on the classic editor, and the stored data is identical either way, so switching editors later does not strand anything. Because the FAQs are held as post meta rather than inside the content itself, they survive a theme change or a move to a different page builder, and the same entries keep working wherever the post is edited.

Yes. The accordion is fully responsive and tested across common breakpoints, from small phones to wide desktop screens. Long questions wrap rather than overflowing their container, and the tap targets stay large enough to use comfortably on a phone. Styling inherits your theme's typography and colors by default, so it reads as part of your site instead of a bolted-on widget, and any of it can be overridden with your own CSS. Nothing depends on a fixed width, so it behaves correctly inside narrow columns and sidebars as well.

Yes. Valid FAQPage structured data is generated automatically, so your answers are eligible for rich results in Google Search, and schema output can be switched off in Settings if you would rather not use it. The markup is emitted as JSON-LD and only on pages that actually contain FAQs, which avoids the common mistake of declaring FAQ schema on a page with no visible questions. Because the schema is built from the same entries rendered on the page, your structured data and visible content cannot drift apart, which is exactly what Google's guidelines ask for.

No. The plugin loads one small CSS file and one small script, and only on pages where the accordion actually appears, so the rest of your site is untouched. There is no jQuery dependency and no external requests, which means nothing is fetched from a third-party domain and no extra connection is opened while your page loads. The accordion is plain JavaScript with CSS transitions rather than an animation library. In practice it adds a negligible amount to page weight and does not block rendering, so it will not show up in your Core Web Vitals.

Yes. The code follows WordPress Coding Standards, sanitizes all input and escapes all output, and every string is translation ready. Answers support simple inline HTML such as links, bold text and lists, so you are not restricted to plain text. The markup uses predictable class names, which makes restyling it from your theme straightforward without editing the plugin itself. Because the FAQs are stored as post meta, you can also read them directly in a custom template if you want to render the questions somewhere other than their default position on the page.

Yes, completely free under the GPLv2 or later license, with no ads, no premium tier and no locked features. Everything described here is in the version published on WordPress.org, and there is no upsell prompting you to pay for schema output or styling. There is also no trial that expires and no account to create before you can use it. Updates arrive through the normal WordPress plugin update process, the same as any other plugin installed from the directory, so staying current never requires a license key or a subscription.

Yes. The GPL license allows use, modification and redistribution on any number of sites, including client and agency work. There is no per-site limit, no activation step, and nothing that needs transferring when you hand a finished site over to a client. You are also free to modify the code for a particular project, though keeping any customization in your theme rather than in the plugin files means a future update will not overwrite your changes. Agencies commonly install it as part of a standard build, which the license explicitly permits.

Only if you tick the option to delete FAQ data on uninstall in Settings. By default your questions and answers are kept, so deactivating or removing the plugin does not destroy content you spent real time writing. That matters when you are trialling plugins or tracking down a conflict, because you can safely deactivate it and reactivate later with everything still intact. If you do want a genuinely clean removal, enabling that setting before uninstalling also clears the stored post meta, leaving no orphaned rows behind in your database.