On a Wix blog that has been running a while, the content jobs add up. Rewrite a backlog of posts in a new tone. Refresh the SEO slug and excerpt across the archive. Retag and recategorize everything after a content reshuffle. By hand it means opening each post in the Wix editor one at a time, and there is no fast way to work across the whole blog at once.
Scratch pulls your Wix Blog down to files on your computer, one file per post. Your AI rewrites every post, 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 publishes 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 blog in sync with the rest of your tools, and Scratch is where you wrangle the content into shape first.
What Scratch edits in Wix Blog
- Post body (rich content / Ricos preserved)
- Post title and excerpt
- SEO slug
- Tags, categories, and hashtags
- Featured flag, comments toggle, language, and hero image
How it works
- Scratch pulls your blog into files. Every post comes down to a local folder, one file per post, with rich content (Ricos) preserved so block structure, embeds, and image positions round-trip without touching layout. Nothing touches the live post.
- Your AI rewrites the fields you point it at. Open the folder in the agent you already use. Try a prompt on one post, then let it run across the whole blog. Rewrite every post in this tone and tighten the excerpts. It edits the body, title, excerpt, slug, tags, and the rest in the files, never the live post.
- 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 sends the edits back through the Wix API to the draft side of each post, never the published version. Posts are created one at a time, since the Wix API does not support bulk create, so the first run can take a minute on a big blog.
What teams use it for
- Rewrite a backlog of posts in one consistent tone in a single pass.
- Refresh SEO slugs and excerpts across the whole archive.
- Retag, recategorize, and clean up hashtags after a content reshuffle.
- Set the featured flag, comments toggle, and language in bulk.
- Swap or standardize hero images across a run of posts.
- Tidy older posts for tone and SEO without rebuilding them in the editor.
Why not let AI write straight to Wix?
A direct API write or an MCP server hands the AI the publish button straight to your live blog. There is no diff, no review queue, no rollback. One confident pass rewrites every post and ships it, and by the time you spot the wrong tone or the wrong fact it is already live in front of readers. It is also the slow path, because every post is a separate API call.
Scratch gives the AI the same full read and write access, but against a local copy of your blog. It works on the draft side of each post, not the published version, and it pulls the publish step out and hands it to you. The AI can change anything, only you can ship it, and every published change is reversible per record.
What's safe, and what's locked
Scratch edits the draft side of a post, never the published version, so a run never changes what readers see until you publish the draft yourself. Block structure, embeds, and image positions round-trip without touching layout. 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. Optional Python validators check length and required fields before anything reaches you for review. One thing to expect: posts are created one at a time, since the Wix API does not support bulk create, so the first run can take a minute on a big blog.
Questions Wix users ask
Does Scratch edit my live Wix posts directly?
No. Scratch edits the draft side of each post, not the published version, so a run never changes what readers see. You review every change as a word-level diff in the Scratch desktop app, and the edits land in the draft for you to publish when you are ready.
Does it preserve my post layout and embeds?
Yes. Rich content (Ricos) is preserved, so block structure, embeds, and image positions round-trip without touching layout. The AI rewrites the prose and fields, and the post structure comes back intact.
Why does the first run take a while on a big blog?
Posts are created one at a time because the Wix API does not support bulk create. On a large blog the first run can take a minute as Scratch brings every post down to files. After that, you are editing local files, which is about 10x faster than working over the API.
If a published change is wrong, can I undo it?
Yes. Every published change is reversible per record. The original stays next to the rewrite until you decide which one stays, so a bad edit is never a one-way door.
See it on your own Wix blog
The fastest way to trust it is to watch it run on your blog. Book a 30-minute demo on your blog, or try Scratch free and run the first pass yourself.