Release Notes - April 2026

Modified on Mon, 25 May at 5:05 PM

April brought significant advances to the Knowledge Assistant, giving customers and CSMs direct control over their configuration for the first time, alongside a new mechanism for keeping client-side rendered schema in sync in near real-time. Rounding out the month: self-serve page count reporting, search relevance controls, and a series of Highlighter reliability improvements.


Knowledge Assistant Self-Service Configuration

The Knowledge Assistant now has a dedicated Settings page that lets customers and CSMs view and control their tenant configuration without filing an engineering request. The initial release surfaces read-only settings (tenant ID, enabled sites, branding defaults), and the new Site Scope selector — also shipping this month — lets Digital Experience Leaders choose exactly which enterprise sites the Knowledge Assistant queries. Both capabilities replace what previously required direct engineering intervention via AppConfig, improving response times and reducing dependency on the technical team.


Real-Time Updates for Client-Side Rendered Schema

Schema injected via JavaScript or Tag Managers (Client-Side Rendered, or CSR) has historically been invisible to traditional crawlers. This month, Schema App introduced an event-driven push mechanism that allows client-side JavaScript or Tag Managers to send updated JSON-LD data directly to NLWeb via a dedicated ingestion pipeline. The result is near real-time schema freshness for dynamic sites, without requiring a full page crawl. Updates are applied incrementally and securely, eliminating delays between a schema change and its appearance in the Knowledge Assistant.


Self-Serve Page History CSV Reports

CSMs can now generate project-wide deployed page count reports directly from the admin panel, without requiring a manual Athena query. A new view allows users to select a date range and specific project URIs, then download a CSV of currently deployed pages — the same data previously accessible only by running a bespoke query. This removes a recurring dependency on the data team for a routine reporting task. Documentation for this feature has been updated accordingly.


Other Improvements at Schema App

  • Knowledge Assistant search relevance controls: Search results are now visually styled by relevance score — high-relevance results appear with larger cards and highlighted borders, while lower-relevance results are visually de-emphasized. Users can also set a minimum relevance threshold (50–100) via a new slider in the UI, filtering out results below their chosen cutoff. Preferences persist across sessions.
  • Highlighter AI suggestions reliability: Fixed a race condition that caused AI and property suggestions to fail to appear after template creation in the Highlighter Extension. A related fix resolved a TagPrediction failure caused by an incorrect parameter type when writing to S3, restoring AI-assisted highlights for affected users.
  • Highlighter: Remove All generated XPaths: A new "Remove All" action in the Highlighter Extension's manual XPath panel clears all auto-generated XPaths at once. This saves users from removing each XPath individually when they want to replace the generated set with custom overrides.
  • Shopify multi-market markup localization: Links within generated Shopify markup now dynamically incorporate locale-specific URL suffixes (e.g., en-us), ensuring accurate schema for stores with multiple markets or regional variants.
  • Entity Manager tree performance: The Entity Manager Tree now offloads search and data batching to the backend, significantly reducing load times and improving responsiveness for accounts with large entity datasets.
  • Deployment Monitoring improvements: Several UX improvements landed this month: the Publishing widget now shows a template's real publish state (Draft or Published) rather than a static value; the URL monitoring view loads contextually rather than blocking the entire screen behind a full-height spinner; and links within Monitoring Reports now point only to valid, accessible destinations.
  • Schema.org updated to v30.0: SchemaApp's vocabulary has been updated to match the latest schema.org release, ensuring all users have access to current schema types and properties.



In Brief

April's releases were heavily focused on the Knowledge Assistant product, delivering self-service configuration controls and a new real-time schema ingestion path for client-side rendered content. CSMs also gained direct access to page count reporting. On the tooling side, the Highlighter Extension saw meaningful reliability improvements to AI suggestions, XPath management, and subtemplate cloning.


As always, reach out to your Customer Success Manager if you have questions about any of these updates.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article