Schema App now integrates with Google Tag Manager.
If you are not using WordPress and want to save time on implementation of Schema.org markup, we have good news. Google Tag Manager automates code deployment by allowing you to automatically pull JSON-LD from our Cache. However, because Google Tag manager loads the JSON-LD asynchronously, this solution only works for Google Search Engines, not Bing, Yahoo, or Yandex. Stop cutting and pasting code, and contact us for an API key.
How to Add the Google Tag for Schema App
- Request an API Key
- Create a GTM account
- From Google Tag Manager, “Add New Tag”.
- Give the new tag a name, E.g. Schema App
- Click on Tag Configuration and choose “Custom HTML Tag”
- Turn on “Support Document Write” checkbox
- Click on “Triggering”, choose “All Pages”
- Click “Publish”
Watch the video to see how to add a new Tag for Schema App. For more detailed step-by-step instructions, click here
JSON-LD Support Across Search Engines
– or –
What Works with Google Tag Manager?
Yandex has better support for Schema.org than Bing, Yahoo, but not as good as Google. They are the dominant search engine in Russia and several other countries.
If you’re looking for full support today from Bing, Yahoo and Google you have to use Microdata or RDFa (neither JSON-LD or Google Tag Manager). This is done in your page templates, within inline modification to your page template.
There are two unique variable settings in this code: x-api-key and x-account-name.
- x-api-key: The API Key will be the same for each implementation (every domain and sub account) and is assigned one per licensee (to Schema App customers).
- x-account-name: A licensee can setup multiple sub-accounts, and therefore, the x-account-name is used to identify the sub account.
Find more examples in our step-by-step GTM setup guide
This example shows the x-api-key is consistent across multiple x-account-name.
Your default x-account-name is in your Account ID, found in Schema App under WordPress Plugin or Profile. If the Account I is http://schemaapp.com/db/Hunch_Manifest then the x-account-name is Hunch_Manifest.
How It Works
- You add markup for a data item (entity) in Schema App.
- The platform generates the JSON-LD and puts it in the cache.
- Using the URL you defined when creating the data item, when the page loads, it queries the cache and pulls the JSON LD with your markup.