Official statement
Other statements from this video 9 ▾
- 28:11 Google traite-t-il vraiment tout le contenu d'une page de la même façon pour le ranking ?
- 45:21 Le contenu généré par les utilisateurs peut-il vraiment saboter votre référencement naturel ?
- 55:03 Le contenu utilisateur toxique peut-il réellement pénaliser tout votre site dans Google ?
- 97:32 Pourquoi le contenu non textuel peut-il nuire au référencement de votre site ?
- 170:33 Faut-il vraiment publier une politique de contenu UGC pour améliorer son référencement ?
- 174:08 Faut-il vraiment bloquer par défaut tout contenu généré par vos utilisateurs ?
- 181:21 Faut-il vraiment baliser tous les liens de contenu utilisateur avec rel='ugc' ?
- 186:55 Faut-il vraiment retirer rel='ugc' pour récompenser vos contributeurs de confiance ?
- 208:15 Le contenu utilisateur booste-t-il vraiment l'engagement sans nuire au SEO ?
Google recommends moving comments to a separate page instead of displaying them on the same page as the main content. The goal is to protect the perceived quality and relevance of your page by the algorithms. Essentially, this approach prevents low-quality or off-topic comments from diluting your SEO signal, but it requires a redesign of your content page architecture.
What you need to understand
Why does Google suggest separating comments from the main content? <\/h3>
The reasoning is simple: Google's algorithms evaluate the quality of a page as a whole, not just the editorial content. When you publish a 2,000-word in-depth article and 50 comments pile up at the bottom, Google analyzes this block as part of the indexable content.<\/p>
If these comments are of low quality, redundant, or even spam, they can weaken the relevance signal of your page. By isolating comments on a distinct URL, you allow Google to crawl and index your main content without interference.<\/p>
What’s the difference between displaying and indexing comments? <\/h3>
Google differentiates between what is visible to the user and what is crawlable for the bot. If your comments are loaded via client-side JavaScript or through an iframe, they may not be indexed at all. However, if you integrate them in native HTML, Googlebot can read and consider them.<\/p>
The Splitt recommendation specifically targets cases where comments are natively present in the DOM, thus technically indexable. By moving them to a separate page accessible via an explicit link, you retain user experience while segmenting the SEO signal.<\/p>
Is this a requirement or a tactical option? <\/h3>
Let's be honest: this is not an official directive nor a documented ranking factor. It’s a practical suggestion to avoid potential risk. If your comments are moderated, relevant, and actually enhance the content, leaving them on the same page may even strengthen your freshness and engagement signal.<\/p>
On the other hand, if you run a blog with a high volume of unmoderated comments or a site where comments often go off-topic, separation becomes a defensive strategy to protect your SEO.<\/p>
- Segmenting comments allows precise control over the indexed content on each URL.<\/li>
- An explicit link like 'See Comments' maintains user accessibility and the crawling of secondary content.<\/li>
- This approach is only relevant if your comments pose a documented quality risk (spam, low added value).<\/li>
- Websites with moderated and enriching comments can maintain a unified display without negative impact.<\/li>
- Google does not penalize comments per se, but evaluates the overall quality of the crawled page.<\/li><\/ul>
SEO Expert opinion
Is this recommendation consistent with field observations? <\/h3>
Yes and no. In practice, it’s observed that pages with quality comments — particularly forums, niche articles with expert discussions, or product pages with detailed reviews — perform very well. Google values user-generated content when it adds real value.<\/p>
Conversely, sites that let generic, repetitive, or spammy comments proliferate do indeed experience a dilution of the thematic signal. The crawler struggles to identify the main topic when 60% of the indexed text consists of 'Thank you for this article!' or spam links. [To be verified]: Google has never published a quantitative threshold to determine when comments become problematic.<\/p>
What are the risks of systematic separation of comments? <\/h3>
Moving all your comments to a separate page can create unanticipated side effects. First, you may potentially lose the benefits of fresh content: regular comments signal to Google that your page is active, which can influence crawl frequency.<\/p>
Second, you fragment the user experience. If a user clicks on 'See Comments' and lands on a nearly empty or poorly structured page, it degrades the engagement rate and can indirectly harm SEO through behavioral signals. Finally, if your comments contain relevant long-tail keywords, isolating them reduces the semantic density of your main page.<\/p>
In what cases does this separation make no sense? <\/h3>
If you're operating a site like Stack Overflow, Reddit, or a specialized forum, comments or responses are the core of added value. Separating them would be like amputating your main content. Similarly, on an e-commerce site, integrated customer reviews enrich the semantics of the product sheet and strengthen rich snippets.<\/p>
The Splitt recommendation primarily targets editorial blogs and media sites where comments are ancillary, unmoderated, and potentially counterproductive. If your comments are rare, qualified, or enriched by a voting system, keeping them on the same page is likely more beneficial.<\/p>
Practical impact and recommendations
How can you effectively implement this separation of comments? <\/h3>
The first step is to audit the quality of your existing comments. Analyze a representative sample: spam rate, thematic relevance, average length, presence of useful keywords. If over 30% of comments are generic or spammy, separation becomes relevant.<\/p>
Technically, create a dedicated URL for each comments page — for example, The classic mistake: moving comments without managing existing URLs. If your comments were previously indexed with anchors like Another pitfall: creating a completely orphaned comments page. Google must be able to crawl this page via an explicit internal link, or it will never be indexed. Lastly, don’t sabotage the UX: if the user expects to see comments directly, forcing them to click without a valid reason will degrade your engagement metrics.<\/p> Before any migration, establish a baseline: average positions of the affected pages, crawl rate, quality metrics in Search Console. Segment a test group (20% of your articles) and compare performance over a minimum of 60 days.<\/p> Pay particular attention to the organic click-through rate (a decrease could signal a degradation of experience), crawl frequency, and changes in featured snippets. If you see a clear improvement in the test group, gradually roll out the changes across the site. Otherwise, revert to the initial configuration.<\/p>\/article-slug\/comments<\/code>. Integrate a visible link at the end of the article with an explicit anchor like 'Read the 24 comments'. Ensure that this URL is crawlable (no noindex, no blocking JavaScript) but never duplicate the main content on this page.<\/p>What mistakes should you avoid when migrating comments? <\/h3>
#comment-123<\/code>, those URLs will generate 404s. Set up 301 redirects to the new comments page.<\/p>How can you measure the impact of this change on your SEO? <\/h3>
❓ Frequently Asked Questions
Les commentaires sur la même page nuisent-ils systématiquement au SEO ?
Comment Google détecte-t-il la qualité des commentaires sur une page ?
Faut-il noindexer la page de commentaires séparée ?
Cette séparation s'applique-t-elle aux avis produits sur un site e-commerce ?
Quel impact sur le taux de crawl si je déplace les commentaires ?
🎥 From the same video 9
Other SEO insights extracted from this same Google Search Central video · duration 228h36 · published on 10/03/2021
🎥 Watch the full video on YouTube →Related statements
Get real-time analysis of the latest Google SEO declarations
Be the first to know every time a new official Google statement drops — with full expert analysis.
💬 Comments (0)
Be the first to comment.