Webflow Release Notes

If you've ever needed to rearrange choices in a multi-reference field in the CMS, like changing the order of authors on a blog post, you've probably resorted to the tedious workaround of deleting every selected option, then re-adding them one by one in the order you want. This approach worked, but it was often time consuming and error prone.

Starting today, you can drag-to-reorder selected choices in multi-reference fields. Open a CMS item with one of these fields, hover over a selected entry, and simply drag the entry to a new position.

Re-ordering is also fully keyboard compatible – use left/right arrows to navigate to the entry you want to move, click spacebar to “grab” the entry, and then move left/right again to put the entry in your desired location. Once it’s in the right spot, click spacebar again to “drop” the entry into place. Changes save as a draft the moment you drop an item, just like any other CMS edit. When you're ready, you can hit publish and the new order will go live.

Get page metadata now accepts translatable, alongside the endpoints that already supported it:

• Get page content
• Get component content and get component properties
• List and get collection items, including their live counterparts

Pass the id of the secondary locale you're translating into to omit page-level fields (title, slug, SEO title/description, Open Graph title/description) excluded from translation for that locale — they're left out of the response entirely rather than returned as null. Behavior matches the other endpoints: the value must be a secondary locale id (400 otherwise), and the request returns a 403 if translation exclusions aren't enabled for the site.

Bulk add options to a select field for easier form configuration — no need to add each one manually.

Previously, adding options to a select field in a form required typing every item one at a time, which made building long lists (e.g. all countries, industry categories, etc.) time consuming.
Now, you can paste in a list of fields at once to add options in bulk.

How it works:

• Separate each option with a line break.
• Use a comma to separate the option's visible text from its underlying value (e.g., United Kingdom, UK).
  • If you don't need a separate value, you can enter the text on its own and the value will automatically match it.
• If something in your list is formatted incorrectly, the line with the error will be flagged so you can fix it without hunting through the whole list.

Tip: Pasting data from a spreadsheet? Pasted data will land as tab-separated values, and will work out of the box. No need to reformat as comma-separated!

Paste a full name=value string directly into the custom attribute field, and it will automatically split into the correct name and value fields for you.

When adding a custom attribute, you can now paste a full name=value string directly into the attribute field, and it will automatically split into the correct name and value fields for you. This enhancement removes a repetitive manual step for adding custom attributes, so all you have to do is paste once to get both fields populated correctly.

Pasted attributes are also validated automatically. If your attribute is a duplicate of an existing attribute or contains invalid characters, you’ll see a clear error message.

AEO analytics now tracks Perplexity alongside ChatGPT, Gemini, and Claude, so you can see how your brand shows up across every major answer engine.

Webflow AEO Analytics (included with Analyze for Enterprise) now runs your tracked prompts through Perplexity, alongside Claude, Gemini, and ChatGPT.

More LLMs, more signal

Your brand doesn't show up the same way across every AI model, and now you can see those differences directly. By running each of your tracked prompts through Perplexity, Claude, Gemini, and ChatGPT, you get a fuller picture of where your brand is appearing, where it's missing, and how coverage varies by model. Filter your AI Discovery dashboard by LLM to compare results.

What's next

We're also working on MCP and API access to full response data, which will let you use your own AI tools to run deeper analysis — like sentiment checking or accuracy validation — across all your prompts and topics at scale.

Webflow's AI Assistant panel now docks to the right, left or floats freely within the browser window — pick whatever fits your workflow.

The AI Assistant panel no longer covers Styles, Settings, Props, or Interactions. It opens in its own panel so you can keep editing while you chat.

Position it to fit your workflow:

• Dock right — the default. Nothing to change if this already works for you.
• Dock left — moves the panel to the left side.
• Float — detaches the panel from either dock position so you can move it anywhere within the browser window.

Switch anytime from the AI Assistant panel menu.

The translatable parameter introduced on July 27 couldn't express the workflow it was built for, so its shape has changed.

Why it changed

A translation integration reads the primary locale to get the source text, translates it, then writes the result to a secondary locale. As originally shipped, translatable=true resolved exclusion rules against the same localeId used to select the content, which left no way to do that first step correctly:

Requesting the primary locale returned the right content, but only matched exclusion rules scoped to "all languages" — rules scoped to a specific language were silently ignored, so you could receive content the site owner had excluded for the language you were translating into.

Requesting a secondary locale scoped the rules correctly, but returned content that was already translated rather than the source text.

What changed

translatable now takes the id of the secondary locale you're translating into, independent of localeId:

?localeId={primary locale id}&translatable={target locale id}

translatable=true and translatable=false now return a 400. Pass a locale id, or omit the parameter entirely.

The value must be the id of one of the site's secondary locales. The primary locale id, or any other value, returns a 400.

