LLM Optimizer (ABV)
Market Signals for Adobe Firefly
Market Signals detects spikes in brand mentions across social media and news and shows how they relate to what AI says about your brand.
For each event, it shows the signal and how it is trending and how its sentiment shifted.
Events shape AI narrative and we show the matching claims.
Recommendation can be turned into a strategy and measured in the next runs.
Semantic Matching in Lookup Engine
This feature will enable easily and meaningfully to connect signals/insights with actions (opportunities) in ABV. The customer will be able to prioritize actions based on topics and claims that matter.
Main use cases are finding suggestions by topics, by claims but also finding topics & claims by market events (extending semantic matching to different types of data across our platform.)
Unified Brand Context
Unified Brand Context (UBC) is one governed, per-brand record that combines the brand profile (Layer 0 brand facts) with what the customer told us (business goals, brand context, markets and competitors). Every field is labelled where it came from, and the sources consulted are listed for transparency. Customers see it as the Brand Foundation tab in Brands Management.
AEM Sites Optimizer
WebMCP ASO Opportunity
Stemming from the 2026’s summer garage week, we took the WebMCP recommendation and tool discovery further and surfaced them through ASO’s Opportunities landscape.
Inside the new WebMCP Opportunity, we’re showcasing the discovered agentic flows for which a set of associated WebMCP tools are also generated.
This opportunity was already presented to customers (COX), unlocking the co-innovation path.
Code Suggestions Pre-verify mechanism
Similar to the content fix opportunities, we recently introduced a similar mechanism for code altering opportunities.
An aria-label fix is just a proposed diff until it's deployed and re-checked. Heavy pre-verify merges all of a site's fixes into one patch, builds and deploys it through our Code Patch API, then re-renders each page and checks each fix on its own — first confirming the new label is actually live on the element, then re-running axe-core to confirm the violation is gone. Only fixes that come back verified ever become a shippable code-change suggestion.
Web Performance Alerts
Sites Optimizer is now able to highlight significant CWV degradations and report them as detailed alerts.
At the same time, the alerts are correlated with the existing CWV Opportunity’s suggestions, making them actionable.
Published fixes live in ASO UI
Until now, “Fixed” in the ASO UI only meant the change was written to the AEM author. Customers couldn’t tell whether it had reached their live site.
Fixes now move through two clear states:
• Deployed to author: the fix is applied in AEM.
• Live: the page has been published, and the fix is confirmed on the live site, detected automatically.
AEM Sites Omnichannel/Coworker
Content Advisor Side Rail - Content Fragments Support
Content Advisor can now be integrated in modal view or rail view. From rail view same functionality is supported as in dialog view, but in addition drag&drop to canvas is also available .
MSM Support for Content Fragments
- Backend support for CF folders
- Admin UI improvements for MSM
Coworker Panel for Content Fragments
Just like we needed context awareness in AI Assistant we need it in Coworker as well. We currently have conversational authoring capabilities where we can
act directly on the AEM Content Fragments page you currently have open.
WebMCP Inside Experience Workspace
Similar to the ASO’s WebMCP Opportunity, we surface the agentic flow recommended to be represented via WebMCP Actions.
The generated recommendations and actions are visible inside the customer’s Experience Workspace via a tailored plugin.
The generated recommendations can be configured and also previewed using a “play” extension.
ABV Brief to Page Workflow
Demo case for Lloyds. ABV captures signals from LLM top cited web sources and identifies opportunities, generating strategies and briefs. Customer downloads the brief and uploads it to CX Coworker following a process to create and approve a new page which is finally published through Workfront.