Optimizely reverse logo on green gradient background

Optimizely 13 has arrived – and here's what it means for your marketing team

If you’re considering a move to Optimizely’s CMS 13, here’s what you need to know.

Liam Thomas

13 May 2026

7 minute read

This article was originally published in SMBTech.

Optimizely CMS 13 is the latest major release of Optimizely’s enterprise content management platform, released in March. It introduces Visual Builder (a drag-and-drop page editor with a new content model), an embedded digital asset manager (DAM), the ability to pull external content from third-party systems into the CMS, AI agents via Opal, native Generative Engine Optimisation (GEO) capabilities, and Content Variations for managing test content. For marketing teams currently running CMS 12, it represents the most significant editorial experience upgrade in years.

But the real question isn’t what’s new. It’s whether the upgrade changes how your team actually works day to day. Here’s our independent assessment.

How Optimizely CMS 13 changes page creation

Visual Builder is the headline feature for marketing teams in CMS 13. In CMS 12, building a new landing page or campaign page typically meant briefing your development team, waiting for a sprint slot, and hoping the final result matched what you had in your head. Visual Builder changes that. It’s a drag-and-drop page editor with a live preview that lets you compose, rearrange, and publish pages without a developer.

It also introduces a new way of thinking about pages. To get the most from it, it’s worth understanding the building blocks.

Experiences are the new primary content type in Visual Builder – think of them as enhanced pages. An Experience has a URL and appears in your page tree like a normal page, but it gives you access to Visual Builder’s full layout system. You start with a blank canvas or a saved template, then build by adding sections and content. Traditional pages still work in CMS 13, but Experiences are where the new editorial power sits.

Sections are self-contained horizontal slices of your page – a hero banner, a three-column feature grid, a testimonial strip, a call-to-action footer. Within each section you organise content using rows and columns in a grid layout. You can drag and drop sections to reorder them, copy and paste layout structures between sections, and save any section as a reusable template.

Elements are the smallest building blocks – the actual content that sits inside your columns. A heading, a paragraph, an image, a button, a testimonial card. Your development team defines which element types are available, so the richer the element library they build upfront, the more flexibility your content team has ongoing.

Blueprints are reusable layout templates that your content team can create and manage directly in the CMS. Save any Experience or Section as a blueprint, and anyone on the team can use it as a starting point. Blueprints generate automatic thumbnails, are browseable in a visual gallery, and can be exported and imported between environments. This is where Visual Builder shifts from a page builder to a genuine content operations capability.

Styles let you control appearance based on pre-approved design guidelines – colour schemes, spacing, alignment, background treatments – at any level from individual elements up to entire Experiences. Your developers set the guardrails; your content team works within them.

One important note: Visual Builder adoption is optional when upgrading. You can run a hybrid model, migrating pages to Visual Builder at whatever pace suits your team. You choose which pages and when.

Embedded DAM

CMS 13 includes an embedded digital asset manager at no additional cost. You can find, tag, and reuse assets directly inside the CMS without switching to a separate platform. The DAM includes AI-powered tagging, smart image renditions, and full integration with Visual Builder – meaning your content team can search for and place assets while building pages without leaving the editor.

If you’ve been managing media through basic folder structures in CMS 12, this is a meaningful step up. If you’re already using Optimizely DAM, the set-up is minimal.

Finding content at scale

CMS 13 replaces the traditional content tree navigation with Content Manager, a search-first interface powered by Optimizely Graph. Instead of clicking through folder hierarchies to find what you need, you search, filter by content type, status, and language, and get results instantly. For teams managing large content libraries, this significantly speeds up day-to-day editorial work.

Connecting third-party data to your CMS

CMS 13 lets you map content from external systems – DAMs, CRMs, product databases, APIs – directly into your CMS through a dedicated interface, without developer involvement or custom integrations. Once connected, external content is searchable and reusable in Content Manager and Visual Builder alongside your native CMS content.

CMP-to-CMS publishing

If your organisation uses Optimizely’s Content Marketing Platform (CMP) for content planning and collaboration, CMS 13 introduces a direct publishing workflow from CMP to CMS. You can publish content from CMP to your website in a single connected workflow, with prebuilt templates and live previews keeping both systems aligned. This is particularly useful for scaling high-volume content like blog posts and campaign pages.

Opal AI in Optimizely CMS 13: Embedded, not bolted on

Opal is Optimizely’s AI layer, and in CMS 13 it’s embedded directly in the editorial workflow. The platform includes purpose-built AI agents and tools across the content lifecycle – from content generation and image creation through to compliance review, translation, and SEO optimisation.

A few notable agents are worth highlighting: the Content Model Creation agent can analyse a URL or screenshot and generate a production-ready CMS content model; the Content Refresh agent audits your content library against rules you define (last modified dates, brand guidelines, outdated claims) and flags pages for review.

For CMS 12 users, Opal is available today, though agents and tools need to be built manually rather than being available out of the box. CMS 13 unlocks deeper integration through Optimizely Graph, which lets the AI understand and reference content across your entire site via retrieval-augmented generation (RAG).

What is GEO, and why does Optimizely CMS 13 support it?

GEO stands for Generative Engine Optimisation. It’s the practice of structuring your website content so that AI-powered search engines – such as ChatGPT, Google AI Overviews, and Perplexity – can understand, cite, and surface it in their responses.

CMS 13 builds GEO support natively into the platform. It automatically generates llms.txt files, structures your content for machine readability, and provides GEO Analytics that track which AI models are crawling your site, how often your pages are surfaced in AI answers, and which content gets the most or least AI attention.

It’s worth noting that GEO Analytics is also available to CMS 12 (PaaS only, excluding on premises) users who have Opti ID enabled – you don’t need to wait for CMS 13 to start tracking AI crawler activity.

SEO has been table stakes for years. GEO is where the next competitive advantage sits, and Optimizely CMS 13 is one of the first enterprise CMS platforms to build it in natively.

A foundation for smarter testing

CMS 13 includes a native Content Variations feature that lets editors create and manage multiple published versions of the same content item directly in the CMS. Each variation has its own publishing lifecycle and approval workflow, and you can promote a winning version back to the original without duplicating pages.

One important clarification, because Optimizely’s own marketing materials aren’t always precise on this point: Content Variations provides the content authoring layer for experimentation. The actual A/B testing engine – traffic splitting, visitor bucketing, conversion tracking, statistical analysis – requires Optimizely’s separately licensed Feature Experimentation product.

Should you upgrade from Optimizely CMS 12 to CMS 13?

The good news is there’s no burning platform here. Optimizely has not announced an end-of-life date for CMS 12, and it continues to receive active updates. You have plenty of time to be thoughtful.

It’s also worth understanding that upgrading to CMS 13 is exactly that – an upgrade, not a content migration. Your existing content stays in place. The technical work involves updating the platform framework, switching from Search & Navigation to Optimizely Graph, and implementing Opti ID. Visual Builder and the embedded DAM can be adopted at your own pace after the core upgrade is complete.

We’d recommend starting the planning conversation now. Build the business case based on the editorial productivity gains from Visual Builder, the embedded DAM, and the strategic value of GEO. Start exploring Opal on CMS 12 – and start tracking your AI crawler activity with GEO Analytics if you have Opti ID enabled. Work with your technology team and implementation partner to scope the upgrade for your specific site.

Organisations that take a planned, phased approach over the next six to 12 months will be in the strongest position. There’s no need to rush, but there’s every reason to start.

Want to tap into the expertise of a multi-award winning Optimizely Solution Partner?

Get in touch

Keep Reading

Want more? Here are some other blog posts you might be interested in.