Webflow and personal agents: the Cloudflare route, hosting choices and the headless case Free & Pro

Webflow sites come in two kinds: hosted by Webflow, where the owner’s tools are the project settings, and exported, where the site’s HTML runs on hosting the owner controls. The Personal Agent Protocol’s discovery file is possible in both, by different routes. This page is as of 16 October 2026 and says where we have not confirmed behaviour. Agent Adapt is a WooCommerce plugin and is not affiliated with or endorsed by Webflow, Sierra or Meta.

Hosted on Webflow

A Webflow-hosted site cannot upload a file to /.well-known/, and it cannot proxy a path. It can set 301 redirects in the project’s publishing settings, from an old path to a new one, and Webflow allows the destination to be an address on another domain; until 16 October 2026 a redirect from /.well-known/poppy.json to a provider’s address was the thing to try. The protocol now says the document speaks for the host that serves it after any redirects, so a redirect to the provider’s host gives agents a document for that host, not yours. Whether Webflow applies redirects under /.well-known/ no longer matters.

The route is Cloudflare in front of the site: with the proxy on, a Cloudflare Worker answers the path before Webflow does and serves the provider’s document on your domain, and the site stays on Webflow. Webflow’s documentation on using Cloudflare with Webflow hosting covers the DNS and SSL settings that must be right for the proxy; follow that first, then add the Worker from Serving poppy.json with a Cloudflare Worker.

Exported, or hosted elsewhere

If you export the site and host it on Netlify, Vercel, nginx or anything else, the paths are yours. Either upload a poppy.json file at /.well-known/ or proxy the path to your provider’s hosted document in the host’s configuration:

• Netlify: one line in _redirects: /.well-known/poppy.json https://hosted-document-address 200. The status 200 makes Netlify proxy the request rather than redirect it.
• Vercel: a rewrites entry in vercel.json with source /.well-known/poppy.json and your provider’s hosted document address as destination.
• nginx: location = /.well-known/poppy.json { proxy_pass https://hosted-document-address; proxy_ssl_server_name on; proxy_set_header Host hosted-document-host; } The Host header is the hosted document’s hostname (agents.getagentadapt.com for Agent Adapt’s hosted Company), which the provider needs to pick the right site.
• Behind Cloudflare (Cloudflare Pages included): the Worker above.

A file you serve yourself still has to name an issuer and APIs that answer, so for most Webflow sites the proxy to a provider is the practical route. See Headless and custom stores for the static-host details.

What a provider can do for a Webflow site

For a Webflow Ecommerce store, a hosted Company reads your products and policies from the public site or through Webflow’s APIs with a token you create, lets an agent search and build a cart, and hands the customer to your checkout to pay. For a Webflow site that is a studio, an agency or a service business, the useful channel is a Company Agent answering a customer’s assistant from your content and handing off to a person. See Services and bookings.

Agent Adapt’s hosted Company is such a provider, with the Company Agent for sites that are not shops. It is built and running, in early access by email, and not yet on sale; ask at [email protected].

Common questions

Does Webflow reserve /.well-known/?

It uses the folder for its own purposes. Since 16 October 2026 the question no longer decides anything: a Webflow-hosted site cannot serve or proxy the path, so the Cloudflare Worker is the route whatever Webflow does with redirects there.

Can custom code in the head do it?

No. Custom code runs inside your pages; it cannot make a new root path return JSON.

Is Agent Adapt available for Webflow?

Not as an app. The hosted Company is built and running, in early access by email, and not yet on sale. The WooCommerce plugin is the only product you can download today.

Does the customer still pay on my Webflow checkout?

Yes. Under the protocol’s current draft the customer pays; agents have no way to. The agent hands over a link.