A developer and blogger used Claude Code with parallel agents to audit and rewrite posts on his own site after search traffic collapsed. He reports quality scores rose and indexing recovered, but is candid that he cannot say what caused the recovery.
- First reported
- mejba.me · 1 Aug 2026
- Added
- 13 Oct 2026
- Source checked
- 13 Oct 2026
What they did
A Claude Code session read the production database in read-only mode and produced per-post reports, then ten parallel research agents scored posts against target queries. Rewrite agents each owned a fixed set of post IDs and had to cite named evidence, and a Python verifier checked headings, internal links against a slug index, banned phrases and minimum scores before a script backed up each row and updated one post at a time. The 84-post job ran in seven batches, with a manifest file so work could resume when sessions hit usage limits.
What happened
The poster says average internal quality scores rose from about 75 to 86 and indexing recovered over the following weeks after indexed pages had fallen from about 7,100 to about 1,700.
Keep in mind
Automated content had caused real damage first: in one news section most cited sources were dead links and all those articles were pulled. Technical fixes overlapped with the rewrites, so the cause of recovery is unclear, and it was his own site rather than a client's.
Try it with your agent
Connect read-only to <blog database> and produce a report per post: target query, heading structure, internal links and obvious quality problems. Score each post against <target query list> and propose rewrites only for the bottom <number>. Before anything is saved, run a check that every internal link exists in <slug list> and every cited URL loads, and back up each post to <backup folder>.
Replace the <angle brackets> with your own details.
Original source
mejba.meUser storySomeone who uses the agent described their own setup. Figures are theirs.
