SEO (JSON-LD)

Every FAQ you publish automatically generates a FAQPage JSON-LD schema block on the product page. No plugin configuration, no SEO app integration required - it is just there.

What gets emitted

On any product page that has at least one active FAQ assigned and where the FAQ tab is enabled for the current store view, the module injects a <script type="application/ld+json"> block into the page <head>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your return policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Returns are accepted within 30 days of delivery..."
      }
    }
  ]
}
</script>

The block is skipped entirely if no active FAQ data is present, or if the FAQ tab is disabled for the current store view.

How answers are serialised

Questions and answers are strip-tagged before being written into the schema block. That means any rich formatting in the WYSIWYG admin editor - bullet lists, headings, links, images - renders correctly in the on-page accordion but is flattened to plain text in the JSON-LD output. This prevents malformed HTML in the structured data and avoids Google’s schema validator rejecting the page.

Practical implication: answers should read cleanly as a single paragraph of plain text, because that is what Google’s rich result processor sees. If an answer relies on a bulleted list for clarity, consider adding a short summary sentence at the top so the flattened version still makes sense.

Verifying the output

View page source on any product page that has an active FAQ and search for application/ld+json. The block appears in <head>.

Google’s Rich Results Test accepts a live URL and confirms whether the FAQ schema is valid and eligible for rich result display.

Google’s eligibility rules

Google’s FAQ rich result guidelines apply normally. In particular:

The FAQ content must be visible on the page. The module shows all FAQs inside the expandable accordion on the product page, which satisfies this requirement.
Questions and answers should not be promotional or advertisement-only.
FAQs should be genuinely useful to customers, not SEO keyword stuffing.

The module handles the technical side. Editorial responsibility for content quality rests with the admin user who authored the FAQ.