Pagination, Canonical, Prev & Next
-
Hello All
I have a question about my Magento setup. I have lots of categories which have many products so the categories paginate. I've seen info about making sure the Canonical tag doesn't simply send Search Engines back to the first page meaning the paginated pages won't get indexed. I've also seen info about using the rel=next & rel=prev to help Search Engines understand the category pages are paginated... Is it okay to use both?I've made sure that: category/?p=1 has a canonical of category/ to make sure there isn't duplicate content.
Here's an example of category/?p=2 meta data:
http://website.com/category/?p=2" />
http://website.com/category/" />
http://website.com/category/?p=3" /> -
While it can work that way, Google has explicitly stated that they do not want paginated search results to canonical back to page 1. They suggest either using rel=prev/next or using a canonical to a "View All" version.
Now, in practice, it's a bit more tricky, but most SEOs I know have moved away from canonical to page 1. If we don't canonical to "View All" or use rel=prev/next, the next most common approach is to META NOINDEX/FOLLOW pages 2+. Otherwise, Google may stop honoring your canonical tags, which can cause problems sitewide.
-
Hi,
Google recommends using a rel=canonical to a 'view all' page OR prev/next pagination. That being said though, the setup you have now is unlikely to cause any issues, the pagination is correct and the canonical is pointing to the same page so no technical reason for confusion.
One thing to keep in mind is if you have any filters available on these pages (like sort by price for example). In this case the recommendation IS to use both rel canonical and prev/next pagination. The rel=canonical in this case would point back to the main unfiltered page's url and the prev/next links would point to the relevant pages with the filtering included. So something like:
Page is **category/?p=2&sortby=price and **meta data is:
-
Hi Allen
Thanks for your reply. I don't think you understod the question though.I know the product pages will get indexed. My questions is purely about Category pages. If I had 10 paginated pages and they all had http://website.com/category/" /> then the 9 paginated pages won't get indexed (I've seen this on many ecommerce sites). Because the 9 other paginated pages on my site aren't duplicate content I won't them to get indexed as well.
There are some great articles out there you may want to read. I just haven't seen any advice on using the methods I've ended up with.
http://moz.com/blog/rel-confused-answers-to-your-rel-canonical-questions
http://www.ayima.com/seo-knowledge/conquering-pagination-guide.html
http://searchengineland.com/the-latest-greatest-on-seo-pagination-114284 -
Si,
Your concern about sending search engines back to the "Root" page is unfounded. Simply the search engines WILL index not only your category page but also your individual product pages.
So if you had a category, lets say "batteries" and that category had 100 different batteries, each category page having 10 of the different batteries. All 10 of the category pages should be Canonicalized to point to the first battery category page. That page is now receiving link juice from the lower 9 pages. But your 100 individual battery product page has its own link juice and they should NOT be directed back to the category page.
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
-
Self referencing canonicals and paginated content - advice needed
Hi, I help manage a large site that uses a lot of params for tracking, testing and to help deal with paginated content e.g. abc.com/productreview?page=2. The paginated review content correctly uses rel next and rel prev tags to ensure we get the value of all of the paginated review content that we have. The volume of param exclusions I need to maintain in Google & Bing Webmaster tools is getting clunky and frustrating. I would like to use self referencing canonicals, which would make life a lot easier. Here's my issue: If I use canonicals on the review pages the paginated content urls would also use the same canonical e.g. /productreview?page=2 pointing to /productreview I believe I am going to lose the value of those reviews, even though they use the rel next rel prev tags. BTW airbnb do this - do they know something I don't, don't care about the paginated reviews, or are they doing it incorrectly, see http://d.pr/i/14mPU Is my assertion above correct about losing the value of the paginated reviews if I use self referencing canonicals? Any thoughts on a solution to clearing up the param problem or do I have to live with it? Thanks in advance, Andy
Intermediate & Advanced SEO | | AndyMacLean0 -
Rel=“next” and rel=“prev” on category pages and galleries
Hi there, I am running an WordPress blog and i was looking a couple of days on the source code of the categories. From a SEO point of view would make sense to include into the header of the categories the rel=“next” and rel=“prev” tags ? Same question would be for the image galleries . Should i add the rel=“next” and rel=“prev” tags on the image galleries ? So for example if i upload 10 images to a gallery, the user will check the post and see the gallery. It will click on an image and will redirected on the attachment page of that displays that image > from where he can click next to see the next image or prev for the previous image. Therefore should i add the rel=“next” and rel=“prev” tags here too ? Many thanks
Intermediate & Advanced SEO | | MirceazetelSerafim1 -
Hreflang and paginated page
Hi, I can not seem to find good documentation about the use of hreflang and paginated page when using rel=next , rel=prev
Intermediate & Advanced SEO | | TjeerdvZ
Does any know where to find decent documentatio?, I could only find documentation about pagination and hreflang when using canonicals on the paginated page. I have doubts on what is the best option: The way tripadvisor does it:
http://www.tripadvisor.nl/Hotels-g187139-oa390-Corsica-Hotels.html
Each paginated page is referring to it's hreflang paginated page, for example: So should the hreflang refer to the pagined specific page or should it refer to the "1st" page? in this case:
http://www.tripadvisor.nl/Hotels-g187139-Corsica-Hotels.html Looking foward to your suggestions.0 -
Paging Question: Rel Next or Canonical?
Hi, Lets say you have a category which displays a list of 20 products and pagination of up to 10 pages. The root page has some content but when you click through the paging the content is removed leaving only the list of products. Would it be best to apply a canonical tag on the paging back to the root or apply the prev/next tags. I understand prev/next is good for say a 3 part article where each page holds unique content but how do you handle the above situation? Thanks
Intermediate & Advanced SEO | | Bondara0 -
How far can I push rel=canonical?
My plan: 3 sites with identical content, yet--wait for it--for every article whose topic is A, the pages on all three sites posting that article will have a rel=canonical tag pointing to Site A. For every article whose topic is B, the pages on all three sites posting that article will have a rel=canonical tag pointing to Site B. So Site A will have some articles about topics A, B, and C. And for pages with articles about A, the rel=canonical will point to the page it's on. Yet for pages with articles about B, the rel=canonical will point to the version of that article on site B. Etc. I have my reasons for planning this, but you can see more or less that I want each site to rank for its niche, yet I want the users at each site to have access to the full spectrum of articles in the shared articles database without having to leave a given site. These would be distinct brands with distinct Whois, directory listings, etc. etc. The content is quality and unique to our company.
Intermediate & Advanced SEO | | TheEspresseo0 -
Should we use the rel-canonical tag?
We have a secure version of our site, as we often gather sensitive business information from our clients. Our https pages have been indexed as well as our http version. Could it still be a problem to have an http and an https version of our site indexed by Google? Is this seen as being a duplicate site? If so can this be resolved with a rel=canonical tag pointing to the http version? Thanks
Intermediate & Advanced SEO | | annieplaskett1 -
Can I use rel=canonical and then remove it?
Hi all! I run a ticketing site and I am considering using rel=canonical temporary. In Europe, when someone is looking for tickets for a soccer game, they look for them differently if the game is played in one city or in another city. I.e.: "liverpool arsenal tickets" - game played in the 1st leg in 2012 "arsenal liverpool tickets - game played in the 2nd leg in 2013 We have two different events, with two different unique texts but sometimes Google chooses the one in 2013 one before the closest one, especially for queries without dates or years. I don't want to remove the second game from our site - exceptionally some people can broswer our website and buy tickets with months in advance. So I am considering place a rel=canonical in the game played in 2013 poiting to the game played in a few weeks. After that, I would remove it. Would that make any sense? Thanks!
Intermediate & Advanced SEO | | jorgediaz0 -
Implementing Canonicals on Existing ASP Ecommerce Store with Pagination
So I have a store which has been around for a while and is custom built on ASP.net. Store has thousands of sku's and at least a few hundred subcategories. Have been tackling a bunch of the onsite issues and for categories which have more than 6 products in them, there are multiple pages and a view all present. Example.com/category example.com/category?PageIndex=2 example.com/category?PageIndex=3 example.com/category?PageIndex=4 example.com/category?viewall=True As well as the following for every page example.com/category?PageIndex=2&viewall=True So I know how I wish to handle the pagination/canoncial issue as per google's suggestions you do it to the view all or they have the rel=next/prev. But my question is google says if view all is present they should already do a good job at ranking the view all version. Well in the rankings, there are a lot of page1 variations showing. So once this is implementated, is it safe to assume that I will see a drop? Feel like if it was a brand new site it is easy but for something this old and established, it could cause some decent harm which at the current time we are already tackling a massive list of issues which in the long haul will improve it. Looking for some insight for someone who has dealt with ASP.net and this specific area. thanks
Intermediate & Advanced SEO | | Sean_Dawes
Sean0