During my Pubcon presentation this November in Las Vegas, I talked about the working group that adjusts, edits, creates and brainstorms new ideas for Schema.org vocabulary. There are so many elements happening, and the Schema.org vocabulary is constantly morphing – being in on the ground floor, even as a lurker, is a great way to see what is coming down the pike.

There are a few ways to get involved. You can subscribe to the W3C working group – which gets you on a mailing list and all of the email conversations about Schema will come right to your inbox. If you hate email, this might not be your thing. I get probably 10-15 emails a week from this group. I use a filter to label them in my Gmail and take a look once or twice a week.


You can also be more passive, and just check out the releases page on Schema.org.  This only lists the items that have already been released – so this is more of a “what’s new and live” checkup – and doesnt offer the ability for you to get in on the development of Schema.


Whichever way you decide to keep up with updates to schema vocabularies, you have options, and anyone with a good idea and some time can suggest edits and new options!






Getting In On The Ground Floor with Schema
Carrie Hill
Carrie has been working in SEO and Online Marketing since 2006 - she brings a passion for search and a desire to know more to every project she participates in. Carrie is a noted speaker and writer about a variety of topics, including Schema protocols, Google Analytics, Local Search and more. When she's not digging heavily into search & online marketing issues - you can find Carrie in her kitchen or possibly sitting on the porch with a cup of tea, a book, and her 4 dogs.

One thought on “Getting In On The Ground Floor with Schema

  • May 13, 2016 at 2:31 am

    Thanks Carrie. I have been trying to better understand Schema, your tips will help 🙂


Leave a Reply

Your email address will not be published. Required fields are marked *

No Spammers - No Bots :) * Time limit is exhausted. Please reload the CAPTCHA.