On Webflow, the CMS is where the content lives and where the bulk jobs stack up. Rewrite every blog post in a new tone. Refresh the SEO title and Open Graph on hundreds of collection items. Fill missing alt text across the assets. Doing it by hand means clicking through the CMS one item at a time, and Webflow has no native undo, so a blind bulk write through the API is unrecoverable the moment it goes wrong.
Scratch pulls your CMS collections, pages, and assets down to files on your computer, one file per item. Your AI rewrites every item, not a sample, and about 10x faster than it works over an API because it reads the files directly instead of making a call per record. Every change comes back as a word-level diff next to the original, and nothing reaches your live site until you approve it. The same loop cleans up content here and CRM records in Scratch's sibling use case.
Scratch is the companion app to Whalesync: Whalesync keeps your CMS in sync with the rest of your tools, and Scratch is where you wrangle the content into shape first.
What Scratch edits in Webflow
- CMS collection items: rich-text, plain-text, slug, and custom fields
- Page metadata: title, slug, SEO, and Open Graph
- Asset alt text (file uploads supported)
- Multi-locale content (where Webflow exposes it)
How it works
- Scratch pulls your collections into files. CMS collection items, page metadata, and assets come down to a local folder, one file per item, with rich-text, plain-text, slug, and custom fields all available. Nothing touches your live site.
- Your AI rewrites the fields you point it at. Open the folder in the agent you already use. Try a prompt on one item, then let it run across the whole collection. Rewrite every post in this tone and tighten the SEO titles. It edits rich-text, slugs, custom fields, page metadata, and alt text in the files, never the live site.
- You review every diff and publish. In the Scratch desktop app, each changed field shows next to the original, word by word. Approve what ships, and Scratch publishes only the items you approved back through the Webflow CMS API. Designer layout, components, bindings, and reference targets stay untouched, Ecommerce collections (Products, Categories, SKUs) are out of scope, and static page content inside the Designer is never moved.
What teams use it for
- Rewrite an entire blog collection in one consistent tone in a single pass.
- Refresh SEO titles, descriptions, and Open Graph across hundreds of CMS items.
- Fill missing alt text across the asset library.
- Push a rebrand or product rename through every collection item at once.
- Normalize slugs and custom fields so URLs and templates stay clean.
- Update multi-locale content in bulk where Webflow exposes it.
Why not let AI write straight to Webflow?
A direct API write or an MCP server hands the AI the publish button straight to your live site. There is no diff, no review queue, no rollback. One confident pass rewrites every item and ships it, and Webflow has no native undo, so a blind write is unrecoverable: the original is simply gone, and by the time you spot the wrong tone or the wrong fact it is already live on every page. It is also the slow path, because every item is a separate API call.
Scratch gives the AI the same full read and write access, but against a local copy of your collections. Scratch pulls the publish step out and hands it to you. The AI can change anything, only you can ship it, and every published item is reversible per record, which is the undo Webflow itself does not give you.
What's safe, and what's locked
Designer layout, components, bindings, and reference targets stay untouched. Ecommerce collections (Products, Categories, SKUs) are out of scope for this connector, and static page content inside the Designer is never moved; only CMS collections and page-level metadata come down. You bring your own AI: Scratch holds no AI credentials and runs no model, so you sign into Claude, Claude Code, Codex, Cursor, Copilot, Cline, or Windsurf the way you already do. Nothing leaves your computer until you publish, and every published change is reversible per record, which matters most on a platform with no native undo. Optional Python validators check length caps, slug uniqueness, and any never-touch fields you flag before anything reaches you for review.
See Webflow connected to your AI agent
Questions Webflow users ask
Will anything change on my live site before I approve it?
No. Your AI only edits local files. Nothing reaches Webflow until you have seen the change as a word-level diff in the Scratch desktop app and approved it. Scratch then publishes only the items you approved back through the Webflow CMS API.
Webflow has no undo. What happens if a published change is wrong?
That is exactly why the review step matters. Every published change in Scratch is reversible per record, even though Webflow itself has no native undo. The original stays next to the rewrite, so you can roll back any item you changed instead of losing it.
Will it touch my Designer layout or Ecommerce?
No. Designer layout, components, bindings, and reference targets stay untouched, Ecommerce collections (Products, Categories, SKUs) are out of scope, and static page content inside the Designer is never moved. Only CMS collection items and page-level metadata come down for editing.
Can it edit SEO and Open Graph metadata?
Yes. Page metadata, including the title, slug, SEO fields, and Open Graph, comes down as files alongside the collection items, so the AI can refresh it in bulk and you approve every change as a diff.
See it on your own Webflow site
The fastest way to trust it is to watch it run on your collections. Book a 30-minute demo on your site, or try Scratch free and run the first pass yourself.