Integration Process

Modified on Thu, 27 Jun at 12:50 PM

This support document summarizes the goals of Integration, and consolidates Knowledge Base resources that will help you successfully integrate a website with Schema App.


Part 1: Review all integration methods and choose the most appropriate method for the website you're optimizing

Choosing an integration method is important! Review the possible options to ensure you're making the best choice for the specific website you're optimizing. Some factors to consider: content management system, page speed, and frequency of content changes (particularly relevant for Highlighter clients). You can use 

Part 2: Set up the Schema App project for the website you're optimizing

Each domain and subdomain you deploy to will require its own Project. You can easily set up new projects. This is the time to add relevant information about the website URL, and the integration method you've chosen.

Part 3: Add Schema App scripts to the website you're optimizing

To access Schema App Scripts., you will need to be logged into your Schema App account.

  1. Open the Project Settings for the website you're looking to integrate with

  2. Scroll to the Deployment Settings section and open the drop-down section

  3. Follow the instructions for your integration method of choice

Part 4: Confirm Schema App scripts have been configured correctly on the website you're optimizing

There are two ways to confirm scripts have been added and configured correctly. Both require the use of Dev Tools. You can review both approaches here:

Note: Confirming the scripts are configured correctly is distinct from confirming that JSON-LD is deploying correctly & being indexed by search engines. That process will be described in the Editor and Highlighter Authoring Process documents.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article