Viewfield + Webflow
Connect your Webflow site and Viewfield can read its pages and CMS items, stage a change from AI visibility on an item, and publish that item only when you say so.
- CMS items: title, SEO fields and the rich text body, staged as a draft
- Static pages: the SEO title and description; body changes are copy-ready for your designer
- Publish one item live as a separate press
- Your static pages and published CMS items, with their SEO fields and body
- A staged change to a CMS item or a static page's SEO fields, when a person decides a change
- A single item published, only when a person publishes it from Viewfield
What Webflow does in the loop, as your website.
Your own pages
Viewfield connects only a site served on your own hosts, and reads the pages AI answers cite or should.
A draft, on a decision
A change proposed from AI visibility shows every field before and after. Saving it writes the CMS's own draft, a revision or a pull request; nothing goes live on its own.
Publish is yours
Publishing is a separate press, offered only where the CMS has a draft to promote. A page someone edited since the proposal is never overwritten.
Never publishes your whole site
Never edits a static page's body through the API
Never touches a site that is not on your own hosts
Every action here is also an MCP tool, so Claude, Cursor or any MCP client can drive Webflow through the same doors your team uses, with the same QA. npx @viewfieldai/mcp install
Connect Webflow in minutes.
Included on every plan. Every plan starts with a 14 day free trial. No credit card to sign up.