Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Product Schema Markup for All Products
-
Hi Team,
Google search console used to allow you to use their structured data markup helperhttps://www.google.com/webmasters/markup-helper/u/0/ to markup multiple product pages at once that were similar. I do not see this feature anymore with the new search console. Does anyone have a recommendation for marking up multiple product pages without having to have schema markup firing in GTM for each product page?
-
thanks for the schema code .
I already try with my personal website .please have a look at the code seo company in dubai
-
It is a AspDotNetStorefront E-commerce CMS. These developer tools are helpful. I have looked into the dynamic schema markup blog, but am not sure it is the best to implement this if there are a lot of products. I might also consider trying to have a developer implement article markup for a drupal site. This has been helpful thank you.
-
I agree what is storefront I can't find a CMS called storefront?
If Schema markup is being added to a brand new site, it’s much easier for developers to add the Schema as part of the site build, as opposed to layering it on after the website has already been coded. Developers benefit from SEOs telling them specifically which page elements require Schema (location, events, etc.) and a link to the respective Schema type on Schema.org, so the developer can figure out the best approach for implementation.
SEOs have largely taken ownership of writing JSON-LD themselves, which is great for speeding up the process of implementing Schema. JSON-LD is generally easiest for developers to implement, but adding inline Schema is usually simple as well. There are some plugins that can assist with the implementation, but they generally only support basic Schema types, such as the Website or Organization.
One way:
https://moz.com/blog/using-google-tag-manager-to-dynamically-generate-schema-org-json-ld-tags
https://moz.com/blog/json-ld-for-beginners
You can use Cloudflare
https://github.com/cloudflare/doca/blob/master/example/product.json
https://blog.cloudflare.com/cloudflares-json-powered-documentation-generator/
https://www.cloudflare.com/apps/developer/docs/install-json/options
I hope I have been of help,
Tom
-
Thank you Tom,
We are on storefront currently. We had previously used the schema markup tool for some of their products. I have used Google markup helper and technicalseo.com resources before to create JSON-LD to fire in GTM for blogs, vidoes, how-to pages, etc but not for product pages. Mostly because I agree that it can be done in a better way. Maybe consulting with a developer to implement product markup is best.
-
HI
Can I ask what platform you are using? If you're using an e-commerce platform like Magento, Shopify, BigCommerce, etc. There are simple ways of writing code that will do a better job as well as plug-ins that you can purchase and/or use for free.
Or if in the unlikely event you are just running an E-commerce website without a CMS you can still do this via coding. there is a method no matter what flavor of kosher using rather it be Ruby, PHP NodeJS, etc.
FYI
Google does NOT recommend Using Tag Manager to Implement Schema Markup.
John Mueller from Google advises against using Google Tag Manager to deploy Structured Data and mentions that the ideal solution is to add the structured data directly into the HTML. So ideally process it server-side and pass it via HTML instead of relying on a client-side solution like Javascript.
While this is not the ideal solution, as SEOs we know that we are not always in ideal situations and at times our best bet is to deploy it through a solution like Google Tag Manager. You could also look at deploying it via an Edge Computing Solution like Cloudflare Workers.
https://www.cloudflare.com/en-au/products/cloudflare-workers/
It is less than ideal to use Google tag manager to deploy JSON-LD to websites. It can be done but obviously it's not the best way.
just because it's not on the new search console yet does not mean that Google's structured data markup helper tool is obsolete.
https://www.google.com/webmasters/markup-helper/u/0/
Yes if you want to ad JSON-LD
Use any of the tools here
https://www.schemaapp.com/60-structured-data-tools-create-test-plugins-more/
Convert to GTM
https://saijogeorge.com/json-ld-schema-generator/tag-manager-fix/
You can add basic JSON-LD with
https://www.bounteous.com/insights/2017/03/20/seo-structured-data-recipe-gtm/
I use this to make this example
https://technicalseo.com/tools/schema-markup-generator/
GTM Friendly code
I hope I have been of help,
Tom
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
-
Product schema with no offer as owner wants to give price per customer
Hi, Trying to markup products for a site that does not show prices. Is there any way to markup a product price when the business model is: 1. customer calls or contacts shop. 2. shop gives a price quote based on level of detail and finish on the product 3. there is no base or top price. Thanks in advance!
Technical SEO | | plahpoy0 -
Schema.org product offer with a price range, or multiple offers with single prices?
I'm implementing Schema.org, (JSON-LD), on an eCommerce site. Each product has a few different variations, and these variations can change the price, (think T-shirts, but blue & white cost $5, red is $5.50, and yellow is $6). In my Schema.org markup, (using JSON-LD), in each Product's Offer, I could either have a single Offer with a price range, (minPricd: $5, maxPrice $6), or I could add a separate Offer for each variation, each with its own, correct, price set. Is one of these better than the other? Why? I've been looking at the WooCommerce code and they seem to do the single offer with a price range, but that could be because it's more flexible for a system that's used by millions of people.
Technical SEO | | 4RS_John1 -
When should a variant be a variant and when should it be a separate product from an SEO POV?
Hi all, We are looking at changing our current e-commerce store to a new platform and in doing so thinking of making some changes to how we list products in sub-categories. We have seen related questions asking about splitting a single product into multiple products to rank for different terms, but we are wondering about combining multiple products into a single product page? The examples we have seen have been about fashion items with variants of colour and size. However, the products we sell have variances that change the appearance, dimensions and technical specification, so we would like to ask the MOZ community if combining products with these variances would still be deemed good practice? We sell wood burning stoves and a good example of a product that we are considering combining is the Scan 85 stove, which is available in eight different configurations: 85-1, 85-2, 85-3 etc. Scan themselves refer to each version as a separate product and they are bought, stocked and sold as separate products. Wood burning stoves like this typically have a firebox in the centre and then design options that can change the top, side, base, door, colour and fuel. In this example, the firebox is the Scan 85 and the variation is the last number, each of which corresponds to a different design option changing both the appearance and dimensions (see attached image). We have them listed as eight different products on our current site, one for each version. Primarily because each option has its own name (albeit 1-digit difference) which when we created the pages we thought that more pages would present us with more ranking opportunity. However, we have since learnt that because these eight pages are all so similar and it is difficult to write unique content about each product (with the 85-1 and 85-2 the only difference between the models are the black trim on the 85-1 and the silver trim on 85-2). Especially as when talking about the firebox itself, how well the fire burns, how controllable it is etc, will be the same for all versions. Likewise, earning backlinks to eight separate pages is also very difficult. Exploring this lead, us to the question, when is a variant a variant and when is it a separate product? Are there hard and fast rules for what defines variants and products? Or does it simply vary from industry to industry product to product, and if so should we be looking at it from a UX or SEO POV, when making that decision? Our hope is that if we combine these eight products into a single high-quality page, it will present us with a greater ranking opportunity for that one page over eight individual pages. We also hope that in doing so will allow us to create a more intuitive UX on a single page with a unique description, more reviews focused on one page and an explanation of the options available, all of which should lead to more conversions. Finally, by creating a better UX and unique detailed description we hope that there is a higher chance of us earning product level backlinks then we do with eight lower quality pages. One of the issues in creating a single product page for all the variants is the sub-category/results pages, as we would be removing eight simple products and replacing them with one complex product. We have questions over how this would work from a filter/facet level whereby when you apply a filter there is an expectation that the image shown will match the criteria, so if we filter for stoves with a silver trim for example, there is an expectation to only see stoves that have a silver trim in the results. When you have separate product pages you have separate listings which makes this easier to only bring back the models matching the criteria. However, when you have a single page this is more complex as you will need a default image for non-filtered results and then the ability to assign an image to lots of different attributes so that the correct image is always shown that matches the criteria selected. All of which we have been assured is do-able but adds an extra level of complexity to the process from an admin side. The alternative to doing this would be to create eight simple/child products and link them to one configurable/parent product. We could them list the simple products into the results pages and have them all linking back to the main configurable product which could load with the options of the simple product that was selected. From an SEO POV this brings in some more work, redirecting each page to the parent, but ultimately this could provide a better UX and might be the better solution. Has anyone got any experience in doing either of these options before? Both options above with affect the number of products we have available, so does the number of products in a sub-category effect the ability for that category page to rank? We currently have around 500 products in our wood burning stoves category, with perhaps an additional 300 to add. If we go down the combining into a single product page route this will reduce the number of products by around a third. If we keep all the simple/child products, then this will stay around the same. So, have we missed something obvious? Is there a glaring issue that we have overlooked from an SEO point of view as well as from the customer experience? We would appreciate your thoughts on this. Thanks, Reece scan85-1.jpg
Technical SEO | | fireproductsuk0 -
Problems with WooCommerce Product Attribute Filter URL's
I am running a WordPress/WooCommerce site for a client, and Moz is picking up some issues with URL's generated from WooCommerce product attribute filters. For example: ..co.uk/womens-prescription-glasses/?filter_gender=mens&filter_style=full-rim&filter_shape=oval How do I get Google to ignore these filters?
Technical SEO | | SushiUK
I am running Yoast Premium, but not sure if this can solve the issue? Product categories are canonicalised to the root category URL. Any suggestions very gratefully appreciated. Thanks Bob0 -
Product meta tags are not updating in my Magneto website!
I need some help! For some reason, each time I update the product meta tags in my Magento website, it doesn't change on the current website? Could someone help me understand why that is?
Technical SEO | | One2OneDigital0 -
Has anyone had issues with Bazaarvoice and schema.org?
About a year ago we started using Bazaarvoice to get reviews for our products, and it has been great as far as accumulating content, but Google is not taking the schema.org data and displaying it on the SERP. Someone has told me it is because we are offering multiple products, or that our schema.org tags are incorrect but when I compare our code to other travel sites it seems like everyone is doing something different. This is especially annoying since the Google schema markup check says everything is fine. Does anyone have any advice or similar experiences? Thanks.
Technical SEO | | tripcentral0 -
Two websites with similar products
I have two websites with similar products with different tld.I have a keywords that is comman in both.One site is at top in google with that keyword and one is not.Can we implement 301 redirect from one domain to another domain for that keyword or google will consider it spammy?Please help me out.
Technical SEO | | Alick3000 -
Schema for Price Comparison Services - Good or Bad?
Hey guys, I was just wondering what the whole schema.org markup means for people that run search engines (i.e. for a niche, certain products) or price comparison engines in general. The intend behind schema.org was to help the engines better understand the pages content. Well, I guess such services don't necessarily want Google to understand that they're just another search engine (and thus might get thrown out of the index for polluting it with search result pages). I see two possible scenarios: either not implement them or implement them in a way that makes the site not look like an aggregator, i.e. by only marking up certain products with unique text. Any thoughts? Does the SEOmoz team has any advice on that? Best,
Technical SEO | | derderko
schuon0