Should I use rel=canonical on similar product pages.
-
I'm thinking of using rel=canonical for similar products on my site.
Say I'm selling pens and they are al very similar. I.e. a big pen in blue, a pack of 5 blue bic pens, a pack of 10, 50, 100 etc. should I rel=canonical them all to the best seller as its almost impossible to make the pages unique. (I realise the best I realise these should be attributes and not products but I'm sure you get my point)
It seems sensible to have one master canonical page for bic pens on a site that has a great description video content and good images plus linked articles etc rather than loads of duplicate looking pages.
love to hear thoughts from the Moz community.
-
There's no perfect solution, but Google's advice is to use rel=prev/next. This looks like pretty classic pagination. Rel-canonical is a stronger signal, but it's generally going to keep pages 2+ from ranking.
-
Dr. Pete,
I have a internal debate going and I was hoping you might be a tie breaker on rel=canonical vs noindex given these paginated pages and might be a good use case for others:
https://www.newhomesource.com/communityresults/market-269/citynamefilter-cedar-park
https://www.newhomesource.com/communityresults/market-269/citynamefilter-cedar-park/page-2
The individual list items are unique, but clearly want to rank for essentially the exact same terms. Page titles, metas, copy about cit is the same. Just the list elements are different, but not a 12 pack of pens, 24 pack etc. Is this tricky or clear?
-
Thank you Sir. I think we reached the same conclusion.
By the way, the it was a just a simple example of the page hierarchy - we're not doing Horror Books
-
I haven't heard any SEO recommendations or benefits regarding rel="contents". Rel=prev/next has mixed results, but I'd generally only use it for its specific use case of paginated content.
I guess you could treat V2 as "pages" within V1. If you did that, what you'd need to do is treat the main page as a "View All" page and link to it from each author page. I'm not sure if that's the best approach, but it's more or less Google-approved.
If the site has decent authority and we're only talking 100s of pages, I might let them all live in the index and see what happens. Let Google sort it out, and then decide if you're ok with the outcome. If the site is low authority and/or we're talking 1000s of pages, I might be more cautious.
It's hard to speak in generalities - it depends a lot on the quality of the site and nature of the pages, including how much that content is available/duplicated across the web. One problem here is that author pages with lists of books probably exist on many sites, so you have to differentiate yourself.
-
Good. Same page
I was looking in to rel=contents and those variations before, but I can't quite decide whether this is worth the effort or not.
e.g. There's a huge list of resources on a single page, segmented in to categories. The page is HUGE and takes ages to load, so I've been creating new pages for each segment and optimising those pages independently, but there is some common content with the primary page.
V1: Horror Novels page has a section for each author, each section lists all novels by that author.
V2: Each Author has a page which lists novels by that author, but links back to the Horror Novels page which is essentially an index of the Author pages. Would you also
Would you use rel=contents, rel=prev/next or a different approach in this case? From what I've read so far, there doesn't seem any "SEO value" in linking that way.
I guess we're trying to improve the UX through faster load times and segmenting the information in smaller chunks, but also presenting a number of pages to Google as a body of content rather than a single page without causing issues with duplicate or similar content - we just need to make sure that we're optimising it in the right way, of course.
-
I would Meta Noindex an "email this page" template. It has no value for SERPs, it's generally at the end of a path, and no one is going to link to it. Just keep it out of the index altogether.
-
Thanks Pete
So, for a more specific example, if an eCommerce store has an "email this product" page for each product (Magento seems to love doing this and creates a duplicate of the same email page for every product), would you recommend a canonical link for each of those pages to the main Contact page or canonically linking each page to each related product page?
From setup, I'd consider NoIndex on all of those pages anyway, but it's a bit late for that once a site has been live for years.
The email pages are obviously related to the product page, but the content there isn't anywhere near identical.
Or maybe there's a "more appropriate solution" that you alluded to?
-
To clarify, that's the official stance - rel=canonical should only be used on true duplicates (basically, URL variants of the same page). In practice, rel=canonical works perfectly well on near-duplicates, and sometimes even on wildly different pages, but the more different you get, the more caution you should exercise. If the pages are wildly different, it's likely there are more appropriate solutions.
-
Hey Pete
Can you explain, "you can't use rel=canonical on pages that aren't 100% duplicates" a little further please?
Do you mean that only duplicate pages should be canonicalised? Identical pages in two different sub-directories is fine, but two similar pages is not?
-
So, here's the problem - if you follow the official uses of our options, then there is no answer. You can't have thin content or Google will slap you with Panda (or, at the very least, devalue your rankings, you can't use rel=canonical on pages that aren't 100% duplicates, and you're not supposed to (according to Google) just NOINDEX content. The official advice is: "Let us sort it out, but if we don't sort it out, we'll smack you down."
I don't mean that to be critical of your comment, but I'm very frustrated with the official party line from Google. Practically speaking, I've found index control to be extremely effective even before Panda, and critical for big sites post-Panda. Sometimes, that means embracing imperfect solutions. The right tool for any situation can be complex (and it may be a combination of tools), but rel=canonical is powerful and often effective, in my experience.
-
It seems to me that for most ecommerce sites (myself included) that canonical is not the answer. If you have to many near identical products on your site it may be better to re evaluate what you have stocking and if you must stock them then the way forward is to make one page that properly explains them and allows purchase rather than many.
The only uses I can see for canonical is to consolidate old blogs and articles on similar topics. Using it to tidy an ecommerce site seems to be a misuse of the tool.
-
This can get tricky when you dive into the details, but I general agree with Takeshi and EGOL - consolidate or canonicalize. If the products are different brands/versions of a similar item, it's a bit trickier, but these variations do have a way of spinning out of control. In 2013, I think the down side of your index running wild is a lot higher than the up side of ranking for a couple more long-tail terms. It does depend a lot on your traffic, business model, etc., though. I'm not sure any of us can adequately advise you in the scope of a Q&A.
-
Also I forgot to mention that in this way you also don't have to worry about creating tons of different product descriptions because you will put one description for, let's say, 6 different products.
the way we built it, allow us to have just product group pages are reachable; the products pages are indexed and crawled and they have to be there otherwise the whole system wouldn't work, but no optimization is done on them and customers can't see it.
-
Hello there,
I manage an e-commerce site and because we have similar products and issues with duplicate content we have implemented product groups pages with a drop-down menu' listing the different options for a particular product and then we have used the rel="canonical" with the different product pages. In this way we have solved this issue and it works very well.
If you do implement it, make sure every passage is done correctly otherwise, as Matt Cutts says, you will have an headache trying to sort it out.
Hope it helps
-
Those pen offers are very very similar. Identical product descriptions except for perhaps number being sold or color or width of the tip.
If these were on my site they would all be on the same page. One page to concentrate/conserve the linkjuice. One page to make thicker content. One page to present all of the options to the customer at same time. (PITA to click between lots of pages to make up your mind as a shopper). One page to make maintenance easy.
-
Thanks
-
Yes, I've used this approach for a number of ecommerce clients, and it is very effective. There are many advantages to this approach:
- Eliminating duplicate/thin content across the site
- Focusing link value on a single page instead of spreading out across multiple products
- Less effort creating unique content (one page vs multiple)
- Potentially better user experience
Of course, if you have the resources to write unique content for each of your product pages, that is going to be a better solution. You can still create a landing page in this instance, you just wouldn't canonical the product pages to it.
-
Have you used this approach? If so how effective is it?
-
If you want to rank for "flat head screw driver", the canonical approach can still work. Simply create a landing page for flat head screw drivers, and include all of the flat head screwdriver products from each of the different brands. Then canonical each of the individual product pages up to the main landing page.
-
I have all the usual colour size attributes on my products. I just used that as a simple example. Its more to do with similar non branded products that are different enough to be "products" but not when I have 15 similar it's impossible to write fully different descriptions. Screwdrivers, screws or paint would have been a better example. There are hundreds of ranges like that. If you had five unimportant brands of screwdriver and you had flat head and philips head. Each one is marginally different (handle style etc) but there is no keyword benefit to having each optimised for say "flat head screwdriver". Having a good range is beneficial to the customer but seems to be detrimental to SEO. Is it better to employ writers to make every description different no matter how complex or should I canonical it?
-
Yes, that is a good solution, especially in this post-Panda world. Ideally you would just have one page for Bic pens, with a drop down from which you can select different options such as colors & size. If your shopping cart system doesn't allow you to do that, then the canonical is a good approach. This cuts down on the amount of duplicate content you have and the amount of unique content you need to create.
-
Have a client in the exact same situation. Check to see if you are currently getting traffic for terms that would be specific to having separate pages (e.g. "50 blue bic pens" versus a more general "bic blue pens"). If you don't, then you should canonical to one page. If you do, I'd keep it as is and work on diversifying the product pages more.
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
-
Dynamic referenced canonical pages based on IP region and link equity question
Hi all, My website uses relative URLs that has PHP to read a users IP address, and update the page's referenced canonical tag to an region specific absolute URL for ranking / search results. E.g. www.example.com/category/product - relative URL referenced for internal links / external linkbuilding If a US IP address hits this link, the URL is the same, but canonicalisation is updated in the source to reference www.example.com**/us/**category/product, so all ranking considerations are pointed to that page instead. None of these region specific pages are actually used internally within the site. This decision was done so external links / blog content would fit a user no matter where they were coming from. I'm assuming this is an issue in trying to pass link equity with Googlebot, because it is splitting the strength between different absolute canonical pages depending on what IP it's using to crawl said links (as the relative URL will dynamically alter the canonical reference which is what ranking in SERPs) Any assistance or information no matter how small would be invaluable. Thanks!
Intermediate & Advanced SEO | | MattBassos0 -
Product page as homepage
Hello, Is it ok that to use the homepage of website as a product page directly where you present all your products on your homepage or can it penalise you to do that ? and in that case, is it better to have a homepage that you don't rank and create a subpage for your product page. Thank you,
Intermediate & Advanced SEO | | seoanalytics1 -
Migrating to WooCommerce, similar product descriptions but with different urls, cant use variations.
Hi! Ime quite new to SEO and to woocommerce so please help out with this one.. We are migrating from Ithemes Exchange over to WooCommerce and i have come up with some issues. We are selling adhesives and some of the products have the same name and description, the only thing that seperates them are sometimes the widht, or the length on the roll.. As we have it now we have a separate product page for each widht and length. For example here http://siga-sverige.se/siga/fentrim-2-100/ and here http://siga-sverige.se/siga/fentrim-2-150/ The above product pages are for a product called Fentrim 2. its availiable in widhts from 75 to 300mm.. so, its six diffent products pages with more or less the same description. I get that this will create duplicate content, couse the description on the pages are similar.. We cant use variations in woocommerce, couse this cant be set up to exactly match our shipping needs, so, we need them on separate pages.. Soo, my plan is to set a new product page for Fentrim 2, ex http://siga-sverige.se/siga/fentrim-2 and then set that url as canonical url for the variations of the product.. Am i on the right track? Gratefull for any help on this one! / Jonas
Intermediate & Advanced SEO | | knubbz1 -
Thinking about not indexing PDFs on a product page
Our product pages generate a PDF version of the page in a different layout. This is done for 2 reasons, it's been the standard across similar industries and to help customers print them when working with the product. So there is a use when it comes to the customer but search? I've thought about this a lot and my thinking is why index the PDF at all? Only allow the HTML page to be indexed. The PDF files are in a subdomain, so I can easily no index them. The way I see it, I'm reducing duplicate content On the flip side, it is hosted in a subdomain, so the PDF appearing when a HTML page doesn't, is another way of gaining real estate. If it appears with the HTML page, more estate coverage. Anyone else done this? My knowledge tells me this could be a good thing, might even iron out any backlinks from being generated to the PDF and lead to more HTML backlinks Can PDFs solely exist as a form of data accessible once on the page and not relevant to search engines. I find them a bane when they are on a subdomain.
Intermediate & Advanced SEO | | Bio-RadAbs0 -
Using Pagination for eComm Reviews Pages
Hi All, An eComm site has product pages where only 10 customer reviews are found in the source code on the product page, no matter how many reviews the product actually has. ALL reviews (including the 10 displayed on the product page) are located on a subdomain, split into many pages dependong on how many reviews a certain product has (some have well over 100 unique reviews). Reviews page: http://reviews.americanmuscle.com/0065-en_us/charcoalamr-18x8-0512-pirelli-stan/american-muscle-wheels-amr-charcoal-wheel-pirelli-tire-kit-18x8-05-14-all-reviews/reviews.htm Corresponding product page: http://www.americanmuscle.com/charcoalamr-18x8-0512-pirelli-stan.html I'm fearing a Panda related problem here, especially since thousands of products have only 1 or two reviews, duplicated on the reviews.americanmuscle.com page and the corresponding product page. I also do not want to lose the unique content on the second and third reviews pages simply by noindexing/canonicaling them to the product page. My question is whether or not I can paginate the reviews.am pages in a way that the product page is "page 1" and the first reviews page is "page 2," second reviews.am page is "page 3" and so forth. Are there issues associated with domain-to-subdomain pagination? Can I utilize the pagination tab in this manner in the first place? There are currently more than 57,000 of these review.americanmuscle.com pages in the index that I would like to clean up so any/all suggestions are appreciated.
Intermediate & Advanced SEO | | andrewv0 -
Trailing slash and rel="canonical"
Our website is in a directory format: http://www.website.com/website.asp Our homepage display URL is http://www.website.com which currently matches our to eliminate the possibility of duplicate content. However, I noticed that in the SERPs, google displays the homepage with a trailing slash http://www.website.com/ My question: should I change the rel="canonical" to have a trailing slash? I noticed one of our competitors uses the trailing slash in their rel="canonical" Do potential benefits outweigh the risks? I can PM further information if necessary. Thanks for the assistance in advance...
Intermediate & Advanced SEO | | BethA0 -
Canonical links apparently not used by google
hi, I do have an ecommerce website (www.soundcreation.ro) which in the last 3 months had a drop in the SERP. Started to look around in GWT what is happening. Google is reporting a lot of duplicate meta-tags (and meta-titles problem). But 99% of them had already canonical links setted. I tried to optimize my product listings with the new "prev", "next" tags and introduced also the "view-all" canonical link to help Google identify the appropiate product listing pages. SeoMoz is not reporting thos duplicate meta issues. Here is an example of the same page with different links, but with the same common canonical and reported by GWT "duplicate title tag": http://www.soundcreation.ro/chitare-chitari-electroacustice-cid10-pageall/http://www.soundcreation.ro/chitare-chitari-electroacustice-cid10/http://www.soundcreation.ro/chitare-chitari-electroacustice-cid10_999/http://www.soundcreation.ro/chitare-electro-acustice-cid10_1510/What could be the issue?- only that gwt is not refreshing as should be, keeping old errors?- if so, then there is an other serious issue because of why our PR is dropping on several pages?- do we have other problem with the site, which ends up with google penalizing us? Thank you for your ideas!
Intermediate & Advanced SEO | | bjutas0 -
What to do with non-existing products (removed products)?
Hello, I'm selling unique products - only one of a kind of each product.
Intermediate & Advanced SEO | | BeytzNet
This means that whenever a product is sold, it is removed from display. In order not to upset Google by keep removing indexed pages I created a "sold items" page which links to all of the removed products. The problem is (or maybe it's not a problem) is that I got to the point where I have more "sold items" then existing items (and the list keeps adding up). What should I do with the non-existing items?
Was I correct? ---------------------------------------- ADDED INFO --------- The way the site is built is that I have main category pages and each of them is showing a large amount of products. Most of these products got indexed by Google. Each product has its own unique URL (Products do not return...) Once a product is sold it does not come up in the product categories - I only have a general "sold items" in the footer that shows all of them (with a lot of pagination). Since the products are rapidly changing, i thought it would upset Google to have a hundred 301 redirects in each week or two. Since the products are very similar to one another (only different measurements / colors etc.), I thought of having a link from a sold Item to a similar available item so if Google will direct someone it will probably be to the available product. The problem is that the sold items are now 4 times more than the number of available items... I don't think that a store should display 2008's t-shirts on 2012... Another problem that may rise with so many products is that I'm afraid that the one type of product that is being sold much more often will take charge at the end on the entire site since I will end up with 8,000 sold items of this product, 1000 sold items of other products and 1000 available misc products... this might also start causing duplication problems as the products are quite similar. Should I stop with the "Sold" products and use 301's? Thanks0