localeId is optional. Omitting it returns the primary locale's content, filtered for the target locale — the common case for a translation integration.

The parameter requires translation exclusions to be enabled for the site. If they aren't, the request returns a 403.

If the exclusion rules can't be resolved, the request returns a 500 instead of unfiltered content. Retry the request.

Required action: if you're passing translatable=true, replace it with the id of the locale you're translating into. If you're passing translatable=false, remove the parameter.

Affected endpoints

• Get page content
• Get component content and get component properties
• List and get collection items, including their live counterparts

Behavior that hasn't changed: only exclusion rules scoped to manual translation are respected, and omitting translatable returns the same response as if the parameter didn't exist.

Webflow’s AEO agents surface content opportunities and generate on-brand briefs and drafts that help your site get cited by answer engines.

When we launched Webflow AEO in May, we delivered a closed loop solution from measurement execution at scale: AEO analytics show teams how their brand shows up in answer engines, and AEO agents that help teams turn those insights into on brand improvements across their site.

Today, we’re excited to release new content optimization agents that help your team create and improve content that answer engines are more likely to cite. Like our technical AEO agents, they're built natively into Webflow: they read your site's structure and existing content directly, and use business context you provide — so every suggestion starts on brand.

They work in three steps:

• Recommendations — surface prioritized content opportunities, including gaps where competitors are being cited and you aren't, based on your AEO analytics data.
• Brief generation — turn a recommended topic into a structured content brief.
• Draft creation — generate a full article draft as a new CMS item, ready to review.

Plan access: This first set of content optimization agents is available to all Enterprise customers with the Analyze add-on. To learn more about what Webflow’s closed-loop AEO solution can unlock for your brand visibility, contact sales or reach out to your account rep.

How to get started:

Before you can see content recommendations, you’ll need to complete two setup steps:

1. Set up prompt tracking for the topics you want to be cited for
2. Add your competitor information and other context in Organization info under Settings.

Once you complete these steps, your content recommendations will appear in the Insights tab > AEO recommendations, where you can review the reasoning behind each one, then edit, accept, and publish in place. For more information on Webflow’s AEO agents, visit our Help Center here.

Site owners can exclude specific fields, properties, or canvas content from AI translation using the Localization panel in the Designer.

These endpoints now expose those exclusion rules through a new translatable query parameter.

Translation pipeline integrations can fetch exactly the content that should be translated, without tracking exclusion rules themselves.

New parameter

Pass translatable=true along with a secondary locale to return only content that hasn't been excluded from translation for that locale:

• Get page content: returns only page fields not excluded for the requested locale.
• Get component content and get component properties: return only canvas content and properties not excluded for the requested locale.
• List and get collection items, including their live counterparts: return only collection fields not excluded for the requested locale.

Only exclusion rules scoped to manual translation are respected — rules scoped only to automatic translation don't affect the response. Omitting translatable returns the same response as before this parameter existed. Setting translatable=true without also specifying a secondary locale returns a 400 error, since exclusions are resolved per locale.

A minor (maintenance) release to improve how the Webflow MCP works with Claude. Three groups of actions moved out of two large tools into focused tools of their own. The actions themselves are unchanged (same inputs, same behavior).

Element settings

data_element_settings_tool takes over element settings and data bindings from data_element_tool: reading and writing settings, discovering bindable sources, and setting an element's tag, visibility, and DOM id (static or bound).

Component props

data_component_props_tool takes over prop work from data_component_tool: creating, updating, and removing prop definitions, reading an instance's props, setting prop values, and resetting all props to their defaults.

Component variants

data_component_variants_tool takes over variant work from data_component_tool: creating, duplicating, deleting, reordering, and renaming variants, and reading or setting per-variant styles.

Skills based on earlier versions of Webflow MCP may need to be updated. The skill migration guide covers the updated tools and actions.

Build without a Designer session

In earlier versions, working with elements, components, styles, and variables required an active Designer session through the Webflow MCP Bridge App. In 2.0, those capabilities work on their own:

• Query and edit the element tree: text, styles, links, images, attributes, tags, settings, visibility, and display names, plus moving and removing elements.
• Create, transform, and manage components, including instances, props, and variants.
• Create, update, rename, and remove styles (classes and combo classes), and manage per-style variable modes.
• Create, update, rename, and delete variables (color, font family, number, percentage, size), and build and reorder collections and modes.
• Build elements on a page from a schema, insert component instances (including nested trees), and insert elements from HTML and CSS.
• None of these need a Designer session anymore.

New capabilities

MCP 2.0 opens up five areas of Webflow that agents couldn't reach before. Each works without a Designer session.

Analyze reporting

