Duplicate Content Issues on Product Pages
-
Hi guys
Just keen to gauge your opinion on a quandary that has been bugging me for a while now.
I work on an ecommerce website that sells around 20,000 products.
A lot of the product SKUs are exactly the same in terms of how they work and what they offer the customer. Often it is 1 variable that changes. For example, the product may be available in 200 different sizes and 2 colours (therefore 400 SKUs available to purchase).
Theese SKUs have been uploaded to the website as individual entires so that the customer can purchase them, with the only difference between the listings likely to be key signifiers such as colour, size, price, part number etc.
Moz has flagged these pages up as duplicate content.
Now I have worked on websites long enough now to know that duplicate content is never good from an SEO perspective, but I am struggling to work out an effective way in which I can display such a large number of almost identical products without falling foul of the duplicate content issue.
If you wouldnt mind sharing any ideas or approaches that have been taken by you guys that would be great!
-
The canonical should pass link equity similar to a 301 redirect.
-
Thanks Mike. It certainly sounds like moving all SKUs onto 1 page is preferable. I suspect that I may need to spend a bit of dosh getting the website's on-page structure amended if going down this approach.
With regards to point 1, I assume the pages will still be crawled but any link equity would be passed to the canonicalised version of the page?
-
I agree with Everett from a standpoint of User Experience. It could potentially be better for users if they appeared on a product page where they could then choose color, size, etc. variables for their product instead of having to click through multiple pages to find the right one or scroll through a huge list of variations.
The reduction in pages should also help consolidate link equity and keep pages from cannibalizing each other in the SERPs.
As for Takeshi's suggestion on Canonicals, I'm a fan of the rel=canonical tag but the potential problem with using them in this instance is twofold. 1) As Takeshi mentioned: "as far as Google is concerned you only have 1 page with the content on it" and 2) Canonicals are suggestions not directives so the search engines may choose not to recognize it if not used properly.
-
As I said, that would be a good second choice, but I'd go with the first option (putting all product variants like size/color on the same page and allowing the user to select which one/s they want to purchase) because the other options still leave a potentially huge amount of product URLs out there for Google to crawl.
Google has to crawl them to see the rel canonical tag. You may only have a certain amount of crawl budget. If you can cut down the amount of URLs on your site that Google has to crawl by as much as half simply by allowing users to select a variant color or size on a product page I think that is best for SEO, as well as for user experience.
-
Thanks for the advice guys.
What do you think of Takeshi's advice below regarding adding canonical link to product page that points to a product category page
I.e. we have 20 of the same jumpers of different sizes, colours. A canonical tag is added to the product page that points to a parent page for the jumper, rather than the specific product page.
-
Thanks Takeshi - this approach sounds like something I can implement sooner rather than later.
Have you had success using it?
-
Thanks Mike - this certainly makes sense.
My product pages do not currently change the URL parameters depending ont he product sku the visitor changes , but the approach you've taken sounds perfect for your setup
-
Similar to what BJS1976 and Takeshi stated, the way we handled the bulk of duplicate content issues from a similar circumstance for our ecommerce site was handling the different varieties of the same product through parameters and then canonicalizing the parameters to the version of the URL sans parameter.
For example, due to database reasons /product1.php?color=42 and /product1.php?color=30 are the same product but one is red and one is blue, the pages are exactly the same & have radials/buttons/dropdowns to choose any available color, /product1.php would default to one specific variation we chose (usually the best selling color) and then /product1.php?color=42 and /product1.php?color=30 had a rel=canonical tag added pointing at /product1.php
For any remaining products flagged as duplicates that couldn't be fixed that way, we set those aside to have myself and another copywriter work on creating further content that would set them apart enough as to not be duplicates.
-
BJS1976 makes some good suggestions.
Another option is to create a category type page that lists all the product variations on it, then canonical each of the individual products to the category page. That way, you still have multiple product pages, but as far as Google is concerned you only have 1 page with the content on it.
-
Hi there,
I'm also working on an ecom site using Magento - in short, there are a couple of ways that come to mind in how to deal with this:
-
Create grouped or configurable products that bring these simple products into 1 single product - customer then chooses size and colour for example.
-
Rewrite a lot of unique content in the product descriptions for each variation.
In my experience, sales convert better on option 1, plus my gut tells me they are favoured by Google.
Good luck!
-
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
-
Issues with Duplicates and AJAX-Loader
Hi, On one website, the "real" content is loaded via AJAX when the visitor clicks on a tile (I'll call a page with some such tiles a tile-page here). A parameter is added to the URL at the that point and the content of that tile is displayed. That content is available via an URL of its own ... which is actually never called. What I want to achieve is a canonicalised tile-page that gets all of the tiles' content and is indexed by google - if possible with also recognising that the single-URLs of a tile are only fallback-solutions and the "tile-page" should be displayed instead. The current tile-page leads to duplicate meta-tags, titles etc and minimal differences between what google considers a page of its own (i.e. the same page with different tiles' contents). Does anybody have an idea on what one can do here?
Technical SEO | | netzkern_AG0 -
Content relaunch without content duplication
We write great Content for blog and websites (or at least we try), especially blogs. Sometimes few of them may NOT get good responses/reach. It could be the content which is not interesting, or the title, or bad timing or even the language used. My question for the discussion is, what will you do if you find the content worth audience's attention missed it during its original launch. Is that fine to make the text and context better and relaunch it ? For example: 1. Rechristening the blog - Change Title to make it attractive
Technical SEO | | macronimous
2. Add images
3. Check spelling
4. Do necessary rewrite, spell check
5. Change the timeline by adding more recent statistics, references to recent writeups (external and internal blogs for example), change anything that seems outdated Also, change title and set rel=cannoical / 301 permanent URLs. Will the above make the blog new? Any ideas and tips to do? Basically we like to refurbish (:-)) content that didn't succeed in the past and relaunch it to try again. If we do so will there be any issues with Google bots? (I hope redirection would solve this, But still I want to make sure) Thanks,0 -
Duplicate content on Product pages for different product variations.
I have multiple colors of the same product, but as a result I'm getting duplicate content warnings. I want to keep these all different products with their own pages, so that the color can be easily identified by browsing the category page. Any suggestions?
Technical SEO | | bobjohn10 -
Container Page/Content Page Duplicate Content
My client has a container page on their website, they are using SiteFinity, so it is called a "group page", in which individual pages appear and can be scrolled through. When link are followed, they first lead to the group page URL, in which the first content page is shown. However, when navigating through the content pages, the URL changes. When navigating BACK to the first content page, the URL is that for the content page, but it appears to indexers as a duplicate of the group page, that is, the URL that appeared when first linking to the group page. The client updates this on the regular, so I need to find a solution that will allow them to add more pages, the new one always becoming the top page, without requiring extra coding. For instance, I had considered integrating REL=NEXT and REL=PREV, but they aren't going to keep that up to date.
Technical SEO | | SpokeHQ1 -
How to prevent duplicate content at a calendar page
Hi, I've a calender page which changes every day. The main url is
Technical SEO | | GeorgFranz
/calendar For every day, there is another url: /calendar/2012/09/12
/calendar/2012/09/13
/calendar/2012/09/14 So, if the 13th september arrives, the content of the page
/calendar/2012/09/13
will be shown at
/calendar So, it's duplicate content. What to do in this situation? a) Redirect from /calendar to /calendar/2012/09/13 with 301? (but the redirect changes the day after to /calendar/2012/09/14) b) Redirect from /calendar to /calendar/2012/09/13 with 302 (but I will loose the link juice of /calendar?) c) Add a canonical tag at /calendar (which leads to /calendar/2012/09/13) - but I will loose the power of /calendar (?) - and it will change every day... Any ideas or other suggestions? Best wishes, Georg.0 -
I am trying to correct error report of duplicate page content. However I am unable to find in over 100 blogs the page which contains similar content to the page SEOmoz reported as having similar content is my only option to just dlete the blog page?
I am trying to correct duplicate content. However SEOmoz only reports and shows the page of duplicate content. I have 5 years worth of blogs and cannot find the duplicate page. Is my only option to just delete the page to improve my rankings. Brooke
Technical SEO | | wianno1680 -
Duplicate Page Content
Hi within my campaigns i get an error "crawl errors found" that says duplicate page content found, it finds the same content on the home pages below. Are these seen as two different pages? And how can i correct these errors as they are just one page? http://poolstar.net/ http://poolstar.net/Home_Page.php
Technical SEO | | RouteAccounts0 -
Duplicate content issues caused by our CMS
Hello fellow mozzers, Our in-house CMS - which is usually good for SEO purposes as it allows all the control over directories, filenames, browser titles etc that prevent unwieldy / meaningless URLs and generic title tags - seems to have got itself into a bit of a tiz when it comes to one of our clients. We have tried solving the problem to no avail, so I thought I'd throw it open and see if anyone has a soultion, or whether it's just a fault in our CMS. Basically, the SEs are indexing two identical pages, one ending with a / and the other ending /index.php, for one of our sites (www.signature-care-homes.co.uk). We have gone through the site and made sure the links all point to just one of these, and have done the same for off-site links, but there is still the duplicate content issue of both versions getting indexed. We also set up an htaccess file to redirect to the chosen version, but to no avail, and we're not sure canonical will work for this issue as / pages should redirect to /index.php anyway - and that's we can't work out. We have set the access file to point to index.php, and that should be what should be happening anyway, but it isn't. Is there an alternative way of telling the SE's to only look at one of these two versions? Also, we are currently rewriting the content and changing the structure - will this change the situation we find ourselves in?
Technical SEO | | themegroup0