Stuctured data for different sized packages
-
Hi all,
We are currently working on implementing structured data to our webshop, for SEO and for google shopping.
We sell stones, pebbles, gravel etc. (to be used in gardens).We offer each product in different sized bags. Customers can buy 20KG minibags, 250KG minibags, 500KG midibags, 1500KG bigbags and bulk quantities (ranging from 3000KG up to 35000KG).
For example, we sell Black Beach Pebbles in the bags as described as above (+ the bulk quantities). We have a product page for these Black Beach Pebbles and on that product page customers can choose the desired bag or desired bulk quantity. For google shopping, visitors land on these productpages. A while back that caused a problem; the landing page contained different prices so sometimes google could not match the prices on the landing page with the prices in our productfeed (because of course, each bag has a different price). So, besides SEO, another reason for us to implement structured data. I have two questions regarding the implementation.
1. For the landing page as described above, the idea now is to mark 1 product with different offers (an offer for each bag + an offer for the bulk quantities). This raises a problem regarding the bulk quantities; the price of the bulk quantity depends on the chosen quantity (customers can pick the desired bulk quantity using a dropdown) on the productpage. How should we markup the price? The idea know is to markup 1 product with different offers for each bag and 1 aggregate offer for the bulk quantities (and using the lowest price, so the price for the smallest bulk quantity). So, for the Black Beach pebbles:
Product = Black beach Pebbles
Offer (= 20KG minibag)
Price = ...
Offer (= 250KG minibag)
Price = ...
Offer (= 500KG midibag)
Price = ...
Offer (= 1500KG bigbag)
Price = ...
AggregateOffer (= Bulk quantities)
Lowprice = ...Is combining Offer and AggregateOffer within 1 product the right solution?
2. For the 1500KG Bigbags and bulk quantities we have separate landing pages (because people specifically search for bigbags and bulk quantities). So those landing pages are dedicated to bigbags / bulk quantities. How should we mark up those pages? Should we for example just do this:
On the page for te bigbag:
Product = Black Beach Pebbles 1500KG bigbag
Offer (=Black Beach Pebbles 1500KG bigbag)
Price =....and on the page for the bulk quantities:
Product = Black Beach Pebbles bulk quantities
AggregateOffer (=Black Beach Pebbles bulk quantities)
Lowprice=......Could that cause any confusion for google, because on the productpage with all the available bags, the bigbag is an offer for the product 'Beach Pebbles Black'. And on the second page it is a product on its own.
Thanks in advance!
Best!
-
Hey! No problem.. Just trying to figure the best way to do this too!
Thanks for the detail reply. All valid points - regarding indexing thin content, and showing customers more than 1 size - but those can be solved.
Lets look at this with an actual example...
Redbubble.com (an Alexa top 1000 website in the US) are selling a throw pillow in different sizes and different types. The costs are different based on the size and type chosen. This is their main product page for this product:
https://www.redbubble.com/people/straungewunder/works/25221192-familiar-sooty-owl?p=throw-pillow
On this main product page they are sending the customer to a default size (16*16) and type (cover only) option.. But as it is a dropdown, the customer is not stuck with just 1 size - he/she can choose multiple from dropdown.
And on this same page, they have this schema markup.
.....
Then they have duplicate pages for all the other pricing options.
E.g. for size (26*26) and type (cover only) - this is the URL
and the schema markup is identical to the one list above, _except for the price. _
All these pages are all exactly similar except for the default size and type chosen, and therefore the price is different for each page.
Duplicate pages are not a problem as they use canonical tags properly. All the pages have this canonical tag.
The canonical tags point to the original page always.
Regarding indexing the pages - **only the original page is indexed. **
If you go to Google and search for their main product url - it comes up on Google.
If you go to Google and search for the other product pages with different pricing options - they are not indexed.
So **Google isn't wasting crawl budgets on these duplicate pages.**But in your case you would index more pages if the search volume is high for different quantities (and then also change H1/title/meta tags respectively for these indexed pages).
Also, updated this as a blog as I think more people have this problem and will find this useful.
Apologies if you have already considered this, but let me know if this still doesnt work for you.. Interested to know what you finally go with!
-
Hi Arjun,
Thanks for your input, really appreciate it!
Actually, we already have seperate pages for each quantity. So for the Beach Pebbles black example we have:
- The overall product page with all quantities
- A 'simple' productpage for the 20KG bag
- A 'simple' productpage for the 250KG bag
- A 'simple' productpage for the 500KG bag
- A 'simple' productpage for the 1500KG bag
- A 'simple productpage for the bulk quantities
But, these pages are all near duplicates (only difference is the price). Plus, we have a lot of those pages. We noticed that google didn't even index all of them (i guess because they are all near duplicates). Plus, people really aren't searching for those quantities (i.e. googling those quantities), with an exception for the bigbags and bulk quantities. So we really didn't want google to spend it's time crawling all those pages, and because those are kind of thin-content pages we decided to first noindex them so google would take them out of the index. And after they disappeared we made sure there were no internal links pointing to them anymore so google wasn't going to crawl them anymore (we are keeping an eye on the logfiles to be sure google doesn't still crawl them with the same frequency. Would that be the case we will probably just block them through robots.txt).
But, long story short, for SEO we don't really want to use these 'simple' quantity pages (except for the bigbag + bulk quantities --> we gave them all unique and qualitative content). Also, for google shopping we don't want to send visitors to one specific quantity. I think it's kind of the same when someone is clicking (in google shopping) on a certain shoe and you present them with just 1 size.
I'm curious to your thoughts about this! And again: really appreciate your input!
-
Hey!
Great question.. Did you consider using different landing pages for all the different pricing options.
Eg.. For Black Beach Pebbles - suppose the main product page is yourwebsite.com/black_beach_pebbles .. And then for each pricing option - you have different URLs like these
- For the 20 kg minibag - you have yourwebsite.com/black_beach_pebbles?quantity=20kg
- For the 500 kg minibag - you have__ yourwebsite.com/black_beach_pebbles?quantity=500kg__
- etc..
Also for each of the bulk quantities options, you have different URLs like these
- For the 3000 kg bulk quanitity - you have_ yourwebsite.com/black_beach_pebbles?quantity=3000kg_
- For the 20,000 kg bulk quanitity - you have_ yourwebsite.com/black_beach_pebbles?quantity=20000kg_
- etc..
The advantage of having different URLs for each quantity option, is that you can then add the schema markup relevant just for the page. And if you add canonical tags for each page, then there is no issue of duplicate content.
For example, for the 20,000 kg url - yourwebsite.com/black_beach_pebbles?quantity=20000kg - the schema markup would be:
similarly for each page, you would add the relevant schema markup for that page.
Think this maybe better as each price has a different landing page, and each landing page has the correct schema reference.
The AggregateOffer schema markup maybe more useful when the same product is sold by different manufacturers. E.g. if you are selling black beach pebbles from 10 different manufactures, then you could use the AggregateOffer schema on the respective page (e.g. yourwebsite.com/manufactures/black_beach_pebbles which lists all the manufacturers.)
_$39_ _$950_ _from 10 sellers_
Just another option for you to consider. From a developer point of view the Offer property is better as each page (each quantity page URL) is totally independent, and only has markups regarding it. So, in the future if you delete one or add 20 more pricing options, you dont have to modify the existing ones.
Curious to know what you went with and why..
Cheers
Arjun
-
Not a problem
hopefully it will prove useful...
-
First of all, thanks a lot for your reply!
Yes, you're completely correct. Regarding point 3 --> prices are already shown for all bags, but for the bulk quantities, the customer has to choose the desired quantity first.
I will dive into those recources first thing tomorrow! Thanks for providing them!
-
Wow that's quite a query. If I am understanding you right, you have this problem:
- You sell bags of stones and stuff
- They come in multiple sizes
- The user goes to the product page, selects the size - and is then presented with a price
- But because the price depends upon the user's interaction, because there are multiple product variants, Google doesn't understand your product pages very well - or the prices of your products
- This is particularly true for Google shopping
I can't say I have experienced this exact issue as Google shopping is one thing that, I haven't had much to do with it - since the good old days (when it was free, and all you needed was an XML feed!)
But your basic problem is how do you mark up product 'variants' with Schema, right?
I have tried to find some resources for you on the subject:
- https://www.schemaapp.com/tips/schema-org-variable-products-productmodels-offers/ - this seems really in-depth and helpful. Suggest giving it a read
- https://schema.org/ProductModel - Product models seem like a concept you'd need to know about
- https://schema.org/isVariantOf - this seems to be a symmetrical schema, going from variant to master (also something you'd need to know about)
From a top-line check, it seems that you need to establish product models and variants. The model seems to be the master 'thing' that has children, whilst the variant seems to be one of the children (makes sense I guess)
I'd try to get as close to those materials as possible, then debug with Google's official structured data testing tool (until everything is perfectly digested...)
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
-
Job Posting Page and Structured Data Issue
We have a website where we do job postings. We manually add the data to our website. The Job Postings are covered by various other websites including the original recruiting organisations. The details of the job posting remain the same, for instance, the eligibility criteria, the exam pattern, syllabus etc. We create pages where we list the jobs and keep the detailed pages which have the duplicate data disallowed in robots.txt. Lately, we have been thinking of indexing these pages as well, as the quantum of these non-indexed pages is very high. Some of our competitors have these pages indexed. But we are not sure whether doing this is gonna be the right move or if there is a safe way to deal with this. Additionally, there is this problem that some job posts have very less data like fees, age limit, salary etc which is thin content so that might contribute to poor quality issue. Secondly, we wanted to use enriched result snippets for our job postings. Google doesn't want snippets to be used on the listing page: "Put structured data on the most detailed leaf page possible. Don't add structured data to pages intended to present a list of jobs (for example, search result pages). Instead, apply structured data to the most specific page describing a single job with its relevant details." Now, how do we handle this situation? Is it safe to allow the detailed pages which have duplicate job data and sometime not so high quality data in robots.txt?
Intermediate & Advanced SEO | | dailynaukri0 -
Difference LSI and and secondary related keywords
Hi, It is confusing to me. So far what I understand is the following: LSI are synonyms of the keyword your target (the one in the H1 and title tag). For example my keyword would be "Tuscany bike tour" and my LSI would be "Tuscany cycling vacation", "bicycle tour in Tuscany" etc... Then secondary related keyword are for me the other topics I need to cover in my content. In this case for example it would be "Florence", "Siena". But from what I understand a good writer wouldn't use "Siena" or "Florence" multiple times in it's content it would replace it by keywords that support them such as "the town of Florence", "the city of Siena"," the Palio of Siena" etc...Is my understanding correct ? If so what is the use of using those secondary related keyword, is it to rank on other keywords such as Palio of siena tuscany bike tour ? or just not to repeat a secondary keyword too many times. If i write the Palio of Siena isn't it considered as another topic that the topic siena ? Thank you,
Intermediate & Advanced SEO | | seoanalytics0 -
Should I implement Structure Data Markup before implementing AMP?
I am about to implement AMP and structured data markup on my site which one should be done first?
Intermediate & Advanced SEO | | Leebi0 -
Does Google frown on using 3 different page titles with same content to secure the top 3 results in SERPs?
Is it frowned upon by Google to create 3 different pages with the sames content yet different titles to secure the top three results in SERPs? For example: Luxury Care Homes in Liverpool Care Homes in Liverpool Private Care Homes in Liverpool The page titles are different with slightly different meta data but the user content is exactly the same, would this be considered a cheeky win or negative to rankings?
Intermediate & Advanced SEO | | TrustedCare.co.uk1 -
What is the difference between Multilingual and multiregional websites?
Hi all, So, I have studied about multilingual and multiregional websites. As soon as possible, we will expand the website languages to english and spanish. The urls will be like this: http://example.com/pt-br
Intermediate & Advanced SEO | | mobic
http://example.com/en-us
http://example.com/es-ar Thereby, the tags will be like this: Great! But my doubt is: To /es-ar/ The indexing will be only to spanish languages in Argentina? What about the other countries that speak the same language, like Spain, Mexico, etc.I don't know if it will be possible develop a Spanish languages especially for each region. Should I do an multiregional website or only multilingual? How Google sees this case? Thanks for any advice!!1 -
Different language with direct translation: duplicate content, meta?
For a site that does NOT want a separate subdomain, or directory, or TLD for a country/language would the directly translated page (static) content/meta be duplicate? (NOT considering a translation of the term/acronym which could exist in another language) i.e. /SEO-city-state in English vs. /SEO-city-state Spanish -In this example a term/acronym that is the same in any language. Outside of duplicate content, are their other conflict potentials in rankings you can think of?
Intermediate & Advanced SEO | | bozzie3110 -
Can you use multiple rel alternate tags for different device subdomains?
When redirecting from desktop to mobile with a separate URL structure, you need to have a rel alternate - rel canonical handshake to define the relationship between the pages. But if you have a different subdomain for different mobile devices, can you add more than one rel alternate tag on the desktop page? EG if site.com is redirecting to iphone.site.com, m.site.com, android.site.com
Intermediate & Advanced SEO | | AdiRste0 -
Google crawling different content--ever ok?
Here are a couple of scenarios I'm encountering where Google will crawl different content than my users on initial visit to the site--and which I think should be ok. Of course, it is normally NOT ok, I'm here to find out if Google is flexible enough to allow these situations: 1. My mobile friendly site has users select a city, and then it displays the location options div which includes an explanation for why they may want to have the program use their gps location. The user must choose the gps, the entire city, or he can enter a zip code, or choose a suburb of the city, which then goes to the link chosen. OTOH it is programmed so that if it is a Google bot it doesn't get just a meaningless 'choose further' page, but rather the crawler sees the page of results for the entire city (as you would expect from the url), So basically the program defaults for the entire city results for google bot, but for for the user it first gives him the initial ability to choose gps. 2. A user comes to mysite.com/gps-loc/city/results The site, seeing the literal words 'gps-loc' in the url goes out and fetches the gps for his location and returns results dependent on his location. If Googlebot comes to that url then there is no way the program will return the same results because the program wouldn't be able to get the same long latitude as that user. So, what do you think? Are these scenarios a concern for getting penalized by Google? Thanks, Ted
Intermediate & Advanced SEO | | friendoffood0