Agents can work with Webflow Analyze data: pull traffic over a chosen window (sessions, users, or pageviews), rank a site's top pages, break down leading values for a dimension like country, browser, or traffic source, surface the most frequent engagement events with page context, and read time on page as an aggregate or over time. Available for sites with Webflow Analyze.

Forms and submissions

Agents can read a site's forms and their schemas, list and retrieve submissions (with optional element and locale filters), update the hidden fields on a submission, and delete submissions.

Custom fonts

Agents can list and inspect a site's uploaded custom fonts, register and upload new font files, replace the file behind an existing font, update font metadata, and remove fonts individually or in batches.

Sitemap indexing

Agents can read, list, update, and bulk-update sitemap inclusion for CMS collection items and static pages.

Agent instructions

Agent instructions are markdown-based skills and rules that give agents custom guidance for working on a site. They can reference Webflow primitives like variables, styles, components, pages, CMS collections and items, and locales, and those references resolve against the site's own data. In 2.0, these instructions are provided automatically to external agents, and agents can manage them directly: searching a site's rules and skills, reading them (with referenced instructions resolved inline), and creating, updating, moving, renaming, and deleting them.

Expanded existing tools

Several existing capabilities gained new actions in 2.0:

• Pages: create a page, update settings across many pages at once, and read and bulk-update page schema markup and structured data.
• Assets: full asset and folder management (list, get, update, delete, and organize into folders), plus asset compression jobs with task tracking.
• Custom code: read and write the freeform custom code embedded at the site and page level, alongside existing registered-script management.

Still requires a Designer session

A few capabilities still depend on an active Designer session (through the Webflow MCP Bridge App):

• Element snapshots. Capturing a visual snapshot of an element, so an agent can read the current state of a site and verify its own changes before publishing.
• Selection and canvas navigation. Selecting and reading the selected element, navigating the canvas between pages and component views, reading the current page, mode, and branch, reading a site's breakpoints, and creating page folders.
• Uploading an image from a URL. Adding an image to a site directly from a public URL.

Governance

MCP enforces your workspace's permissions and roles, including custom roles: if a user can or cannot do something in the Designer, the same applies through MCP. Changes made by agents are recorded to the site audit log. This means you can give external agents site access while keeping the same permissions and audit trail as the rest of Webflow.

Migrating from an earlier version

Several tools and actions were renamed or relocated in 2.0, so skills, prompts, and automations written against an earlier version may call names that no longer resolve. A few examples:

• set_id is now set_dom_id, and add_or_update_attribute is now set_attributes.
• Element selection and canvas navigation moved to the dedicated Designer-session capabilities described above.
• Full asset and folder management moved off the image-upload tool, which now handles uploading an image from a URL only.
• The skill migration guide lists every name that changed and what to replace it with. You can also point an agent at that page and have it update a skill on its own.

Known limitations

A few things to be aware of in this release:

• Element snapshots require a Designer session. Capturing a visual snapshot still depends on an active Designer session through the Webflow MCP Bridge App. If you want an agent to run independently, let it publish to a staging domain, which supports full agent loops without the Designer.
• One workspace per authorization. When you authorize the MCP server, you choose a single workspace it can access. To use a different workspace, reauthorize. In clients like Claude and ChatGPT, that means removing the connector and reinstalling it.
• Interactions (IX3) aren't supported. Agents can't create or apply Webflow Interactions through the MCP server. Build and edit interactions manually in the Designer.
• Custom fonts cover uploaded files only. The custom font capabilities manage font files you upload. Remotely hosted Google and Adobe Fonts are still managed manually in site settings. For Google Fonts, you can download the files and upload them through the MCP server.
• Some uploads require sending a file to a presigned upload URL. Uploading an asset, or uploading or replacing a custom font file, is a two-step flow: the tool returns a presigned upload URL, and the client sends the file's bytes directly to that URL. If the client's environment or network blocks that outbound request, the upload can't complete. In that case, upload the file manually in Webflow instead.

Webflow MCP 2.0 gives your agents the context, control, analytics, and governance they need for high-impact work in production.

Webflow’s MCP makes it easy to connect with AI tools like Claude, ChatGPT, and Cursor, so you can design, build, and manage your Webflow sites inside your existing AI workflows.

With this major update, we’re adding deeper support for design & build workflows, site performance analysis, and governance.

Expanded design & build support

Build with your existing design system: Leverage the full power of Webflow styles, elements, and components – including props, slots, and variants – so you can create on-brand content that’s structured for efficient long-term maintenance.

Create and manage dynamic content: Connect elements and components to CMS data so every update made in the CMS is instantly reflected everywhere your content appears.

Manage custom fonts: Register, upload, list, update, and delete fonts.

Work without the bridge app: The bridge app has been eliminated for most use cases, giving you a smoother, more reliable workflow, and making it possible to build across multiple pages or sites simultaneously.

