General Considerations: How To Ensure Successsful Integration, Deployment, and Indexing

We want integration to be as simple as possible for you. If you are integrating with Schema App using scripts, add them according to the support documentation for your deployment method of choice.  To ensure you get results quickly, this article discusses some critical considerations for integrating using JavaScript tags.

Canonical URLs

The Highlight JS script is configured so that markup will only deploy on URLs that match the canonical URL referenced in the HTML. You can review this support document for more information regarding Canonical Link Elements.

Script Contents and Timing

The scripts must reference the Account ID of the Schema App Project associated with that website. For best results, the scripts should run within the first 4 seconds of the page loading. Use Dev Tools or WebPageTest.org to review when the Schema App scripts load.

Script Visibility and Permissions

To see value from GoogleBot or other bots indexing your markup, the integration scripts and JSON-LD must be accessible to GoogleBot and other relevant web crawlers.  Recall that GoogleBot does not interact with a webpage. The integration scripts and JSON-LD must load without any user action.

Review the list of common scenarios below and take action to ensure the scenarios are avoided.

Scenario: Tag container only fires after cookies are accepted

This is prudent practice when scripts in a tag container require user consent to fire, in order to comply with GDPR policies. Schema App does not collect user data or engage in customer tracking. 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?

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 [email protected] or your CSM.

Scenario: Tag container only fires upon first click 

Fixing this often involves opening the settings of your tag manager and changing the trigger for the tag to run. For example, Google Tag Manager has a list of "trigger types"

Scenario: Tag Container holding schema markup and scripts is marked as no-index

This scenario always makes our team chuckle and shake our heads. There's a poetic irony in explicitly preventing a search engine from seeing your SEO efforts, that you have to laugh at because you'd cry otherwise.

Signs and symptoms of this scenario include:

• Expected results not appearing in the GSC Enhancement report
• Validator and Rich Result Tests show valid markup
• Site speed is not a concern
• Reviewing the indexed page in GSC's URL inspection reveals that the Schema App integration scripts are not present