As of September 2026, six things. Webflow used its opening keynote on September 2 to announce Source, a new platform, plus Campaigns, Assets, Releases, MCP 2.1, and expanded agents inside Webflow AEO. Most are in beta, preview or coming soon rather than generally available today.
That last point is the one that gets lost in the coverage. A conference keynote is a roadmap as much as a release, and confusing the two leads teams to plan around things they cannot use for months.
So this is our read of the announcements: what each one is, when Webflow says you can have it, and which of them we would actually change a project plan for. We build in Webflow every week, so the filter here is practical rather than enthusiastic.
It is Webflow's new platform for marketing teams working alongside AI agents, and it is the largest announcement of the event. Webflow describes it as connecting your codebase and your martech stack, bringing agentic and visual development into one shared operating environment.
The idea underneath it is that code becomes the foundation for everything that ships on your site. With direct access to that code, Webflow says its agents can take on larger and more complex changes without the constraints of an abstraction layer. That is a meaningful shift for a company whose whole history is a visual layer on top of code.
Source also introduces Views, described as a new primitive that lets teams shape their software to the exact jobs and outcomes they own, with dedicated surfaces for site building, campaigns, content and optimization. Source is available in a limited research preview, which means it is a direction to understand rather than a tool to plan around.
Only one of them fully. Agent Instructions generation began rolling out to everyone on the day of the keynote. Everything else sits somewhere between later this month and later this year, and Source is preview only.
| Announcement | What Webflow said about availability |
|---|---|
| Agent Instructions generation | Rolling out to everyone from the keynote day |
| MCP 2.1 | Available to everyone later that month |
| Agent Presence | Available for all customers later that month |
| Campaigns | In beta, available for purchase the following month |
| Assets | Entering beta in October |
| Releases | Available in beta later in the year |
| Source | Limited research preview |
Performance marketers, specifically. Campaigns is built to take a team from a brief to a live campaign in hours. You give it a URL to your live site and an agent pulls your colours, fonts and interface elements to build a brand system, and Webflow notes this works whether or not your main site runs on Webflow.
From there it reviews your brief, helps refine audience and channel choices, then generates a primary landing page plus variants for each audience, target account or keyword. It also generates ad creative and can push ads and pages into channels like Google Ads.
The part that will decide whether marketers adopt it is the measurement. Once a campaign is live, Campaigns tracks conversions and connects to HubSpot or Salesforce so teams can measure pipeline, with agents recommending updates to improve conversion. Landing page generators are not new. Ones that close the loop to pipeline are rarer.
It gained agents that write. Webflow AEO already showed where you are mentioned and cited across ChatGPT, Claude, Gemini and Perplexity. The new content creation agents find the topics where competitors get cited and you do not, then write the brief and draft original content directly in your CMS.
Webflow also published the study behind the product. It analyzed the websites of 2,000 companies and found the median company appeared in 16% of the AI answers it would want to be part of, and was cited in those answers only 6% of the time. That is a useful benchmark whatever platform you are on.
Two things are flagged as coming. Agents that refresh existing content are due in the following months, and later in the year external agents will be able to reach a site's AEO data through the Webflow MCP. Webflow says all Enterprise customers have AEO agents by default, with analytics through the latest version of Webflow Analyze for Enterprise. If you want the platform neutral version of this work, our piece on optimising service pages for AI search covers it.
Read them carefully rather than quoting them. Webflow states that AEO customers get 70% more mentions and 120% more citations than non-Webflow brands. It also publishes an unusually candid footnote explaining what that figure is.
The footnote calls it a directional finding from internal Webflow data covering 158 customers who accepted AEO recommendations, compared with 187 who received the same recommendations and did not, measured from May 19 to July 13 of 2026. It says plainly that the difference does not isolate the recommendations from other drivers, including seasonality, indexing changes, marketing activity and site changes.
We think publishing that caveat is to Webflow's credit, and we would still not repeat the headline number as evidence. It compares customers who acted on advice against customers who did not, which is a group difference as much as a product effect. Teams that act on recommendations tend to do other things well too.
Three practical additions. MCP 2.0 shipped earlier in the summer and gave agents in Claude, ChatGPT and Slack access to design systems, component props and variants, and site analytics via Webflow Analyze. MCP 2.1 extends that.
Agents can now build Interactions using GSAP, including complex timeline based animations, while keeping the visual controls for timing. CMS querying improved from sorting and filtering on a few known fields to filtering on custom fields, searching across reference fields and paging through results, which Webflow frames as fewer requests and less token burn on content audits. And Webflow Cloud deploy error logs now surface to agents, so tools like Claude Code, Codex or Cursor can work an issue and redeploy.
Of everything announced, this is the update we expect to change day to day work soonest for developers. Our overview of Webflow Cloud covers the deploy side it plugs into.
They make staging a whole site possible rather than a page. Releases branches an entire site, including pages, CMS content, components, assets and locales, so a team can build and stage a large launch before anything moves live. A Release Manager tracks what has been updated, by whom, and where it stands.
The detail we like is that as individual releases ship, you can pull those updates into your open branches, which is the thing that stops long running work drifting from production. Agents can contribute inside a release and are subject to the same roles and permissions as teammates when it is time to merge and publish.
This is squarely aimed at enterprise teams, and it addresses the single biggest complaint we hear from them about Webflow. It is in beta later this year, so it does not solve anyone's problem this quarter. Our piece on page branching in Webflow covers what exists today.
Mostly it confirms a direction we were already building for. Every one of these products assumes that agents are working on your site alongside people, and that the site needs to be legible to them. That makes structured, well named, documented builds more valuable than they already were.
The concrete change we would make now is writing agent instructions properly. It is the only thing here you can do today, it costs an hour, and it improves the output of every agent that touches the site regardless of which of these products you eventually buy.
We would not restructure a project around Source. A limited research preview is a signal about where the platform is heading, and building on it before it is generally available is a way to pay for someone else's roadmap risk.
Generate your agent instructions this week and edit them until they say something specific about your brand, your design system and your CMS. Then run the AEO benchmark question honestly: of the questions your buyers ask, how many answers do you appear in? If it is anywhere near the median of 16%, that is your project for the quarter.
Wait on the rest. Campaigns, Assets and Releases will be easier to judge when they are out of beta and priced. If you want help preparing a Webflow site so agents can work on it safely, or a second opinion on which of these is worth budget, we are happy to talk it through at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.