All resources Experiment · Experiment

Product FAQ Schema vs. AI Synopsis

We ran a six-week A/B test comparing classic FAQPage schema against AI-generated synopsis blocks to see which format earned more visibility in generative search surfaces — and which drove qualified clicks back to the PDP.

At a glance

  • Goal: GEO visibility lift
  • Duration: 6 weeks
  • Format: A/B test recap

Hypothesis

If product pages expose concise, attributable answer blocks (synopsis) in addition to FAQ schema, generative engines will cite the brand more often and SERP real estate will expand without hurting classic FAQ rich results.

Setup

Two matched PDP cohorts on the same catalog vertical, split by URL hash.

  1. Control: FAQPage schema only, existing accordion UX.
  2. Variant: FAQPage schema plus a GEO synopsis block (40–60 words, sourced claim, entity links).
  3. Instrumentation: impressions in AI overviews / answer cards where detectable, organic CTR, scroll to buy box, and add-to-cart rate.
  4. Guardrails: no copy changes outside the synopsis/FAQ module; theme and offers held constant.

What we learned

Synopsis pages earned more generative citations and a measurable GEO visibility lift. Classic FAQ rich results held steady when schema remained valid. CTR improved on mid-funnel queries; ATC was flat — synopsis won discovery, not checkout.

Recap takeaways

  • Keep FAQ schema; add a short synopsis for answer engines — don't replace one with the other.
  • Source every claim (spec, policy, lab) so models can attribute confidently.
  • Judge experiments on visibility + qualified landing, not ATC alone.

Want help putting this into practice?

Book a strategy call and we'll adapt this resource to your stack and goals.

Book Strategy call Back to resources
Scroll