Official statement
Other statements from this video 22 ▾
- 0:33 Pourquoi Googlebot ignore-t-il vos cookies et comment adapter votre stratégie de contenu personnalisé ?
- 1:02 Googlebot crawle-t-il avec les cookies activés ou ignore-t-il votre contenu personnalisé ?
- 1:02 Peut-on rediriger les utilisateurs connectés vers des URLs différentes sans pénalité SEO ?
- 1:35 Changer de framework JavaScript fait-il chuter vos positions Google ?
- 1:35 Changer de framework JavaScript ruine-t-il vraiment votre SEO ?
- 4:46 Le HTML rendu suffit-il vraiment à garantir l'indexation du JavaScript ?
- 4:46 Comment vérifier si votre contenu JavaScript est réellement indexable par Google ?
- 5:48 Le contenu derrière login est-il vraiment invisible pour Google ?
- 5:48 Le contenu derrière un login est-il vraiment invisible pour Google ?
- 6:47 Faut-il vraiment rediriger Googlebot vers www pour contourner les erreurs CORB ?
- 8:42 Faut-il traiter Googlebot différemment des utilisateurs pour gérer les redirections ?
- 11:20 Faut-il vraiment masquer les bannières de consentement à Googlebot pour améliorer son crawl ?
- 11:20 Faut-il afficher les écrans de consentement à Googlebot au risque d'être pénalisé pour cloaking ?
- 14:00 Comment identifier précisément les éléments qui dégradent votre Cumulative Layout Shift ?
- 18:18 Pourquoi vos outils de test PageSpeed affichent-ils des scores LCP et FCP contradictoires ?
- 19:51 Pourquoi vos URLs avec hash (#) ne seront jamais indexées par Google ?
- 20:23 Faut-il vraiment supprimer les hashs des URLs d'événements sportifs pour les indexer ?
- 23:32 Le pré-rendu pour Googlebot : faut-il vraiment s'en passer ?
- 24:02 Faut-il vraiment désactiver JavaScript sur vos pages pré-rendues pour Googlebot ?
- 26:42 Le JSON-LD ralentit-il vraiment votre temps de chargement ?
- 26:42 Le balisage FAQ Schema est-il vraiment inutile pour vos pages produits ?
- 26:42 Le JSON-LD FAQ Schema ralentit-il vraiment votre site ?
Google confirms that FAQ markup mainly works for informational queries, not for generating customers. Displaying answers directly in the SERPs reduces clicks to your site. If your FAQs serve a business purpose, this markup risk undermines your acquisition funnel by providing too much information without engagement.
What you need to understand
Why does Google differentiate between informational and transactional queries for FAQ Schema?
The distinction is based on user intent. When someone searches for "how does a heat pump work," they want a quick answer — the FAQ Schema in SERPs meets that need immediately. But if the query is "heat pump quote Paris," the user wants to compare, contact, purchase.
Martin Splitt points out a risk: displaying promotional answers in an FAQ Schema for non-product questions dilutes the effectiveness of the markup. Google prefers this markup to serve pure information, not direct conversion. The engine may choose not to display FAQ rich snippets if the content appears too commercial.
What does "users get the info without visiting the site" mean for your traffic?
It's the paradox of FAQ Schema: you gain SERP visibility but may lose clicks. If your answer displays entirely in rich results, the satisfied user does not click. For pure informational content — guides, tutorials, definitions — it's acceptable if you're aiming for brand authority.
But for a landing page that must convert into leads or sales, this is counterproductive. You offer the benefit (the answer) for free without getting the action (form, call, purchase). Splitt's statement implies that Google accepts this friction — FAQ Schema was never designed as a customer acquisition tool.
When should you consider this markup an asset rather than a hindrance?
FAQ Schema remains relevant if your primary goal is awareness, not immediate conversion. Typically: an SEO news blog, an institutional site, a public knowledge base. You aim to position your brand as a reference — direct traffic is not the main KPI.
For e-commerce or lead-gen sites, the nuance is crucial. If your FAQs address pre-purchase objections ("free shipping?", "guarantee?"), displaying them in SERPs can reassure and encourage qualified clicks. But if they provide all necessary info without creating tension, you kill the click. The trade-off depends on what you reveal.
- FAQ Schema optimizes visibility for informational queries, not transactional ones — Google officially confirms this.
- Displaying complete answers in SERPs reduces CTR if the user no longer needs to click to be satisfied.
- Promotional content in FAQ Schema limits the effectiveness of the markup — Google favors neutral information.
- Strategic trade-off necessary: awareness vs. conversion, depending on whether you target informational or transactional traffic.
- FAQ rich snippets can reassure on pre-purchase objections without revealing everything, promoting qualified clicks.
SEO Expert opinion
Does this statement align with real-world observations?
Yes, and it is confirmed by data. A/B tests on e-commerce sites show that adding FAQ Schema to category pages or product sheets increases CTR impressions in SERPs by 10-15%, but overall traffic may stagnate or decline if the answers are too complete. Users consume the information without clicking.
In contrast, for editorial content ("what is Core Web Vitals"), FAQ Schema boosts perceived authority and visibility in position zero. The paradox: you gain SERP real estate but potentially sacrifice the click. This is a conscious trade-off to make, not a markup to deploy blindly everywhere.
What uncertainties remain in Google's position?
[To be verified] Splitt remains vague on the exact threshold between "informational response" and "promotional response". No precise guidelines on how many words, what tone, what CTAs make a FAQ "too commercial". We can guess that mentioning prices, special offers, or pushing a specific product in a non-product response poses a problem — but the boundary is subjective.
Another point: Google does not say whether disabling FAQ Schema on transactional pages improves CTR. Real-world observations suggest it does, but Google does not explicitly acknowledge it. Caution: this statement legitimizes informational use; it does not condemn commercial use — it simply states that it's "less effective," which leaves room for interpretation.
Should you revise your existing FAQs in light of this statement?
If you've deployed FAQ Schema on conversion-oriented landing pages hoping to boost qualified traffic, it's time to audit. Check Search Console: do your FAQ pages generate high impressions but low CTR? That's a signal that you're providing too much information in SERPs.
Solution: either you rephrase the answers to create tension ("To know our exact prices, contact us"), or you remove the markup from lead-gen pages and keep it only on pure editorial content. Don't sacrifice conversion for a rich snippet — this is a common mistake since FAQ Schema has been around.
Practical impact and recommendations
How to identify if your FAQ Schema is undermining your business objectives?
First step: segment your FAQ pages by query intent. Extract from Search Console all URLs with FAQ Schema, then categorize them into "informational" vs. "transactional" based on the queries generating impressions. If a page aims for conversion but mainly attracts informational queries, you have a semantic targeting problem.
Second lever: compare average CTR with vs. without displayed FAQ Schema. Google Search Console indicates when a rich snippet is shown. If your CTR drops by 20-30% when the FAQ is displayed, you are cannibalizing your own traffic. In this case, either you rephrase to create teasing, or you remove the markup.
What modifications should you make to your FAQs to maximize ROI?
For commercial objective pages: shorten the answers displayed in Schema, providing just enough to reassure without revealing everything. Example: "Our delivery times vary based on your location — check our simulator for an accurate estimate." You keep the rich snippet without killing the click.
For editorial pages: on the contrary, provide complete and structured answers. You aim for authority and position zero, not immediate conversion. Add complementary questions that delve deeper into the topic — the more you cover, the more Google views you as a reference on the topic.
How to prevent Google from ignoring or devaluing your FAQ Schema?
Google may decide not to display your FAQ rich snippets if the content is too promotional, repetitive, or of low quality. Avoid artificial questions like "Why choose our company?" in a non-product context. Favor questions that users genuinely ask — Google Search Console and Answer the Public are your sources.
Another common mistake: duplicating the same FAQs on all pages. Google detects duplication and may ignore the markup. Each page must have FAQs specific to its context. A regular technical audit via Google Rich Results Test confirms that your FAQs remain eligible for rich display.
- Audit Search Console to identify FAQ pages with high impressions but low CTR
- Segment pages by query intent: keep FAQ Schema on pure informational content
- Rephrase answers on commercial pages to create teasing without revealing everything
- Check markup eligibility via Google Rich Results Test every quarter
- Remove FAQ Schema from lead-gen landing pages if CTR drops significantly
- Avoid duplication of identical FAQs across multiple pages — personalize by context
❓ Frequently Asked Questions
Le FAQ Schema réduit-il systématiquement le trafic vers mon site ?
Dois-je retirer le FAQ Schema de mes pages produit ?
Google pénalise-t-il les FAQ trop promotionnelles ?
Comment savoir si mes FAQ sont trop commerciales selon Google ?
Le FAQ Schema aide-t-il pour la position zéro ?
🎥 From the same video 22
Other SEO insights extracted from this same Google Search Central video · duration 28 min · published on 01/07/2020
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.