Optimizely CMS 13: What's New, Why It Matters & How Dotcraft Maximizes Its Power
Anyone who has spent time working inside a legacy CMS will recognise the pattern: content teams waiting on developers to make the simplest layout change, personalisation and A/B testing running as separate, disconnected tools, and a slow creep of plugins and workarounds that make every future upgrade feel riskier than the last. Add rising hosting and maintenance overhead into the mix, and it's easy to see why many enterprise teams feel their CMS is holding their digital strategy back rather than driving it forward.
Optimizely CMS 13 has been built to remove exactly these bottlenecks. It shifts to a cloud-first, headless architecture running on .NET 10, replaces on-page editing with a real-time Visual Builder, and bakes native AI – through Optimizely Opal – directly into everyday content workflows. Combined with a unified search and delivery layer in Optimizely Graph, the result is a platform that publishes faster, scales further, and finally gives marketing and development teams a genuinely shared way of working.
As a bronze Optimizely partner, Dotcraft has been tracking this release closely – mapping out what it means for our clients’ roadmaps and how to make the move from CMS 12 as smooth as possible. Read on to uncover what’s new in Optimizely CMS 13 and how Dotcraft can help clients fully exploit its potential.
What’s New in Optimizely CMS 13
Optimizely’s latest release is less an update than a re-platform, with seven changes standing out for the impact they’ll have on day-to-day content operations:
• Cloud-first, headless architecture on .NET 10 – content management is now fully separated from content presentation, and the platform runs on the latest .NET runtime – a faster, more modern foundation and quicker page delivery for every client.
• Visual Builder as the default authoring experience – a drag-and-drop canvas with real-time preview, autosave and direct property editing replaces on-page editing entirely, so content teams can build and adjust pages without waiting on a developer.
• Optimizely Graph replaces Search & Navigation – indexing, filtering and delivery across every content type, language and channel now run through a single GraphQL-based service, powering more consistent and considerably faster search.
• Optimizely Opal built into the editor – a generative AI agent orchestration platform, accessible via Opal Chat, supports content creation, translation and workflow automation without ever leaving the CMS.
• Content Variations for personalisation at scale – multiple published versions of the same content item – for A/B testing, personalisation or seasonal campaigns – are stored as lightweight deltas rather than full duplicates, keeping performance and storage efficient as personalisation programmes grow.
• Opti ID single sign-on – one login across the entire Optimizely product suite, with multi-factor authentication and SCIM provisioning, simplifying access management for larger teams and agencies.
• Built-in governance, collaboration and composability – inline comments, approval sequences and Projects let teams coordinate multi-page changes and sign-off in one place, while deeper integration with Optimizely CMP and DAM brings content marketing and asset management into the same ecosystem.
For Dotcraft, these enhancements translate into faster, more flexible, and future-proof enterprise solutions.
How Dotcraft Will Deliver Customer Success with Optimizely CMS 13
Knowing what’s new in Optimizely CMS 13 is one thing; implementing it well – without disrupting a live enterprise site – is another. Here’s how we approach it:
• A proven, staged upgrade methodology – rather than a single high-risk cut-over, we assess breaking changes, refactor affected code, test thoroughly in staging and run full regression checks before go-live, reducing downtime risk and protecting existing functionality.
• Headless and Graph-first architecture expertise – we rebuild content models and search around Optimizely Graph from day one, so clients get the full benefit of faster indexing and unified delivery, rather than a like-for-like lift of old CMS 12 patterns.
• AI-enabled content operations – we configure Optimizely Opal’s agents and workflows around each client’s editorial process, so content teams get genuine time savings from AI-assisted drafting, translation and optimisation, not just a generic bolt-on.
• Performance-first, personalisation-ready builds – by designing around Content Variations and delta-based storage, we help clients run more A/B tests and personalised campaigns without the infrastructure overhead that used to come with them.
• Governance and adoption support – we configure approval sequences, Projects and role permissions to match how each team actually works, and run hands-on Visual Builder training so adoption is fast and confident.
• Ongoing partnership beyond go-live – from Opti ID and access management to DAM and CMP integration under Optimizely One, we stay involved after launch, monitoring performance and evolving the build as requirements change.
Dotcraft’s CMS 13 framework ensures every deployment is engineered for speed, measurable ROI, and long-term scalability.
Optimizely CMS 13 vs CMS 12 – Comparison Table
|
Area |
CMS 12 |
CMS 13 |
|
Architecture |
Traditional MVC rendering, on-premises or lift-and-shift hosting |
Cloud-first, headless architecture built on .NET 10 |
|
Authoring experience |
On-Page Editing |
Visual Builder – drag-and-drop canvas with real-time preview and autosave |
|
Search & indexing |
Search & Navigation |
Optimizely Graph – GraphQL-based, unified across content types and languages |
|
AI capabilities |
Limited, largely third-party add-ons |
Native Optimizely Opal, built into the editor via Opal Chat |
|
Identity & access |
Per-application login |
Opti ID single sign-on with MFA and SCIM provisioning |
|
Personalisation & testing |
Manual content variants, higher storage overhead |
Content Variations stored as deltas, built for scale |
|
Site configuration |
Site Definitions |
Applications |
|
Collaboration & governance |
Basic workflow and approvals |
Inline comments, approval sequences and Projects |
|
Ecosystem integration |
Largely standalone |
Composable with Optimizely CMP, DAM and Optimizely One |
Real-World Impact for Dotcraft Clients
The value of an upgrade like this is ultimately measured in outcomes, not features. While every CMS 13 project we deliver is scoped around a client’s specific goals, three scenarios show the kind of impact enterprises can expect:
Retail & eCommerce
• Challenge: seasonal campaigns required duplicating entire page trees to run limited-time offers, slowing the team down at their busiest time of year.
• Solution: rebuild key templates around Content Variations, letting merchandising teams schedule seasonal versions of the same pages.
• Result: campaign pages go live in a fraction of the time, with no extra storage or maintenance burden.
Financial Services
• Challenge: strict governance requirements meant every content change needed multiple manual sign-offs across departments, creating publishing bottlenecks.
• Solution: configure approval sequences and Projects so compliance and marketing teams can review and approve changes within the CMS itself.
• Result: faster, fully auditable publishing without compromising on governance.
B2B & Manufacturing
• Challenge: fragmented search across multiple regional sites made it hard for customers to find the right product or technical documentation.
• Solution: consolidate content delivery through Optimizely Graph, unifying search and filtering across every market and language.
• Result: a single, consistent search experience that’s easier for customers to use and far simpler for the team to maintain.
These scenarios reflect the type of outcomes we design toward on CMS 13 projects; as our own case studies complete, this section can be updated with client-specific figures.
It’s this combination of technical depth and a genuine focus on business outcomes that’s why Dotcraft remains a partner enterprises trust for complex Optimizely builds.
Optimizely CMS 13 FAQs
The headline changes are a move to a cloud-first, headless architecture on .NET 10, Visual Builder replacing on-page editing, Optimizely Graph replacing Search & Navigation, native AI through Optimizely Opal, and Content Variations for scalable personalisation and testing.
Optimizely CMS 13 FAQs
The headline changes are a move to a cloud-first, headless architecture on .NET 10, Visual Builder replacing on-page editing, Optimizely Graph replacing Search & Navigation, native AI through Optimizely Opal, and Content Variations for scalable personalisation and testing.
Not immediately, but it’s worth planning ahead. CMS 13 introduces genuine breaking changes – from Site Definitions moving to Applications to the removal of Dynamic Properties – so migrating on your own timeline, with proper testing, is far safer than being forced into a rushed upgrade later.
Faster publishing comes from Visual Builder’s real-time editing, more consistent search and delivery comes from Optimizely Graph, and more efficient personalisation comes from Content Variations, which store alternate versions as lightweight deltas rather than duplicating whole pages.
Faster publishing comes from Visual Builder’s real-time editing, more consistent search and delivery comes from Optimizely Graph, and more efficient personalisation comes from Content Variations, which store alternate versions as lightweight deltas rather than duplicating whole pages.
Opal is Optimizely’s native generative AI agent platform, accessible directly inside the CMS editor via Opal Chat. It supports content creation, translation and workflow automation, reducing the manual effort involved in day-to-day content operations.
Some will, but not all. CMS 13 involves changes to the dependency injection namespace, a shift from Newtonsoft to System.Text.Json, and known incompatibilities with certain third-party packages, so every integration should be audited as part of the migration plan.
We follow a staged methodology – reviewing breaking changes, refactoring code, testing in staging and running full regression checks before go-live – so clients get all the benefits of CMS 13 without unplanned downtime or lost functionality.
To find out what an upgrade to Optimizely CMS 13 would look like for your business, explore Dotcraft’s Optimizely development services or get in touch with our team.
Final Thoughts
Optimizely CMS 13 is a genuine step-change rather than an incremental release - and for enterprises still running CMS 12, it’s a strong argument for treating this as a strategic upgrade rather than routine maintenance. Done well, with the right migration partner, it’s an opportunity to publish faster, personalise more effectively, and give content teams a platform that finally keeps pace with the business.
If you’re weighing up your options for Optimizely CMS 13 - or want a clearer picture of what migration would involve - get in touch with Dotcraft. As a bronze Optimizely partner, we’re ready to help you make the most of it.