Rel="prev" and rel="next" implementation
-
Hi there
since I've started using semoz I have a problem with duplicate content so I have implemented on all the pages with pagination rel="prev" and rel="next" in order to reduce the number of errors but i do something wrong and now I can't figure out what it is.
the main page url is : alegesanatos.ro/ingrediente/
and for the other pages :
alegesanatos.ro/ingrediente/p2/ - for page 2
alegesanatos.ro/ingrediente/p3/ - for page 3 and so on.
We've implemented rel="prev" and rel="next" according to google webmaster guidelines without adding canonical tag or base link in the header section and we still get duplicate meta title error messages for this pages.
Do you think there is a problem because we create another url for each page instead of adding parameters (?page=2 or ?page=3 ) to the main url
alegesanatos.ro/ingrediente?page=2
thanks
-
Using rel=prev and rel=next will help to avoid duplicate content issues and is entirely separate from your meta tags. If you wish to avoid duplicate meta title errors then you will need to add 'page x' to your titles, similar to what Matt Cutts has done with his blog.
Hope that helps,
Adam.
-
Adding rel=next/rel=prev, will not fix issues with Duplicate Titles. You need to edit your templates so that paginated pages actually have unique titles. For example
Ingrediente - Page 1 of 5
Ingrediente - Page 2 of 5
Ingrediente - Page 3 of 5
-
Technically, rel=prev/next doesn't de-duplicate the way the canonical tag does, but it should solve any problems for Google. I don't believe we currently consider rel=prev/next when determining duplicate titles. Klarke is right - you could just give those pages semi-unique titles. We're not handling rel=prev/next as well as we could be (it turns out to be a tricky tag to parse well).
Looking at your pages, your implementation appears to be correct. My gut reaction is that your probably ok here. You're doing what Google claims they want (at least what they want this week).