Pages with rel "next"/"prev" still crawling as duplicate?

[paul-bold]

Howdy!

I have a site that is crawling as "duplicate content pages" that is really just pagination.

The rel next/prev is in place and done correctly but Roger Bot and Google are both showing duplicated content + duplicate page titles & meta's respectively.

The only thing I can think of is we have a canonical pointing back at the URL you are on - we do not have a view all option right now and would not feel comfortable recommending it given the speed implications and size of their catalog.

Any experience, recommendations here? Something to be worried about?

/collections/all?page=15"/>

[max.favilli]

As far as I know. Even after implementing rel prev/next, the pages are still de facto duplicated (unless unique beforehand). What rel prev/next does is just signal google their are part of pagination. Google algo will then pick the page he think more appropriate to show in serp answering a user query.

If you add canonical pointing the series to one page (probably the first) you are again suggesting google algo to pick that one and ignore the others. But most seo crawling tools like moz will keep signaling those pages are duplicate, because in fact they are duplicate. If you look at the crawler report for those duplicate pages you should also see the canonical in another column, so you can just filter them out (as far as this is the result you was expecting).

Rel prev/next is not making duplicate content unique, how could it? I heard of someone who could transform water into wine, but he did't deal with SEO.

[KeriMorgret]

Hi Dylan,

Just wanted to check and see if this took care of your duplicates, and if you have any more questions. Happy New Year!

Keri