5 Things You Need to Know About Schema App

Schema App makes doing Schema markup easier. In order to fully harness the power of Schema App, there are 5 things you need to know. At first you may think we are just the uber geeks who created the tool this way, but we hope that when you learn WHY we ask you to create Schema this way, you’ll see that it saves you time, helps you implement Schema accurately and makes Schema App kind of awesome. 

1. Schema App Wants to Know What Page You are Optimizing.

When you start with Schema App, we ask you the name of the page and the URI. What’s a URI? No it is not the short form of a disease, it means Uniform Resource Identifier. Basically, it’s how you tell us WHAT you want to add Schema markup to. Usually, it is the URL of the page you are optimizing. Why is it important that you use it? The URI is used by WordPress, Google Tag Manager and our API to automate the JSON-LD deployment. If you don’t enter a URI, your code isn’t getting automatically deployed and you’ll have to cut and paste it in, wasting 15 minutes of your life that you could spend on something else.

2. Schema App Wants to Deploy Your Code Automatically.

Cutting and pasting code is so 1990. Schema App has created three different ways for you to be able to click save in the editor and whoosh! Your code is deployed. How do you do it? If you are on WordPress, setup your WordPress Plugin with your Account ID. If you are on any other platform, use Google Tag Manager to deploy your code. If APIs are more your style, use our javascript to deploy. Once it’s setup, you can forget about deployment!

3. Schema App Wants to Connect Your Data.

Schema App helps you do it easily! Ever wonder why you can’t just enter text in all the fields and be done? With Schema and Google features, they want to know more than just the surface data. For example, for a Contact Number (or Contact Point in Schema speak), they want to know the type of contact (Sales, Support, etc), the phone number, the email, whether it’s toll free and more. In order to help you create these related data items, Schema App will prompt you to create a related “data item” and then add the details afterwards. The way that you do this in Schema App is click on the downward facing triangle next to the field. The greyed out writing tells you the type of “thing” that is needed. Once you create the “thing”, you can re-use it across Schema App. So create it once, and then re-use it.

4. Schema App Wants to Tell Google Exactly What You Mean by Referring to Wikipedia Definitions.

Schema App will prompt you to create an data item (#3 above), sometimes you just need to define what you are talking about and not add additional details. For example, when you are creating an data item for a County (or other thing that has a fixed definition – city, state, etc). In order to tell Google exactly what you mean you can insert the Wikipedia link in the URI field. See the example below for USA, we use the Wikipedia page link as the URI. It’s fast and explicit, Just like SchemaApp!

5. Schema App Tries to Guide You on the Type of Input to Enter.

Schema.org can be tricky. Some fields, like Area Served, can have three or four different inputs. When you see something that says Select AdministrativeAreaORGeoShapeORPlace, Schema App is just trying to guide you on the types of “thing” it wants you to pick from previously created data items or to create a new data item (#3 above).  

When you create the thing, make sure you pick the most specific way to describe it. This may mean entering the Wikipedia entry for the city as the Identifier and choosing city from the datatype pull down. 

So that’s it. These are the things that Schema App makes easy for users. We do it so that you can leverage the whole power of schema.org and do Schema right!