We write and run a script performing a bulk action across many users or pieces of content — a one-time, scripted operation executed once and verified, not something left running afterward. Once it’s done and confirmed correct, there’s nothing ongoing for you to own.
Bulk user or content action script
A one-time bulk action across users or content, tested on staging, nothing left running after.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- A clear spec of exactly what action should be performed and on which users or content
- Access sufficient to run the script against your site’s data
- A staging environment or agreement to test on one first, given the scale of a bulk action
This or something else?
| You have a specific, one-time bulk action ready to run across many users or content items | This fix covers it |
| You want this action to run automatically and repeatedly, not just once | Scheduled task automation setup, the ongoing-automation version |
| You need a simpler WP-CLI command, not a more complex, custom script | WP-CLI batch operation from supplied spec, a more contained version of this same principle |
| You want categories or tags reassigned specifically, or authors reassigned | Bulk category & tag reassignment, or Bulk author reassignment, in the Content & Updates bucket, more specific versions of this same idea |
What we do
- Review the supplied spec and confirm the exact scope of the action
- Write the script to perform the specified bulk action
- Test thoroughly on a staging copy first
- Run the verified script against the live site
- Confirm the result matches the intended outcome
- Provide a written summary of what was executed and its outcome
What is included
- A one-time bulk action executed exactly to your supplied spec
- Staging testing before the live run
- Verified outcome matching your intent
- The pre-operation backup, kept for 30 days
Not included
- Setting this action up to run automatically on a schedule, a separate, different kind of fix
- Designing the action’s logic if you don’t already have a clear spec — worth discussing your actual goal first
- Ongoing maintenance, since this is a one-time, completed operation
- Reversing the action once verified and confirmed correct, beyond the standard 30-day backup
Questions about this fix
Is there any residual automation left behind once this action completes?
No — once the script finishes and the result is verified, nothing about it persists on your site; it's a completed, one-time action rather than anything installed or scheduled.
How large a scope can this realistically handle — thousands of users or posts?
This scales reasonably well to a large scope — a bigger action just needs more careful staging testing beforehand, given how much more there'd be to verify before running it live.
What if I want this same action available to run again on new users or content later?
This specific fix is scoped as a one-time execution against a defined set — if you expect to need the same logic applied repeatedly going forward, that's a different kind of fix involving ongoing automation, worth mentioning upfront.
Is this reversible if the result isn't what I expected?
We keep a pre-operation backup specifically so the action can be rolled back if genuinely needed, though thorough staging testing beforehand aims to catch any issue before the live run happens.
Can this action target a very specific, narrow subset of users or content?
Yes, we build the script to precisely match whatever criteria your spec defines, rather than a broad, imprecise action affecting more than intended.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.