In general I pretty much like the idea of canonicalization. And in most cases, Google explains possible procedures in a clear way.

For example: If I have duplicates because of parameters (eg: &sort=desc) it's clear to use the canonical for the site, provided the within the head-tag.

However I'm wondering how to handle "small - no to say thin content - sites". What's my definition of a small site? An Example: On one of my main sites, we use a directory based url-structure. Let's see:

  • example.com/ (root)
  • example.com/category-abc/
  • example.com/category-abc/produkt-xy/

Moreover we provide on page, that includes all products

  • example.com/all-categories/ (lists all products the same way as in the categories)

In case of reviews, we use a similar structure:

  • example.com/reviews/product-xy/ shows all review for one certain product
  • example.com/reviews/product-xy/abc-your-product-is-great/ shows one certain review
  • example.com/reviews/ shows all reviews for all products (latest first)

Let's make it even more complicated: On every product site, there are the latest 2 reviews at the end of the page. So you see, a lot of potential duplicates.

Q1: Should I create canonicals for

  • a: example.com/category-abc/ to example.com/all-categories/
  • b: example.com/reviews/product-xy/abc-your-product-is-great/ to example.com/reviews/product-xy/ or to example.com/review/ or none of them?

Q2: Can I link the collection of categories (all-categories/) and collection of all reviews (reviews/ and reviews/product-xy/) to the single category respectively to the single review.

Example: example.com/reviews/ includes - let's say - 100 reviews. Can I somehow use a markup that tells search engines: "Hey, wait, you are now looking at a collection of 100 reviews - do not index this collection, you should rather prefer indexing every single review as a single page!".

In HTML it might be something like that (which - of course - does not work, it's only to show you what I mean):

<div class="review" 
rel="canonical" href="http://example.com/reviews/product-xz/abc-your-product-is-great/">

Reason: I don't think it is a great user experience if the user searches for "your product is great" and lands on example.com/reviews/ instead of example.com/reviews/product-xy/abc-your-product-is-great/. On the first site, he will have to search and might stop because of frustration. The second result, however, might lead to a conversion.

The same applies for categories. If the user is searching for category-Z, he might land on the all-categories page and he has to scroll down to the (last) category, to find what he searched for (Z).

So what's best practice? What should I do?

closed as too localized by Simon Hayter, John Conde Apr 14 '13 at 15:35

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Quick question before answering your initial one: Are your different pages content exact duplications? If yes, the answer is easy, if no, how much duplication do you think are on the pages? 10%, 50%, more? – David K. Nov 22 '11 at 11:14
  • To be exact, we have 6 category pages. All these 6 are exactly the same way (100% dupl.) on the /all-categories/ sites. E.g. /category-a/ lists all products in cat. a with a short intro text (same for b, c, ...) then the /all-categories/ site lists cat a, b, c... This might help you: pastebin.com/Z8DZ4Ms5 - same applies for reviews. A single review shows up as a single review page, on the product's reviews page and on the /reviews/ page. As it might be ok to "combine" categories to one site, I (and users) pretty much prefer the single review site to collections. – ptmr.io Nov 22 '11 at 12:07

Browse other questions tagged or ask your own question.