The Gist
- Full CMS rollout. Webflow has completed migration of all customer sites to its next-gen CMS architecture, following an Enterprise-only release in January.
- Expanded limits. Teams get double the Collection lists per page, tenfold more items per nested list, and nesting up to three layers deep — up from one.
- AEO push. Webflow is simultaneously launching an answer engine optimization product in private beta, connecting the CMS upgrade to a broader AI search visibility play.
Webflow's next-gen content management system (CMS) is now live for all customers, bringing expanded design flexibility and higher collection limits to every plan tier.
The company announced April 9 that it completed migration of all customer sites to the overhauled architecture. The rollout follows an enterprise-only release in January 2026.
The architectural overhaul targets marketing and web teams building content-heavy sites with dynamic data. Webflow said the update supports AI-driven discovery by enabling richer, more interconnected content structures — reducing the need for custom development.
The next-gen CMS is available to all customers with CMS access, from Starter through Business Site plans, as well as Ecommerce customers.
Webflow has made expanded content design capabilities available across every plan tier — from Starter through Business, as well as Ecommerce customers.
Table of Contents
- What Changed Technically for Webflow CMS
- How Customers Are Using It
- The Broader Context for Webflow CMS
- Next-Gen CMS Capability Breakdown
- Webflow Acquisition and an AEO Release
- What Webflow AEO Does Not Yet Establish
- CMS Migration in Context
- The Operational Reality Gap
- Webflow Background
What Changed Technically for Webflow CMS
The next-gen CMS delivers three primary capability increases over the previous architecture:
- Collection lists per page: Teams can now use up to 40 Collection lists per page, double the previous limit.
- Nested Collection lists and items: Support increases to 10 nested lists per page — a fivefold increase — with up to 100 items per nested list, a tenfold increase.
- Multi-level nesting: Teams can now design up to three layers deep with CMS data, up from one.
Webflow says the architectural changes also improve performance and reliability for publish, restore, and backup operations at scale.
How Customers Are Using It
Webflow highlighted two agency practitioners in its announcement blog.
Sumit Tejani, a project manager at Concatstring, said the expanded flexibility changes how he approaches structuring content in Webflow, particularly for content-heavy portfolio projects with interconnected service pages and case studies.
Leslie Crosby, a senior frontend developer at Civilization, pointed to a real-world example at restaurant chain Hopdoddy, where deeper nesting allows the team to surface layered nutritional and allergen data — menu items, ingredients and supporting details — within a single, maintainable page structure.
Both practitioners described the primary value as eliminating custom development workarounds previously required for complex, relational content builds.
The Broader Context for Webflow CMS
Webflow is positioning the architectural upgrade as infrastructure for what it calls "AI-driven discovery" and answer engine optimization — the argument being that richer, interconnected content structures give AI search engines more structured context to interpret and surface brand content. The company did not cite third-party data supporting that connection in its announcement materials.
Enterprise-specific CMS capabilities remain separate and are not detailed in the general availability announcement.
This type of interconnected content structure would have previously required custom development — but now, it's entirely achievable in Webflow.
- Leslie Crosby, senior frontend developer
Civilization
Next-Gen CMS Capability Breakdown
Webflow's next-gen CMS introduces expanded limits and architectural improvements.
| Capability | Description |
|---|---|
| 2X Collection lists per page | Up to 40 Collection lists per page, doubled from prior limit |
| 5X nested Collection lists | Up to 10 nested lists per page, up from two |
| 10X items per nested list | Up to 100 items per nested Collection list |
| Multi-level nesting | Up to three layers deep, up from one |
| Improved publish performance | Faster, more reliable publish, restore and backup operations |
Webflow Acquisition and an AEO Release
Webflow, founded in 2012 and backed by over $330 million in funding, has executed aggressive AI-driven platform expansions throughout 2025 and into 2026. The company launched Webflow Cloud in May 2025 for full-stack app hosting. At Webflow Conf 2025 in September, it unveiled a prompt-to-production solution featuring an AI Assistant, AI code generation and AI-powered SEO tools.
In 2026, Webflow deepened its AI and enterprise capabilities. In February, the company added a Claude connector enabling Anthropic's Claude to design pages, manage CMS content and run audits. On March 12, Webflow acquired Vidoso.ai to address AI-generated marketing content that fails to reflect brand identity.
Webflow Also Launches AEO Product in Private Beta
On April 13, Webflow announced Webflow AEO, a closed-loop answer engine optimization solution in private beta. The product entered private beta on April 13 and is described by the company as an agentic system that handles measurement, recommendations, and content execution within the Webflow platform itself.
The product is built around three functions.
- First, expanded analytics within Webflow Analyze would show enterprise teams how frequently their brand is cited in AI answer engines, which prompts trigger those citations, and how AI-driven visibility connects to on-site engagement.
- Second, AEO agents would surface prioritized recommendations — technical fixes such as broken links and outdated metadata, as well as content opportunities tied to specific prompts the team is tracking.
- Third, the agents would help teams push approved changes live across their site at scale, with a review-before-publish step built in.
Webflow CPO Rachel Wolan framed the product around execution speed, arguing that most teams understand AEO matters but lack tooling built to act on it quickly. The company's pitch is that because Webflow already houses a team's site, content and brand context, its agents can close the loop between insight and shipped improvement without requiring teams to move between platforms.
What Webflow AEO Does Not Yet Establish
Webflow AEO is currently limited to private beta, with general availability for Enterprise customers described as coming soon. No pricing or timeline was disclosed. Webflow officials cited prior AEO-adjacent investments — including support for llms.txt, LLM-referred traffic insights, and an AI-assisted SEO auditing tool — and claimed the auditing tool drove 75% more monthly organic traffic for customers who adopted it, without providing methodology or third-party validation for that figure.
The two customer voices included in the announcement — a digital marketing manager at Walker & Dunlop and a director of product management at DailyOM — both spoke to anticipated value rather than documented results, consistent with a private beta rollout. AEO as a discipline remains early-stage, and Webflow is among a growing number of martech vendors staking out positioning in the space ahead of established measurement standards.
CMS Migration in Context
Technical flexibility alone doesn't guarantee operational success when migrating to headless CMS and composable architectures.
While API-first models deliver performance gains and omnichannel reach, recent analysis found they often strip marketers of visual context and day-to-day autonomy.
Modern CMS migrations center on MACH principles — microservices, API-first, cloud-native and headless. These composable architectures enable teams to assemble best-of-breed stacks rather than relying on monolithic platforms.
The Operational Reality Gap
CMSWire DXP Market Guide findings revealed that API-first architectures alone don't determine digital success. Many teams traded speed for developer queues, turning routine content changes into engineering tasks.
The market now prioritizes:
- Composable foundations with visual, low-code tooling over pure developer-centric control
- Parallel workflows where marketing and engineering move independently
- In-context editing layered on API-first delivery
Webflow Background
Webflow, founded in 2012, targets marketing, design and product leaders at mid-market and enterprise organizations seeking to accelerate website deployment without relying on engineering resources. The company offers a visual website builder combined with AI tools, including an AI Site Builder and AI Assistant. Managed hosting is provided via Webflow Cloud.
Have a tip to share with our editorial team? Drop us a line: