Canonical page 1 and rel=next/prev

[teconsite]

Hi!

I'm checking a site that has something like a News section, where they publish some posts, quite similar to a blog.
They have a canonical url pointing to the page=1.

I was thinking of implementing the rel=next/ prev and the view all page and set the view all page as the canonical. But, as this is not a category page of an ecommerce site, and it would has more than 100 posts inside in less than a year, It made me think that maybe the best solution would be the following

Implementing rel=next/prev
Keep page 1 as the canonical version.

I don't want to make the users wait for a such a big page to load (a view all with more than 100 elements would be too much, I think)

What do you think about this solution?

Thank you!

[Keszi]

Hi there!

First of all, I believe that you shouldn't use both canonical and rel=prev/next. The two techniques do not work together well: "In cases of paginated content, we recommend either a rel=canonical from component pages to a single-page version of the article, or to use rel=”prev” and rel=”next” pagination markup." (quoted from http://googlewebmastercentral.blogspot.com/2013/04/5-common-mistakes-with-relcanonical.html"

Basically you have more possibilities:

• Do not set up canonical or rel="prev/next", but use noindex, follow meta robots tag for pages 2+ (kind of old school, but still works as a charm)
• Implement Rel="Prev/Next" but without a canonical! the two elements do not work together (as mentioned above)

I think the best method for you would be to have a rel="prev/next" and have the canonical removed.

I hope this helps, Keszi