⚠ This guide explains the concept and benefits – it does not provide the full code. The actual solution is a paid module which we implement (licensed for your store). This protects both your and our investment – price for integration in OpenCart – 25 Euro.

By default, OpenCart 3 does not offer a category-level FAQ section and does not generate structured FAQ data. Our paid module fills this exact gap: it adds an “FAQ” tab in the admin area, shows the questions below the category description and generates a valid FAQPage JSON-LD. The technical implementation and OCMOD code stay with us – you get a ready-to-use solution.

1) Why you should have FAQs per category

Category pages are often the first contact point between your customer and your store: they come from Google, from ads, from email campaigns, etc. This is where typical questions arise:

• Is shipping different for this category (bulky shipments, pallets, installation)?
• What is the warranty and return policy for this type of products?
• How do I choose the right product in this category (size, power, compatibility)?

If you do not answer these questions directly on the category page:

• The customer hesitates and often leaves the page.
• You overload support with repetitive questions.
• You miss a chance for Google to “understand” your content better and show it as a rich snippet.

A well-structured category-level FAQ section solves all three problems at once.

2) What schema.org and FAQPage are

schema.org is a shared vocabulary of data types that Google, Bing and other search engines use to better understand web content (products, articles, events, FAQs, etc.).

FAQPage is a specific schema.org type describing a page that contains a list of questions and answers.

• Each question is represented as @type: "Question".
• Each answer – as @type: "Answer".
• All of them are collected in a mainEntity array on the FAQPage object.

This data is usually provided in a JSON-LD block in the page HTML. This is Google’s preferred format – easy to maintain and independent from the visual code.

3) What rich snippets are and how FAQPage helps

Rich snippets are “enriched” Google search results – besides title, URL and meta description, you might see:

• ratings (stars),
• prices, stock status,
• events, breadcrumbs,
• a FAQ block with expandable questions and answers.

When Google detects a valid FAQPage JSON-LD and decides it is useful:

• it may add several of your FAQ questions below the search result;
• your result becomes visually larger and more noticeable;
• you get a higher CTR (more clicks for the same impressions).

Important: Google never guarantees that it will show FAQ rich snippets – even if the JSON-LD is perfectly valid. But without structured data, the chance is practically zero.

4) How the solution works (without module code)

Let’s describe the principle, without publishing the paid module or its code:

1. A new “FAQ” tab is added in the category admin page.
   For each language you can add multiple questions and answers, sorted by sort order.
2. On category save the questions and answers are written into a dedicated table in the database (one row per question/answer and language). The exact structure and SQL are part of the paid module.
3. On the frontend – when the category loads, the system:
   – retrieves the FAQ for the corresponding category and language;
   – passes them to the category template (e.g. Journal3);
   – displays them as an accordion / list of questions and answers under the description.
4. In parallel, a JSON-LD FAQPage object is built from the same data and injected in a <script type="application/ld+json"> in the HTML.

This entire process is wrapped in a paid module, so the client sees only a convenient interface and the final result in the store, without having to assemble OCMOD, Twig and PHP changes by hand.

5) JSON-LD example (generic, not tied to the module)

Below is a generic example of FAQPage JSON-LD. It is illustrative – it is not an excerpt from the paid module, but simply demonstrates the structure Google expects.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the delivery time for products in this category?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Delivery takes 1–3 business days. For bulky shipments we offer palletized shipping."
      }
    },
    {
      "@type": "Question",
      "name": "Can I return the products?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. You can return products from this category within 14 days according to legal requirements."
      }
    }
  ]
}
</script>

In our paid solution this JSON is generated automatically from the FAQs entered in the admin area – you don’t edit JSON manually and you don’t need to understand the format in detail.

6) Content tips for FAQ sections

Whether you use our module or another solution, the following rules always apply:

• Questions should be real – frequently asked by customers, not pure SEO filler.
• Answers should be short and clear, without unnecessary marketing fluff.
• Don’t copy text 1:1 from other pages on your site – Google doesn’t like duplication.
• Use different FAQs for different categories, not one template everywhere.
• Don’t use FAQPage for promotions, discounts or offers – Google may ignore them.

7) Testing in Rich Results Test and Search Console

After implementing structured data (whether via our paid module or another solution) you should:

1. Open Google’s Rich Results Test and test the category URL.
2. Check whether FAQPage is detected and whether there are any errors/warnings.
3. Monitor Search Console → Enhancements to see if an FAQ section appears and how many URLs are valid.
4. Compare the category’s CTR before and after adding FAQ and FAQPage.

Showing FAQ rich snippets can take time – Google needs to crawl and reindex your pages.

8) Limitations and best practices from Google

• FAQPage is for static questions and answers, not for forums or user-generated Q&A.
• Don’t use FAQPage for aggressive promotional text – the goal is information, not banners.
• Don’t apply exactly the same FAQ structure to all pages – this can be considered spam.
• Keep an eye on Google’s official guidelines – FAQ rich results policy changes over time.

9) What the paid module includes and how we implement it

The implementation we use for clients is a paid module for OpenCart 3. It is not distributed as a free download – we install and configure it ourselves.

Typically, it includes:

• A license for one online store (one domain/instance).
• Module installation and basic configuration.
• Theme adjustments (e.g. Journal3) so the FAQ fits visually.
• FAQPage JSON-LD validation in Rich Results Test.
• Short training on how to add and manage category FAQs.

If you wish, we can also handle the content side – writing the questions and answers for your most important categories in coordination with your SEO team.

10) FAQ about the module itself

• Is the FAQ module free to download?
  No. This is a paid solution. The code is not published or distributed publicly in order to avoid pirated copies and support issues.
• Will you give me the full OCMOD/XML/Twig code?
  No. You get a working module in your store, but the full code is not uploaded as a downloadable article. We can discuss technical details, but we don’t publish the entire implementation.
• Does it work with Journal3?
  Yes. The module is tested with Journal3 and adapted so the FAQ is displayed naturally in the category layout. For other themes we make minimal adjustments during implementation.
• Will I have issues when updating OpenCart?
  The solution is based on OCMOD and respects typical OpenCart 3.x changes. For major upgrades we can perform additional checks and adjustments as a service.
• Can we add other schema.org types as well?
  Yes – we often combine Product, BreadcrumbList and FAQPage on one page, but always within Google’s official guidelines.

Tip: keep a document (or Git repo) with described FAQs per category, change dates and key notes. This makes future SEO audits or team changes much easier to handle.

Comments