Duplicate title-tags with pagination and canonical

[MagicDude4Eva]

Some time back we implemented the Google recommendation for pagination (the rel="next/prev"). GWMT now reports 17K pages with duplicate title-tags (we have about 1,1m products on our site and about 50m pages indexed in Google)

As an example we have properties listed in various states and the category title would be "Properties for Sale in [state-name]".

A paginated search page or browsing a category (see also http://searchengineland.com/implementing-pagination-attributes-correctly-for-google-114970) would then include the following:

The title for each page is the same - so to avoid the duplicate title-tags issue, I would think one would have the following options:

• Ignore what Google says
• Change the canonical to http://www.site.com/property/state.html (which would then only show the first XX results)
• Append a page number to the title "Properties for Sale in [state-name] | Page XX"
• Have all paginated pages use noindex,follow - this would then result in no category page being indexed

Would you have the canonical point to the individual paginated page or the base page?

[garyshack]

Dr. Pete,

Do you have any search/sort filters that may be spinning out other copies, beyond just the paginated series? That could be clouding the issue, and these things do get complicated. - How about this is the case? What would you recommend?

Gary

[MagicDude4Eva]

Since last week we have chosen to append the page number to the title. Let's see if/how GWMTs status changes.

I would think that the next possible flag would then be on the page-description on paginated pages

[Dr-Pete]

I suspect you're ok, then. I'd watch those GWT numbers, but unless you're seeing problems with indexation and ranking, then I'd just consider that a notice. I think you're handling it by the book, at least as well as currently possible with Google's changing and somewhat mixed signals on the subject.

[MagicDude4Eva]

Thanks for that answer. I am already using the pageNo in GWMT (as paginates). None of the searches spin out other copies - what I see in GWMT is only related to browsing through a product category and paginating.

[Dr-Pete]

Unfortunately, it can be really tough to tell if Google is honoring the rel=prev/next tags, but I've had gradually better luck with those tags this year. I honestly the GWT issue is a mistake on Google's part, and probably isn't a big deal. They do technically index all of the pages in the series, but the rel=prev/next tags should mitigate any ranking issues that could occur from near-duplicate content. You could add the page # to the title, but I doubt it would have any noticeable impact (other than possibly killing the GWT warning).

I would not canonical to the top page - that's specifically not recommended by Google and has fallen in disfavor over the past couple of years. Technically, you can canonical to a "View All" page, but that has its own issues (practically speaking - such as speed and usability).

Do you have any search/sort filters that may be spinning out other copies, beyond just the paginated series? That could be clouding the issue, and these things do get complicated.

I've had luck in the past with using META NOINDEX, FOLLOW on pages 2+ of pagination, but I've gradually switched to rel=prev/next. Google seems to be getting pickier about NOINDEX, and doesn't always follow the cues consistently. Unfortunately, this is true for all of the cues/tags these days.

Sorry, that's a very long way of saying that I suspect you're ok in this case, as long as the tags are properly implemented. You could tell GWT to ignore the page= parameter in parameter handling, but I'm honestly not sure what impact that has in conjunction with rel=prev/next. It might kill the warning, but the warning's just a warning.

[matbennett]

I frequently use the page number in titles.  It's not a bad solution where you want them all to get indexed.

Keep an eye on whether it affects CTR from the results though. I also like to ensure that there is always a link to the first page of results. This is useful for the user and also helps push more authority to that first page so that it is more likely to be the one that appears.