What’s New in Optimizely CMS 13 What PaaS Customers Need to Know

Optimizely CMS 13 was released on March 31, 2026. For PaaS customers, the self-hosted platform officially catches up to SaaS and achieves feature parity.

While CMS 13 isn't a migration event like a move to a new platform, it isn't a routine upgrade either. It introduces architectural requirements that affect how your content is delivered, how your editors work, and how your site is found, including by AI-driven search.

Key Takeaways

• CMS 13 is not a routine version update, but it makes Optimizely Graph mandatory, deprecates Search & Navigation, and introduces architectural changes that require scoping work well beyond a standard upgrade.

• Graph and Visual Builder together remove the two main blockers PaaS customers have cited for not going headless, making CMS 13 the most practical trigger yet to evaluate that move.

• Structured, Graph-indexed, component-based content is what makes a site performant across channels and readable by AI agents.

• Oshyn helps Optimizely PaaS customers upgrade to CMS 13, migrate to a headless architecture, and structure their content and platforms for AI-driven search and discovery.

What Changes with an Optimizely CMS Upgrade

While previous Optimizely upgrades have largely been about staying current, including security patches, performance improvements, and incremental features, CMS 13 is different in a few specific ways:

• Graph and Opti ID are now mandatory: Unlike previous releases, where Optimizely Graph was an optional add-on, CMS 13 makes Graph and Opti ID required components included in your license.

• CMS 12 is no longer the focus: Optimizely has confirmed that all new product development is focused exclusively on the latest major version. CMS 12 will continue receiving security and bug fixes, but no new functionality will be added.

• The upgrade touches your architecture: CMS 13 includes changes to service registration, API surfaces, and site management, which require additional scoping work not necessarily present in previous upgrades.

The Features That Enable Modern Digital Experiences

CMS 13 introduces several new features, but a few are particularly important for enterprises planning modernization.

Visual Builder

Visual Builder is now the default editing experience in CMS 13, replacing on-page edit, which is disabled by default.

Marketers can build page layouts, drag in shared blocks, create content variations, and launch experiences without developer involvement. Also, governance guardrails, predefined styling controls, and reusable blueprints maintain brand consistency and enable marketers to rely on developers less for layout work.

Optimizely Graph

Graph is now the primary content delivery mechanism in CMS 13, and Optimizely Search & Navigation is deprecated and unsupported. Teams running Search & Navigation need to plan a migration to Graph as part of the upgrade.

Beyond that requirement, Graph changes how content works at a platform level, acting as a unified delivery layer for search, APIs, external content integrations, and AI capabilities. It also structures your content for how AI-driven channels consume it.

Opal AI

Opal AI is embedded directly into CMS 13 editorial workflows, meaning that content creation, SEO, GEO, and AEO, metadata generation, and content audits all happen inside the CMS.

As part of these updates, markdown for AI Agents, currently in beta, is also available. It delivers a clean markdown version of your pages to AI agents instead of full HTML, reducing ingestion cost and improving the accuracy of AI-generated responses that reference your content. While this doesn't affect the experience for human visitors, it can be important for how content performs in AI-driven search.

What a CMS 13 Upgrade Makes Possible

Upgrading to CMS 13 gives enterprises the opportunity to embrace the performance benefits of going headless and the ability to make their websites and digital properties AI-ready.

Graph and Visual Builder Remove Headless Blockers

PaaS customers who haven't made the move have typically encountered two friction points: technical delivery complexity and the marketer's reliance on developers for layout work. Graph handles the first, and Visual Builder handles the second.

For Optimizely PaaS customers still running a traditional, non-headless setup, CMS 13 is the clearest trigger yet to evaluate a headless move and the performance, SEO, and composability benefits it brings.

Making Digital Properties AI-Ready

Structured, Graph-indexed content built around components rather than pages, designed for reuse across channels, is the same architecture that makes your content readable by AI agents. The Markdown for Agents feature also provides a clean content structure directly that affects how LLMs reference your site in AI-generated responses.

Technical and Workflow Changes Required for CMS 13

Upgrading to CMS 13 can also introduce various technical and content modeling changes compared to previous versions of Optimizely. Having an experienced Optimizely partner to assist with your upgrade can make these changes easier, but it helps to be aware of them.

Technical Requirements

Optimizely CMS 13 runs on the latest version of .NET, so the .NET 10 SDK is required. Teams will need to undergo a full database backup before starting and use Visual Studio 2026 (18.0+) or another compatible IDE.

Organizations will also need to audit their solutions for compatibility issues before changing any packages or code, and to account for breaking changes in CMS 13 that affect service registration, API surfaces, and site management model changes.

Search & Navigation Migration

Search & Navigation is not supported in CMS 13. If your implementation relies on it, migrating to Optimizely Graph is a required part of the upgrade.

Content Modeling and Editorial Changes

To get value from Graph, Visual Builder, and Opal, content models need to shift from page-centric to component-based, structured for reuse and AI consumption. Additionally, as part of the editorial changes, on-page editing is off by default and needs to be planned for immediately, as it can also mean changes to editorial workflows that teams have grown accustomed to.

AI Governance

If you're enabling Opal, you will need to define approval workflows, brand guardrails, and data access policies before launch. AI-generated content moving through an editorial workflow without governance creates compliance and brand risk.

Your Upgrade Window

For PaaS customers, new feature development for CMS 12 won't return, so there will be a stronger case for upgrading now and going headless at the same time rather than treating them as separate projects.

Upgrade and Go Headless With Oshyn

Upgrading to CMS 13 and a headless website on Optimizely means improved performance, better SEO and discoverability, and an improved digital experience for your website visitors.

As a certified Optimizely partner, Oshyn has helped enterprises implement, upgrade, and migrate across the Optimizely ecosystem. Now, enterprises have the opportunity to pair their upgrade with a headless website and modern, AI search and discovery strategies.

Whether you're assessing upgrade scope, planning a headless migration, or thinking through AI-readiness for your content architecture, we can help you map the path. Through our upgrade assessment and agentic CMS/DXP implementation services, you can not only understand what CMS 13 requires from your current implementation and how to sequence the work, but also how to structure your content and platform for AI-driven search and discovery so you can start generating revenue from your new website faster.

Contact us to see how Oshyn can help.