August was a big month for deployment visibility and Entity Hub management. The team shipped several coordinated enhancements to the Markup Monitoring & Analytics (MMA) results screen, giving clients a much clearer picture of their schema health over time. Entity Hub also took a significant step forward, with new in-app tier management tools that reduce the need for manual admin intervention. And for clients using External Entity Linking, two new capabilities — salience scoring and language auto-detection — make EEL V2 more intelligent and multilingual-ready.
Deployment Monitoring Dashboard
The MMA results screen received a series of updates this month that together form a comprehensive deployment monitoring view. A new Last Scan panel now shows when each URL was most recently scanned and how its markup classified (valid, non-critical, or critical). Alongside this, a Scan History component displays scan classification trends over time as a stacked bar chart, making it easy to spot regressions. The results view now also shows detected markup items at the URL level, with direct navigation to the source. Finally, a Monitoring Results link has been added to the Maintenance section of the sidebar for quick access.
Entity Hub Tier Management
CSMs can now assign and change Entity Hub tier levels directly in the Admin interface, without needing to use the data editor. Entity limit restrictions are now enforced in-app, and banners throughout the Entity Hub tools communicate how many optimized entities an account has access to and how many have been consumed. This streamlines the EH onboarding and tier management process considerably.
EEL V2: Salience Scoring and Language Auto-Detection
External Entity Linking V2 gained two new capabilities. Salience scores are now captured for all linked entities — this data will power future features such as filtering out low-relevance entities and identifying the most important entities for an organization (visible now in the Salience column of the Entity Debugging admin report). EEL V2 also now performs automatic language detection, restricting entity results to either the language defined on the highlight config or the detected language of the content. This is particularly valuable for multilingual sites.
Other Improvements at Schema App
- Entity Hub sidebar navigation now includes a direct link to Performance Analytics (EPA), so users can access EPA from the menu without navigating away from the Entity Hub.
- Google Search Console now displays a clear message when a token has been removed, helping CSMs and clients diagnose authentication errors encountered during SPA setup.
- Fixed a bug where blocking an entity in Entity Hub would incorrectly mark it as "Edited" in Entity Reports, causing inaccurate reporting on entity status.
- Fixed a bug in the Highlighter Extension where empty HTML payloads were being sent to Tag Prediction, resulting in inaccurate or fabricated tag suggestions.
- Fixed the EPA landing page displaying the wrong view for clients who do not have EPA configured.
- Shopify clients can now include sub-categories in PLP and Category page markup, so that products matching the page content are accurately reflected in the schema.
In Brief
August 2025 brought meaningful improvements across three areas: deployment monitoring, Entity Hub management, and External Entity Linking. The new MMA monitoring components give clients real-time and historical visibility into their schema deployment health. Entity Hub tier management is now fully self-serve for CSMs, reducing admin overhead. And EEL V2 is now smarter about which entities it surfaces, with salience scoring and automatic language detection. Several quality-of-life bug fixes round out a productive month.
As always, reach out to your Customer Success Manager if you have questions about any of these updates or want to take advantage of new capabilities.
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