Pagination solution
-
I'm using pagination following Google's guidelines to resolve duplication on pages such as:
Is it sufficient to apply rel="prev" and rel="next" to search results navigation or is it wise to apply a canonical tag on www.domain.be/product-overview/2/ to www.domain.be/product-overview/?
Many thanks for your insights!
-
Hi Dr. Pete. Thanks a lot for your additional expertise. I think I've got a pretty good understanding how to use canonicals and pagination with eachother. Thanks!
-
Just following up on Matthew's comment. The reason for the canonical to Page 2, in that example, is to cover any kind of additional duplicates, like sorts. For example, if you had URLs like:
...where those pages sorted by price or product rating. Then, you'd want to canonical all sorted versions to "/2". In that case, the rel=prev/next tags should actually include "/price" and "/rating", depending on which page you're currently on. It's a mess, honestly, and I'm not thrilled with Google's implementation, but it seems to work fairly well.
Bing's implementation is limited, unfortunately.
FYI, if there are no other duplicates (just pagination), you don't really need the canonical. It won't hurt you, but it's unnecessary.
-
Thanks THB for that additional explanation. Lessons learned! Many thanks.
-
Thanks Matthew. It's crystal clear to me now!
-
Not all web crawlers honour the rel="prev" and rel="next" attributes, but I always use them because they cannot harm you and are especially helpful for crawlers that do take them into consideration.
I made the mistake, ages ago, of placing the canonical tag on my pagination pages that pointed to the first page. I didn't have a firm grasp of the canonical tag at that time, and i paid the price for it. Now I find that the canonical tag is grossly over/misused as you don't even need to place it on any of the pagination pages. Google knows what page it's on and will usually just disregard the canonical tag. It will only take it into consideration if the URL and canonical tag don't match.
Make sure to change up your title/meta tags to accommodate the various pages, ie.
<title>Car Parts - Page 2/3/4/5/6/etc</title>
Adding a page reference to your <h>tags is not necessary as the content of the page is still the same, just another page.</h>
Consider adding the title attribute to your paging links as well as a notifier:
There are additional rel attribute values that can be helpful, too: http://www.w3.org/TR/html4/types.html#type-links
-
Hi Jacob,
You do want to include a canonical on page 2 but you want the canonical to reference page 2. This confused me at first but the reason is that you want Google to see page 2 as something separate from page 1, but part of the same series as page 1, page 3, etc. So, for that page 2, your should have:
I look at it this way: the canonical says, page 2 is a page that Google can index but the prev/next links reminds Google that this page doesn't stand alone.
Here is more from Google. See the "A few points to mention:" section.
http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html
I hope that helps. Thanks,
Matthew
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Query for paginated URLs - Shopify
Hi there, /collections/living-room-furniture?page=2
On-Page Optimization | | williamhuynh
/collections/living-room-furniture?page=3
/collections/living-room-furniture?page=4 Is that ok to make all the above paginated URLs canonicalised with their main category /collections/living-room-furniture Also, does it needs to be noindex, follow as well? Please advice, thank you!1 -
Need w3c validation error solution
http://validator.nu/?doc=http%3A%2F%2Fwww.topnotchlawsuitloans.com Stray end tag head. An body start tag seen but an element of the same type was already open. Cannot recover after last error. Any further errors will be ignored.
On-Page Optimization | | JulieWhite0 -
Pagination with parameter and rel prev rel next
Hi there: I have a doubt about how using the pagination and rel prev | rel next, I will try to sum up this example of pagination: the page number 1 is SEO friendly in order to index it, It also gets metarobots: index, follow. The other ones (pagination), instead, have noindex, follow. In fact, these URLs are not SEO friendly because of they have the parameter "?" to set up pagination, so for this reason, in the past, It has been decided not to index them. Would you suggest also to use rel="prev" rel="next" in this situation? Or would it be better to set up the others ones (pagination) in "SEO friendly" and then, to set up the rel prev | rel next? Thanks a lot in advance for helping 🙂 Greetings Francesca
On-Page Optimization | | Red_educativa0 -
Experiences with pagination rel=next and prev
I have read about people saying that using the rel next and prev tags did not take any positive effect on their sites... In my case I do not have a typical pagination 1,2,3 but a site about tours in the amazon where each tour-description is divided into a page with an overview, itinerary, Dates & Prices so instead of Site 1,2,3 Buttons I have the Btns: Tour Overview, Itinerary, Prices So as all the of pages belong together I thought the rel=next & prev tags will be useful.
On-Page Optimization | | inlinear
Also I want to avoid duplicate content when the page title of the three is pretty similar. Right now the Title is like this:
Amazon Tour XXX YYYY
Amazon Tour XXX - itinerary
Amazon Tour XXX - prices The description text is more different... Is this the best practice in my case? Thanks for all your opinions! 🙂 best regards,
Holger0 -
What if Paginated Pages all have PageRank?
Paginated Pages, page 2,3,4 etc.... they aren't supposed to have a PageRank, right? If they are only linked to from themselves, only the original page, Page 1, is supposed to be showing PageRank? I'm trying to double check that I am handling this right. I'm not using canonical, or noindex or any of that... just using rel next and prev, which I thought would be fine. Thoughts?
On-Page Optimization | | MadeLoud0 -
Pagination for image galleries
We have photo galleries that load new URLs with new content/photo on each page, yet I'm still seeing "duplicate meta description" in GWT for each separate URL in the gallery. Will rel="next" rel="prev" take care of this? Just want to confirm as it requires a CMS upgrade/release.
On-Page Optimization | | Aggie0 -
SEO and Pagination on search results
Hi Our new site is still in beta mode, and I just wanted to check from an SEO perspective that on search results and on the pagination at the bottom of the page, is there anything we need to do so its compatible with the search engines and not have duplicate content issues etc I have implemented search friendly URL's, but I would welcome any other issues or suggestions you have that will help improve the sites SEO performance The URL of a search results page is http://www.cheapfindergames.com/category-arcade-and-platform
On-Page Optimization | | ocelot0