FAQ and HowTo Schema: More Visibility for Instructional Content

1. Why FAQ and HowTo schema matter for instructional content

FAQ and HowTo schema are among the most widely used content schema types for instructional and guide content, because they structure exactly what users already want to read: questions with clear answers and step-by-step instructions. For Magento stores with buying guides, assembly instructions, or support FAQs, marking up this content is a natural fit, since it explicitly tells Google, voice assistants, and AI-based search systems which text section is a question and which is the matching answer, instead of forcing them to guess from unstructured body text.

Since August 2023, however, Google has significantly restricted visible rich results for both schema types, which has left many site owners uncertain. That doesn't make the markup itself worthless: valid FAQPage and HowTo schema remains a reliable data source for AI Overviews, voice assistants, and other answer systems, even though the classic expandable snippet appears less often in the Google results list. Understanding the difference between technically correct schema and a visible rich snippet leads to more realistic decisions about where implementation effort actually pays off.

2. FAQPage schema: structure and technical requirements

The schema.org FAQPage type consists of an array called mainEntity that holds a list of Question objects. Each Question needs a name property with the exact question text and an acceptedAnswer property of type Answer with a text property that contains the full answer as plain text. Google allows simple formatting like line breaks, but no complex HTML structure, images, or links inside the text field; these are either ignored during rendering or trigger parsing warnings in Google Search Console.

What matters most for technical validity is an exact match between schema and visible content: the question and answer must exist in the HTML for every visitor without any additional interaction. An accordion that merely toggles visibility on click, rather than lazily loading the text, still satisfies this requirement. Pure marketing copy, FAQs that are repeated identically across every page, or questions unrelated to the actual page content violate Google's guidelines and can trigger a manual action.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does installing the Hyvä theme take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The technical installation usually takes two to three business days, depending on how many custom layout adjustments the existing store requires."
      }
    },
    {
      "@type": "Question",
      "name": "Does Hyvä work with all Magento extensions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most core functionality works out of the box, but classic Luma extensions built on Knockout.js need a Hyvä compatible port."
      }
    }
  ]
}

3. The 2023 Google restriction: rich results only for authoritative sites

In August 2023, Google announced that it would only show FAQ rich results for well known, authoritative websites in the government and health sectors going forward. For the vast majority of websites, including practically every e-commerce store, that means the FAQPage schema can still validate perfectly, but no longer produces an expandable snippet in the regular Google results list. At the same time, HowTo rich results were restricted to desktop searches and their overall frequency was reduced, independent of domain authority.

According to Google, the reasoning behind this change was to reduce cluttered search results pages and curb abuse of both schema types for pure SERP land grabbing, regardless of whether the content was genuinely helpful. In concrete terms for Mironsoft clients: FAQPage schema on a product page or blog article neither automatically improves click-through rate nor guarantees a visible snippet, but it remains technically clean, semantically valuable markup that stays relevant for other uses such as AI powered search assistants.

4. HowTo schema: structure with step, tool, and supply

The HowTo schema models an instruction set through several elements: name for the title, step as an array of HowToStep objects, and optionally tool and supply for required tools and consumable materials. Each HowToStep has a text property with the actual instruction, can reference an anchor within the page via url, and can include a step image via image. For multi-part individual steps, itemListElement with HowToDirection or HowToTip objects can further break a single step down into sub-actions.

Additional properties like totalTime in ISO 8601 format and estimatedCost with a MonetaryAmount increase the information density for search systems, but remain optional. The exact match requirement applies here too: every step listed in the schema must appear as its own, clearly recognizable section on the page, ideally as a numbered list. Tools and supplies in the schema that are never mentioned anywhere in the instruction text are a common validation error and a signal to Google that the markup doesn't match the actual page content.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "Clear the Magento cache via the CLI",
  "description": "Step by step instructions for fully clearing the Magento cache from the command line.",
  "totalTime": "PT2M",
  "supply": [
    { "@type": "HowToSupply", "name": "Access to the server command line" }
  ],
  "tool": [
    { "@type": "HowToTool", "name": "SSH client" },
    { "@type": "HowToTool", "name": "Magento CLI (bin/magento)" }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "name": "Open a server connection",
      "text": "Connect to the server that hosts the Magento installation via SSH.",
      "url": "https://mironsoft.de/blog/seo-faq-and-howto-schema-more-visibility-for-instructional-content#step-1"
    },
    {
      "@type": "HowToStep",
      "name": "Check cache types",
      "text": "Run bin/magento cache:status to see which cache types are currently enabled.",
      "url": "https://mironsoft.de/blog/seo-faq-and-howto-schema-more-visibility-for-instructional-content#step-2"
    },
    {
      "@type": "HowToStep",
      "name": "Flush the cache",
      "text": "Run bin/magento cache:flush to fully clear all cache types.",
      "url": "https://mironsoft.de/blog/seo-faq-and-howto-schema-more-visibility-for-instructional-content#step-3"
    }
  ]
}

5. When HowTo rich results actually appear

Unlike FAQPage, the HowTo restriction isn't tied to domain authority but to the device: since 2023, Google shows HowTo rich results with step images and expandable instructions almost exclusively on desktop search results, and on mobile devices, where the bulk of search traffic happens, they rarely appear anymore. That significantly reduces the realistic visibility impact, even though the schema itself remains technically valid and can still be marked as eligible in the Rich Results Test.

In practice, that means: anyone implementing HowTo schema purely for the visual snippet is often disappointed, because even valid markup is no guarantee of a display; Google decides on a case by case, time varying basis which pages get a rich result. The Google Rich Results Test only shows technical eligibility, not the actual display frequency; a regular look at the Google Search Console report for how to results reveals how often a snippet has actually appeared over the past weeks.

