In schema performance analytics, the Scope signifies different schema sources that contribute to the performance of a website. These sources are mainly composed of the following elements:


Highlighter Templates

  • Scope from individual Highlighter templates will be represented by their template labels. If a template doesn’t have a label, the associated schema type will be used instead. If both the template label and schema type are not available, then the template ID will be used.

Editor

  • This scope type presents performance of those pages receiving schema markup from Schema App Editor.

Data Feeds

  • This may include standard data feeds like Merchant Center or custom Data Feeds specific to clients.

Comprehensive

  • This scope demonstrates the performance of all unique URLs where schema markup is deployed  by Schema App. In other scopes that are linked to the Schema App, one URL (e.g., containing a product insight) might be part of multiple templates such as Article and FAQPage. Hence, counted separately in the performance of each scope. Whereas, Comprehensive scope computes the performance of all unique URLs deployed by Schema App by avoiding any duplicates. 

Other_Pages

  • This scope type presents the performance of all those pages where schema markup is not deployed via Schema App.  It is important to note that we are currently only including Schema App authored data (Editor, Highlighter, API Feeds, etc). Data generated from other vendors or themes are not included, and so are marked as Other_Pages.