FAQ Professional
Description
Highlights
- Flexible assignment: Assign FAQ groups by tag to products, categories, variants, landing pages or shipping methods — categories and products can also be assigned directly, without a tag
- Customised display: Show FAQs as a tab on product pages, as a CMS block in shopping experiences, or in the shop search
- Analytics in the administration: Views per question and group, trend over recent days, most-clicked questions — filterable by sales channel and language
- Customer feedback: Visitors indicate whether an answer helped; the evaluation shows which answers need improving
- SEO optimisation: Machine-readable schema.org FAQ markup — readable by search engines and AI assistants, complemented by an llms.txt endpoint
Features
- FAQ group management: Create your own groups, assign questions and prioritise the order in which they are displayed
- Product detail page integration: Display FAQs as a tab or alternatively as a CMS block in individual experience worlds
- Variant and shipping method support: Assign FAQ groups to specific product variants or shipping methods
- Detailed configuration: Freely choose the position of the FAQ tab or deactivate individual tabs to use CMS blocks instead
- Content maintenance in the admin area: Create questions and answers with formatted text, assign groups and manage them centrally
- Direct assignment to a category or product: Assign FAQ groups to a single category page or product in addition to tags, without subcategories inheriting the assignment
- Release for all sales channels: Enable FAQ groups and questions for every sales channel with a single switch instead of selecting them one by one — channels added later are covered automatically
- Shop search integration: Show matching questions in the search suggestions and on the search results page, position freely selectable; uses Elasticsearch or OpenSearch where available
- Analytics dashboard: Views, trends, rankings and a comparison between groups — with filters for sales channel and language
- Customer feedback: "Was this answer helpful?" below every question, evaluated per question and over time
- Multilingual with fallback: If a translation is missing, the default language can be shown instead of a gap; the administration list shows the translation status
- Accessibility: The FAQ accordion can be operated with keyboard and screen reader and meets WCAG 2.2 levels A and AA
- Answer editor: Insert images, YouTube and Vimeo videos, quotes and callout boxes; quick commands via the slash key
- Link to a single question: Readable anchors instead of ID chains, plus a copy button that puts the link to one answer on the clipboard
- Click log retention: 12 months, 24 months or indefinitely, with a daily cleanup task
About the Extension
Shopware 6 comes with no module of its own for frequently asked questions. Answers therefore end up in a product’s description text or in a shopping experience built specifically for them. Whatever finds no place there is answered by support, one enquiry at a time. FAQ Professional manages questions and answers centrally and shows them at the point where the question arises. In the administration you see which of them get read.
Assignment: by tag, category or product
You group your questions into FAQ groups. There are two routes for assigning these groups to the pages of your shop. Via tags you reach products, categories, product variants, landing pages and shipping methods; a tag applies to everything carrying it. In addition, a group can be assigned directly to a single category page or a single product, with no tag involved. Subcategories do not inherit this direct assignment – to reach a whole category branch, keep using a tag.
A dedicated switch releases a group or a single question for all sales channels, including channels you create later. Switch it off again and your previous selection applies unchanged.
Display in the shop
Where an FAQ group appears is set on the group itself: as a tab on the product page, as a CMS block in a shopping experience, or as an FAQ element in a single column, in the right half of a two-column layout for instance. Category pages show assigned groups even without a CMS block; an existing block takes precedence. In the final step of the checkout, questions can be tied to the selected shipping method, current delivery notices for example.
Where the same question sits in two places on one page, it is still output only once, visibly as well as in the markup for search engines. In the shopping experience editor, a preview based on a sample product or category shows which groups and questions will actually appear.
FAQs in the shop search
If you wish, matching questions appear in the search suggestions and on the search results page. The position is freely selectable: above, below or beside the products. Anyone who does not want the suggestions can switch them off. Where you maintain a dedicated FAQ page, the hits link there and open the matching question automatically.
Where Elasticsearch or OpenSearch is in use, the plugin uses the existing instance. Without one, the search runs over the database as before.
Figures instead of guesswork
A dedicated dashboard in the administration shows which questions are actually being read: four key figures with a trend over recent days, the most-clicked questions, a comparison between the groups and a list of the questions nobody has opened since recording began. A further evaluation breaks the views down by language and domain. All of it can be filtered by sales channel and language.
The list of unread questions is the most revealing of these. A question nobody opens is either hard to find, awkwardly worded or simply not being asked. Repeated views of the same question by the same visitor count only once within a configurable cooldown.
Customers rate the answers
Below every answer sits the question of whether it helped; one click on Yes or No is enough. The evaluation shows satisfaction per question and over time, and names the answers most often marked as unhelpful. In the question list the figure appears as a column of its own, colour-coded.
Composing answers
Answers and group descriptions are maintained in an editor that goes beyond simple formatting: images, videos from YouTube and Vimeo, quotes, callout boxes and tables. A slash opens a command menu that narrows with every further character.
The question itself is a plain text field. A question needs no formatting, and a link in that position would make the expand control unusable for screen readers.
Links to individual questions
Every question can be linked individually, and the address is readable: instead of a chain of identifiers it carries the group name and the question in short form. A copy button behind the question puts the link on the clipboard – useful for sending a customer the one relevant answer by email instead of pointing them at the FAQ page.
Every question additionally keeps an unchanging anchor. Links you sent out months ago therefore keep working.
Machine-readable for search engines and AI assistants
Questions and answers are marked up as schema.org FAQPage, exactly once per page and limited to what is actually visible on that page. Added to this are two endpoints following the llmstxt.org standard: /llms.txt holds an index carrying one section per group and linking every question directly to its place, while /llms-full.txt holds the full collection with all answers.
For context: Google has not shown FAQ rich results in its search results since May 2026. The markup nevertheless remains the basis for crawlers and AI-based services reading your answers correctly. Whether any particular service picks them up is that service’s decision.
Multilingual
Questions and answers are maintained per language. If a translation is missing, the plugin can show the default language instead of omitting the question. The administration list marks which translations are still missing, per language.
Accessibility
The FAQ accordion can be operated with the keyboard and with a screen reader. The keyboard focus is visible, and links inside a question are rendered as text so that the expand control stays operable. Both points concern levels A and AA of WCAG 2.2. The statement refers to the FAQ accordion; whether your shop as a whole meets the requirements depends on the theme, the content and the other extensions.
Adjusting the appearance
Icon type and icon position, separators and their colour, bold or regular group headings, and the colour and duration of the highlight when a question is opened from a direct link can all be set. The settings apply globally or per sales channel.
Setup
Installation and updates run through Extensions > My extensions in the Shopware administration. After that you create an FAQ group, assign it a sales channel and a target, and enter the questions. The plugin settings all come with defaults; to get started you need change nothing there. Individual appearance settings take effect through the theme and become visible after the next compilation.
Existing questions and groups can be imported from CSV, provided the file matches the format of the export generated beforehand. How long the click log is kept is up to you: twelve months, twenty-four months or indefinitely. The setting is on indefinitely out of the box; a daily task then prunes on its own.
On uninstalling, you decide what happens to your data. With the option to keep user data, all tables remain in place; without it, tables, scheduled tasks and all plugin settings are removed.
Documentation: FAQ Professional
Shopware 6 comes with no module of its own for frequently asked questions. Answers therefore end up in a product’s description text or in a shopping experience built specifically for them. Whatever finds no place there is answered by support, one enquiry at a time. FAQ Professional manages questions and answers centrally and shows them at the point where the question arises. In the administration you see which of them get read.
Assignment: by tag, category or product
You group your questions into FAQ groups. There are two routes for assigning these groups to the pages of your shop. Via tags you reach products, categories, product variants, landing pages and shipping methods; a tag applies to everything carrying it. In addition, a group can be assigned directly to a single category page or a single product, with no tag involved. Subcategories do not inherit this direct assignment – to reach a whole category branch, keep using a tag.
A dedicated switch releases a group or a single question for all sales channels, including channels you create later. Switch it off again and your previous selection applies unchanged.
Display in the shop
Where an FAQ group appears is set on the group itself: as a tab on the product page, as a CMS block in a shopping experience, or as an FAQ element in a single column, in the right half of a two-column layout for instance. Category pages show assigned groups even without a CMS block; an existing block takes precedence. In the final step of the checkout, questions can be tied to the selected shipping method, current delivery notices for example.
Where the same question sits in two places on one page, it is still output only once, visibly as well as in the markup for search engines. In the shopping experience editor, a preview based on a sample product or category shows which groups and questions will actually appear.
FAQs in the shop search
If you wish, matching questions appear in the search suggestions and on the search results page. The position is freely selectable: above, below or beside the products. Anyone who does not want the suggestions can switch them off. Where you maintain a dedicated FAQ page, the hits link there and open the matching question automatically.
Where Elasticsearch or OpenSearch is in use, the plugin uses the existing instance. Without one, the search runs over the database as before.
Figures instead of guesswork
A dedicated dashboard in the administration shows which questions are actually being read: four key figures with a trend over recent days, the most-clicked questions, a comparison between the groups and a list of the questions nobody has opened since recording began. A further evaluation breaks the views down by language and domain. All of it can be filtered by sales channel and language.
The list of unread questions is the most revealing of these. A question nobody opens is either hard to find, awkwardly worded or simply not being asked. Repeated views of the same question by the same visitor count only once within a configurable cooldown.
Customers rate the answers
Below every answer sits the question of whether it helped; one click on Yes or No is enough. The evaluation shows satisfaction per question and over time, and names the answers most often marked as unhelpful. In the question list the figure appears as a column of its own, colour-coded.
Composing answers
Answers and group descriptions are maintained in an editor that goes beyond simple formatting: images, videos from YouTube and Vimeo, quotes, callout boxes and tables. A slash opens a command menu that narrows with every further character.
The question itself is a plain text field. A question needs no formatting, and a link in that position would make the expand control unusable for screen readers.
Links to individual questions
Every question can be linked individually, and the address is readable: instead of a chain of identifiers it carries the group name and the question in short form. A copy button behind the question puts the link on the clipboard – useful for sending a customer the one relevant answer by email instead of pointing them at the FAQ page.
Every question additionally keeps an unchanging anchor. Links you sent out months ago therefore keep working.
Machine-readable for search engines and AI assistants
Questions and answers are marked up as schema.org FAQPage, exactly once per page and limited to what is actually visible on that page. Added to this are two endpoints following the llmstxt.org standard: /llms.txt holds an index carrying one section per group and linking every question directly to its place, while /llms-full.txt holds the full collection with all answers.
For context: Google has not shown FAQ rich results in its search results since May 2026. The markup nevertheless remains the basis for crawlers and AI-based services reading your answers correctly. Whether any particular service picks them up is that service’s decision.
Multilingual
Questions and answers are maintained per language. If a translation is missing, the plugin can show the default language instead of omitting the question. The administration list marks which translations are still missing, per language.
Accessibility
The FAQ accordion can be operated with the keyboard and with a screen reader. The keyboard focus is visible, and links inside a question are rendered as text so that the expand control stays operable. Both points concern levels A and AA of WCAG 2.2. The statement refers to the FAQ accordion; whether your shop as a whole meets the requirements depends on the theme, the content and the other extensions.
Adjusting the appearance
Icon type and icon position, separators and their colour, bold or regular group headings, and the colour and duration of the highlight when a question is opened from a direct link can all be set. The settings apply globally or per sales channel.
Setup
Installation and updates run through Extensions > My extensions in the Shopware administration. After that you create an FAQ group, assign it a sales channel and a target, and enter the questions. The plugin settings all come with defaults; to get started you need change nothing there. Individual appearance settings take effect through the theme and become visible after the next compilation.
Existing questions and groups can be imported from CSV, provided the file matches the format of the export generated beforehand. How long the click log is kept is up to you: twelve months, twenty-four months or indefinitely. The setting is on indefinitely out of the box; a daily task then prunes on its own.
On uninstalling, you decide what happens to your data. With the option to keep user data, all tables remain in place; without it, tables, scheduled tasks and all plugin settings are removed.
Documentation: FAQ Professional
Details
- Available: English, German
- Latest update: 17 November 2026
- Publication date: 13 November 2025
- Version: 6.7.10
- Category: Special features
Resources
Reviews (1)
Average rating of 5 out of 5 stars
Flexibel einstellbar und sehr empfehlenswert
Average rating of 5 out of 5 stars
About the Extension Partner
SYNERGY NETWORKS GmbH
Partner Status
-
Shopware
Bronze Partner -
Shopware
Extension Partner
Details
-
Ø-Rating:
4.8
Average rating of 4.8 out of 5 stars
- Partner since: 2014
- Extensions: 23
- Certifications: 18
Support
- Based in: Germany
- Speaks: German, English
- Response time: Very quickly
Installation or updates are carried out via the extensions in Shopware Administration.
Install plugin
- Extensions → My Extensions open
- Install or update plugin
- Activate plugin (if not already done)
- Clear cache completely and reload administration page.
Detailed documentation: FAQ Professional
Note for shops running Elasticsearch or OpenSearch: After updating to 6.7.6, run bin/console es:index once. Without this step the "All sales channels" switch has no effect in the shop search, while it already applies in the FAQ accordion. Shops without Elasticsearch are unaffected.
6.7.10 6.7.0.0 - 6.7.16.0
New
- The CMS element “FAQs” has a “Groups” field. If groups are chosen there, the element shows exactly these, also on pages without a category, product or landing page. Without a choice, the groups that match the page apply. The preview in the Shopping Experiences shows the chosen groups with their questions.
- The CMS element “FAQs” can show its first question open (setting “Show the first question open”, off by default).
- The question “Was this answer helpful?” can be switched off per sales channel. When switched off, the block and its request on page load are left out.
- Every question in the accordion is a heading, one level below the group name. Screen readers can jump from question to question.
- Answers and group descriptions take videos from the media library.
- The group edit page shows the number of questions, and the question list can be paged (10, 25, 50 or 100 per page).
- With Advanced Search, FAQ hits appear in the search suggestions as a section of their own above the product hits.
Improved
- Compatibility with Shopware 6.7.0 to 6.7.16.
- Search suggestions, the search index and structured data work with plain text, and paragraphs and list items stay apart. Rebuild the search index after the update.
- The copy button in the search results copies the link to the question on the FAQ page; without a configured FAQ page it is left out there.
- The display position “Product tab, or CMS block if present” also takes the CMS element “FAQs” into account, regardless of the order on the page.
- Better accessibility: questions, answers, group names and group descriptions from the default language carry a lang attribute, also in the search suggestions, whose entries no longer repeat their text as a tooltip. Copying and voting are announced, copy buttons name the question, the labels have more contrast, and the administration menu is a single, clearly labelled button.
- Questions without text in the sales channel's language or its parent language follow the setting “Fall back to default language for untranslated FAQs” on pages, in the CMS element, in the structured data and in search: they stay hidden, or appear with the default language text and its language attribute. The preview in the Shopping Experiences shows the FAQs in the language of the selected sales channel.
- Several accordions on one page and the copy in the offcanvas work independently of each other.
- Large FAQ pages load the visitor's own vote state in blocks.
- The structured data follows what the layout shows, on product pages as well as with the CMS element “FAQs” and its group selection.
- Video placeholders in group descriptions can be played, and the spacing between groups is output.
- A theme can set the colour of the questions through --syn-faq-header-color.
- The storefront scripts of the plugin load only when a page contains FAQ.
- More precise statistics: a filtered reset subtracts only the deleted views, “Never opened” with a channel filter includes questions for all sales channels, and the group comparison counts only active questions.
- More privacy: votes are kept for two years so that the previous-year comparison is complete. The retention period of the click log applies per sales channel. The hash in the click log is removed once the cooldown has passed, and the plugin does not store a session identifier.
- More security for transfers to another shop: the connection code is bound to the target address and access, and the target address is checked before every operation, also when a proxy is configured on the server. Existing codes are converted during the update.
- The administration follows the rights of the role. Without edit, create or delete rights the matching buttons do not appear, and the forms are read-only.
- Unsaved input is kept when assignments are applied on the group edit page, and the form asks before a language switch.
- The administration uses the Meteor components that are also available on Shopware 6.8, shows numbers in the format of the chosen language and follows the Shopware style in type, colour and shadows.
- Questions and answers may be longer: questions and group names up to 65,535 characters, answers up to 16 MB.
- The title of the CMS block “FAQs” is output like a text element: mapped fields and placeholders are resolved.
- More precise import: if a file has several columns of the same language, the column naming the target shop's language by name applies; the dry run reports the others. The dry run detects changes also in columns whose language has another name in the target shop, and the file choice is locked while it runs.
- The confirmation for resetting the statistics names the chosen selection.
- Images pasted in the editor are named faq-image-… in the media library.
- The llms.txt tells apart “no FAQ page configured” from “not published in this language”.
- Stability and performance improvements.
6.7.9 6.7.0.0 - 6.7.16.0
New
- With SynAgentReady installed, the FAQ appears as a section of its site-wide /llms.txt and /llms-full.txt. SynAgentReady then serves both files for the whole shop; the FAQ plugin contributes the same content as its own files, without the file header and, in the full text, one level lower under ## FAQ. Without SynAgentReady the plugin keeps serving both files itself, unchanged.
6.7.8 6.7.0.0 - 6.7.16.0
New
- Every page of the FAQ module has a tab bar at the top with Dashboard, Groups and Questions & Answers including their counts. Next to it, a menu behind the cog icon collects Export all, Import, Transfer to … and the plugin configuration.
- The start page of the module is a full-width statistics dashboard. At the top you choose the period (7 to 365 days), the comparison (previous period, previous year or none), sales channel and language. Below are four key figures with a trend and their change against the comparison – views in period, helpful, votes and FAQs opened, which shows how many of the active FAQs were read at all in the period, together with total views –, a daily chart for views or votes with the comparison period in the background, the rating ring, the most read and the worst rated questions, clicks per language, the group comparison and the questions never opened in the period. Rankings and lists apply to the chosen period.
- When editing a question or group, a slim row shows its key figures: total views, last 30 days and last 7 days each with the change against the period before, helpful rate with the number of votes, active FAQs for groups, and the last activity.
- Translations and sales channels appear in the question and group lists as a compact bar with counters for present, inherited and missing. Inherited means a language has no text of its own but inherits one from its parent language (for example English (US) from English) – previously it counted as missing. Hovering shows every language with its full code and name (for example “EN-GB · English”), ordered by inheritance, or every sales channel, each with its status.
- FAQs and groups can be exported, imported and transferred to another shop. The export produces a ZIP with groups.csv, faqs.csv and every image used in answers and group descriptions; Excel opens the CSV files directly (one row per question, one column per language), and a file saved by German Excel as “CSV (Trennzeichen-getrennt)” (Windows-1252) is read correctly as well. You can import the whole package or a single, hand-edited CSV; an empty cell in a column that is present clears the value, and nothing is ever deleted. In the import dialog the file is dragged onto a drop area or chosen with a click. Sales channels, tags, categories, products and languages are matched in the target shop by name, category path, product number and locale, so transfers between stage and live work even though their IDs differ. Before every import a dry run shows what would be created, changed or skipped, plus row errors (those rows are not applied), unresolvable references (skipped) and notes; nothing is written until you confirm, and then in one go. Statistics are not transferred. A target shop releases itself with one click under “Release this shop as a target” in the plugin settings and creates a connection code (the access created for it may only create and change FAQs and FAQ groups and create images; the code is shown only once, and the release can be withdrawn). The sending shop enters the code in one of up to three target fields and checks it with “Test connection”. “Transfer to …” in the cog menu at the top of every FAQ page then sends the FAQs straight there, which requires FAQ edit rights; “Export all” and “Import” are there as well. For scripts and deployments there are the commands syn:faq:export and syn:faq:import.
- The FAQ labels in the storefront are available in French, Italian, Spanish, Dutch and Danish – the tab, the search headings, the question “Was this answer helpful?” with its answers, and the button for copying the link. Previously they appeared in English in these languages.
- The “Groups” filter in the “Questions & Answers” list is a selection list. You choose one or more existing groups and see exactly the questions assigned to them. Previously it was a free-text field that also matched groups with a similar name.
- Every column of the “Questions & Answers” list can be filtered. New are views and helpfulness (each from–to) and “Without own translation in” with a choice of language. The helpfulness column can also be sorted.
- The group list has new filters: position, “Without own translation in”, number of FAQs, views, helpfulness, categories and products. FAQs, views and helpfulness filter by the group totals as shown in the list; “FAQs up to 0” finds the groups without questions. The “Tags” filter is a selection list instead of a free-text field and therefore matches exactly the selected tags.
Fixed
- FAQs appear in an inheriting language with the text of its parent language – on the product page, in the structured data and in the search. This affects languages that inherit from another one (for example German (Austria) from German, or English (US) from English) when no FAQ translation of their own is maintained. Previously the FAQs stayed hidden there, although the parent language was translated.
- The setting “Fall back to default language for untranslated FAQs” only applies once the parent language has no text either. Previously it went straight to the default language, so a sales channel in English (US), for example, showed German questions although an English version existed.
- The plus and minus signs for expanding and collapsing take on the text colour of the question. Previously they were always black, so the minus of an open question was hard to make out in themes with a dark background.
- The number in the counters next to “Yes” and “No” is centred. Previously its position depended on the line height and the browser's rounding, and depending on the zoom level it sat slightly too high.
- The plugin's administration is readable in the dark colour scheme – the text editor for answers and group descriptions including its label, statistics tiles, bars, dividers, hints and markers take on the colours of the selected scheme. Previously several of them were fixed to light colours and hard to make out on a dark background.
- The table “Clicks by Language & Domain” keeps its columns. Long domains are shortened and shown in full in the tooltip. Previously a long name pushed the bars and numbers out of line.
- Uninstalling with "delete data" no longer aborts. The mapping tables between groups and categories/products were missing from the list of tables to drop; their foreign keys then blocked dropping the groups after some tables were already gone.
- Views and votes can no longer be inflated. Only active FAQs visible in the current sales channel are counted. Repeated views and votes are detected server-side regardless of cookie and user agent (via a hash; the IP address is not stored), and too many requests in a short time are rejected. As views influence the search order, this previously also allowed shifting search results.
- Editors without admin rights can maintain FAQs. The plugin now registers its permissions in role management (Catalogues → FAQ: view, edit, create, delete). Statistics require read permission for FAQs, resetting them requires edit permission.
- Changes to FAQs and groups show up in the storefront immediately. Previously pages from the HTTP cache kept the old state until the cache expired.
- "Already voted" is no longer baked into the cached page. The page now asks on load whether the visitor has voted. Previously one visitor's state could end up in the HTTP cache so that others could no longer vote.
- Search and search suggestions no longer show questions from inactive groups or groups of other sales channels. Questions without a group appear as before.
- Search keeps the relevance order. Hits from OpenSearch are no longer re-sorted by views; without OpenSearch a match in the question weighs more than one in the answer, and views only break ties.
- Search suggestions load faster. Each keystroke now loads only the matched questions instead of all FAQs of the landing page.
- The search suggestion no longer ships its own fixed light stylesheet and shows the "FAQ" and "Product hits" headings only when there are FAQ hits and the setting does not hide them. Colours follow the theme.
- The FAQ accordion styling now applies to the FAQ only. Previously some rules also changed other accordions in the shop.
- At checkout the FAQ of a shipping method sits below its radio button instead of inside its label. Clicking into an answer no longer changes the shipping method, and screen readers no longer read the whole FAQ when the shipping method gets focus.
- Automatically opened questions are also counted in sales channels with a path (such as /en).
- The headings on the search page follow the correct order (h1, h2, h3), as screen readers and audit tools expect.
- Deprecated calls replaced or marked, so the Shopware Store check against the lowest and the highest supported Shopware version passes without errors.
- Tags and sales channels with FAQ assignments can be deleted again. A migration switches the foreign keys of the mapping tables to cascading deletes; previously the deletion failed with a database error.
- Uninstalling also removes the integration and role of a transfer share. Previously both remained in the target shop.
- An import that deletes data checks the delete privilege up front instead of failing halfway through writing.
- The FAQ search follows the shop's minimum search length (counted in characters, umlauts included). Reloading and further pages of the search result no longer search FAQs again.
- Answers and attributes in the storefront are sanitized or escaped. Images, tables, links and video placeholders are kept.
- The video placeholder labels are translated.
- The "beside the products" layout of the search suggestion works without JavaScript and stays a valid list for screen readers.
- The search card sits in the right place below the search page headline, anchors honour the "group name in anchor" setting per sales channel, and an accordion without groups no longer renders an empty frame.
- Error responses of the mapping API no longer expose internal details.
- Image captions and highlights survive saving. Shopware's sanitizer removed figure, figcaption and mark from answers and group descriptions, so a captioned image lost its alignment and size and the caption ended up as loose text after it. A caption that was already lost has to be entered again in the editor.
Changed
- The FAQ associations on tags, products, categories and sales channels are only available through the Admin API. Through the Store API they exposed names and descriptions of inactive groups and groups of other sales channels.
- Transfer to another shop hardened. "Test connection" only contacts http/https addresses, follows no redirects, refuses link-local and cloud metadata addresses and reports success only if FAQ Professional really answers at the target. The secret in the connection code is stored encrypted (key derived from APP_SECRET; if it changes, the code has to be entered again). The access of a shared target shop no longer has a general permission to delete media. Cells starting with =, +, -, @ are protected against formula execution in Excel in the CSV export and restored on import, and an import ZIP is checked for size, number of entries and paths before reading.
- The services for searching via Elasticsearch/OpenSearch are loaded from a YAML file instead of XML. Shopware 6.8 no longer loads Symfony configuration written in XML, so the plugin is prepared for that update. Nothing changes in how the shop behaves.
- /llms.txt is held in the HTTP cache and cleared with every change to FAQs or groups.
- The storefront plugin for copying the link is now called FaqCopyLink, the CSS class faq-accordion-header--copy-link. The old class faq-accordion-header--kopierlink is still in the markup but deprecated and will be removed in a later version; please move custom styles to the new class.
- Code identifiers are English throughout. Relevant for extensions: service ids and PHP classes such as FaqSeitenAdresse are now English (FaqPageAddress). Twig functions keep their previous names as deprecated aliases.
Note
- The helpful rate for a chosen period is calculated from the individual votes. Votes store neither sales channel nor language, so the channel and language filters apply to views, not to the rate in the period.
6.7.7 6.7.0.0 - 6.7.16.0
Fixed
- Saving was blocked — across the whole shop, not just the FAQs. Anyone trying to save a product, an order, a category or a setting could not get through while this plugin was active. The plugin called a function of the shop system that only exists from Shopware 6.7.13 onwards. Only shops on a Shopware version below 6.7.13 were affected — for them this update resolves it completely. If your shop already runs 6.7.13 or newer, nothing ever went wrong for you.
- The statistics tile “Unanswered FAQs” was misleading. It lists questions nobody has ever opened — not questions without an answer. It is now called “Never opened FAQs”, matching the line beneath it.
- The product assignment of an FAQ group needed two lines. The field showed as many entries as the fields above it, although product names are considerably longer — the remainder wrapped onto a second line and the form looked untidy. It now shows fewer entries and stays on one line; the count beside them still names the full set.
- Updating from an older version could stop halfway through. If a table the plugin expected was missing from the database, the update halted there and everything after it was left undone. The visible symptom was the new category and product assignments simply not being there afterwards. The update now steps over a missing table instead of stopping.
- If a table belonging to this plugin is missing because an earlier update failed, the update now brings it back itself, instead of leaving it permanently missing. Running the update again used not to help either: once the migration that creates the table was already marked as done, it never ran a second time, and the table stayed gone for good. Anyone who wants to check or trigger this by hand can now use the console command syn:faq:tables:check (with --repair to fix it).
Important when updating
If your update to 6.7.6 broke off, there is nothing to repair by hand. The steps left undone will run automatically during this update.
6.7.6 6.7.0.0 - 6.7.16.0
Fixed
Affects managing FAQs in the backend unless stated otherwise.
- A newly assigned question lands at the end of the list instead of the top. Previously every save reset its position in every group. Existing groups are numbered once during the update; your order is preserved.
- The Quote button in the answer editor deleted the selected text instead of converting it. It now wraps it.
- The search term you typed stayed behind after picking an entry. It now disappears, and the list offers all entries again.
- The question and group lists remember which columns you switched on — per user account, including column order and compact mode.
- After saving you return to where you came from. To stay on the screen, use the second button next to it.
- The save buttons show that writing is in progress. With many assignments this takes a noticeable moment.
- An active entry can always be switched off, even after losing its last assignment. Only switching it on is blocked.
- Groups with more than roughly 9,400 assignments were shown incompletely. Saving in that state could lose the part not loaded. The full set is now read.
- An FAQ group's description now appears in the shop, between the group heading and the first question.
- The Cancel button in the delete dialog shows "Cancel" again instead of an internal text key.
- Labels in the administration have been tidied up, including placeholder texts and the spelling of "FAQ group".
- The answer field's label sits above the field again, with proper spacing below.
New
- "All sales channels" with a single switch — including channels created later. Your existing selection stays saved and applies again once you switch it off.
- FAQ groups can be assigned to categories and products, not only through tags. A tag is still enough, and so is a category. Subcategories do not inherit the assignment.
- Anchor links optionally without the group name. shipping-how-long-does-delivery-take then becomes how-long-does-delivery-take. Links you have already shared keep working either way. The previous form is preconfigured — change nothing and nothing changes.
- Selecting groups, tags, categories and products is clearer. What you type is matched at the start of a word first; for large numbers there is a "Show all" dialog with search and an alphabet index.
- Groups sharing a name can be told apart — the question count follows, for example "Shipping & Delivery (195)".
- The question and group lists can be filtered by sales channel.
- The group list shows the "Categories" and "Products" columns.
- Category pages show assigned FAQ groups even without a CMS block. An existing block still takes precedence.
Important for this update
Shops running Elasticsearch need a reindex so that "All sales channels" also takes effect in the shop search. Details in UPGRADE.md.
Your existing links are unaffected.
6.7.5 6.7.0.0 - 6.7.16.0
Fixed
Affects how the FAQs appear in the shop, and there above all visitors working
without a mouse — with the keyboard or with a screen reader.
- An outline shows again where the keyboard currently is. Anyone moving
through the questions with the tab key now sees the current question
highlighted; previously there was no way to tell which question would open on
pressing enter. When operating with a mouse the outline stays away — there you
know where you are anyway. - A link inside a question no longer gets in the way. When a question
contained a link, that link sat inside the expand control. Screen readers
cannot resolve a control within a control: the link was unreachable and the
control not reliably operable. Links in the question are now shown as text;
formatting such as bold or italic is preserved. Nothing changes in the
answer — links stay clickable there, and that is where they belong.
Both points concern mandatory levels of accessibility (WCAG 2.2, levels A and
AA). For online shops the European Accessibility Act has required them since
June 2025.
Improved
- Source code optimisations for better readability.
6.7.4 6.7.0.0 - 6.7.16.0
Fixed
Affects installations where the administration is rebuilt from source —
typically agency and deployment environments. Anyone installing the plugin from
the store and using the prebuilt files supplied with it was not affected.
- The administration build completes again. The package was missing the
file that lists the required JavaScript packages. Without it Shopware does not
fetch them and the build stops with "Rollup failed to resolve import"; until
now the only remedy was to add the file by hand. - Seven JavaScript packages are now listed explicitly. Until now they came
along only because another package brings them. With package managers that use
strict layouts — pnpm or Yarn, for instance — the build could fail on this.
Improved
- The list on a statistics page that is still empty ends with punctuation and
writes "30 days" as a figure.
6.7.3 6.7.0.0 - 6.7.16.0
Fixed
Affects the statistics page in the backend, and there above all shops where
little or nothing has happened yet. Wherever a figure was still missing, the
page either left parts out or moved them.
- Four tiles stand side by side again. The fourth one — "Ratings" — was
missing as long as nobody had rated an answer; it now shows a dash until the
first rating arrives. - The small charts inside the tiles have their full height again. When the
green or red comparison figure above a chart is missing — the normal case
during a shop's first days — the chart was previously squeezed into a quarter
of its height, leaving a large empty area beneath it. - Tiles without figures show a fine line where the bars will later appear.
Previously the area was simply empty. - The period below the first tile appears only once there is one. On a new
shop the word "History:" previously stood there with nothing behind it. - Anyone narrowing down by sales channel or language that has no views yet
now reads exactly that. Previously the same sentence appeared as on a shop
without any data at all — even when other channels had long been delivering
figures. - The "Reset statistics" button appears only when there is something to
reset. - An internal association between question and FAQ group carried the wrong
name. This had no effect on the display in the shop or in the backend — the
association is not read anywhere in the plugin. Anyone extending the plugin
with their own code now receives it as expected.
New
- A statistics page that is still empty explains what will appear there —
and names the condition for it: the FAQs have to be visible in the shop, as
their own page, as a product tab, in the category or as a CMS block.
Improved
- Source code optimisations for better readability.
6.7.2 6.7.0.0 - 6.7.16.0
Fixed
Affects all shops. The command palette in the answer editor — the menu that
appears after typing a slash — was missing two behaviours that only become
apparent when you keep typing after the slash.
- The selection narrows with every character typed. Typing tab after the
slash now shows only the matching commands; previously the full list
remained. - The menu follows the caret. It now sits below the position being typed at
with every character; previously it stayed where the slash had been typed.
Improved
- The supported PHP versions are now stated explicitly: 8.2 to 8.5.
Installation on an older version is refused up front instead of failing
during operation — previously the lower bound was left open, although the
code uses language features from 8.2 onwards. - The source code has been brought in line with the expressive means of
those versions throughout, making it shorter and more uniform to read.
Behaviour is unchanged.
Also included
Version 6.7.1 was not released separately. If you are coming from 6.7.0, this
update brings its changes as well:
- The statistics show trends. Below each of the four tiles you can see how
the value developed: one bar per day for views, a ring for the ratings.
Hovering over a day shows the date and the count. - The rating percentage is put into context. Next to the percentage there is
a sentence naming it. How meaningful the figure is depends on the number of
votes cast. - Every tile states the change against the preceding period of equal length.
- Notification titles and column headings appear in the language set for the
administration. This affected the list and edit pages for questions and
groups.
6.7.1 6.7.0.0 - 6.7.16.0
New
- Statistics now include charts. Each of the four tiles shows how its value developed: one bar per day for views, a ring for ratings. Hovering a day reveals its date and count, including days without a single view. Previously the tiles held four numbers with no chart.
- The rating percentage is put in context. A sentence next to the figure states what it amounts to. How dependable the figure is depends on the number of votes cast: where there are few, the hover text names the range the actual value falls in.
- Each tile states the change against the preceding period of equal length — green for an increase, red for a decrease, grey where the value is unchanged. Where no complete preceding period exists yet, the absolute increase is shown instead of a percentage.
Fixed
Affects shops whose administration is run in English.
- Notification titles and column headings appear in the language the administration is set to. The lists and editing pages for questions and groups were affected; previously these texts were hard-coded and stayed German in an English backend.
Maintenance
- The foundations of the editor for answers and group descriptions have been updated. The changes concern tables, lists and the interplay with the administration. Editing questions and answers is unaffected.
- Builds of the plugin are reproducible. All third-party packages are pinned to fixed versions and checksums. Previously this applied to only some of them, so two installations could end up with different packages. Storefront operation is unaffected.
- Statistics processing is split into individually testable parts, both administration indexers share a common base, and the route definition is YAML. Behaviour is unchanged.
6.7.0 6.7.0.0 - 6.7.16.0
- The update deactivates questions and groups that have no sales channel or no group. The rule has always been stated next to the active switch: a question can only be active once a sales channel and a group are assigned. Until now it was enforced by the admin list view — silently, on opening the page, with no feedback. That had a consequence few would suspect: such questions remained findable through the shop's search until someone happened to open the right admin page. Whether a customer saw a result depended on backend behaviour. The update now enforces the rule once, traceably. The entries themselves are kept and still appear in the list with a red notice — they are simply no longer active.
- Sales channels without a storefront can no longer be selected. The selection fields for FAQ groups, for questions and in the statistics filter offered every channel, including "Headless" and "Product comparison". None of them has an HTML storefront: an FAQ assigned there is never displayed, and the statistics filter reliably produced an empty report without any indication why. Existing assignments to such channels are removed by the update. Questions and groups themselves are left untouched.
- The FAQ lists in the admin open considerably faster. The group list attached every question of a group to each row, merely to show four numbers: count, clicks and the helpfulness rating. With a well-filled FAQ inventory that added up to several megabytes per page view; now it is a few dozen kilobytes. The question list likewise loaded complete sales channel records per row just so one column could show names. The displayed figures are unchanged; they are now calculated rather than collected.
- Entries per page are now the same in both lists: 25, 50 or 100. Previously questions offered 15/30/50/100 starting at 15, groups 15/25/50/100 starting at 25. The smallest step is gone — fifteen rows fill half a screen these days.
- New: how long the click log is kept. Selectable under "Data retention": 12 months, 24 months or keep indefinitely. A daily task then cleans up by itself. The default is "keep indefinitely" — an update should not delete statistics nobody asked to remove. Choose a period there if you want the table pruned.
- Statistics evaluate noticeably faster. The filter by sales channel and language used columns that were in no index, so every report read the entire click table. That goes unnoticed with a few rows, not with real traffic. In addition, "reset statistics" now respects the active filter instead of always clearing everything.
- The admin search now finds umlauts. Searching for "Größe" or "Rückgabe" previously returned no results at all, even though the questions were there.
- A question now appears only once per page. Where the same question belongs to two groups — for instance a general question meant to appear everywhere, alongside the product tab — it was previously output more than once, both visibly and in the markup for search engines. This now applies across the whole page, not just per output area.
- The copy icon is off by default. New under “Formatting / Appearance”: “Show copy link behind each question”. Nothing about your FAQ page changes on update — the spacing of the questions is untouched as well. Turn it on there if you want it.
- A linked question now appears at the top instead of mid-screen. The same link used to end up in three different places depending on whether you opened it fresh, confirmed it again in the address bar, or reloaded the page. All three now land in the same spot, clear of the header.
- A copy icon behind every question. One click puts the link to that exact question on the clipboard — handy for mailing a customer the one answer that fits instead of pointing them at the FAQ page. Deliberately built as a button, not a link: with thousands of questions there would otherwise be just as many extra internal links on one page for search engines to follow. It adds no extra links to your page.
- Switching language keeps the question you were reading. Open a question, switch the language, and you land on the same question in the new language instead of at the top of the page. If it does not exist there, the page top it is.
- FAQ suggestions in the search led nowhere in other languages. In a shop with language domains every suggestion pointed at the address without the language prefix — a page that does not exist. It went unnoticed because it never happens in the default language.
- Links to a single question are now readable. Instead of …/faq-page#faq-d4d4d4d4…-f6f6f6f6… it now reads …/faq-page#general-questions-how-do-i-order — group name and question in short form. Anyone passing such a link on by email, chat or ticket can see at a glance where it leads; an AI assistant reading llms.txt passes on the same readable link. Applied to the FAQ accordion, the search suggestions, the search result page and llms.txt.
- Links already shared keep working unchanged. Every question additionally keeps its previous anchor faq-{groupId}-{faqId} in exactly the place it has always been. A link a customer saved months ago, or left in a forum, still jumps to the right question and opens it. No previous anchor is dropped.
- Fixed: a single incompletely translated FAQ group took down /llms-full.txt for that language entirely. The page answered with a server error, so not just that one group was missing but all the others with it. This state arises in any shop as soon as someone creates a group and adds the translation later. A group without a translation now simply appears without a name.
- The machine-readable files are now correct per language. Addresses carry the language path of the respective sales channel domain (/en/… instead of the default-language address), and the FAQ page is resolved via the SEO address of that very language. Where the page does not exist in a language, no per-question links appear — and the file says so explicitly instead of looking as if the shop had no FAQs at all.
- Anchor links follow the text actually displayed in each language. With "Fall back to the default language when a translation is missing" enabled, the page shows the default-language text — and the link then points there too. Every question keeps its own unique anchor in every language.
- llms.txt is now an index instead of a data dump. It carries one section per FAQ group and links every question straight to its place on your FAQ page — an AI assistant jumps to the single answer instead of reading through everything. Previously the entire stock sat in this one file; in a mid-sized shop that meant several megabytes, and many requests broke off before the end. It is now a few dozen kilobytes.
- New: /llms-full.txt with the complete collection. Every question with its full answer, linked from llms.txt so a model actually finds it. Answers are no longer cut off after 500 characters.
- Lists and paragraphs in answers no longer run together into one word. "Payment methods:PayPalCredit cardPrepayment" reads as "Payment methods: PayPal, Credit card, Prepayment" again — the same applies to lists, paragraphs, headings, line breaks and tables. Of all places, the file meant for machines was full of gibberish.
- The link to /faq is gone: that address does not exist in the shop, so the link led nowhere. The page from the "FAQ landing page for search results" setting is linked instead. If none is selected, no question link appears at all — better none than a dead one.
- Both files only list groups that actually appear in the shop, and are served as Markdown, as llmstxt.org requires. The existing /llms.txt address keeps answering unchanged.
- FAQs can now be placed in a column. Until now the FAQ output was only available as a full-width block. There is now an FAQ element that can be placed into any column via "Replace element" in the Shopping Experiences editor — for example into the right half of a two-column layout. Which questions appear is governed by the page's tags as usual. The heading level of the group name is configurable on the element so it fits the outline of the page it sits on.
- The FAQ block now shows in the Shopping Experiences editor what will later appear in the shop. Previously it showed only the title and an empty box below it. Pick a sample product or category under "Demo entity" in the sidebar and you will see the groups and questions that actually apply to that object. Without a selection, a note explains what the selection depends on — nothing is shown that the shop would not output later.
- The FAQ block and the FAQ element now appear under their own heading "FAQ Professional" in the selection dialog instead of under "Text". Existing Shopping Experiences are unaffected.
- When several FAQ sections sit on one page they no longer collapse each other. Previously, opening a question closed an open question in the other section.
- The schema.org markup now appears exactly once per page, regardless of whether the FAQs come from the product tab, the block or the new element.
- New editor for answers and group descriptions. The previous text field is replaced by an editor with images, video, quotes, callout boxes and slash commands. Existing content is carried over unchanged — verified against a cross-section of real field content, every one of them character-exact.
- The question is now a plain text field. A question needs no formatting. Questions already saved remain untouched and are displayed unchanged in the shop; anyone editing one will see the markup it contains as text.
- Opening an FAQ entry in the editor no longer alters the links it contains. Previously the editor would have added rel="nofollow" and a new target window on save — affecting how search engines rate them, without anyone having edited anything.
- The search results page now groups FAQ hits by their group and shows the group name as a heading instead of a badge next to each question. This matches the CMS block and the product tab.
- "Was this answer helpful?" now actually works on the search results page — the buttons were visible there but had no effect.
- On a non-default language the field again shows the default-language text as a placeholder, so translators can see what they are working on.
- Four display settings take effect again: icon style, icon position, separator line and its colour could be configured but had no effect on the output.
- The options "Show group name as heading", "Display group name in bold" and "Display question in bold" can now actually be switched off.
- FAQs next to the search suggestions now also appear in shops with multiple language domains.
- The structured data now only contains questions that are actually visible on the page, and is capped at 100 entries.
- The scheduled cleanup task for votes older than one year aborted on its first deletion run. Fixed.
- The description texts no longer promise Google rich snippets: Google switched off the FAQ presentation in search results in May 2026. The schema.org markup itself is unchanged and is still read by search engines and AI assistants.
- New version scheme: the first two digits name the Shopware line this release targets. In terms of content it is the direct continuation of 2.4.0.
6.6.0 6.6.0.0 - 6.6.10.31
- First release for Shopware 6.6. Feature set matches version 2.4.0 of the Shopware 6.7 line.
- New version scheme: the first two digits name the Shopware line a release is built for. Versions 6.6.x run on Shopware 6.6, versions 6.7.x on Shopware 6.7.
2.4.0 6.7.0.0 - 6.7.16.0
- You can now choose whether FAQs appear above or below the products on the search results page. New setting under "Search".
2.3.0 6.7.0.0 - 6.7.16.0
New Features
- New setting under "General": "Fall back to default language for untranslated FAQs" (off by default). When turned on, FAQs that have not been translated yet are shown in the shop's default language instead of being hidden.
- New "Translations" column in the FAQ list and the FAQ Groups list. It shows at a glance which languages already have a translation (✓) and which are still missing (✗).
Improvements
- FAQ search now only shows FAQs in the language you are browsing. A German FAQ no longer shows up when searching in the English shop (unless you turn on the new fallback setting above).
- FAQ search now stays up to date automatically. No separate command needs to be run anymore.
- Clearer wording in the search settings ("search suggest" instead of "search dropdown") so the option is easier to find.
- When editing a FAQ or FAQ group in a language other than the shop's default, you can now leave the text empty and the default language content is used instead. Only the default language still requires the text to be filled in.
Bugfixes
- Fixed an error that could break product and other pages in a language where the FAQs had not been translated yet (for example an English shop with FAQs maintained only in German). Untranslated FAQs are now simply hidden, or shown in the default language if the new fallback setting is turned on.
- Fixed the "Question & Answer need to be filled" and "Groupname needs to be assigned" messages appearing when saving a translation in a non-default language. These texts are no longer required there.
2.2.0 6.7.0.0 - 6.7.16.0
## New Features
- Plugin configuration "Search": new toggle "Show FAQs on search result page" (default: on) — completely disables the FAQ list on the `/search` result page
- Plugin configuration "Search": new "Hidden" option for the search dropdown position — completely disables FAQ suggestions in the suggest dropdown
## Improvements
- FAQ accordion anchor IDs switched from question slug to the stable format `faq-{groupId}-{faqId}` — prevents anchor collisions when identical questions exist across groups and survives question rewordings. Applied consistently to search result page and search-suggest links
- Administration: `flagUrl` in the FAQ overview now uses Shopware's `asset` filter instead of a hardcoded `/bundles/` path — resolves correctly in setups with external asset storage (CDN/S3)
## Bugfixes
- Search result page and search-suggest: HTML entities in FAQ questions (e.g. `&`) were double-encoded and rendered as `&` — appended `|raw` after `|striptags` so already-encoded entities from the rich-text field are not escaped again
2.1.1 6.7.0.0 - 6.7.16.0
Fixed missing use statement for FaqGroupCollection in ProductPageLoadedSubscriber
2.1.0 6.7.0.0 - 6.7.16.0
- New feature: Dynamic /llms.txt route — outputs all active FAQ groups with questions and answers as machine-readable plain text, compatible with the llmstxt.org standard for AI readiness.
- Improvement: Revised display position logic — "Product tab, or CMS block if present" now shows FAQs in the product tab only when no CMS FAQ block is present on the page (CMS takes priority).
Configuration label updated accordingly.
- Bugfix: Display position "Everywhere" did not show FAQs in the product tab when a CMS FAQ block was simultaneously present on the page — condition corrected.
- Improvement: Removed "Don't display FAQ tab" option from plugin configuration — tab visibility is controlled per FAQ group via the group's "display position" setting.
- Security: LIMIT values in SQL queries of the statistics controller are now explicitly cast to int. Added whitelist guard in FaqHelpfulService — column name is validated before being used in SQL
statements.
2.0.5 6.7.0.0 - 6.7.16.0
- Statistics: Most-read FAQs are now always read from `syn_faq_click_log` — fixes missing entries when the denormalized `click_count` cache was stale
- Statistics: Country flags in the "Clicks by Language & Domain" widget were not displayed — corrected file extension (`.svg` → `.png`), fixed mapping for `en-US` (→ `us`) and `no-NO` (→ `nb`)
2.0.4 6.7.0.0 - 6.7.16.0
2.0.3 6.7.0.0 - 6.7.16.0
2.0.2 6.7.0.0 - 6.7.16.0
2.0.1 6.7.0.0 - 6.7.16.0
1.1.4 6.7.0.0 - 6.7.16.0
- Faq search setting + improved search with search term for index pages
- Schema.org answerCount error fixed
- Refactor frontend to control cms/tab/both views
- Add missing snippets
- Faq/FaqGroup pages now update the global search filter to Faq/Faq group
1.1.3 6.7.0.0 - 6.7.16.0
- restrict faq and groups to selected sales channels only for all pages
1.1.2 6.7.0.0 - 6.7.16.0
- restrict faq and groups to selected sales channels only
1.1.1 6.7.0.0 - 6.7.16.0
- fix issue with FAQ styles
1.1.0 6.7.0.0 - 6.7.16.0
- first Shopware-store relaunch
1.0.9 6.7.0.0 - 6.7.16.0
- Migration tables added
1.0.8 6.7.0.0 - 6.7.16.0
- add manufacturer prefix to css classes and twig blocks
- renamed files to include manufacturer prefix
- refactoring to make inner css classes plugin specific
- add Migration missing folder
1.0.7 6.7.0.0 - 6.7.16.0
- fix error in FAQ-Grouping
1.0.6 6.7.0.0 - 6.7.16.0
- Shopware-Code-Review-Errors fixed
1.0.5 6.7.0.0 - 6.7.16.0
- Shopware-Code-Review-Errors fixed
1.0.4 6.7.0.0 - 6.7.16.0
Removed broken namespaces