Is the FAQ Schema markup actually useless for your product pages?

What does "informational query" versus "transactional query" really mean in this context?

An informational query corresponds to a search intent focused on discovering information: "how to clean a leather sofa", "what to do if my package is lost", "difference between SSL and TLS". The user is looking for an answer, not necessarily to make a purchase. Google prioritizes featured snippets, People Also Ask, and indeed, rich results FAQ that provide information without a click.

In contrast, a transactional query reveals an intention to buy or take action: "buy black leather sofa", "car insurance quote", "book hotel in Paris". The user wants to compare, order, convert. For these queries, Google rather displays Shopping ads, product reviews, comparison sites—and the FAQ Schema does not add differentiating value in SERPs.

Why doesn't the FAQ Schema impact direct conversions?

The FAQ markup allows Google to extract and display your question-and-answer pairs directly in search results. For an informational query, this is powerful: it occupies space, answers quickly, and captures attention. But for a transactional query, the user scans prices, product images, and CTAs—they're not looking for an FAQ.

Simply applying FAQ Schema to a product sheet will not improve your click-through rate or your conversion because the intent is not aligned. Google probably won't even display the rich result FAQ for "buy cheap iPhone 15"—it prefers to show Shopping offers. Splitt reminds us here that markup does not create demand, it responds to an existing informational demand.

In what concrete cases is the FAQ Schema still useful?

The FAQ Schema remains entirely relevant on customer support pages, practical guides, help centers, and educational blog articles. A typical example: "how to return a package", "what are your delivery times", "is your service compatible with X". For these queries, Google seeks to provide a quick answer—and gladly displays a rich result FAQ if the markup is clean.

In practical terms, if you manage an e-commerce site, focus the FAQ Schema on your Help/FAQ section, your tutorial blog articles, your "How it works" pages. Don't waste time structuring fictitious FAQs on every product sheet just to fill the SERP—this won't work, and Google may even see it as spammy structured markup.

• Performing FAQ Schema: support pages, practical guides, informational articles, help centers
• Ineffective FAQ Schema: product sheets, commercial landing pages, transactional category pages
• Risk of abuse: creating artificial FAQs solely for markup can be penalized by Google
• User intent: always align markup type with the dominant search intent
• Rich results: Google displays the FAQ Schema only if the query intent matches

Is this statement consistent with field observations?

Yes, and it's even a finding we've been making for months. Sites that have stuffed their product sheets with FAQ Schema in hopes of boosting their CTR have quickly become disillusioned: Google does not systematically display rich results FAQ for commercial queries. Worse, some have seen their rich results disappear after an update because the markup did not align with the actual intent of the query.

In contrast, blogs, support pages, and educational content that use FAQ Schema continue to benefit from visible rich results on informational queries. Splitt's position validates what we observe: Google filters the display of FAQs based on intent, not just the presence of markup. Let's be honest—adding FAQ Schema everywhere was already a bad practice.

What nuances should be applied to this statement?

The boundary between informational and transactional queries is not always clear. Consider "best CRM for SMEs": it's a mixed intention—the user seeks information (comparisons, criteria) but is also close to making a purchase. For such navigational or investigative commercial queries, the FAQ Schema can add value if the questions address real purchase objections.

Another nuance: even if the FAQ Schema does not directly boost conversion, it can improve user experience on the page and reduce bounce rates—which, indirectly, can impact ranking. But be careful, Splitt speaks here of the effect of markup in SERPs, not on-page UX. Distinguishing these two aspects is crucial. [To be verified]: Google has never communicated specific figures on the CTR impact of the FAQ Schema depending on the query type—we remain in the declarative realm.

In what cases does this rule not fully apply?

If your page mixes several intents—typically a blog article with an integrated product CTA—the FAQ Schema can remain relevant if the dominant intent is informational. For example: "how to choose home insurance" + commercial proposal at the end of the article. Here, the target query is informational, so the FAQ Schema retains its usefulness.

Another exception: branded queries. On "FAQ Brand_Name", users explicitly seek your questions and answers—the markup is then highly relevant, even if your activity is transactional. But this is a particular case, not the norm. And this is where it gets tricky: many SEO practitioners generalize a good punctual practice to their entire site—classic mistake.

What concrete actions should be taken with this information?

First action: audit your pages with FAQ Schema and identify those targeting transactional queries. If you have FAQ markup on product sheets, commercial landing pages, or sales-oriented category pages, remove it—or replace it with Product Schema, Review Schema, or Offer Schema. These tags are much more aligned with transactional intent.

Second reflex: focus the FAQ Schema on your help content and educational articles. Create a real FAQ or Support section if you haven't already, structure it properly with the markup, and optimize it for long-tail informational queries. This is where you will attract qualified traffic and improve your visibility on recurring questions.

What errors should be absolutely avoided?

Do not create artificial FAQs just for the sake of having markup. Google detects generic, copy-pasted FAQs with no real value. Worse, if your questions do not match the content of the page or if you stuff the markup with commercial keywords disguised as questions, you risk manual action or algorithmic filtering. The FAQ Schema is not a keyword stuffing tool.

Another common error: duplicating the same FAQ Schema across multiple pages. Google may interpret this as duplicated content or markup spam. Each FAQ must be unique, contextual, and provide a specific answer to the page it resides on. And this is where it gets tricky—many CMS generate the same FAQ block everywhere automatically, without customization.

How to check that your FAQ Schema strategy is compliant?

Use the Search Console to check the actual display of your rich results FAQ. Look at impressions, CTR, and especially the queries that trigger the display. If your FAQs show up on transactional queries, it indicates that Google is not filtering yet—but that can change at any moment. Also, monitor markup errors via the Improvements report.

Test your pages with Google's Rich Results Test to validate syntax, but don’t rely solely on that—a technically valid markup may be semantically inappropriate. The tool won't tell you if your FAQ is relevant to the intent of the query. Only a manual analysis of the targeted SERPs will confirm this for you.

• Audit all pages with FAQ Schema and identify transactional intents
• Remove FAQ Schema from product sheets and commercial pages
• Concentrate markup on support pages, guides, educational articles
• Create unique and contextual FAQs, never generic or duplicated
• Check the actual display of rich results in the Search Console
• Test syntax with the Rich Results Test, but manually validate semantic relevance