How to Hire Someone to Fix a Broken WordPress Site (Critical Error, White Screen, 500)

You updated a plugin, and now your WordPress site shows “There has been a critical error on this website.” You may see a blank page or a “500 Internal Server Error” instead.

If you run a store, you may be missing orders. Your posts and pages are usually still there, even if the site won’t load.

When I work on a broken WordPress site, I start with a few simple checks. I’ll show you what to try first and how to hire someone safely if they don’t work.

What this error usually means

All three messages usually mean WordPress couldn’t finish loading the page because something in the code failed. Newer WordPress versions may show a critical error message, some setups show a white screen, and server failures can return a 500.

The usual causes, roughly in the order I run into them:

• A plugin or theme update It clashes with another plugin or with your PHP version. This is the most common one by far.
• A PHP upgrade by your host An older plugin or theme can’t run on the new version.
• The site ran out of memory Heavy page builders and stores with many plugins hit the PHP memory limit.
• A broken file A failed update, a bad edit in functions.php, or a damaged .htaccess file, which is a classic cause of the 500 error.

Your posts, pages, products and orders live in the database, separate from the code that failed. A code fix usually brings the site back without removing that content. WordPress has a guide to common errors if you want more technical detail.

Try this first (10 minutes)

These are four checks I’d try on a typical broken site.

1. Check the admin email inbox. WordPress sends a recovery email to the site’s admin address with the subject “Your Site is Experiencing a Technical Issue”. It names the plugin or theme and includes a Recovery Mode link that lasts one day. Use that mode to open the dashboard and deactivate or update the plugin. Check spam too.
2. Undo the last change. Did you update WordPress, a theme or plugin, or get a PHP-upgrade notice? Roll back that change. Most hosting panels let you switch PHP versions back.
3. Restore yesterday’s backup. Most hosts keep automatic backups you can restore from the hosting panel. For a blog or a business site, this is often the fastest fix. For a store, skip it: restoring a backup removes every order and customer account created after it.
4. Turn off all plugins at once. In your host’s File Manager, open wp-content and rename the plugins folder to plugins_old. WordPress will stop loading those plugins. If the site loads, rename the folder back and reactivate plugins one by one to find the likely cause.

Skip DIY and hire help if a store has live orders, you see strange redirects or a hack warning, or the message says “Error establishing a database connection”. Experimenting can cost more than the fix.

If this didn’t bring the site back, or you’d rather not touch files on your hosting, stop here. Every extra change makes the developer’s job harder. The next step is choosing who fixes it.

Where to hire a developer

I recommend Fiverr for this kind of fix. I work there myself, so I know how orders, payments and reviews work from the inside.

You see the price before you order, sellers in the WordPress bug fix category often deliver within a day, and Fiverr holds your payment until the order is complete.

What it costs

The price depends less on the error message and more on how much is unknown. At the time of writing, Fiverr prices for this kind of work fall into three levels:

Fiverr also adds a small service fee at checkout.

What the cheap price usually skips

A $20 gig can work when you know the cause and it’s one issue. If the cause is unknown, the cheapest option may leave out the work that helps the fix last:

• a backup before anything changes
• the cause, not only the symptom (turning a plugin off brings the site back; replacing it with one that works on your PHP version is the actual fix)
• testing past the homepage: forms, checkout, mobile
• a short note on what went wrong, so it doesn’t happen again

When the cause is unknown, paying for a proper diagnosis costs less than paying twice.

How to choose the right developer

Many sellers can fix a plugin conflict. Look at how they handle your site, access and backup.

Check reviews for the same problem

Look for reviews that mention “critical error”, “white screen” or “500 error”, not only the overall rating. Read the one- to three-star reviews and the seller’s replies. A calm, specific reply is a good sign.

Send your brief before you order

Send two or three sellers the brief below. A good seller asks about your PHP version, backup or recent changes. “Yes, I can fix it. Place the order” tells you little.

Read the Basic package

Check what “one issue” means, the delivery time and the number of revisions. A seller who mentions a backup has considered your risk, not only the fix.

Don’t read too much into the seller level

On Fiverr, a seller’s level shows their order history, not their WordPress skill. A newer seller can handle a simple plugin conflict. For a store or a possible hack, I’d pick someone with reviews on that exact kind of job.

The questions I’d ask before ordering

• Will you take a full backup before you change anything?
• Will you work on a staging copy or on the live site?
• What access do you need, exactly?
• Will you tell me what caused it?
• Will you install any plugins? Which ones, and are they licensed?
• If the error comes back next week, what happens?

Red flags

• They ask for your hosting account password or your domain login when a WordPress user and file access would do.
• They want to move the chat or the payment off Fiverr. Fiverr asks buyers to keep both on the platform, and its support can only help with orders placed there.
• They promise to fix “any error in one hour” without asking a single question about your site.
• They offer a premium plugin for free. That’s a pirated copy, and pirated plugins can carry malware.
• They never mention a backup.
• They offer a discount for a five-star review.

How to give access safely

Give the developer as little access as the job needs, for as short a time as possible, through accounts you control.

1. Take your own backup first. Download a full backup from your hosting panel and keep a copy off the server.
2. Create a separate WordPress user for the developer instead of sharing your login. If the dashboard works, the free plugin Temporary Login Without Password creates a login link that expires on its own. With a critical error the dashboard is often down, so the developer will mostly need file access.
3. Give file access through a separate SFTP user. Create it in your hosting panel. Never share the password to your hosting account itself.
4. Keep some logins to yourself: your domain registrar, Stripe or PayPal, and the inbox of the site’s admin email.
5. Share passwords safely and only after you order. Use a password manager’s share link, not plain text in the chat.
6. Close everything when the job is done. Delete the extra WordPress user and the SFTP user, change your passwords, and check Users → Administrators for accounts you don’t recognize.

One rule protects you more than all the others: keep your hosting and your domain in your own name. Whoever controls those controls the site.

What to send before the work starts

A clear brief saves time and helps the developer understand the job. Send it before you order, or paste it into the order requirements:

• your site’s URL and a staging copy, if you have one
• what’s broken and what “fixed” means to you (for example, “the homepage loads and the contact form sends”)
• the exact error text and a screenshot
• when it started and what changed just before
• your host, WordPress version and PHP version (Tools → Site Health → Info, if the dashboard works)
• your theme or page builder and main plugins (WooCommerce, cache, security)
• whether you have a fresh backup and where it’s stored
• what you’ve already tried
• any limits, such as “no changes to the live checkout during business hours”, and your deadline
• which access you’re ready to give

On Fiverr, what you write in the order requirements is what revisions are measured against. A good brief protects your money as much as it helps the seller.

After the fix: check, accept, prevent it

On Fiverr you have three days to review a delivery. After that, the order completes on its own. So check the work the same day:

• open the homepage and a few inner pages, on your phone too
• send a test message through the contact form
• if you run a store, place a test order
• ask what caused the error, and write it down
• ask for any changes through Fiverr before you accept the delivery

Then revoke the access you gave (see above) and lower the chance of another break. Keep automatic backups on, update plugins one at a time, test updates on a staging copy if you run a store, and remove plugins you no longer use. If the site keeps breaking after updates, regular maintenance can cost less than paying for one fix after another.

Summary

Hiring someone to fix a broken WordPress site is often a small job, but the wrong hire can create another problem. Try the four checks first. If they don’t help, choose a seller with reviews for the same error, a backup process and a temporary login from you. To keep the risk low, start with a one-issue order.