Summary
Optimizely CMS 13, generally available since March 31, 2026, is where Optimizely is building Visual Builder, Optimizely Graph, Mark (formerly Opal, the Optimizely Agent Platform), and every release that follows. For a marketing organization on CMS 12, the upgrade changes what editors can do without a developer, where AI-assisted work can happen, and how content reaches the channels and systems that depend on it. This article covers what those capabilities deliver, what each depends on to perform, what the upgrade involves, and how The C2 Group delivers it as a fixed-price project with adoption planned from the start.
The Constraints Most CMS 12 Teams Are Working Around
Most CMS 12 teams describe a similar issue. A new landing page or layout change waits for a development sprint, so campaign timing is set by the backlog rather than the market. AI-assisted drafting happens in tools outside the CMS, which means output has to be pasted in, reviewed against standards the tool never saw, and reconciled with content that already exists. Each workaround is reasonable on its own, but together they put the marketing team’s pace under the control of queues and systems it does not own.
CMS 13 addresses each of these constraints directly, but the value does not arrive with the upgrade alone. Editors get a new interface and search moves to a new service, but the way content is planned, built, reviewed, and improved stays the same until someone decides how the new capabilities will be used and who owns them. Before committing budget, the useful questions to ask are what the upgrade gives your team, what it costs, and how much of that value is available at launch.
Five Reasons to Upgrade to CMS 13
1. Editors Can Build and Personalize Pages Without Waiting on a Development Sprint
Visual Builder replaces on-page editing as the default experience, giving editors one interface for pages, blocks, experiences, and media. Layout changes, new landing pages, and personalized variants move out of the development backlog and into the marketing team’s workflow, which shortens the distance between a campaign decision and a live page.
You don’t have to rebuild your site to get there. Visual Builder supports existing CMS 12 pages, and blocks and traditional pages can sit alongside the new model. The constraint is your content model: a page type works in Visual Builder only after its model has been updated, so choosing which page types to bring over first is a scoping decision. Teams that start with the page types behind their highest-volume work see the change in their workflow soonest.
2. Drafting, Optimization, and Governance Work Can Happen Inside the CMS
Mark brings agents for content creation, optimization, and governance into the editing environment, and Optimizely has stated that CMS 13 will include out-of-the-box agents equivalent to those in its SaaS CMS. First drafts, metadata improvements, and checks against your standards start in the system where the content lives, working from content the agent can actually read, instead of in a separate tool whose output has to be carried back in.
Agents read your content through Graph, so they perform only as well as the content they retrieve. Duplicated pages, inconsistent classification, or content types without a named owner will produce unreliable output regardless of the model behind it, which makes content readiness the variable that decides how much this capability delivers. Mark is provisioned separately, runs on credits, and requires Opti ID, so it carries its own budget and hosting considerations.
3. Graph Connects Your Content to Every Channel and Capability That Uses It
Graph replaces Search & Navigation, which CMS 13 no longer supports, and it is included in the CMS 13 license. Your team is unlikely to work in Graph directly. Its value shows up downstream: content variations, connections to external content sources, delivery to other channels, and agents all depend on content being queryable in a structured way, and Graph provides that. If your site relies on Search & Navigation today, migrating those features is the most common reason an upgrade goes beyond the baseline, and it is also a natural point to reconsider how search should behave rather than simply reproducing it.
4. Assets and Discoverability Move Closer to the Work
On the DXP, CMS 13 includes an embedded DAM, so editors find and place approved assets without switching systems, and the approved version is the one that gets published. The platform also adds built-in generative engine optimization to improve how your content is found and represented in AI-driven search, a channel where structured, well-described content has an advantage over pages written only for a human visitor.
5. Your Site Keeps Gaining Capabilities With Each Release
New features ship on CMS 13, and Optimizely’s published roadmap already includes additional agents and tools. A CMS 12 site will keep working, but it will not receive what Optimizely releases next, and the gap between your site and a CMS 13 site widens with each release. For an organization that intends to use Optimizely’s AI capabilities, being on CMS 13 determines whether each new release becomes available to your team as it ships or waits behind a future project.