Adding FAQ Schema: SEO Split Testing Lessons from SearchPilot

This SEO case study documents a successful optimization initiative, providing actionable insights for practitioners. The documented approach demonstrates how strategic SEO implementation drives measurable results.

Initial Situation

Understanding the starting point is essential context for evaluating any case study. This documentation covers the initial challenges, competitive position, and business objectives that shaped the SEO strategy.

Strategy and Approach

The strategic approach combined multiple SEO disciplines to address identified opportunities. Key decisions around prioritization and resource allocation provide a template for similar initiatives.

Implementation

Moving from strategy to execution required specific technical implementations, content development, and process changes. This case study documents the practical steps that translated strategy into action.

Results and Learnings

The outcomes demonstrate effectiveness through measurable improvements in rankings, traffic, and business metrics. Analysis of successes and challenges provides learning value for practitioners.

Case studies like this contribute to the SEO knowledge base, helping practitioners learn from documented real-world experiences.

Source: https://www.searchpilot.com/resources/case-studies/seo-split-test-lessons-adding-faq-schema/

Practitioner commentary

FAQ schema once expanded a result with a stack of question and answer accordions that dominated vertical space on the SERP. This case study tests whether adding FAQPage structured data to a template moves organic click through rate, and the answer has shifted dramatically since the original test ran.

What FAQ schema was supposed to do

When you mark up on page questions and answers with FAQPage structured data, Google was once able to render them as expandable rich results beneath your listing. The theory was twofold: the extra vertical space pushed competitors down and could lift click through rate, and the visible answers pre qualified the click. In practice the effect was mixed, because the expanded answers sometimes satisfied the searcher on the SERP itself and reduced the need to click, a classic case where a rich result can cannibalise the very traffic it was meant to attract.

That ambiguity is exactly why it was worth a controlled test rather than a blanket rollout. The only honest way to know whether FAQ markup helped or hurt a given template was to add it to half the pages, hold the other half, and measure the click through rate difference against a forecast.

How to test it, then and now

The mechanics are the same as any SearchPilot style test. Assign templated pages to control and variant buckets, add valid FAQPage markup built from genuinely visible on page questions and answers to the variant, keep the control unchanged, and measure click through rate against the control forecast over the same window. A required rule, both then and now, is that the marked up content must be visible on the page, because structured data that does not match visible content is a guidelines violation.

The critical difference today is eligibility. In August 2023 Google restricted FAQ rich results to well known, authoritative government and health sites, so for almost every other site the FAQPage markup no longer produces the expandable rich result at all. That turns the classic version of this test into a null by default: with no rich result to win, adding FAQ schema will usually not move click through rate for a typical commercial or content site.

What to do about FAQ content in the current landscape

Keep the FAQ content, drop the expectation of a rich result. Well structured questions and answers still help users, still target long tail question queries, and are strong candidates for featured snippets and for citation in AI Overviews and other generative answers, none of which depend on FAQPage markup. If you already ship FAQPage schema and it validates without errors, there is little harm in leaving it, but do not invest in adding it to earn a rich result you are not eligible for.

The durable lesson is that structured data eligibility is a moving target set by Google, not a permanent property of a schema type. Test the outcome you can actually win today, which for FAQ content is answering question intent in visible copy and competing for snippets and generative citations, rather than chasing a deprecated enhancement.

FAQ schema then and now

What has changed since this test

In August 2023 Google limited FAQ rich results to authoritative government and health sites, and reduced HowTo rich results at the same time. For the vast majority of sites FAQPage markup no longer generates the expandable rich result, which removes the main mechanism this test relied on.

Visible FAQ content has taken on a new value as source material for AI Overviews and other generative search answers, which pull concise question and answer passages regardless of FAQPage markup. The winning move has shifted from marking up FAQs for a rich result to writing clear, citable answers in visible copy.

Related reading

• changing microdata to JSON-LD
• adding ratings and reviews structured data
• metadata case studies

Frequently asked questions