An update broke your site. We put it back — then fix it properly.

Yesterday everything worked; today the layout’s collapsed, checkout errors out, or the whole site is gone. Updates do this — quietly, and usually at the worst time. Tell us what changed and what you’re seeing, in your own words.

  • From $490, agreed in writing first. No fix, no fee. 30-day reinfection warranty.
  • We reply within 2 hours, 9am–5pm Pacific, every day.
  • Fee credited over your first 3 months if you join a care plan after.
Start emergency triage → Email us instead

The next ten minutes — what you can do right now.

Before anyone gets paid, these four things help — whether it’s us who fixes it or not.

01

Stop updating

When one update breaks something, running the rest to “catch up” buries the evidence — and can stack a second conflict on top of the first.

02

Write down what went out

The Updates screen in wp-admin, or the notification email your site sent, lists what moved. Knowing the suspects turns a hunt into a checklist.

03

Screenshot what’s broken

The exact error text and where it appears — front page, checkout, admin — is half the diagnosis.

04

Use your host’s restore carefully

A one-click restore to before the update can bring the site straight back — and quietly roll back every order and edit since. Check the snapshot’s timestamp and know what you’re trading before you click.

How we un-break it.

Take our own backup first

Before anything is touched — so nothing we do can make today worse.

Roll back the right thing

The one update that failed, not the whole site. Your orders, posts, and settings from today stay.

Fix the conflict underneath

A patch, a replacement, or the update held until the vendor fixes it — so the same update doesn’t break the site again next week.

Leave it in writing

Which update failed, why, what we changed, and what we’d watch — a written summary after the engagement.

This is the exact failure care plans exist for: on every plan, updates go out backed up first and get rolled back the moment anything breaks — you find out from our note, not from a customer. For scale: care starts at $149/mo — one emergency is $490. Fee credited over your first 3 months if you join a care plan after.

See plans & pricing

Asked in exactly this situation.

Should I just restore last night’s backup?
It can work — and it erases everything since: orders, posts, form entries, settings changes. It also fixes nothing, so the same update breaks the site again next time it runs. The safe order is: roll back the one thing that failed, keep everything else, then fix the underlying conflict.
How do I know which update did it — a plugin, the theme, or WordPress itself?
The error logs usually say: the failing file’s path names the plugin or theme. When several things updated together, it’s a short process of elimination on a copy of the site — not guesswork on the live one.
Can this be prevented, or is it just WordPress being WordPress?
It’s preventable — this scenario is most of what a care plan is. Updates go out on a schedule, backed up first, rolled back if anything breaks, and the conflicts get caught before your customers do the testing.

Not quite what’s happening to you?

Same fee, same promises, whatever it turns out to be. If none of these fit, describe it in your own words — you don’t need to know what’s wrong.

Send the URL. That’s enough to start.

One line about what you’re seeing, in your own words — a senior engineer reads it and replies within 2 hours, 9am–5pm Pacific, every day. From $490, and if we can’t recover the site, you pay nothing.

Start emergency triage → Email info@wppirates.com