Make WordPress Core

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#4696 closed enhancement (wontfix)

Comment feeds need to be noindex by default

Reported by: joostdevalk Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Administration Keywords: has-patch 2nd-opinion
Focuses: Cc:


One of the most common SEO problems a WordPress blog has, is that all the comment feeds get indexed.

Why is this a problem? Well, first of all, it's duplicate content, the comments are in the article page, AND they're in the feed, and Google get's to decide which of the two to show in a search result page.

Secondly, because they're hardly ever useful WHEN they show up in the search for something (the article would be way better), they're a waste of spidering time... If you want your blog to be well indexed, you don't want the spider to waste time on comment feeds, when he could be grabbing your articles.

So my proposition is to add the relatively new robots noindex tag for rss feeds to them by default:

<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />

Attachments (1)

comments-rss2-noindex.diff (652 bytes) - added by joostdevalk 8 years ago.

Download all attachments as: .zip

Change History (5)

#1 @Otto42
8 years ago

-1 to this. People might want their comment feed indexed, there's never a good reason to use noindex by default.

Suggest implementing the patch in #4694 instead, thus allowing this to be a very simple plugin instead.

#2 @joostdevalk
8 years ago

The patch in #4694 was indeed the reason for this bug :) I think though that by making it easier for people, by getting the defaults right, you might make a lot of people happy... I'm of course willing to settle for #4694 though ;)

#3 @matt
8 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

This is not the right solution. Google's current indexing of feeds in normal search results is a bug, and one I believe they will fix within the next month or so.

#4 @Nazgul
8 years ago

  • Milestone 2.3 (trunk) deleted
Note: See TracTickets for help on using tickets.