The Monitoring Reports page displays a week-by-week overview of health metrics for your site's schema markup deployment. To access these reports, navigate from the home screen to Maintenance > Monitoring Reports.
Select a Reporting Period
Switch between any of the last 12 weeks reports using the selector. This default to display the latest reporting period.
Scan Details
The reports are displayed in the Scan Details section, including several components listing overall status, trends, detailed error data, and lists of pages scanned.
Overall Status
Includes overall metrics for the reporting period including an error rate trend over time.
Celebrating Successes
Displays metrics related to successful deployments. This includes sources or templates (e.g. Editor, Highlighter Templates, WordPress) that are deploying, no longer in error, or contain zero errors.
Error Status Details
Displays metrics and data related to pages that have errors in their schema markup deployment. This includes various error groupings that list sources or templates in error:
| Errors (High-traffic) | Sources containing the most-trafficked pages that reported errors in deployment, allowing you to prioritize resolving any deployment issues on your pages with the highest traffic. |
| Errors (SHACL) | Sources containing pages that deployed successfully, but that report SHACL validation errors. Resolving SHACL validation errors ensures your schema markup remains complaint with various data requirements and recommendations that Schema App has identified (such as structured data rules for pages eligible for rich results). |
| New errors | Sources with pages that reported errors that are new to this reporting period (compared with previous reporting period). |
| Persistent errors | Sources with pages that reported errors carried over from the previous report. |
Issue Detected
The Issue Detected column in this report provides more information about the primary issue detected on the failed page(s).
- Structured data violations that may impact rich result eligibility.
Examples:- Google requires the name of the main entity of the profile page.
- date must be in ISO format, eg 2018-12-18. Google recommends including the hour information in addition to the day
- Accepted Answer must be a schema:Answer
- Status code based errors that prevented SchemaBot from accessing the Schema Markup.
Examples:- SchemaBot encountered an internal error (HTTP CODE: DESCRIPTION)
- SchemaBot was unable to scan after retrying (HTTP CODE: DESCRIPTION)
- SchemaBot was redirected when scanning (HTTP CODE: DESCRIPTION)
- SchemaBot was denied access to the page (HTTP CODE: DESCRIPTION)
- JavaScript deployment errors.
Examples:- Markup from this source is missing
- No markup was found
- highlight.js was not detected
- highlight.js was detected, but markup from this source is missing
Scanned Pages
Displays the pages analyzed for each source or template during the selected reporting period.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article