[wp-hackers] Known when on Comment page x?

[Stephen Rider]

No it isn't, but it certainly matters to some.

I was thinking in terms of using a GET to show different comment pages:

example.com/2008/mypost/?commentpage=2

Drawbacks to that as well, I'm sure, but I'm don't see them.

Wouldn't hurt end-user usability, unless you suspect many readers are  
directly typing in URLs to particular comment pages.

I've been using the "paged comments" plugin on my blog for a while  
now, which uses similar URLs to those produced by the new WP comment  
paging, and one thing I noticed was that it made my stats all wonky  
because hits on popular posts were being spread out among several  
comment-page URLs.  The more comment pages, the farther **down** in  
the stats!

Dan's suggestion of nofollow-ing the comment-page URLs is a good one,  
but only a partial fix.

On Dec 15, 2008, at 1:08 PM, Rick Boatright wrote:

> For some of us,  end-user functionality trumps SEO.   Some of us don't
> actually CARE about search engines hardly at all.   SEO is NOT the  
> be-all
> and end-all of the web.
>
> On Mon, Dec 15, 2008 at 12:55 PM, Stephen Rider
> <wp-hackers at striderweb.com>wrote:
>
>> Isn't this bad for SEO?  We now have a post with multiple pages,  
>> but the
>> post content is repeated over multiple URLs.  This will screw up  
>> search
>> engines, as well as site stats (popular posts will end up  
>> "splitting the
>> vote" between comment-page-1, comment-page-2, comment-page-3, etc...)