The Schema App JavaScript integration method generates schema markup from the page as your content is displayed in the browser. Some sites have needed to take the following considerations into account to ensure Google indexes their markup.

  1. Audit your site speed

    • If your site has speed issues, there’s a chance GoogleBot won’t see your schema markup. 

    • To test your site speed, run it through Lighthouse or PageSpeed Insights.

    • JavaScript execution time should be less than 3.5 seconds.

  2. Perform a Webpage Test 

    • The Waterfall portion of this test shows the order in which tags are executed on a page as it loads.

    • This can help you identify if the Schema App tag should be moved earlier in the queue (tag priority or rule ordering).

  3. Google Tag Manager - Ensure tag priority is set to 100.

    • Tags with higher values will fire before those with lower values.

    • In Google Tag Manager, you can control tag firing prioritization in the Advanced Settings of a tag.

  4. Adobe Launch - Ensure rule ordering is below 50

    • Rules with lower values will fire before those with lower values.

    • In Adobe Launch, edit your rule component and give it a number lower than 50 (40 for example) to ensure it runs before other rules. All rules have a default value of 50.

  5. Switch to the Crawler deployment method (for Highlighter templates)

    • With the Crawler, Schema is pulled from the Schema App cache and rendered server-side

    • Overhead on the page is very low, but the schema markup will only be as current as the last crawl.

    • The crawler runs every 7 days, so this is a good option if the content on your site doesn’t change frequently.