Advanced FAQ
Put the answer where the question happens. Advanced FAQ shows the right questions and answers on product pages, category pages and a searchable help centre, so shoppers get unblocked at the moment they would otherwise open a support ticket — and every answer can become a page that search engines index.
Latest version: 1.1.0 — changelog
Who it's for
- Stores whose support inbox fills with the same delivery, returns and product-care questions: each answer is written once and shown on the hub, the product pages and the category pages it applies to.
- Multi-language and multi-store shops: questions, answers and URL keys can be translated per store view, and an FAQ can be switched on or off for one store view only.
- Catalogues too large to curate product by product: rules attach FAQs to every product that matches catalog conditions, including products added later.
- Hyvä and headless storefronts: a native Hyvä companion module, plus REST and GraphQL for PWA front ends.
Why it matters
- Fewer support tickets: shoppers find delivery, returns and product answers themselves, without leaving the page they are on.
- More organic traffic: an answer can have its own page with meta title, meta description and FAQPage structured data that qualifies for rich results.
- Higher conversion: product-page and category-page FAQs answer purchase-blocking questions at the decision point.
- Content gaps made visible: storefront FAQ searches are recorded with their result counts, so you see what customers ask that you have not answered yet.
See it in action
You set a topic with identifier shipping, and on the FAQ "How long does delivery take?" switch on Has dedicated page with URL key how-long-does-delivery-take. You get the page /faq/shipping/how-long-does-delivery-take: breadcrumbs, the full answer, a link back to the topic, and FAQPage JSON-LD in the source.
You set the category Gear > Bags on the FAQ "What is your return window?". You get that question in the Bags category page's FAQ block and in the FAQ tab of every bag, next to the bag's own FAQs.
You set the widget {{widget type="Qoliber\AdvancedFaq\Block\Widget\Faqs" source="topic" topic_id="1" title="Shipping FAQs" limit="5" display_mode="accordion"}} in a CMS page. You get a "Shipping FAQs" accordion with that topic's questions on the page.
What you get
| Feature | Benefit |
|---|---|
| Create and manage FAQs | Write each answer once, translate it per store view, and give it its own indexable page with FAQPage JSON-LD |
| Organize with topics and tags | Group hundreds of answers into the hub's sections and URLs, and label them so search finds them |
| The FAQ hub and search | One self-service help centre at /faq with topic pages, search and a top-menu link, on Luma and Hyvä |
| Show FAQs on product and category pages | Purchase-blocking questions answered in a product tab and a category block, with an item cap and above/below placement |
| Assign FAQs automatically with rules | Catalog conditions, priorities and date windows attach the right FAQs to new products without manual work |
| Publish guides | Longer policies and care instructions as their own pages under /faq/, listed on the hub |
| Embed FAQs in CMS content | Reuse curated FAQ lists on any CMS page or block with the Qoliber FAQ Block widget, by topic, hand-picked or featured |
| Find content gaps with search insights | See what shoppers search for and which phrases return nothing, without storing emails or order numbers |
| Draft answers with AI | A first draft from Anthropic Claude, OpenAI GPT, Google Gemini or xAI Grok, reviewed by you before it is saved |
| Keep FAQ search fast with OpenSearch | Prefix and tag matching with a self-healing reindex queue, so search stays fast as the FAQ grows |
| REST and GraphQL API | Store-scoped reads for headless storefronts and token-protected writes for your own tools (API reference) |
Competing solutions
The right-hand column describes common practice on the extension market, not any particular vendor.
| Qoliber | Typical marketplace extension | |
|---|---|---|
| Packagist installation | Installed and updated with Composer from our private Packagist (qoliber.repo.packagist.com) | Varies by vendor |
| Slack access to the development team | A shared Slack channel with the developers who build and maintain the module | Usually ticket-based |
| Unit tests | 173 PHPUnit unit tests (39 classes) in the repository | Not typically published |
| Integration tests | 93 Magento integration tests (31 classes), run before every release | Not typically published |
| E2E Playwright tests | 45 Playwright end-to-end tests on Luma and Hyvä (27 spec files), run before every release | Not typically published |
| Documentation | Full docs portal: install, configuration, usage and API reference | Varies by vendor |
| Hyvä support | A dedicated Hyvä companion module with native Tailwind/Alpine templates | Varies by vendor |
| PHP / Magento range | PHP 8.1 to 8.5; Magento Open Source 2.4.x and Mage-OS | Varies by vendor |
Why merchants pick Advanced FAQ
- Hyvä-native. A dedicated Hyvä companion module renders the hub, topic pages, answer pages and product/category FAQs with Tailwind and Alpine, without CSP violations.
- API-first. Anonymous, store-scoped REST and GraphQL reads for headless storefronts, plus token-protected REST endpoints to create, update and delete FAQs from your own tools — see the API reference.
- Runs in your store. Content, search and reporting need no external service. Only the optional AI drafting calls out, to the provider and API key you choose.
Good to know
- The suite is modular: one core package plus seven optional packages. Rules, OpenSearch search, AI drafting, Hyvä, REST and GraphQL each need their own package — see the module reference.
- AI drafting needs your own API key for Anthropic, OpenAI, Google or xAI; the provider bills you for usage.
- OpenSearch FAQ search reuses the store's OpenSearch connection; without the Search package, the built-in database search answers.
- GraphQL is read-only. Writes go through REST.
Supported versions: PHP ~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0; Magento Open Source 2.4.x and Mage-OS (magento/framework ^103.0, magento/module-catalog ^104.0, magento/module-cms ^104.0).