November's releases were anchored by improvements to monitoring transparency and entity data quality. Users will find significantly more actionable detail in the Monitoring Report, new validation guardrails in Entity Hub, and a long-awaited filtering capability in Entity Reports — alongside a solid set of bug fixes across the platform.
Enhanced Monitoring Report with Richer Error Detail
The Monitoring Results screen now surfaces HTTP status codes, detailed error messages, and deployment error information directly in the results view, giving users far more context when investigating deployment issues. Alongside this enhancement, two persistent bugs were resolved: the editor pop-out pane now correctly loads Required and Recommended Fields, and the Data Monitoring sources list properly displays template information for subaccounts.
sameAs URI Format Validation in Entity Hub
Entity Hub now validates URI formatting on sameAs fields in real time, providing immediate feedback when a value doesn't conform to expected URI format. This prevents silent save failures and helps users catch formatting errors before they affect downstream data quality. Entity Manager documentation has been updated to reflect this behaviour.
Filtering in Entity Reports
Entity Reports now support filtering, allowing users to narrow results and see a clear display of which filters are currently active. This makes it considerably easier to work with large entity datasets and to understand how the current view has been scoped.
Other Improvements at Schema App
- Improved error state classification in the Markup Monitoring & Analysis (MMA) tool, with a reworked frontend that more accurately reflects the severity and nature of deployment errors.
- Internal Entity Linking (IEL) entities now include a source PropertyValue in the markup they produce, enabling differentiation between entity sources for graph data quality purposes. Internal Entity Linking Setup documentation has been updated accordingly.
- Fixed a bug in the Highlighter Extension where deleted Templates were incorrectly appearing in the "View All Templates" view.
- Page Count now correctly filters out URLs containing UTM query parameters, preventing these from being misclassified and improving URL count accuracy.
- Clarified the Bot User Agent input field in deployment configuration to make clear that partial and substring matches are supported, with an updated placeholder and in-app instructions.
- Fixed a bug in Project Settings where triggering a save could inadvertently duplicate or modify the account ID of the project.
In Brief
November centred on making the platform's feedback loops clearer and more trustworthy. The Monitoring Report now tells you more about what went wrong and why; Entity Hub guides users toward correctly formatted data before errors occur; and Entity Reports give users control over large datasets through filtering. The accompanying bug fixes — particularly around templates, page count accuracy, and project settings — address issues that had been generating support requests, and should reduce friction for CSMs and end users alike.
As always, if you have questions about any of these changes, please reach out to your Customer Success Manager.
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