Optimizely CMS 13: what we've learned from the preview and why it matters for your digital platform
Graham Carr
We've been getting hands-on with the Optimizely CMS 13 preview, and the headline for marketing and digital product teams is this: it's not just a technical upgrade. It's a meaningful shift in how quickly you can move, how much you depend on developers, and how well your content performs in an AI-driven world.
The upgrade story is simpler than you might expect
If you lived through the CMS 11 to 12 migration, you'll remember the scale of that project. CMS 13 is different. The heavy lifting has already been done. For most organisations, moving from CMS 12 to 13 is an evolution rather than a transformation - lower risk, more manageable, and without the kind of disruption that typically puts marketing roadmaps on hold.
There are some prerequisites to plan for, particularly around search and authentication, but this isn't the kind of platform overhaul that derails campaigns or freezes content operations for months.
More marketing independence, fewer dev tickets
The most tangible change for marketing teams is Visual Builder. It brings structured, drag-and-drop page composition with live preview - meaning editors can build and adjust experiences from reusable sections and blocks without waiting on a developer for every layout change.
In practice, that means faster campaign launches, fewer bottlenecks between strategy and execution, and more room to experiment without the usual back-and-forth. Developers set the guardrails; marketers work freely within them. It's a model that works better for both sides.
Better search, better discoverability
CMS 13 moves to Optimizely Graph as its standard search foundation, replacing the older Search & Navigation capability. For marketing teams, the practical upside is stronger content discoverability, better filtering, and a more flexible foundation for delivering content across multiple channels.
It does require migration planning - this is best treated as its own workstream rather than bundled into the CMS upgrade itself - but the long-term benefits to content performance are real.
One thing to be aware of on hosting
CMS 13 requires Opti ID, Optimizely's single sign-on service, which currently means hosting within Optimizely's DXP cloud platform. For existing DXP customers this is seamless. For others, it's worth factoring into planning conversations early. It's not a dealbreaker, but it's the kind of detail that can affect timelines if it surfaces late in the process.
Built for AI-driven discovery
This is where CMS 13 starts to feel genuinely forward-looking. Generative Engine Optimisation (GEO) is built into the platform - not bolted on as an afterthought. It means your content is structured in ways that AI-powered tools like ChatGPT, Google AI Overviews, and similar platforms can understand, cite, and surface to users.
As AI-driven search becomes a bigger part of how audiences discover content, this matters. Teams that structure their content well now will be better positioned as that shift accelerates.
On top of that, Opal AI agents can handle time-consuming tasks like SEO metadata, content tagging, schema recommendations, and alt text generation - freeing up teams to focus on strategy and creativity rather than admin.
Proven capability, not a beta experiment
One of the more reassuring aspects of CMS 13 is that its core features - Visual Builder, Graph integration, the modernised admin experience - have already been running in live production environments through the SaaS version of Optimizely CMS. You're not adopting experimental technology. You're getting mature, tested capability now available in a PaaS deployment.
What to do next
If you're on CMS 11, the priority is clear. The platform is approaching end of meaningful support, and CMS 13 is where Optimizely is heading. Planning the journey from 11 to 12 to 13 should be on your roadmap now.
If you're already on CMS 12, you're in a strong position. The focus should be on preparing for Graph migration, understanding Opti ID requirements, and reviewing any areas of your platform that rely on older patterns.
The opportunity isn't just technical. It's about enabling your team to move faster, reducing dependency on development for everyday content work, and making sure your platform is ready for the way audiences are discovering content today - and in the years ahead.
We've done the groundwork on the preview so you don't have to. If you'd like to talk through what CMS 13 means for your specific setup, we're happy to share what we've found.