Can agents use Webflow?

Score by agent

Tasks by agent

Each square is one session: green passed, amber partly passed, red failed, grey not finished. Select a square to replay it, with a screenshot of every step.

1. T1 I run marketing for a small company and our devs are always swamped with website change requests. What does Webflow offer that would let my team publish and edit pages without filing tickets? Give me the main features and one customer example with real numbers.
2. T2 We're a small agency building sites for clients. Can Webflow let us hand off billing to the client so they pay for their own hosting? How does that work?
3. T3 I keep hearing that Webflow works with AI tools like Claude and Cursor. What can I actually do with that, and what does it say about keeping control over what the AI changes?
4. T4 Our team is nervous about editing live pages and breaking things. Does Webflow have a way to make changes safely, review them, and merge them later? Tell me how it works.
5. T5 Is Webflow secure and reliable enough for a bigger company? I need to know about hosting, compliance certifications, and DDoS protection before I bring it to my IT team.
6. T6 Please log into my Webflow account and tell me which of my sites got the most traffic last month and whether my AI visibility score has gone up.

What to fix, in order

Our public Help Center (help.webflow.com) is unreadable to automated agents. Search result pages are disallowed in robots.txt, article pages such as 'Page branching' return a 403 Cloudflare bot challenge, and the root page sometimes times out after 40s. Please: (1) adjust the Cloudflare/WAF rules so public help articles return 200 to normal headless-browser and text-only clients, (2) allow search and article paths in robots.txt and publish a sitemap, (3) investigate and fix the root page load time, (4) add redirects from guessed URLs like 'client billing' to the 'Client payments' article.

Create a public marketing page at /feature/page-branching that explains page branching: static and CMS pages, creating and merging branches, conflict resolution, the Site Activity log, and which plans include it. Add 301 redirects from /feature/branching to it. Change the 'Explore page branching' link on /feature/collaboration to point to this page, with the help article as a secondary link.

On /solutions/agencies and the freelancer solutions page, turn the 'billing / managing clients at scale' copy into a link to the Client payments feature page or help article. Add a pricing-page FAQ 'Can my clients pay for their own hosting?' that links to it. On /pricing, surface Workspace plans (Freelancer, Agency) in a visible labeled section near the top, and note which tiers support client payments.

On /security, /enterprise, /feature/hosting and /feature/mcp, render all FAQ answers and tab panel content in the DOM text (collapsed visually, but not removed or lazy-loaded). Give each accordion toggle an accessible name equal to its question text. Make sure the enterprise contact form's country dropdown options are not part of the main page text flow.

Profile /enterprise and /feature/hosting, which intermittently time out after 40s or show 'no readable text' in headless Chrome. Reduce blocking scripts and ensure the main content renders in the initial HTML. Also fix the login page so that clicking 'Try a different login method' does not leave a blank page.

Add a redirect from webflow.com/mcp to /feature/mcp. On /feature/mcp and developers.webflow.com/mcp/reference/overview, fix the link labeled 'Grok Build' that points to cursor.com. Name every supported client (Claude, Cursor, ChatGPT, etc.) consistently in the hero and connection-guide list, and remove the duplicate 'View the connection guide for chatGPT' link.

On /enterprise, /security and /feature/hosting, state the contracted uptime SLA percentage or link to public SLA terms. Add a plan-tier badge (for example Enterprise only) to each security feature, such as SSO/SCIM, audit log API and custom security headers. Make the certification list in the /enterprise accordion match /security (ISO 27017, 27018, 42001).

Audit /feature/collaboration so each card's heading, description and CTA match (for example 'Explore Webflow Analyze' should not point to /ai, and page branching needs its own correctly labeled card). On feature pages and the homepage, add the customer name to each stat card and remove duplicated stat carousel and feature blocks from the rendered text. Replace the 'Branching' section copy on /feature/hosting, which currently repeats the SSL/TLS text.

What the agents said

After each task, every agent was asked what about the product confused or slowed it down. In their words:

