You want to point Claude at your WordPress archive and say add a meta description to every post that is missing one, fix the inconsistent titles, and refresh the posts that mention the old product name. What stops you is the live site. It has real traffic, a bulk-edit plugin writes straight to the database, and one bad pass means restoring from a backup.
Scratch changes where the edit happens. Claude does 99% of the work, reading and rewriting every post and page as files on your laptop. The last 1%, deciding what actually goes live, stays with you. Nothing publishes until you have seen the change as a diff and approved it.
How it works
- Scratch pulls your content into files. Posts, pages, and any custom post types come down to a folder on your laptop, auto-discovered, one file each.
- Claude edits the content. Open the folder in the Claude desktop app. Try a prompt on a few posts in Chat, then let Cowork or Code run it across the archive. Add a meta description under 158 characters to every post that is missing one. Claude edits the files, never the live site.
- You review every diff and publish. Scratch shows each change next to the original, word by word. Approve what ships, and Scratch writes only those posts back over the REST API.
What people use it for
Most people arrive with an archive that has aged, because updating it by hand means opening every post one at a time.
- Add a meta description to every post that is missing one, each under the limit.
- Fix inconsistent title case and formatting across the whole archive.
- Refresh older posts that mention an old product name, price, or policy.
- Add alt text across the media library.
- Tidy excerpts, categories, and tags so archives and feeds read cleanly.
Pull 50 posts to feel the loop, then point Claude at the whole archive.
Why not a plugin?
A bulk-edit plugin or an MCP server writes straight to your live database. The publish button is wired straight in, so one bad pass and you are restoring from a backup.
Scratch gives Claude the same full read and write access, but against a local copy. The publish step is pulled out and handed to you. Claude can change anything; only you can ship it. On a site with real traffic, that is the difference that matters.
What Claude edits in WordPress
- Post and page bodies, with block content preserved
- Titles, slugs, excerpts, and publication status
- Custom post types and taxonomies, auto-discovered
- Advanced Custom Fields and image alt text across the media library
Templates and template parts are excluded, and post meta is hidden by default so plugin-owned SEO fields stay safe. Validators check length, required fields, and any rule you set. For the full picture, see Scratch for WordPress.
Questions people ask
Is this an MCP server or a WordPress plugin?
No. A plugin or MCP gives Claude the publish button straight to your database. Scratch does not. Claude gets the same access, but publishing is a separate step you approve, one post at a time.
Will Claude touch my theme or plugin settings?
No. Templates and template parts are excluded, and post meta is hidden by default, so plugin-owned SEO fields are not edited by accident.
Can I undo a change after it ships?
Yes. Every published post is reversible from Scratch, per row. The original sits next to the rewrite until you decide which one stays.
Why not just use a bulk-edit plugin or a script?
A bulk-edit plugin and a custom script both write straight to the live database with no word-level diff and no per-post approval, and a find-and-replace only does exactly what you spelled out. Scratch puts an agent on the edit, so it handles the messy cases a rule cannot, and holds every change as a diff you approve before anything ships.
Can it handle hundreds of posts at once?
Yes, that is the use case. Pull 50 posts to feel the flow, then pull the whole archive. Cowork and Code are built for archive-scale jobs.
Do I need to be technical?
No. Install Scratch, connect WordPress, point Claude at the folder, and approve the diffs. Validators are optional, for when you run the same job often enough to want guardrails.
See it on your own archive
The fastest way to trust it is to watch it run on your posts. Book a 30-minute demo on your WordPress site →, or try Scratch free and run the first pass yourself.