Changelog

In August we said automated guideline checks were coming to app submissions. They’re live. The App submission form now checks your submission before it accepts it, and names the field to fix when a check fails.

What the form checks

• Listing content, URLs, and install URL against the Marketplace Guidelines: English copy, disclosed pricing, explained scopes, review access that doesn’t expire, hosted demo videos, and an install URL whose client_id and scopes match your submission and that starts a valid install when probed.
• Submission artifacts. A published .webflow.io testing site with your app installed and, for new or changed Designer Extension bundles, the private review ZIP with source maps, package.json, and the lockfile.
• Your App Review Preflight receipt. A receipt is now required for new Apps and for updates that change your App’s code or scopes; listing-only updates skip it. The form verifies the receipt with Preflight and reads the result of that run. ready and needs_review pass. changes_required blocks submission until you fix every Blocker and Required update and run Preflight again.

Preflight’s production-runtime findings don’t block submission. The published-site practices they check, such as subresource integrity and immutable script URLs, are recommended practices, not review gates.

Preflight only blocks on certain matches

App Review Preflight now labels each finding on two axes. The published guideline sets the weight: a MUST is a Blocker or Required update, a recommended practice is a Suggested update. How certain the match is decides whether it gates: only a certain match produces changes_required, a probable match goes to Manual review (needs_review), and a hint stays a suggestion. A syntax-tree pass confirms context the pattern match can’t see, such as whether window.open runs at load or inside a click handler, and React DOM’s resource hoisting no longer registers as script injection.

What to do before you submit

Run Preflight on the bundle and review ZIP you’re about to upload, fix what it reports, and paste the receipt into the form. A clean run is not an approval, but it removes the round where a reviewer finds what Preflight would have told you first. See Submitting your app for the full list of checks.

Questions

Open a ticket at support.webflow.com. Support tickets are the reliable path to the Marketplace team.

MCP v2.2 gives agents the data to run an optimization loop. They can read Optimize results to see which variation is winning, track your AEO performance across answer engines and AI crawlers, and use new page-level Analyze reports (scroll depth, window height, page flow, and goals) to understand why. Together, that gives agents what they need to validate the tests you run and improve your AEO scores.

v2.2 also adds team administration, so agents can manage workspace and site access and tie Webflow permissions into your other systems.

New tools

AEO

Agents get read access to answer engine optimization AEO data, which shows how AI bots visit your site and how answer engines mention and cite you. Agents can now:

• Measure LLM crawler traffic, as a total request count or as the pages crawlers request most.
• Review tracked prompts and the history of their executions, including the full response when it is still stored.
• Track brand visibility as one score or a time series, or grouped by topic or prompt.
• Analyze citations: citation rate by topic or prompt, the most-cited domains, cited paths for a domain, citation share for a page or CMS item, competitor citations, and individual citation rows.
• Read the query guide before building a query.

Optimize

Agents get read access to Webflow Optimize results, so they can report on which variation is winning. Agents can now:

• List the Optimize resources a token can access, and the optimizations in each with their type, status, and intervals.
• Read results for one optimization over a report window: per-variation results overall, split by an audience dimension, or per daily or weekly bucket.
• Discover the goals and dimensions available for an optimization, and the values a dimension took.

Team Admin

Agents can manage who can work in a workspace and on its sites.

• List a workspace’s members and invites, the members with access to a site, and the built-in and custom site roles a workspace can assign.
• Invite someone to a workspace by email, with initial site access.
• Grant, change, or revoke a member’s access to a site.
• Change workspace roles for one member, or for up to 100 members and invites in a single call.
• Remove a member from a workspace and all of its sites.

Updates

Analyze

Deep page-level data like scroll-depth distribution, average browser window height, page flow, site goals, and daily conversion counts

Campaigns

Campaigns can now personalize images. Agents can create image fields as well as text fields, and bind them to element settings and component props.

Box element

Agents can now build with Box, Webflow’s single element for structure and layout. Box replaces the Div Block, Section, Container, Columns, Grid, V Flex, and H Flex elements, and the HTML tag is a setting on the Box: div, section, header, footer, nav, main, article, aside, address, or figure.

• Agents can create a Box directly and set its tag.
• Asking an agent for a Section or Container now creates a Box, with the section or div tag.
• Elements already on your sites keep working.

Migration

No tool or action names changed in v2.2, and everything in this release is additive.

Learn more

See the MCP Reference for the full set of actions and required parameters.