Important Considerations when Using Schema App and OneTrust

OneTrust is a privacy and security software provider used by some Schema App clients to fulfil privacy regulation requirements. If you are using OneTrust, this support document outlines critical information to ensure markup from Schema App can deploy and be successfully indexed. This support document can help you assess whether your page is affected by access concerns typical to OneTrust.

TABLE OF CONTENTS

• Schema App Integration Scripts Must Run Before OneTrust Permissions are Accepted
  • Possible Solution: Place Schema App Scripts in a Separate Tag Container
• OneTrust Containers with Schema App Scripts Must Be Accessible to GoogleBot
  • Recommended Solution: Modify Robots.txt to ensure GoogleBot has Access
• Do the Schema App Integration Scripts Collect User Data or Engage in Customer Tracking?

Schema App Integration Scripts Must Run Before OneTrust Permissions are Accepted

A key requirement for successful indexing is that Schema App's integration scripts must run upon page load. Some OneTrust configurations have Schema App scripts only able to load once users accept Cookies. This must be changed in order for markup to be seen and indexed by GoogleBot and other Crawlers. 

Possible Solution: Place Schema App Scripts in a Separate Tag Container

A common solution for this scenario is to place the Schema App integration scripts in a separate tag container with no user interaction conditions. If you have additional questions about data collect, GDPR compliance, or practical strategies to address this scenario, contact support@schemaapp.com or your CSM.

OneTrust Containers with Schema App Scripts Must Be Accessible to GoogleBot

Another key requirement for successful indexing is that the tag container with the Schema App integration scripts is accessible for GoogleBot (and other crawlers) to see and index. The OneTrust container holding the integration scripts cannot be blocked. If a crawler is blocked from seeing and running the container with the scripts, the markup will not deploy to the version of the page that the crawler has access to and you will not see the value of your markup.

Recommended Solution: Modify Robots.txt to ensure GoogleBot has Access

The most common solution for this scenario is to simply allow GoogleBot and Crawlers access to the OneTrust container with the integration scripts. 

Do the Schema App Integration Scripts Collect User Data or Engage in Customer Tracking?

No, the Schema App integration scripts do not collect user data or engage in customer tracking. The integration scripts are used to: generate JSON-LD, fetch JSON-LD from Schema App's CDN, and communicate success/failure information to Schema App's CDN. Visitors to a webpage where Schema App is deployed will not have their identity and behaviour tracked by Schema App.

For a complete overview of how Schema App uses gathers and uses data, you can review the support document: What does Schema App do with my data?