Should you really hide user comments from Google?

Does Google really distinguish between user content and editorial content?

Martin Splitt claims that Google natively identifies user comments and treats them differently from the main content. In practice, the algorithm can detect sections of comments, forums, customer reviews without you having to specifically mark them up or exclude them from crawling.

This distinguishing ability likely relies on several signals: repetitive HTML structure, presentation patterns (avatars, dates, reply buttons), density of short and conversational content, implicit metadata. Google has never detailed exactly how it does this — and that's where it gets interesting for us.

Why is this statement being made now?

Because too many sites implement complex technical solutions to hide comments from Google, often based on persistent SEO myths: fear of content dilution, concern over spam, desire to control internal PageRank. These practices cause more problems than they solve.

The main risk? Accidentally blocking critical resources. A misconfigured robots.txt that aims to exclude /comments/ could also block /comments.css or /comments.js if those files are used elsewhere. An overly aggressive lazy loading may prevent Google from crawling valid URLs found in the comments.

What impact on ranking if I keep everything visible?

Splitt states that leaving comments visible in the rendered HTML neither benefits nor harms SEO. In other words, their presence is neutral — Google sees them, processes them, but doesn't use them to evaluate the quality of your main page.

This neutrality aligns with our observations: a blog post with 200 comments does not rank better than a similar post without comments. However, a post with comments rich in natural keywords may attract long-tail traffic if Google indexes those segments — and that’s where it gets a bit complicated.

• Google automatically identifies user comment sections without specific markup
• Hiding comments creates more risks than benefits (blocking resources, crawl errors)
• Their presence is neutral for the main page's ranking
• No need for robots.txt, noindex, or lazy loading to exclude them
• Focus your efforts on the quality of your editorial content, not on marginal technical optimizations

Is this claim consistent with real-world observations?

Yes and no. On mature platforms (WordPress, phpBB forums, standard e-commerce sites), Google seems indeed capable of distinguishing comments from main content. We see this in featured snippets: Google rarely extracts text from comments to answer a query, preferring the body of the article.

However, on custom sites with non-standard HTML structures, or SPAs (Single Page Applications) where everything is rendered in JavaScript, this distinction becomes less reliable. I've seen cases where Google massively indexed comment threads as standalone pages, creating unintentional duplicate content. [To verify]: Google has never published benchmarks showing the accuracy rate of this detection across different site types.

In what cases does this rule not apply?

The first obvious case: mass unmoderated spam. If your comments are saturated with links to dubious sites, Google may indeed degrade the overall perception of your page. Splitt says it’s neutral, but in reality, a site that allows 500 spam comments per day will take algorithmic hits.

The second case: sites where comments are the main content (Reddit, Stack Overflow, Quora). Here, Google does not apply this separation logic — everything is treated as editorial content. Splitt's statement clearly targets blogs, news sites, e-commerce, not conversational platforms.

What is the real nuance that Google does not mention?

Google claims that keeping comments visible is neutral for ranking, but fails to mention that some user signals may still come into play: time spent on the page extended by reading comments, reduced bounce rate if comments add value, boosted organic CTR if rich snippets display a number of comments.

In other words, comments do not directly impact the content algorithm, but may indirectly influence through behavioral signals. Google will never publicly make this distinction because it opens the door for manipulation. [To verify]: no official data on how these signals weigh in the overall algorithm.

What should I practically do with existing comments?

If you currently have robots.txt rules blocking /comments/ or noindex directives on these sections, consider removing them. But do it gradually: remove the block on a sample of pages, monitor Search Console for 2-3 weeks to detect any anomalies (crawl spikes, 404 errors, unwanted massive indexing).

For new sites or redesigns, the recommendation is simple: do not create a specific exclusion mechanism for comments. Leave them in the rendered HTML, and Google will handle it. Focus your energy on qualitative moderation rather than technical gymnastics.

What mistakes should you absolutely avoid?

The classic mistake: using ultra-aggressive lazy-loading JavaScript that only loads comments on scroll, hoping Google won’t see them. Not only does Google now execute JS (so it will see them anyway), but you also risk blocking critical resources if your comment script shares dependencies with other modules.

Another trap: attempting to mark up comments with schema.org Comment to “help” Google. This is unnecessary in 99% of cases — Google already detects the structure. Worse, poorly implemented markup can generate errors in Search Console and clutter your rich snippets. Keep it simple.

How can I check if my implementation is correct?

Use the URL inspection tool in Search Console to see the rendered HTML as Google sees it. If your comments appear in the rendered DOM, you're good. If you see empty blocks or JS errors, you have a problem — but it's probably not specifically related to the comments.

Also, check that your comment URLs (e.g., /article#comment-123) are not generating massive indexing in Google. If they are, use the canonical tag to point to the main article URL, not a brutal noindex that risks creating inconsistencies.

• Gradually remove robots.txt rules blocking /comments/ or /reviews/
• Remove noindex directives on user sections if they exist
• Avoid aggressive lazy loading that blocks comments from initial rendering
• Do not over-optimize with schema.org Comment unless you have a specific use case (rich snippets reviews)
• Check the rendered HTML in Search Console to confirm that Google sees the comments
• Monitor crawl and indexing metrics after modifications to detect anomalies