Off and on, I’ve been on a quest for understanding how to FULLY implement schema for WooCommerce. I’ve gotten an ‘above-average’ (but not perfect) understanding of WooCommerce, and I’m quite comfortable with working with it. Here’s the two ‘main’ articles that keep coming up regardless of what I put into the google machine.
Now, I understand what each of these are saying (mostly), but…
Even w/ Yoast WooCommerce Seo I’m looking for more than just the Brand & Manufacturer.
And even via Tyler Longren‘s solution, I’m needing a plugin type approach.
Check out this link to see the FULL POTENTIAL (not just Brand & Manufacturer) of the schema markup for a product:
No really, go back over and look at all the schema attributes. It’d take me about 4 or 5 hours to type up all of them! I’m sure you’ll agree though that WooCommerce alone is clearly not even close to using the full potential of schema’s markup. Forget about the rich snippets part that a person sees once the search result comes up for a second (that part is second). Do you realize that we are not even coming CLOSE to telling Google and Bing what’s actually ON our WooCommerce site in the first place! When search engines are looking at (crawling) our WooCommerce site, they are seeing little (if any) schema markup at all.
Please tell me I’m missing something.
Surely there’s a plugin or something that can get all this (below) to output from the backend of a WooCommerce site.
There’s all sorts of potential for related products, part numbers, ISBN numbers, color, depth, manufacturer’s sku, reviews, schema in the related products (& a ton more)
I’m sort of ‘at the crest of the hill’ on being able to make a fully functioning plugin myself. But before I take on this endeavor, I want to double check (with everyone and anyone in the world) to make sure I’m seeing this correctly. The potential for schema in WooCommerce is a HUGE hole that’s being danced around and no one is actually bridging the gap between Schema’s full potential and WooCommerce.
again, I’d love to be ‘wrong’ 😉