Schema App Integrations

Introduction

Schema App is capable of integrating with any website. Read on to learn more about our integration options, and access resources to support selection, installation, and troubleshooting.

TABLE OF CONTENTS

• Technical Design
• Selecting an Integration Method
• CMS-Specific Integrations (Plugins)
• JavaScript
  • Option 1. JavaScript Directly on Page
  • Option 2. JavaScript via Tag Managers
• Authoring Tools
• Integrating with Multiple Sites

Technical Design

Once integrated, any Schema Markup authored using the Schema App Editor, Schema App Highlighter, or Merchant Center is saved to the Schema Markup Graph Database. From here, the JSON-LD can be exported and reused, or deployed to any website through our Schema Delivery Network by way of one of our integration methods.

Selecting an Integration Method

CMS-specific integrations (Plugins) should always be the first method considered. If this is not an option, multiple JavaScript integrations are available, each created for different use cases. Finally, the Crawler is available for websites that require an integration with no impact on rendering time.

If you're unsure which deployment method to use, fill out our Integration Determination Form to determine which Deployment Type is best for your Project.

Site speed is the primary concern when selecting the right integration. For more information, see our article, Performance Impact of Integration Methods.

CMS-Specific Integrations (Plugins)

If available, we recommend using a CMS-specific integration to deploy your Schema App markup. These plugins allow the Schema Markup to reside server-side (faster load time) and also be read by all search engines.

As an added bonus, some of our plugins automatically generate Schema Markup for your website for specific classes and properties. If you'd like to add to or modify the auto-generated plugin markup, you can pair it up with the Schema App Editor and Highlighter.

Schema App currently offers the following CMS-Specific Integrations:

• Adobe Experience Manager
• Shopify**
• BigCommerce**
• WordPress**
• BazaarVoice
• Drupal 10 & 11**
• Brightcove**
• Google Merchant Center

(** Works with Editor & Highlighter with a valid subscription) 

For more information, see our article on Schema App Plugins. 

JavaScript

JavaScript is the most common way of integrating Schema App's authoring tools with any CMS or website. Once the scripts are added, the JavaScript library asynchronously runs on page load, generating and rendering the markup. This method adds some overhead to the pages.

For more information see our Schema App JavaScript Page Impact Overview article.

Option 1. JavaScript Directly on Page

The JavaScript for your account can be added directly to all the pages on your website. This can be done on a page-by-page basis, or by adding it to your website's header so it appears across all pages. This will usually require IT support. If access to IT is limited, we recommend integrating via a Tag Manager instead.

Option 2. JavaScript via Tag Managers

Add a JavaScript element to your site with a Tag Manager or in your theme. This is the fastest method for rendering Schema Markup in your browser and is by far the most common integration method. This puts the digital marketing team in control of Schema Markup deployment and provides them with the ability to do maintenance and updates outside of a development release.

Schema App's JavaScript tag can currently be added using the following Tag Managers:

• Tealium
• Google Tag Manager
• Adobe Launch

Authoring Tools

Schema App currently has 3 authoring tools available:

• The Schema App Editor - for single pages
• The Schema App Highlighter - for templated pages
• Google Merchant Center data feed -  for Merchant Center users

Each authoring tool has different integration requirements. For more information, see Schema App Integrations By Authoring Tool article.

Integrating with Multiple Sites

If integrating multiple sites, a unique project will need to be created in Schema App for each domain and deployment method. Note that this does not apply to subfolders within the same website, as seen below with the example of "https://www.schemaapp.com/intl/".