Please note: the bridge app will still be required for tasks that need live visual context including: snapshots, or prompts that reference a specific element on screen, like “change this heading.”

Agent Instructions

Centralize important context: Point agents at Webflow resources like your design system or CMS content, or add resources like legal docs and voice and tone guidelines so agents have all the context they need.

Define how your agents should work: Create skills and rules that instruct agents on how to complete tasks and leverage provided resources to get production-ready outputs faster.

Use instructions wherever you need them: Agent instructions can be used both by Webflow AI, and third-party agents via the MCP.

Site performance analysis

Analyze site data conversationally: Ask AI agents about traffic trends, top performing pages, engagement events, time on page, and traffic sources to get real-time insights without leaving your chat.

Share analyze data with other tools: Share site performance data with other MCP connectors in an agentic workflow, like Amplitude, Slack, Asana, and more.

Governance

Build on branches: Agents can now iterate on changes in a secure, isolated environment before pushing updates to your live site.

Enforce strict access control: Webflow’s MCP fully enforces your account roles and permissions, including custom roles, and granular access per: site, CMS collection, page, and locale.

Track MCP actions in site activity logs: Know exactly when a change was made via MCP, who triggered it, and what was affected. You can also query the activity log directly via MCP for faster, more scalable site auditing.

MCP 2.0 is now available to all users at no additional cost. To learn more, check out our Help Center articles on the Webflow MCP and Agent Instructions.

Webflow for Slack brings website management into Slack, helping teams analyze site data, manage content, and take action without leaving the conversation.

Webflow integrates with Slack, bringing AI-powered workflows directly into the place where teams already collaborate. Whether you're working independently or alongside your team, you can access your Webflow sites, surface insights, and take action without leaving Slack.

How it works

Webflow for Slack lets you interact with your Webflow sites simply by chatting in Slack. Describe what you want to accomplish, and Webflow interprets your request, uses the appropriate tools, and completes the task on your behalf.

For example, you can:

• Create, update, and publish CMS items directly from Slack
• Audit page SEO and apply metadata improvements without leaving Slack
• Ask questions about Webflow and receive step-by-step guidance in Slack

The integration is powered by Webflow's MCP server, which makes your Webflow sites, content, and workflows accessible to agents. This enables Webflow to retrieve context, surface insights, and complete tasks on your behalf directly from Slack, while honoring your existing permissions and governance controls.

Accessing Webflow for Slack

Accessing Webflow for Slack

There are multiple ways to access Webflow for Slack. Regardless of how you access the integration, the underlying capabilities remain the same.

Message Slackbot - Generally available and free to use

• DM Slackbot — Ask Slackbot questions about your Webflow sites or take action using natural language.

Webflow Slack Agent - Available in public beta

• DM @Webflow — Start a one-on-one conversation with Webflow directly within Slack to access the same capabilities in a dedicated chat experience. You can also launch a DM with @Webflow from Slack's Agents menu.
• Mention @Webflow in public Slack threads — Bring Webflow into team conversations to answer questions, surface insights, and take action without leaving the thread.

The Webflow Slack Agent is free to use during the public beta period.

AI credits will apply once it's generally available.

We're actively improving the Webflow Slack Agent and would love to hear what you think. Share your feedback here.

Learn more

• Install the Webflow for Slack app
• View setup instructions and supported capabilities

DevLink Export supports a new opt-in camelCaseVariantNames setting in webflow.json that converts Style Variant names into camelCase values for the exported variant prop.

What changed

New camelCaseVariantNames option under devlink-export in webflow.json. It's off by default, so existing exports are unaffected.

When turned on, a Style Variant named Papaya With Whip exports as papayaWithWhip instead of the raw display name. Names that would collide, or that would otherwise produce an invalid value (a number-only name, or a JavaScript reserved word), fall back to safe, deduplicated values.

To use

Set "camelCaseVariantNames": true under devlink-export in webflow.json, then re-run webflow devlink export.

For more information, see Configuration options.

Webflow is now available as an app in ChatGPT — so whether you're optimizing content or managing your site, you can do it without leaving ChatGPT.

Here are a few ways you can use the Webflow app:

• Audit your site for SEO, content quality, and usability, then implement fixes directly
• Create and update CMS content across your collections
• Analyze site structure, content, and performance to find out what's working and what to improve

To get started, open the Webflow app listing in Chat GPT and grant access to the Webflow sites you'd like it to manage.

Note: Webflow for ChatGPT is currently available at no additional cost and does not consume AI credit AI credits. As we expand capabilities over time, certain AI-powered actions may require AI credits in the future.

Learn more:

• Connect Webflow to ChatGPT
• Read the Help Center documentation