A free Claude Code plugin, by unfayr
Pit fixes every page in one stop. You drive.
Pit Crew crawls your whole site, asks you a few questions once, then rewrites every page’s title, meta description and H1 in one naming style. You review it all in one Excel workbook and approve what you want.
/plugin marketplace add timlaneseo-tech/unfayr-ref/plugin install pitcrew@unfayrFree. No account. Runs inside Claude Code on your machine. Try it first with no setup: /pitcrew --sample ridgeline-plumbing.example
| Current title | New title | Status |
|---|---|---|
| Water Heater Repair and Replacement in Boise, Idaho | Ridgeline Plumbing | Water heater repair in Boise | Ridgeline Plumbing | ok |
| Sewer Line Repair, Camera Inspection and Trenchless Replacement | Ridgeline Plumbing | Sewer line repair in Boise | Ridgeline Plumbing | needs review |
| 24/7 Emergency Plumber in Boise | Ridgeline Plumbing | Emergency plumber in Boise | Ridgeline Plumbing | has [ADD] |
A fictional plumber. The full sample run is 12 pages.
What you get
One workbook. One style. Your yes.
Pit Crew reads what your pages say, what the search results look like and a short interview about your business. Then it does the tedious part.
The workbook.
Current and new title, meta description and H1 side by side, the reason, where each fact came from, an Issues column and an Approve column. Other tabs cover a summary, deeper fixes for your 25 most important pages and your naming style.
The naming style interview.
A handful of questions it can’t answer from your pages: what you do, where you work, what proves you are established. Every title then follows one pattern you can see and change.
Publishing with a yes.
Tick the rows you want and say publish. You see a dry run first. Nothing goes live until you say yes in the conversation.
Safety
It never invents. It never publishes on its own.
Every number, price, year, place, credential and guarantee in the new copy has to be on that page or in your answers. When good copy needs a fact Pit Crew does not have, it leaves a slot instead of guessing, and that row can’t be approved until you fill it in.
For example: [ADD: years in business]
- Dry run first. You see what will change, which rows will be skipped and why, and a few before and after examples.
- Backup before every publish. The live values are saved first, and every publish prints a rollback command.
- Rollback restores only what Pit Crew applied. Edits someone else made since are left alone.
- Changed pages are skipped. If someone edited a live page after the crawl, Pit Crew will not overwrite it.
- Failed rows are never published. That includes any row that still has an [ADD] slot.
- H1 renaming is opt-in. On Shopify and WordPress an H1 can rename a product or post, so it is skipped unless you ask.
Platforms
Publishes where your site lives.
You only set up access for the platform you use, with the narrowest permissions that work. You don’t need any of it to run Pit Crew and get the workbook.
Shopify.
SEO title and description for products, collections, pages and articles, through a custom app token.
WordPress.
Through an application password. If Yoast or Rank Math can’t be written to, you get a CSV for your SEO plugin’s own importer instead.
Webflow.
Static pages and CMS items. CMS edits stay staged until you click Publish in Webflow. Pit Crew never publishes the site.
Static sites and Git.
Edits the files in your local clone and shows the diff. Committing and deploying are separate yeses, and it never pushes.
Wix, Squarespace and others: the workbook is your handoff. Setup steps for each platform.
Built on current guidance
Follows Google’s own documentation.
Titles are descriptive and concise, meta descriptions are unique and factual, and titles are checked for rendered width, not just characters. Its AI-answer advice comes from published research and promises nothing.
Our test
In one fixture site of 12 pages (one run each, scored by Pit Crew’s own lint), Pit Crew’s rewrites had unsourced numbers or claims in 1 row, length failures in 0 and duplicates in 0, and 11/11 (100%) of titles matched the naming convention, against 1, 1, 0 and 9/11 (81.8%) for plain Claude.
The rules are Pit Crew’s own and Pit Crew was told them, so this shows how well each follows that way of writing, not which is better in general. Read the full benchmark.
Install
Two commands, then try the sample.
Run these in Claude Code. Pit Crew needs Node 22.18 or newer, and installs three small runtime dependencies the first time it runs.
/plugin marketplace add timlaneseo-tech/unfayr-ref/plugin install pitcrew@unfayrThen try it in 90 seconds.
No site, no accounts, no keys. Sample mode runs the whole process on a fictional plumber, with no network.
/pitcrew --sample ridgeline-plumbing.exampleFor your own site, type /pitcrew example.com.
Questions
The short answers.
Is it really free?
Yes. Use it on your own site and your clients’ sites. It can’t be sold, modified or rebranded. The Pit Crew Free Use License is in the GitHub repository. A run uses your own Claude plan; there is no API, subscription or per-page fee from us.
Does it publish on its own?
No. Nothing leaves your machine until you approve rows in the workbook, read the dry run and say yes in the conversation. It takes a backup first and prints a rollback command.
What does it need?
Claude Code and Node 22.18 or newer. To publish, access to your platform with the narrowest permissions that work. For the workbook alone, no keys are needed. Everything runs on your machine, with no telemetry and no account.
Which sites does it work on?
Up to 1,000 indexable pages per run. It publishes to Shopify, WordPress, Webflow and static sites in Git. On other platforms the workbook is the handoff.
What is in the Excel workbook?
Five tabs: Summary, Pages, Deep fixes, Naming style and Read me. Pages is where you work: current and new copy, the reason, the source of each fact, an Issues column and an Approve column.