New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | FAQ and accordion block for Gutenberg. Bulk paste a whole FAQ at once — add, reorder and edit every question inside one block. | You have to log in to add a translation. | Details |
Original untranslated
FAQ and accordion block for Gutenberg. Bulk paste a whole FAQ at once — add, reorder and edit every question inside one block.
You have to log in to edit this translation. |
|||
| ↑ | Ordessa – FAQ & Accordion Block with Bulk Add | You have to log in to add a translation. | Details |
Original untranslated
Ordessa – FAQ & Accordion Block with Bulk Add
CommentPlugin name. You have to log in to edit this translation. |
|||
| The default output is the standard FAQ format, and for most sites that is what you want. If one of those plugins is active, the block shows a <strong>Structured data format</strong> choice: | You have to log in to add a translation. | Details | |
Original untranslated
The default output is the standard FAQ format, and for most sites that is what you want. If one of those plugins is active, the block shows a <strong>Structured data format</strong> choice:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <strong>Questions only</strong> — emits each question separately, without saying what kind of page this is, so it cannot compete with your SEO plugin at all. Use it if your SEO plugin already marks the page up as an FAQ, so the page is not described as an FAQ twice. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Questions only</strong> — emits each question separately, without saying what kind of page this is, so it cannot compete with your SEO plugin at all. Use it if your SEO plugin already marks the page up as an FAQ, so the page is not described as an FAQ twice.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| <strong>Standard FAQ page</strong> (default) — emits <code>FAQPage</code> with a <code>mainEntity</code> list. This is the format validators and AI assistants recognise as an FAQ. <code>FAQPage</code> is a subtype of <code>WebPage</code>, so your SEO plugin's page description and this one will both be present; in practice that is usually fine and is what most FAQ plugins do. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Standard FAQ page</strong> (default) — emits <code>FAQPage</code> with a <code>mainEntity</code> list. This is the format validators and AI assistants recognise as an FAQ. <code>FAQPage</code> is a subtype of <code>WebPage</code>, so your SEO plugin's page description and this one will both be present; in practice that is usually fine and is what most FAQ plugins do.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| <strong>Optional structured data.</strong> Off by default. Adds standard schema.org <code>FAQPage</code> data describing your questions, which AI assistants read when deciding what to cite. Google retired FAQ rich results in May 2026, so this is for machine readability — not search snippets. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Optional structured data.</strong> Off by default. Adds standard schema.org <code>FAQPage</code> data describing your questions, which AI assistants read when deciding what to cite. Google retired FAQ rich results in May 2026, so this is for machine readability — not search snippets.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| If your SEO plugin already outputs FAQ data for a page, use one or the other, not both. | You have to log in to add a translation. | Details | |
Original untranslated
If your SEO plugin already outputs FAQ data for a page, use one or the other, not both.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Enable it under <strong>FAQ settings → Add FAQPage structured data</strong>, on one block per page. | You have to log in to add a translation. | Details | |
Original untranslated
Enable it under <strong>FAQ settings → Add FAQPage structured data</strong>, on one block per page.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| What it still does: <a href="https://schema.org/FAQPage">FAQPage</a> and <code>Question</code> remain valid, widely used schema.org types. Google still reads them to understand what your page covers, and AI answer engines read the same data when deciding what to quote. That is the reason to enable it — not search snippets. | You have to log in to add a translation. | Details | |
Original untranslated
What it still does: <a href="https://schema.org/FAQPage">FAQPage</a> and <code>Question</code> remain valid, widely used schema.org types. Google still reads them to understand what your page covers, and AI answer engines read the same data when deciding what to quote. That is the reason to enable it — not search snippets.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Google <strong>retired FAQ rich results on 7 May 2026</strong>. The expandable question boxes that used to appear under a search listing are gone, for every site, including the government and health sites that kept them after Google's 2023 restriction. Google's note is on its own <a href="https://developers.google.com/search/docs/appearance/structured-data/faqpage">FAQPage documentation</a>. So enabling this will <strong>not</strong> change how your page looks in Google. | You have to log in to add a translation. | Details | |
Original untranslated
Google <strong>retired FAQ rich results on 7 May 2026</strong>. The expandable question boxes that used to appear under a search listing are gone, for every site, including the government and health sites that kept them after Google's 2023 restriction. Google's note is on its own <a href="https://developers.google.com/search/docs/appearance/structured-data/faqpage">FAQPage documentation</a>. So enabling this will <strong>not</strong> change how your page looks in Google.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, optionally — it is off by default, and you should know what it does and does not do before switching it on. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, optionally — it is off by default, and you should know what it does and does not do before switching it on.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Will this conflict with Yoast, Rank Math or All in One SEO? | You have to log in to add a translation. | Details | |
Original untranslated
Will this conflict with Yoast, Rank Math or All in One SEO?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Does this add FAQ schema / structured data? | You have to log in to add a translation. | Details | |
Original untranslated
Does this add FAQ schema / structured data?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| <code>.wb-faq__heading</code> — the question element inside that row (H2–H6, or <code><p></code>, whichever you chose) | You have to log in to add a translation. | Details | |
Original untranslated
<code>.wb-faq__heading</code> — the question element inside that row (H2–H6, or <code><p></code>, whichever you chose)
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| <strong>Inherits your theme.</strong> Typography and colours come from your theme rather than being overridden, and the question element is yours to choose — a heading (H2 to H6) so the block does not break your document outline, or plain text where a heading would be wrong. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Inherits your theme.</strong> Typography and colours come from your theme rather than being overridden, and the question element is yours to choose — a heading (H2 to H6) so the block does not break your document outline, or plain text where a heading would be wrong.
CommentFound in description list item. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.