September Updates to Schema App


Our development team has been making incremental updates to Schema App as the months go by. Here are the newest fixes and improvements:

There are a few things to note regarding the Form Builder vs Multi-Type Entities…

There are times where you may want to create a Thing that doesn’t perfectly fit into a Type. Richard Wallace posted a blog that talks about how a TouristAttraction is a new class in schema 3.3. So for example places like Whistler BC would be best served as a multi-type entity – it is both a Mountain and a TouristAttraction. We have ensured that the Form Builder loads the properties for both Types so that you can edit them at the same time.

What if you want to create a Thing that isn’t easily described by any combination of types? For example, you may have a local business that isn’t easily described by any sub-type of LocaBusiness. If you utilize the Additional Type property and reference the concept in Wikipedia or Wikidata, we have ensured that it won’t break the form. So if you have a multi-type entity or an externally defined entity it will work just fine.

Some users were reporting “Phantom properties” when switching from one Type to another. Say that you had created an Article and filled out all the required and recommended fields in the form builder but then decided it was best to change the Type to Service or Product. Those properties which are no longer relevant to the new Type would still apply, except they’re no longer visible. We’ve fixed it so that the irrelevant or “orphan properties” can be identified and deleted.

Improved server performance

We improved server performance for all of our paid customers! In the past Schema App offered free accounts (with limited functionality) and a lot of those were no longer being used. So we archived a number of them and opened up those resources to paid accounts so that they would receive improved performance.

URI/URL Suggestions

There were a few people who wondered why the default URI/URL suggestion was a Schema App URL. The answer is simply that we needed a default URL to be populated and we used our own. We’ve changed this. Now when you’re creating a related Data Item the URL suggestion will come from one of two places. Either it will come from the URL attached the Data Item you’re working on. Or if you’re connected to WordPress / Shopify it will come from the URL at that domain. Hopefully, this makes it a little more user-friendly!

Required and Recommended Field Errors

Latitude and Longitude were changed to the Required field for GeoCoordinates, which is expecting those properties.

Organization had the property URL show up in both the required and recommended fields, leading to repetition and some confusion. You will now only see the URL field once through the whole list.

Help links to knowledge base

The help icon will now take you to our new Schema App Knowledge Base! Before it would direct you to a pretty long google document.

Fix to improve JSON-LD

We also made an improvement for how we generate the JSON-LD. So if the case arises where you need to flush the cache to re-generate the JSON-LD… you now have that option.


Within V3.3 there is a new class of HowTo and they use a property called steps. Steps wants you to create an ItemList. ItemList wants you to create ListItems… We’ve made the process much more user-friendly by including an embedded form for steps. This is similar to what we did for Recipe instructions.

Fixed Recipe Instructions

Speaking of Recipe Instructions… since v3.3 came out the schema model was reorganized a little bit and the Recipe Instructions embedded form stopped working! So we’ve fixed the issue and it works just fine now for both Steps and Recipe Instructions.

Mark walks us through the updates himself


, , , , , ,
Previous Post
Schema Doctor: URL Healthcheck
Next Post
Slaying Phantom Properties