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 -
NoIndex or Rel=Canonical Pagination
Hello, I had a question about noindex and Rel=Canonical on category page pagination. On my site, the category page the meta="robots" has "Index,Follow" tags and the rel="canonical" is the main category page, but when a user sorts the page the meta="robots" changes to "NoIndex, Follow." My question is should the sorted page be name="robots" content="INDEX,FOLLOW" /> since the rel="canonical" is pointing to the main page?? Or does it matter that it is NoIndex?? Any thoughts on this topic would be awesome. Thanks. Main Category Page
On-Page Optimization | | chuck-layton
https://www.site.com/category/
name="robots" content="INDEX,FOLLOW" />
rel="canonical" href="https://www.site.com/category/"/> Name Sorted Page
https://www.site.com/category/?dir=asc&order=name
name="robots" content="NOINDEX, FOLLOW" />
rel="canonical" href="https://www.site.com/category/">0 -
Paginated URLs are getting Indexed
Hi, For ex: - My site is www.abc.com and Its paginated URLs for www.abc.com/jobs-in-delhi are in the format of : www.abc.com/jobs-in-delhi-1, www.abc.com/jobs-in-delhi-2 and vice versa also i have used pagination tags rel=next and rel=prev. My concern is all the paginated URLs are getting indexed so is their any disadvantage if these URLs are getting indexed as somewhere i have read that link juice may get distributed in case of pagination. isn't it good to use Noindex, Follow so that we can make the Google to understand that paginated page are not so much important and that should not be ranked.
On-Page Optimization | | vivekrathore0 -
Duplicate content from pagination and categories found in multiple locations
Hey Moz community, Really need help resolving duplicate content issues for an eCommerce utilizing Magento. We have duplicate content issues with category pagination and categories found in multiple locations. here's an example: "www.website.com/style/sequin-dresses" is also found at "www.website.com/features/sequin-dresses" *to resolve this issue do we just need to place a canonical tag on "www.website.com/features/sequin-dresses" pointing to "www.website.com/style/sequin-dresses"? In addition, the category "Sequin Dresses" also has pagination. to resolve duplicate content issues with pagination do we need to implement a rel=next/prev tag? (we do not have a view-all due to the amount of products featured) If anyone has experience with this or any insights on how to resolve these issues please let me know. Thanks!
On-Page Optimization | | LeapOfBelief0 -
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 -
Pagination for product page reviews
Hi, I am looking to add pagination on product pages (they have lots of reviews on the page). I am considering using rel="next/prev, to connect the series of review pages to the main product page. I unfortunately don't have a view-all page for these reviews or the option to get one - the reviews refresh on the same product page (by clicking whatever number page of reviews). This means each page has the exact same description content and everything else, but with different reviews. In this case is rel=next a good option? The format currently would be: On example.com/product link rel="next" href="http://example.com/product?review-p2" On example.com/product?review-p2 link rel="prev" href="http://example.com/product, link rel="next" href="http://example.com/product?review-p3 etc. Would this be a good format for product page reviews? I see rel=nextprev commonly used on ecommerce category/list pages but not really on the paginated reviews on product pages, so I thought I would see if anyone has advice on how best to solve this. I'm also wondering if it would be best to not combine this with a canonical tag on all the different review pages pointing to the product page, seeing as the reviews are actually different (despite the rest of the content being identical). I am hoping to pick up longer tail traffic from this, I figure by connecting the pages and not using canonicals that this way I could get more traffic from the phrases used in the reviews. By leaving out the canonicals, is it possible a user searching for phrases that might be deeper in the series, to land on, say, ?review-p4? Any thoughts if this would drive more traffic? Thanks!.
On-Page Optimization | | pikka0 -
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 -
What is the best solution for printable product pages (duplicate content)?
What do you think is the best solution for preventing duplicate content issues on printable versions of product pages? The printable versions are identical in content. Disallow in Robots.txt? Meta Robots No Index, Follow? Meta Robots No Index No Follow? Rel Canonical?
On-Page Optimization | | BlinkWeb1