• The Add Media dialog now correctly displays alternate text for Content Hub images based on the asset's configured alt text value.

• Workflow-enabled datasource items that inherit workflow settings through template Standard Values now display the correct workflow status in page items.

• Name Value List fields now preserve special characters in keys when edited in Page builder.

• Fixed an issue where Multiroot Treelist fields displayed source roots differently in Page builder than in Content Editor, causing the hierarchy to appear flattened and making content selection more difficult for authors.

Key highlights:

• Full SitecoreAI support – Content SDK for Angular supports all core SitecoreAI functionality, so teams can adopt Angular without compromising access to key platform features.

• Lightweight, bot-aware tracking – a new createBotTrackingMiddleware detects crawler traffic, records a single server-side page view on the bot channel, and skips personalization automatically so bot requests don't skew analytics or trigger unnecessary CDP calls.

• Loaders cache layer with tag-based revalidation – loader results (page and dictionary data) are now cached via unstorage, configurable at the global, per-loader, and per-route level. A new /api/revalidate endpoint lets you invalidate cache entries by tag, for example from a Sitecore Edge webhook.

• Redirects middleware – requests are now matched against SXA redirect items and redirected (301/302) or rewritten before reaching personalization.

• Plugins and adapters architecture – analytics, events, and personalization are now exposed as composable plugins with environment-specific adapters (browser, server, and Express), making it possible to build custom adapters when the default visitor identification or storage behavior doesn't fit your application.

For a complete list of all changes, review the Content SDK release notes.

Key highlights:

• Typeahead suggestions and More Like This (MLT) - typeahead suggestions retrieve query completions and document previews as a user enters a search phrase. MLT queries retrieve items similar to a seed item/URL.

• llms.txt support - Content SDK Next.js apps can serve llms.txt whose content is managed via SitecoreAI configuration alongside robots.txt.

• Page metadata and Open Graph tags - Next.js starter templates now generate metadata and Open Graph tags by default, improving link previews and SEO out of the box. New templates inherit from the Base Page template, so these fields propagate automatically and are consumed without additional configuration.

• Experimental features visibility API - a shared API with editing-secret protected endpoints in Next.js, lets apps check which experimental features are enabled. A new CSDK_GLOBAL_EXPERIMENTAL_FEATURES_ENABLED switch turns all experimental features on without setting individual feature flags. This API lays the foundation for adding experimental features in the future as needed.

For a complete list of all changes, review the Content SDK release notes.

Now, more then ever, SitecoreAI offers

• A consistent experience across applications with a shared design system and familiar navigation patterns.

• One login and unified navigation that make it easier to move between products and workflows

• Simpler onboarding for new users with a more predictable and intuitive experience.

• Faster, more connected workflows through shared services and cross-product experiences.

• Quicker access to innovation as teams can deliver improvements and new capabilities more efficiently on a shared platform.

With fewer context switches and a more unified experience, you can focus more on achieving business outcomes and less on navigating between tools. 

Previously, translation used guidance from either Glossary and Localization or Do's and Don'ts depending on what was configured. Now, SitecoreAI considers guidance from both sections together during the same translation, helping ensure translated content follows both your preferred terminology and broader brand guidance.

We have also resolved an issue where terms configured in the Glossary and Localization section were not applied during AI page translation. Glossary terms are now applied as expected alongside applicable Do's and Don'ts rules.

SitecoreAI DAM stores up-to-date, complete, and accurate brand information from approved product specs and FAQs to rich media. But some of that content is not available on the public Internet and stays invisible to AI search engines and chatbots. AI tools rely on information they find on the public web, which can be outdated, incomplete, or unreliable.

Knowledge Studio, powered by Scrunch, solves this by turning your trusted DAM content into a living source of truth that AI tools can use.

With Knowledge Studio, your team can:

• Generate knowledge documents from DAM content: select source documents stored in SitecoreAI DAM and let Scrunch transform them into a structured, AI-ready knowledge document.

• Review with AI agent assistance: Scrunch agents automatically review every draft, flagging sensitive content, factual errors, and conflicting information before you approve.

• Approve: once a knowledge document is approved, it becomes available as grounding input when generating AI-optimized content, so AI tools can deliver accurate, brand-aligned answers to your audience.

• Stay current: refresh sources after updating DAM content and regenerate the document to keep your knowledge document in sync with the latest brand truth.

To get started:

1. Connect SitecoreAI DAM to Scrunch.

2. Generate a knowledge document from DAM sources.

3. Review and approve the knowledge document.

• You can now select and manage MP3 and MP4 video files in link fields and file fields, expanding media support from the legacy Media library.

• You can now upload images directly to existing child folders or create new child folders during the upload process, making media organization in the legacy Media library easier without leaving the editor.

The latest release of Page builder includes the following resolved issues:

• Fixed an issue where the site tree in Editor mode failed to load when page items were located under a Redirect item in the site hierarchy.

• Fixed an issue where authors encountered an error and could not navigate or manage pages when browsing content located beneath Redirect items.