6. Best practices: visibility over rich-result gaming

The single most important best practice for both schema types stays the same regardless of the visibility restrictions: only mark up content that is genuinely and identically visible to every visitor. Schema markup that simulates content that doesn't exist on the page at all, such as invented questions purely for keyword coverage or generic instruction steps unrelated to the actual product, violates Google's structured data guidelines and risks a manual action that can affect every rich result across the entire domain, not just the offending page.

Equally risky is identical FAQ schema that gets automatically duplicated across hundreds of category pages without any real relevance to the individual page, a clear pattern for algorithmic detection of rich-result abuse. A more sensible approach is a selective strategy: deploy FAQ and HowTo schema specifically on pages where genuinely distinct, editorially maintained questions and instructions exist, such as product guides, assembly instructions, or support articles, instead of spreading the schema across the entire store as a generic SEO tool.

The example below shows a typical anti-pattern: marketing copy with an embedded HTML link instead of a genuine, visibly identical answer.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Why is our store the best choice?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<a href='/deals'>Save now</a>, unbeatable prices, and free shipping on every order!"
      }
    }
  ]
}

7. Magento and Hyvä implementation for blog and product guide pages

In Magento and Hyvä stores, the cleanest way to implement FAQ and HowTo schema is through a ViewModel that provides a single data source for both the visible markup and the JSON-LD, instead of maintaining content redundantly across the template and the schema. In practice, that means: a CMS block, a blog article attribute, or a product guide supplies structured question and answer or step data, which the phtml template renders both as an Alpine.js accordion and serializes into a JSON-LD script.

This single source of truth architecture prevents the most common real-world problem: stale or diverging schema, because editors change the visible text but the JSON-LD stays untouched. The ViewModel gets injected specifically for blog and guide page types via layout XML, not globally across the entire store, which also improves maintainability. For Magefan Blog or custom CMS landing pages, the same pattern can be implemented with a dedicated block argument that reads FAQ or HowTo data from a structured custom attribute.

<!-- Hyvä phtml: visible FAQ accordion, single source for schema and display -->
<div class="not-prose space-y-3" x-data="{ openIndex: null }">
    <?php foreach ($faqItems as $index => $item): ?>
        <details class="group bg-white border border-slate-200 rounded-xl overflow-hidden shadow-sm">
            <summary class="cursor-pointer font-semibold px-6 py-4 text-slate-800">
                <?= $escaper->escapeHtml($item->getQuestion()) ?>
            </summary>
            <div class="px-6 py-4 text-slate-600 text-sm border-t border-slate-100">
                <?= $escaper->escapeHtml($item->getAnswer()) ?>
            </div>
        </details>
    <?php endforeach; ?>
</div>

<!-- Same data source serialized as JSON-LD, no duplicated content -->
<script type="application/ld+json">
    <?= /* @noEscape */ $viewModel->getFaqJsonLd() ?>
</script>

<!-- Layout XML: inject the FAQ schema ViewModel only for blog/guide page types -->
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
    <body>
        <referenceBlock name="blog.post.view">
            <block class="Magento\Framework\View\Element\Template"
                   name="blog.faq.schema"
                   template="Mironsoft_SeoSuite::faq/schema.phtml">
                <arguments>
                    <argument name="view_model" xsi:type="object">Mironsoft\SeoSuite\ViewModel\FaqSchema</argument>
                </arguments>
            </block>
        </referenceBlock>
    </body>
</page>

8. Validating, testing, and monitoring

The Google Rich Results Test remains the most reliable tool for technically validating FAQPage and HowTo schema: it shows whether all required fields parse correctly and whether a page is fundamentally eligible for a rich result, regardless of whether Google actually displays it. Since the 2023 restrictions, the test still shows a positive result for many websites without any visible snippet appearing in practice; that's not a bug, it's the expected consequence of the changed display criteria.

Google Search Console, under "Enhancements" and the dedicated FAQ and how to reports, provides reliable data on how many pages are actually being tracked for a rich result and how impressions for these page types trend over time. A sudden drop in FAQ impressions in the summer of 2023 with an otherwise unchanged structure is, for most websites, not a technical problem but a direct consequence of the Google policy change, and should be interpreted accordingly before making unnecessary changes to the schema itself.

9. FAQPage vs. HowTo compared

FAQPage and HowTo schema differ significantly in how likely a visible rich result actually is. The table below places the most important scenarios in a realistic context instead of setting blanket expectations.

For most Mironsoft clients, this means: FAQ and HowTo schema still pays off as cleanly maintained, valid markup with value for AI search systems and accessibility, but expectations for a guaranteed SERP snippet should stay realistic. Anyone who implements both cleanly and monitors regularly via Search Console benefits in the long run, even if the visual rich result doesn't appear on every page.

10. Summary

FAQ and HowTo schema solve a clear problem: instructional content becomes machine readable and structured for Google, voice assistants, and AI search systems. Since Google's 2023 restriction, however, very few websites still show a visible rich result for it: FAQPage snippets are practically reserved for authoritative government and health sites, and HowTo snippets appear almost exclusively on desktop searches now. Even so, valid schema remains worthwhile because it provides a structured data foundation for AI Overviews and other answer systems, independent of the classic SERP snippet.

What matters for a sustainable implementation is an exact match between schema and visible content, plus a selective strategy that deploys FAQ and HowTo schema only on editorially maintained pages with genuine value, instead of spreading it automatically across the entire store. A single source of truth architecture built around a ViewModel in Magento and Hyvä prevents visible content and schema from drifting apart over time.

11. FAQ: FAQ and HowTo Schema