B2B SaaS SEO case study
SaaS SEO experiment: what happened after useful FAQ content became eligible for rich results.
A SaaS SEO case study about isolating an implementation hypothesis, measuring the result, and separating a page-level experiment from wider site growth.
Discuss a similar problemThe SaaS company already had useful question-and-answer content on its pages. The experiment tested whether implementing the structured data available at the time could improve eligibility and visibility for FAQ rich results.
historical FAQ-result clicks
Compared with two clicks in the baseline filtered Search Console view.
historical FAQ-result impressions
Compared with 964 impressions in the earlier filtered period.
average position
Improved from 14.3 in the earlier period shown.
estimated monthly organic traffic
Separate Ahrefs site snapshot; not attributed solely to the FAQ test.
The team needed evidence for a specific implementation decision.
The question was not whether FAQs were fashionable. It was whether existing, useful FAQ content could become more visible when the page clearly identified the questions and answers with the structured data supported at the time.
A credible SEO experiment also had to avoid a common mistake: attributing the entire website’s later growth to one change. The FAQ filter, wider organic programme, and third-party visibility snapshot are presented as separate pieces of evidence.
The work was designed as one connected system.
Write the hypothesis
Defined the expected search appearance, eligible page set, measurement filter, and comparison periods before interpreting the result.
Use existing useful content
Marked up questions and answers that were already visible to users instead of hiding schema-only copy from the page.
Filter the evidence
Used the Search Console appearance filter available at the time to isolate clicks, impressions, CTR, and position for FAQ rich results.
Keep the site programme separate
Continued content, semantic SEO, and information-architecture work without claiming the experiment caused every later traffic increase.
The source data, translated into a current, readable format.
Every number below comes from the archived Search Console, Analytics, or Ahrefs evidence. The results are unchanged and the public presentation was reviewed in August 2026.
The filtered result changed from two clicks and 964 impressions to 35.8K clicks and 981K impressions.
Verified Search Console experiment. FAQ rich-result availability has changed since the work; the public presentation was reviewed in August 2026.
This is a separate site-level snapshot, not the measured output of the FAQ experiment alone.
Verified third-party Ahrefs estimate. The domain is withheld because the engagement is covered by NDA.
The filtered result showed a material change in FAQ-rich-result visibility.
The historical Search Console view records 35.8K clicks and 981K impressions in the later period, compared with two clicks and 964 impressions in the baseline period. The archived source also records the intervention point and the FAQ-result filter.
Google has since restricted FAQ rich results for most sites. This is therefore evidence of a disciplined historical experiment, not a recommendation to expect the same search feature in 2026. The transferable lesson is the measurement method: isolate the hypothesis, implement valid visible content, and measure the specific result.
What another team can take from this work.
Preserve the intervention date
A chart is more useful when the reader can see when the change began.
Do not confuse eligibility with causality
Structured data can clarify content and enable features; it does not automatically create demand or rankings.
Update the tactic, keep the method
Search features change. Hypothesis design, controlled implementation, and careful attribution remain useful.
Have a comparable search problem?
Tell us the website, market, commercial goal, current evidence, and what your team can implement. We will recommend the right starting point.
Contact us