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.
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
-
Index, follow on a paginated page with a different rel=canonical URL
Hello, I have a question about meta robots ="index, follow" and rel=canonical on category page pagination. Should the sorted page be <meta name="robots" content="index,follow"></meta name="robots" content="index,follow"> since the rel="canonical" is pointing to a separate page that is different from the URL? Any thoughts on this topic would be awesome. Thanks. Main Category Page
Intermediate & Advanced SEO | | Choice
https://www.site.com/category/
<meta name="robots" content="index,follow"><link rel="canonical" href="https: www.site.com="" category="" "=""></link rel="canonical" href="https:></meta name="robots" content="index,follow"> Sorted Page
https://www.site.com/category/?p=2&dir=asc&order=name
<meta name="robots" content="index, follow"=""><link rel="canonical" href="https: www.site.com="" category="" ?p="2""></link rel="canonical" href="https:></meta name="robots" content="index,> As you can see, the meta robots is telling Google to index https://www.site.com/category/?p=2&dir=asc&order=name , yet saying the canonical page is https://www.site.com/category/?p=2 .0 -
Best Practices for Title Tags for Product Listing Page
My industry is commercial real estate in New York City. Our site has 300 real estate listings. The format we have been using for Title Tags are below. This probably disastrous from an SEO perspective. Using number is a total waste space. A few questions:
Intermediate & Advanced SEO | | Kingalan1
-Should we set listing not no index if they are not content rich?
-If we do choose to index them, should we avoid titles listing Square Footage and dollar amounts?
-Since local SEO is critical, should the titles always list New York, NY or Manhattan, NY?
-I have red that titles should contain some form of branding. But our company name is Metro Manhattan Office Space. That would take up way too much space. Even "Metro Manhattan" is long. DO we need to use the title tag for branding or can we just focus on a brief description of page content incorporating one important phrase? Our site is: w w w . m e t r o - m a n h a t t a n . c o m <colgroup><col width="405"></colgroup>
| Turnkey Flatiron Tech Space | 2,850 SF $10,687/month | <colgroup><col width="405"></colgroup>
| Gallery, Office Rental | Midtown, W. 57 St | 4441SF $24055/month | <colgroup><col width="405"></colgroup>
| Open Plan Loft |Flatiron, Chelsea | 2414SF $12,874/month | <colgroup><col width="405"></colgroup>
| Tribeca Corner Loft | Varick Street | 2267SF $11,712/month | <colgroup><col width="405"></colgroup>
| 275 Madison, LAW, P7, 3,252SF, $65 - Manhattan, New York |0 -
Mass uploading low quality product pages
Hi Mozzers! I have a question on mass uploading low quality product pages We have a huge catalogue of products and our product managers are looking to mass reference 17,000 new products quickly on the website. Obviously, this will mean content will somehow have to be made unique - which would take a huge amount of resource. Apart from this issue, will adding this many new product pages in one go be bad for SEO? If we also do manage to make the content unique, but not high quality - we'll have 17,000 new low quality product pages - will this reduce our domain authority? Becky
Intermediate & Advanced SEO | | BeckyKey1 -
Should I Keep adding 301s or use a noindex,follow/canonical or a 404 in this situation?
Hi Mozzers, I feel I am facing a double edge sword situation. I am in the process of migrating 4 domains into one. I am in the process of creating URL redirect mapping The pages I am having the most issues are the event pages that are past due but carry some value as they generally have one external followed link. www.example.com/event-2008 301 redirect to www.newdomain.com/event-2016 www.example.com/event-2007 301 redirect to www.newdomain.com/event-2016 www.example.com/event-2006 301 redirect to www.newdomain.com/event-2016 Again these old events aren't necessarily important in terms of link equity but do carry some and at the same time keep adding multiple 301s pointing to the same page may not be a good ideas as it will increase the page speed load time which will affect the new site's performance. If i add a 404 I will lose the bit of equity in those. No index,follow may work since it won't index the old domain nor the page itself but still not 100% sure about it. I am not sure how a canonical would work since it would keep the old domain live. At this point I am not sure which direction I should follow? Thanks for your answers!
Intermediate & Advanced SEO | | Ideas-Money-Art0 -
301 and Canonical - is using both counterproductive
A site lost a great deal of traffic in July, which appears to be from an algorithmic penalty, and hasn't recovered yet. It appears several updates were made to their system just before the drop in organic results. One of the issues noticed was that both uppercase and lowercase urls existed. Example urls are: www.domain.com/product123
Intermediate & Advanced SEO | | ABK717
www.domain.com/Product123 To clean this up, a 301 redirect was implemented a few months ago. Another issue found was that many product related urls had a parameter added to the url for a tracking purpose. To clean this up, the tracking parameters were removed from the system and a canonical tag was implemented as these pages were also found in Google's index. The tag forced a page such as www.domain.com/product123?ref=topnav to be picked up as www.domain.com/product123. So now, there is a 301 to address the upper and lowercase urls and a canonical tag to address the parameters from creating more unnecessary urls. A few questions here: -Is this redunant and can cause confusion to the serps to have both a canonical and 301 redirect on the same page? -Both the 301 and canonical tag were implemented several months ago, yet Google's index is still showing them. Do these have to be manually removed with GWT individually since they are not in a subfolder or directory? Looking forward to your opinions.0 -
SEO structure question: Better to add similar (but distinct) content to multiple unique pages or make one unique page?
Not sure which approach would be more SEO ranking friendly? As we are a music store, we do instrument repairs on all instruments. Currently, I don't have much of any content about our repairs on our website... so I'm considering a couple different approaches of adding this content: Let's take Trumpet Repair for example: 1. I can auto write to the HTML body (say, at the end of the body) of our 20 Trumpets (each having their own page) we have for sale on our site, the verbiage of all repairs, services, rates, and other repair related detail. In my mind, the effect of this may be that: This added information does uniquely pertain to Trumpets only (excludes all other instrument repair info), which Google likes... but it would be duplicate Trumpet repair information over 20 pages.... which Google may not like? 2. Or I could auto write the repair details to the Trumpet's Category Page - either in the Body, Header, or Footer. This definitely reduces the redundancy of the repeating Trumpet repair info per Trumpet page, but it also reduces each Trumpet pages content depth... so I'm not sure which out weighs the other? 3. Write it to both category page & individual pages? Possibly valuable because the information is anchoring all around itself and supporting... or is that super duplication? 4. Of course, create a category dedicated to repairs then add a subcategory for each instrument and have the repair info there be completely unique to that page...- then in the body of each 20 Trumpets, tag an internal link to Trumpet Repair? Any suggestions greatly appreciated? Thanks, Kevin
Intermediate & Advanced SEO | | Kevin_McLeish0 -
Certain Product Pages Not Indexing
Hey All, We discovered an issue where new product pages on our site were not getting indexed because a "noindex" tag was inadvertently being added to section when those pages were created. We removed the noindex tag in late April and some of the pages that had not been previously indexed are now showing up, but others are still not getting indexed and I'd appreciate some help on why this could be. Here is an example of a page that was not in the index but is now showing after removal of noindex: http://www.cloud9living.com/san-diego/gaslamp-quarter-food-tour And here is an example of a page that is still not showing in the index: http://www.cloud9living.com/atlanta/race-a-ferrari UPDATE: The above page is now showing after I manually submitted it in WMT. I had previously submitted another page like a month ago and it was still not indexing so I thought the manual submission was a dead end. However, it just so happens that the above URL just had its Page Title and H1 updated to something more specific and less duplicative so I am currently running a test to see if that's the problem with these pages not indexing. Will update this soon. Any suggestions? Thanks!
Intermediate & Advanced SEO | | GManSEO0 -
We are changing ?page= dynamic url's to /page/ static urls. Will this hurt the progress we have made with the pages using dynamic addresses?
Question about changing url from dynamic to static to improve SEO but concern about hurting progress made so far.
Intermediate & Advanced SEO | | h3counsel0