Optimizely CMS 13 and why it's the release the platform needed

I've been working with Optimizely for a long time, and I've sat through plenty of version announcements over the years. Some deliver, some are mostly housekeeping with a bit of marketing gloss. CMS 13, which went GA in March, is different. I've had time to dig into it properly and wanted to share what's stood out to me and why I think this one genuinely moves the platform forward. 

Visual Builder coming to PaaS is a big deal 

This is the one I keep coming back to. Visual Builder has been available on SaaS for a while, and anyone who has seen it in action knows it changes the publishing experience completely. The fact that it's now on PaaS means the large proportion of enterprise clients still running on DXP Cloud or on-premise can finally get access to it. 

The model Optimizely have built around it is clever. It's not a free-form page builder where marketers can go rogue and break everything. It's a proper composition hierarchy: Experiences for full pages, Sections for grid-based layout control, Elements for atomic content pieces. Developers define what components exist and how they behave. Marketers work within that framework, building, previewing and publishing without raising a ticket or waiting on a developer for routine work. 

The side-by-side editing with live preview across mobile, tablet and desktop is exactly what content teams have wanted for years. Add Blueprints for reusable templates and the ability to copy entire rows and columns, and you have an editor experience that's genuinely competitive with anything on the market. 

Opal is becoming the connective tissue of the platform 

The Opal integration goes well beyond 'AI that can write content for you'. What Optimizely have built is an ambient layer across the entire content lifecycle - generation, compliance review, translation, bulk publishing and optimisation, all from within the CMS.

The GEO tooling is the part I'm most excited about. Generative Engine Optimisation is the new frontier for content discoverability, and Optimizely have built native tooling for it directly inside the platform. The SEO Metadata Agent, GEO Schema Agent and FAQ Creation Agent are all built around making your content readable and citable by large language models, not just traditional search engines. The GEO Analytics dashboard shows you how AI models are actually crawling and referencing your pages. That level of visibility hasn't existed before. 

What makes it all work is the RAG architecture via Optimizely Graph. Opal doesn't just see the page you're on, it has access to your entire content ecosystem. That context is what makes the AI outputs genuinely useful rather than generic. 

Graph is no longer optional 

In CMS 13, Optimizely Graph becomes the standard content delivery mechanism rather than an add-on. GraphQL-based querying powers the Content Manager, external content integration, Visual Builder's content binding and the RAG layer for Opal. Search and Navigation is removed. 

The new .NET SDK simplifies Graph query development with compile-time type safety, and the Content JS SDK gives frontend teams a modern, TypeScript-friendly way to build headless experiences with less setup. The Smooth Rebuild feature is a nice operational touch too - blue/green slot validation lets you test against production data before going live, with zero downtime and easy rollback.

The embedded DAM and what's on the roadmap 

Anyone who has managed assets across a separate DAM and a CMS knows the friction. Embedded DAM removes it. AI auto-tagging, smart renditions, version control and direct Visual Builder integration mean assets live where the work happens. It's included in the new PaaS packaging, which is a positive change in itself. 

Looking ahead, the items I'm watching closely are the CMS to CMP bi-directional integration for unified planning and publishing workflows, the Optimizely MCP Server for generating frontend components directly from designs, and the Page Variation Agent for spinning up audience-specific landing pages at scale. All in the near-term pipeline. 

The upgrade path 

Two steps are required: Opti ID setup and switching from Search and Navigation to Graph. Both are well-documented and considerably less painful than the CMS 11 to 12 migration. Visual Builder and DAM migration are optional and can be done incrementally, so you can start delivering value quickly without a big-bang approach. One thing worth planning for early: Opal runs on a separate licence, so scope that in from the start rather than leaving it for phase two. 

CMS 13 is the release where Optimizely's platform vision actually coheres. SaaS and PaaS are aligning, the AI layer is purpose-built rather than bolted on, and the composable architecture story is complete enough to deliver on the promise. For anyone who's been waiting for the right moment to upgrade, I think this is it. 

MSQ DX is an Optimizely partner with deep experience delivering CMS migrations, platform architecture and digital experience programmes that drive real commercial impact. Thinking about a CMS 13 upgrade? Let's talk.