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.
-
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
-
Rel Sponsored on Internal Links
Hi all. Should you use rel sponsored on internal links? Here is the scenario: a company accepts money from one of their partners to place a prominent link on their home page. That link goes to an internal page on the company's website that contains information about that partner's service. If this was an external link that the partner was paying for, then you would obviously use rel="sponsored" but since this is a link that goes from awebsite.com to awebsite.com/some-page/, it seems odd to qualify that link in this way. Does this change if the link contains a "sponsored" label in the text (not in the rel qualifier)? Does this change if this link looks more like an ad (i.e. a banner image) vs. regular text (i.e. a link in a paragraph)? Thanks for any and all guidance or examples you can share!
Technical SEO | | Matthew_Edgar0 -
how to set rel canonical on wordpress.com sites
I know how to do this with a wordpress.org site but I have a client that does not want to switch and without a plugin I am lost. any help would be greatly appreciated. Jeremy Wood
Technical SEO | | SOtBOrlando0 -
Rel=Canonical for filter pages
Hi folks, I have a bit of a dilemma that I'd appreciate some advice on. We'll just use the solid wood flooring of our website as an example in this case. We use the rel=canonical tag on the solid wood flooring listings pages where the listings get sorted alphabetically, by price etc.
Technical SEO | | LukeyB30
e.g. http://www.kensyard.co.uk/products/category/solid-wood-flooring/?orderBy=highestprice uses the canonical tag to point to http://www.kensyard.co.uk/products/category/solid-wood-flooring/ as the main page. However, we also uses filters on our site which allows users to filter their search by more specific product features e.g.
http://www.kensyard.co.uk/products/category/solid-wood-flooring/f/18mm/
http://www.kensyard.co.uk/products/category/solid-wood-flooring/f/natural-lacquered/ We don't use the canonical tag on these pages because they are great long-tail keyword targeted pages so I want them to rank for phrases like "18mm solid wood flooring". But, in not using the canonical tag, I'm finding google is getting confused and ranking the wrong page as the filters mean there is a huge number of possible URLs for a given list of products. For example, Google ranks this page for the phrase "18mm solid wood flooring" http://www.kensyard.co.uk/products/category/solid-wood-flooring/f/18mm,116mm/ This is no good. This is a combination of two filters and so the listings are very refined, so if someone types the above phrase into Google and lands on this page their first reaction will be "there are not many products here". Google should be ranking the page with only the 18mm filter applied: http://www.kensyard.co.uk/products/category/solid-wood-flooring/f/18mm How would you recommend I go about rectifying this situation?
Thanks, Luke0 -
Using Rel=Author with Multiple Contributors
I have multiple contributors who provide content on our page. I have created an authors page that shows the picture and bio of each author along with their Google+ profile link. Each profile link goes to the authors respective profile where I have had them verify themselves as contributors. My question is will Google see each of these authors and attribute the rel=author tag correctly (even though they are listed on the same profile page) or will Google only take the first person I point to for Rel=Author?
Technical SEO | | PLEsearch0 -
ECommerce categories in path name or alternative
Our store is in magento and many recommend to turn of category names in product paths as magento creates duplicate pages for the same content when products are in multiple categories. I have a canonical plugin that should fix dup paths. This has not bothered me until I decided to create GA goals for seeing multiple products and realized I dont have an easy filter because the paths dont have categories. I think I can add a suffix to products like /?t=p - If I can do so will that be enough for me to create goals in GA - or am I better off adding back category paths.
Technical SEO | | JohnBerger0 -
Problem wth Crawling
Hello, I have a website http://digitaldiscovery.eu here in SEOmoz. Its strange since the last week SEOmoz is crawling only one page! And before it was crwaling all the pages. Whats happening? Help SEOmoz! :))
Technical SEO | | PedroM0 -
Rel=canonical issue
Re. http://www.appetise.com. We have been alerted that we are "not making appropriate use of the rel=canonical tag". Please could someone just clarify this for us and let us know the recommended remedial action we need to take to rectify the issue? Many Thanks, RB
Technical SEO | | E-resistible0 -
Large Scale Ecommerce. How To Deal With Duplicate Content
Hi, One of our clients has a store with over 30,000 indexed pages but less then 10,000 individual products and make a few hundred static pages. Ive crawled the site in Xenu (it took 12 hours!) and found it to by a complex mess caused by years of hack add ons which has caused duplicate pages, and weird dynamic parameters being indexed The inbound link structure is diversified over duplicate pages, PDFS, images so I need to be careful in treating everything correctly. I can likely identify & segment blocks of 'thousands' of URLs and parameters which need to be blocked, Im just not entirely sure the best method. Dynamic Parameters I can see the option in GWT to block these - is it that simple? (do I need to ensure they are deinxeded and 301d? Duplicate Pages Would the best approach be to mass 301 these pages and then apply a no-index tag and wait for it to be crawled? Thanks for your help.
Technical SEO | | LukeyJamo0