ECommerce Problem with canonicol , rel next , rel prev
-
Hi
I was wondering if anyone willing to share your experience on implementing pagination and canonical when it comes to multiple sort options . Lets look at an example
I have a site example.com ( i share the ownership with the rest of the world on that one ) and I sell stuff on the site
I allow users to sort it by date_added, price, a-z, z-a, umph-value, and so on . So now we have
- example.com/for-sale/stuff1?sortby=date_added
- example.com/for-sale/stuff1?sortby=price
- example.com/for-sale/stuff1?sortby=a-z
- example.com/for-sale/stuff1?sortby=z-a
- example.com/for-sale/stuff1?sortby=umph-value
- etc
example.com/for-sale/stuff1 **has the same result as **example.com/for-sale/stuff1?sortby=date_added ( that is the default sort option )
similarly for stuff2, stuff3 and so on. I cant 301 these because these are relevant for users who come in to buy from the site. I can add a view all page and rel canonical to that but let us assume its not technically possible for the site and there are tens of thousands of items in each of the for-sale pages. So I split it up in to pages of x numbers and let us assume we have 50 pages to sort through.
- example.com/for-sale/stuff1?sortby=date_added&page=2 to ...page=50
- example.com/for-sale/stuff1?sortby=price&page=2 to ...page=50
- example.com/for-sale/stuff1?sortby=a-z&page=2 to ...page=50
- example.com/for-sale/stuff1?sortby=z-a&page=2 to ...page=50
- example.com/for-sale/stuff1?sortby=umph-value&page=2 to ...page=50
- etc
This is where the shit hits the fan. So now if I want to avoid duplicate issue and when it comes to page 30 of stuff1 sorted by date do I add
- rel canonical = example.com/for-sale/stuff1
- rel next = example.com/for-sale/stuff1?sortby=date_added&page=31
- rel prev = example.com/for-sale/stuff1?sortby=date_added&page=29
or
- rel canonical = example.com/for-sale/stuff1?sortby=date_added
- rel next = example.com/for-sale/stuff1?sortby=date_added&page=31
- rel prev = example.com/for-sale/stuff1?sortby=date_added&page=29
or
- rel canonical = example.com/for-sale/stuff1
- rel next = example.com/for-sale/stuff1?page=31
- rel prev = example.com/for-sale/stuff1?page=29
or
- rel canonical = example.com/for-sale/stuff1?page=30
- rel next = example.com/for-sale/stuff1?sortby=date_added&page=31
- rel prev = example.com/for-sale/stuff1?sortby=date_added&page=29
or
- rel canonical = example.com/for-sale/stuff1?page=30
- rel next = example.com/for-sale/stuff1?page=31
- rel prev = example.com/for-sale/stuff1?page=29
None of this feels right to me . I am thinking of using GWT to ask G-bot not to crawl any of the sort parameters ( date_added, price, a-z, z-a, umph-value, and so on ) and use
- rel canonical = example.com/for-sale/stuff1?sortby=date_added&page=30
- rel next = example.com/for-sale/stuff1?sortby=date_added&page=31
- rel prev = example.com/for-sale/stuff1?sortby=date_added&page=29
My doubts about this is that , will the link value that goes in to the pages with parameters be consolidated when I choose to ignore them via URL Parameters in GWT ? what do you guys think ?
-
Thanks Peter .
-
Thanks for your input.
IMHO...If I exclude ? , then paginated pages like ?page=xx wont be crawled , thus the rel=next prev tags on the page are rendered useless.
-
Yeah, it gets ugly fast, and even done "by the book" you're often going to need to monitor your index and make adjustments, I've found. That said, the official Google stance (at least the last I heard) is that you should canonical to the page with no parameters and rel=prev/next to the parameterized versions (your 2nd-to-last example):
- rel canonical = example.com/for-sale/stuff1?page=30
- rel next = example.com/for-sale/stuff1?sortby=date_added&page=31
- rel prev = example.com/for-sale/stuff1?sortby=date_added&page=29
See the bottom of this Google blog post:
http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html
The other option would be to use rel=prev/next on the paginated URLs and then dynamically Meta Noindex anything with parameters. Honestly, it really depends on what works, and it can take a while to sort out. Also, keep in mind that Bing doesn't handle rel=prev/next quite the same way as Google.
-
First of all: did you check this video? http://www.youtube.com/watch?feature=player_detailpage&v=njn8uXTWiGg
-
You can set the ? as exclude from searches in Webmaster Tool
-
I would always set rel="canonical" to the main page (category page): .
Check how big sites work with this issue.
-
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
-
Is dash problem for seo?
My web site http://www.green-lotus-trekking.com is this problem for google search engine optimization? Some little percentage problem or totally I am in Confusion?
Technical SEO | | agsln0 -
Problem of possible duplicate title tag and description. Help me!
Hi everybody, I'm optimizing this huge website that has a lot of identical categories for differente locations. I'm trying to find a smart way to write title and description for these categories, changing the location as a variable on the title and description phrase. Here some examples: Title: Attractions in [CITY]. Sightseeings, monuments and museums in [CITY]. Description: Find travel ideas and suggestions for [CITY]. On [NAME OF THE WEBSITE] you can find a lot of attractions, monuments and sightseeing off the beaten path in [CITY]. Changing only the name of the CITY on these Titles and Descriptions, am I running the risk of duplicate title and description? Thanks in advance for your help!
Technical SEO | | OptimizedGroup0 -
Rel="next"
Hi I was just wondering if there is any difference in using rel='next' rather than rel="next". Would it still work the same way? I mean using the apostrophes differently, would it matter? Thanks!
Technical SEO | | pikka0 -
Implementation of rel="next" & rel="prev"
Hi All, I'm looking to implement rel="next" & rel="prev", so I've been looking for examples. I looked at the source code for the MOZ.com forum, if anyone one is going to do it properly MOZ are. I noticed that the rel="next" & rel="prev" tags have been implemented in the a href tags that link to the previous and next pages rather than in the head. I'm assuming this is fine with Google but in their documentation they state to put the tags in the . Does it matter? Neil.
Technical SEO | | NDAY0 -
WordPress E-Commerce Plugin Duplicate Content Problem
I am working on a wordpress website that uses the WP E-Commerce plugin. I am using the Yoast seo plugin but not totally familiar with it. I have noticed that WP E-Commerce creates duplicate content issues. Here's an example: http://www.domain.com/parent-category/product-url-1/ is the same content as http://www.domain.com/parent-category/child-category/product-url-1/. I was wondering which of these following options are the best solution: 1. 301 redirect the multiple instances to one page
Technical SEO | | theanglemedia
2. noindex all but one instance
3. Use the canonical tag (i've used this tag before for telling SE's to use the www version of a page but not sure if it's the appropriate for this)
4. a combination of one of these 3 options? Thanks in advance!0 -
Should i use NoIndex, Follow & Rel=Canonical Tag In One Page?
I am having pagination problem with one of my clients site , So I am deciding to use noindex, follow tag for the Page 2,3,4 etc for not to have duplicated content issue, Because obviously SEOMoz Crawl Diagnostics showing me lot of duplicate page contents. And past 2 days i was in constant battle whether to use noindex, follow tag or rel=canonical tag for the Page 2,3,4 and after going through all the Q&A,None of them gives me crystal clear answer. So i thought "Why can't i use 2 of them together in one page"? Because I think (correct me if i am wrong) 1.noindex, follow is old and traditional way to battle with dup contents
Technical SEO | | DigitalJungle
2.rel=canonical is new way to battle with dup contents Reason to use 2 of them together is: Bot finds to the non-canonical page first and looks at the tag nofollow,index and he knows not to index that page,meantime he finds out that canonical url is something something according to the url given in the tag,NO? Help Please???0 -
Problems with seomoz profile section
Is anybody else having problems adding or changing their profile on seomoz? I make the changes it comes up saving then logs me out?
Technical SEO | | francesco270 -
Imlementation of Rel connical
http://www.seomoz.org/blog/complete-guide-to-rel-canonical-how-to-and-why-not This is an excellent post. But I couldn't find out one thing: all examples show the whle URL and I wonder if it's a problem to show a relative path instead is a problem? An example: you are on www.domain.com/articles/articles1.htm and you would like to Recl Connical to you are on www.domain.com/articles/articles2.htm Now, would both of these get it done right? Thanks, Andre
Technical SEO | | viventuraSEO0