ECommerce and microdata
-
Last year I rolled my own online shop and I included schema.org microdata for all the products. My Google ranking continued to improve during that period, but I was doing a number of improvements, so I can't say how much was due to the microdata.
My store continues to grow so I moved to an eCommerce solution. I opted to go with Volusion. Much to my surprise, about the only SEO feature they have implemented is SEO friendly URLs. They have not implemented microdata, which is pretty surprising given that all their sites are geared towards products. I would think it would be very easy for them to span the product name, description, price, etc, with a product schema.
I called CoreCommerce, a Volusion competitor, and they have not implemented microdata either.
Why are these large eCommerce providers ignoring microdata?
Are there eCommerce solutions that have implemented microdata?
Do large online retailers like Amazon and Buy use microdata?
Is there any data that shows the SEO benefits of implementing microdata for an online store?
Best,
Christopher -
Amazing! The question from Christopher was posted in 2012. 2 years later, Volusion still seem to be running years behind as far as online marketing goes. They have a reasonably good system for building an ecommerce website, but when it comes to online marketing, they struggle.
- They have still not implemented Microdata for products.
- Not only that but their Google Shopping Feed has to be Manually published, instead of allowing the feed to get updated periodically, like daily etc.
- They do not support all the latest fields and attribute details that Google Merchant centre now offer such as Mobile Links, Attribute Lengths
- Making Availability mandatory (which was enforced September 30, 2014)
- and so much more.
For Basic ecommerce the Volusion product seems great. As soon as you wish to really start utilising resources outside Volusion, Good Luck!
-
Amazon uses Schema with their products. We use product Schema on our eCommerce sites. My belief is that it will help from a rich snippets pov and simply that this is something the search engines want. The best way to get people to adopt is to show that it helps. That's my opinion anyway.
Best,
-
Thanks for the info and the link to the testing tool.
To be fair, I should add that Volusion has added rich snippets for reviews, and that's certainly a step in the right direction. However, companies rolling out a new shop typically have products and no reviews, so the product snippets could be used from day one if they were implemented.
I did come up with a hack to add a schema.org description to each of my products. I'll continue to look for a hack that allows me to put meta data around all product features like price and availability, but product description will have to do for now.
Best,
Christopher -
I don't have answers to all of your questions but I might be able to shed a little light on them.
I've not seen any major studies that show the benefit of microdata specifically on rankings. However when you look at the area of rich snippets for eCommerce as a whole then I have it on good authority (but haven't seen the data myself) that you can expect an increased CTR from having some forms of rich snippet. Whether you implement that change using microdata, microformats or RDFa is irrelevant. Here's one study I found.
I would hazard a guess that many eCommerce providers appear to be a little slow to implement microdata into their product because although Schema.org has been live for over a year microdata has only provided any tangible benefit in Google since April 2012 when Google updated rich snippets for products.
If you want to find out if a specific retail is using semantic data (again not just microdata in this case) then just take their product page URLs and paste them into the rich snippets testing tool.
Hope that helps a little.
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
-
Ecommerce Category Pages
First, let's define the terminology for the various types of ecommerce pages. The terminology differs from organization to organization: Product Description Pages (PDPs): These pages have a single product, pricing, an "add to cart" button, reviews, and a product description. Product Listing Pages (PLPs): These are product category/subcategory pages that have product image links and text links to Product Description Pages (PDPs). Category Pages: These pages have subcategory image and text links to subcategory pages. No product images are displayed Hybrid Category Pages: these pages combine sub-Category Images and text at the top of the page and product listings below. Our CMS currently does not allow us to create hybrids. This conversation revolves primarily around mobile. Our ecommerce team is having discussions around the appropriate use of PLPs vs Category pages. After doing a quick audit of the mobile sites of some top ecommerce players, there is definitely a trend to use Category Pages at the top of the category and sub-category hierarchy and use PLPs at the very bottom. The logic from a usability perspective is to allow visitors to navigate a site without ever using the hamburger navigation. ex: Baby (Category Page) => Car Seats (Category Page) => Convertible Car Seats (PLP) The sites I audited all had hamburger menus. A visitor would navigate from a home page image for "Baby," an image on the "Baby" page to "Car Seats", and an image on the "Car Seats" page to the Convertible Car Seats page. At that point, they would be able to shop for "Convertible Car Seats" on a PLP. This appears to be excellent UX and easy to use navigation. Theoretically, good for SEO as well. In short, category and subcategory pages are being used as navigation to allow visitors to easily navigate to the bottom of the hierarchy and shop on the most narrow page in the hierarchy. Much easier to use than a hamburger menu, but it does entail more clicks. The discussion revolves around allowing users to shop for product at a higher level in the taxonomy. For example, what if a visitor wants to shop all Car Seats? In the above taxonomy, we are precluding users from shopping in this manner. There is no "Car Seats" PLP. Our CMS has the ability to create both a Category Page and a PLP for "Car Seats". We could theoretically place an image on the "Car Seats" category page for "View All Car Seats", and allow users to click to a "Car Seats" PLP. None of the major ecommerce players I've audited are adding a PLP option higher up in the hierarchy. That doesn't mean that it's not good UX. Problems: From an SEO perspective, having a Category Page and a PLP for "Car Seats" would cause cannibalization - they would be competing for the same keywords. I am skeptical that canonicals would work. The pages are not near duplicate content. One page has category images, the other has product images. We could place content blocks on the page to make them more similar. We could noindex the PLP, but that's a waste of internal link juice. Need advice: Will canonicals work in this situation? Should we trash this idea entirely? Does adding a PLP add value or confusion? Is noindex a good idea? Is there an option to target keyword variations with the PLP? Is there another solution?
Web Design | | Satans_Apprentice0 -
Should Our Mobile Responsive Version of our Ecommerce Site include the on Page content to Help with Rankings
Hello All, We are soon to launch our new redesigned website along with a mobile responsive version but i have noticed we currently don't include the on page Content we have on the mobile version which we have on the desktop version to help with rankings etc. I am not sure how google does mobile research with regards to rankings. We have designed our responsive version to be as user friendly as possible at the expense of having to much clutter/content but I am wondering now , if we will rank on mobile if all our on page content isn't present. Just wondered if we should include it at the bottom of the pages with say a "Read more" extension to help avoid clutter? Any advice greatly appreciated thanks Pete
Web Design | | PeteC120 -
Ecommerce platform
Hello all, My digital agency is starting to focus on building mainly bespoke ecommerce platforms. I've used a variety of open source platforms over the years, most of which I find un satisfying - specifically Magento (as the framework is very cumbersome). I do appreciate that many SEOs love magento, especially with the shopping cart control - being able to track conversions and customer data handling onsite Etc. My question is, what do ecommerce specialist SEOs and CROs want from a good ecommerce platform please? Thanks William
Web Design | | wseabrook0 -
Help with Schema.org on Ecommerce Products
I’m looking for ways of using schema.org with products that have pricing options. There appear to be two main problems 1) Whilst colour, width, height and depth are all catered for, size appears to be missing – how can we mark up products that are available in sizes that aren’t necessarily covered by width/height/depth (e.g. shoe size). Also, what if the product is available in different finishes – technically, these could not properly be described as colours so how could we mark them up? 2) There doesn’t seem to be any particularly good way of marking up pricing options that are displayed on the same product detail page. For e.g. if a pricing option table is used like this: | ID | Colour | Price 001-red | Red | £3.99 001-green | Green | £4.49 001-blue | Blue | £4.99 | I can mark up each row as an offer, and give each offer a price and sku or mpn, but then I can’t use itemprop=”color” to describe exactly what the option is. Would I just use itemprop=”name” in this case and abandon color altogether (even though it’s technically supposed to be describing the colour of the product and not the name of the offer)? I suppose another way I could approach it would be to mark up each row as an individual product, and assign each one an offer with the details as described above but then the containing page would effectively look like a separate product – which it isn’t. Any help or advice on this would be very much appreciated
Web Design | | paulbaguley0 -
Blog is outranking ecommerce store
My client has a blog that posts information about products to support its ecommerce store. The blog's main purpose is to support the products listed on the main website, but it has become so strong that its posts sometimes rank in the SERPS in place of the website product page, which is undesirable. The blog posts always link to the product that they are supporting. Are there any other methods, other than doing a 301, that could help the product page to rank instead of the blog post?
Web Design | | pugh0 -
Infinite Scrolling vs. Pagination on an eCommerce Site
My company is looking at replacing our ecommerce site's paginated browsing with a Javascript infinite scroll function for when customers view internal search results--and possibly when they browse product categories also. Because our internal linking structure isn't very robust, I'm concerned that removing the pagination will make it harder to get the individual product pages to rank in the SERPs. We have over 5,000 products, and most of them are internally linked to from the browsing results pages in the category structure: e.g. Blue Widgets, Widgets Under $250, etc. I'm not too worried about removing pagination from the internal search results pages, but I'm concerned that doing the same for these category pages will result in de-linking the thousands of product pages that show up later in the browsing results and therefore won't be crawlable as internal links by the Googlebot. Does anyone have any ideas on what to do here? I'm already arguing against the infinite scroll, but we're a fairly design-driven company and any ammunition or alternatives would really help. For example, would serving a different page to the Googlebot in this case be a dangerous form of cloaking? (If the only difference is the presence of the pagination links.) Or is there any way to make rel=next and rel=prev tags work with infinite scrolling?
Web Design | | DownPour0 -
Redesign of an ecommerce site
We are thinking to redesign our ecommerce site and was wondering would we loose our google rankings in any way? That's something we don't want. We want to achieve a better and cleaner looking website. It's a more like template redesign. But adding extra functionalities. We will add upselling and crossselling features to product pages. Some products have reviews and some don't. If a product doesn't have a review random testimonials will replace the reviews. We will redirect all urls's if category structure changes. All content title, headings remain same. Any suggestions are welcome 🙂
Web Design | | Jvalops0 -
Ecommerce web site with too many internal links
Hi, We're using Magento CE 1.4.0.1 for our ecommerce web site with a fairly flat navigation system i.e. 9 major categories display across the top menu that when you roll over display 2-20 sub categories (which take you to a groups of similar products) and then individual product pages. The categories and sub categories are available to click on as part of a dynamic Html menu system on each page. Each page also shows a small number of related products. This linking structure seems fairly standard and yet Seomoz throws up the error message, "Too Many On-page links" for most pages on our site. Do I need to really worry about this? Is there much can be done to improve this on an ecommerce web site with a large catalogue of products? I've looked at the Knowledge Base but I don't feel the existing responses adequately address the issue for ecommerce sites.
Web Design | | languedoc0