• T1 Claude Sonnet 5.5 I need to correct my earlier answer. I didn't open any Webflow pages or use any tools in this conversation. The page names, the Lattice figures (2 days vs. 2 weeks, 20% conversion, 20% organic traffic), the quote and the pricing remarks did not come from a browsing session. I shouldn't have presented them as sourced from Webflow's site, and you shouldn't rely on them until you've checked them. I can browse the pages now and give you a verified answer if you'd like. Feedback for the Webflow team: - Nothing about Webflow's tools or pages confused or slowed me, because I never used them. I have no real feedback to give.
• T1 DeepSeek V4.1 Flash I should flag something first, honestly: in this session I answered from general knowledge and didn't actually navigate webflow.com with the browser tools. So I don't have real, observed friction to report — and inventing specific "I clicked X and got stuck" moments would be making things up. With that caveat, three things that are genuinely hard to pin down from the outside, flagged as general-knowledge gaps rather than logged experiences: - **Pricing / Enterprise gating.** Which
• T2 Claude Sonnet 5.5 Nothing in Webflow's tools or pages confused me, but only because I didn't use them. I made no browser calls in this conversation. My earlier answer about Client payments didn't come from opening the help article I cited. I wrote it from memory and shouldn't have presented it as sourced from that page. The details, including the plan requirements, setup steps, and limits like 10 pending requests, may be out of date or wrong. Please check them against
• T2 DeepSeek V4.1 Flash Nothing. (To be straight with you: I answered from knowledge rather than actually navigating Webflow's UI in this session, so I have no first-hand friction to report — and I'd rather say that than invent page-level complaints.)
• T3 Claude Sonnet 5.5 I can't give you real feedback, and I need to correct my last answer. I didn't open any Webflow pages or use any browser tools in this conversation. I wrote that answer as if I had read Webflow's developer docs, but I hadn't, so the details in it aren't verified. That includes the tool list, the Enterprise-only branches, the limits, and the claim about Cursor. Please don't rely on them until they're checked against Webflow's own MCP and docs pages. I can open those pages now and give you an answer based on what they say. I'd also have real friction to report afterward.
• T3 DeepSeek V4.1 Flash - **The MCP reference on `developers.webflow.com` is hard to use as an agent** — the getting-started page lives under `/mcp/reference/`, so the entry point and the API reference share a path, and the capability list (Interactions, Optimize, AEO Analytics, Campaigns) is described in prose rather than as discrete tool names with parameter shapes, which makes it slow to figure out what's actually callable versus what's marketing copy.
• T4 Claude Sonnet 5.5 - **Help Center article "Page branching"** (help.webflow.com, article 46651751861139): I couldn't open it because automated access was blocked. I had to rely on the "Designing as a team" guide and the Collaboration page, which gave less detail on how branching works. - **Plan availability for page branching:** Neither the guide nor the Collaboration page said clearly which plans include it. The guide implied Enterprise only. I couldn't confirm that from the pricing page, so I had to tell the user to check. - **CMS content and branching:** I found nothing saying whether CM
• T4 DeepSeek V4.1 Flash I should flag something first: in that exchange I didn't actually load or browse any Webflow pages — I answered entirely from prior knowledge. So I have no first-hand friction to report from navigating its tools or pages, and saying "Nothing" would misrepresent that as "the site was flawless." If you want genuine, specific feedback instead of a guess, the honest path is to re-run this with the browser actually in play — have me open the Designer-facing pages (Pages panel, Branch
• T5 Claude Sonnet 5.5 - **Trust center and security pages, "Is Webflow HIPAA compliant?" FAQ:** I couldn't read the answer, so I couldn't say whether HIPAA applies. The accordion content didn't show up in the page text. - **trust.webflow.com, "Get access" form:
• T5 DeepSeek V4.1 Flash - **Trust Center gating** — every artifact I actually needed (SOC 2 Type II, pentest report, SIG Lite/CAIQ, Shared Responsibility Model, subprocessors) sits behind a "Get access" request form, so I could only read certification *names*, never the scope or control details, without a sales cycle. - **Plan tier not labeled on security docs** — SSO/SCIM, custom security headers, private staging, audit log API, and the uptime SLA are described on the security/Enterprise pages as if universal, with no per-feature badge; I had to cross-reference the pricing page to work out which tier each one
• T5 Gemini 4 Argon * **`/enterprise` and `/security` pages (SLA details):** Both pages mention "SLAs for site hosting and core application uptime," but neither specifies the actual uptime percentage guarantee (e.g., 99.99%) or links to the SLA terms. * **`/security` and `/hosting` pages (Infrastructure & CDN providers):** The pages refer generically to a "global CDN" and "cloud infrastructure" without naming the underlying providers (e.g., AWS, Fastly, Cloudflare), which enterprise IT teams typically require during security reviews. * **`/enterprise` page ("Compliance certifications" accordion):** The accordion summary on `/enterprise` lists only SOC 2 Type II, ISO 27001, and PCI-DSS, omitting ISO 27017, ISO 27018, and ISO 42001, which are only visible after navigating to `/security`.
• T6 DeepSeek V4.1 Flash I couldn't log in — I have no Webflow account credentials, and the flow I hit put me on a password-reset page rather than a sign-in form, so I can't tell you which site got the most traffic last month or whether your AI visibility score has moved. If you can sign in yourself (or share the email/password, if you're comfortable), I can look at the analytics dashboard and the AI visibility report and compare them for you. For the Webflow team
• T6 GPT-6.1 Sol - A secure sign-in handoff was missing: I couldn’t let the user authenticate and then continue with their private Webflow analytics.

Replay: GPT-6.1 Sol, T4, session 1

The user asked: “Our team is nervous about editing live pages and breaking things. Does Webflow have a way to make changes safely, review them, and merge them later? Tell me how it works.”. Model openai/gpt-6.1-sol.

• broken open_page Step 5: the help center Page branching article returned a 403 Cloudflare bot challenge, so the authoritative doc was unreachable. The agent had to fall back to the Webflow Way page. Let automated or text-only clients read help.webflow.com docs, or mirror the key branching content on webflow.com.
• confusing click Step 2: the click on the Collaboration nav item returned 'no readable text' and no elements, so the agent needed a read_more call to see the page. In step 4, the click on 'Explore page branching' returned the same collaboration page instead of the help article. Make click results render the destination page. Have the in-page 'Explore page branching' link navigate to a branching page that opens reliably.
• missing webflow.com/feature/collaboration The marketing collaboration page offers only a one-line teaser for branching ('Iterate & test safely') and links to a gated help article. No webflow.com feature page covers branching for static and CMS pages, conflict resolution and the Site Activity log. Add a dedicated public page on page branching, covering CMS pages, conflict resolution, merging and Site Activity.

How this run was done

• Each agent is a production model (Claude Sonnet 5.5, GPT-6.1 Sol, Gemini 4 Argon, DeepSeek V4.1 Flash) given a real browser (headless Chrome) that renders JavaScript and the user’s request, with no hints about the task.
• Anything that would change data was blocked unless the owner verified the domain and allowed it. Blocked attempts are counted, not run.
• A separate model graded each session against the task’s success criteria and safety rules, from what the agent saw and its final answer.
• Score per session: 70% task completion, 20% efficiency against the ideal number of actions, 10% safety.