Emergency intake · Open right now

Your site is down. We can pick it up right now.

Hacked, broken after an update, or a white screen of death — send the URL and a one-line description. A human reads it, a written acknowledgment goes back promptly, and triage starts the same day. Contractual 30-minute SLA for Premium clients.

Send the SOS →

or email info@wppirates.com · subject line EMERGENCY

Same day
Pickup window
200+
Recoveries completed
0
Ransomware in 6 yrs
30 min
Premium SLA (contractual)
What we'll do in the first 30 minutes

Calm hands, not panic buttons.

Most WordPress emergencies look terrifying and have a small, identifiable root cause. The first half-hour is about finding it without making things worse.

01

Acknowledge

A human confirms receipt in writing — promptly, never an auto-responder. You get a real reply from someone who can act on it.

02

Diagnose

Quick read on hosting status, error logs, recent changes, and any signs of compromise — so we know what we're dealing with before we touch anything.

03

Stabilize

If we can put the site back online safely from a clean backup or by rolling back the change that broke it, we do that first.

04

Plan

Written triage plan: what's broken, what we'll fix, fixed-fee quote where possible, and what we'd recommend after the fire is out.

Emergency intake

Tell us what’s broken — be brief.

Don't write a polished message. A half-finished ticket sent in 30 seconds beats a well-crafted one an hour later.

The exact URL that's broken. If only one page is affected, link that page directly.

Error messages, what you tried, hosting provider, when it started — whatever's at the top of your head.

By sending, your request is logged at [EMERGENCY] priority and goes straight to Andrew. Existing Premium-plan clients should additionally use their dedicated incident channel.

What happens next

Quiet, written, and on the clock.

i.

Promptly

Written acknowledgment with the URL we received, the urgency we logged, and who's looking at it.

ii.

Within the hour

Initial diagnosis or a clear ETA. If we need access to hosting, you'll get the exact list of credentials we need (named accounts only, no shared passwords).

iii.

Recovery

Staging-tested where possible, otherwise smallest-blast-radius fix on production with a backup taken first.

iv.

After the fix

Written incident report: timeline, root cause, what changed, and an honest read on whether ongoing maintenance would have caught it earlier.

What we cover

Six common emergency scenarios.

Hacked site recovery

Malware removal, post-compromise hardening, Google blacklist removal request.

White screen / fatal error

Diagnosis, rollback, plugin conflict isolation.

Broken-update recovery

Restore from snapshot, identify which update caused it, fix forward.

Database corruption / loss

Restoration from backup, table-level surgery if needed.

Locked out of admin

Access recovery via SFTP/SSH/database.

Spam injection / SEO hack

Cleanup, search console removal, prevention setup.

Common questions

Emergencies, specifically.

What counts as an emergency?
Site offline, white screen of death, hacked or defaced, plugin/theme update broke checkout or login, malware injection visible in Google search, or any active outage that's costing you money.
How fast do you actually respond?
New (non-client) emergencies are prioritized for same-day pickup where possible. The 30-minute response SLA is contractually committed only to active Premium-plan clients — for everyone else we'd rather under-promise and over-deliver than make a number up.
How is this priced?
One-off emergencies are billed as a fixed-fee incident: a flat investigation fee plus an agreed recovery quote before any deeper work begins. No surprise hourly bills. Growth-plan clients get same-day priority; Premium clients have the contractual 30-minute SLA included at no extra cost per incident.
What if my site can't be recovered from backup?
If backups are missing or corrupted, we rebuild from the live database, your host's snapshots, and the WordPress.org plugin/theme repos. Worst case we tell you straight: 'this site needs a partial rebuild' with a fixed quote, not a runaway clock.

Already a client? Use your incident channel.

Premium-plan clients have a dedicated incident channel and a contractual 30-minute response SLA. New here? Send the SOS above — same-day pickup where possible, written triage on the way.

Send the SOS Email info@wppirates.com →

Andrew Ivanov · Founder & CTO · WP Pirates since 2020