How to Recover a Deleted Website (Backups, the Host, and the Wayback Machine)

There's a right order to how to recover a deleted website, and most people start at the wrong end. They go straight to trying to rebuild website from Wayback Machine snapshots, which is the last resort, when the host still had a restorable copy sitting on a shelf for another three weeks. Work down this list in order, because each step gives you a lower-fidelity version of your site than the one before it.

One thing to sort out before you spend anything: confirm you still own the domain. Recovering a site you can't put back at its own address is a much smaller win, and if the deletion came from a lapsed account, the domain may be on a clock too.

How to recover a deleted website: the order to try things in

1. 1The host's own backup. Highest fidelity, often still available, usually costs something. Ask before you assume.
2. 2Your own backups. Backup plugin folders, cloud drives, an old laptop, a zip somebody emailed.
3. 3The developer's or designer's copy. They frequently still have a staging site or a local build.
4. 4Search engine caches. Effectively dead now, but there's one narrow exception worth knowing.
5. 5The Wayback Machine. Recovers content and layout, not function.
6. 6Rebuild. Sometimes genuinely the cheaper and better answer.

Start with the host, even if the account was cancelled

This is the step people skip because they assume a cancelled account means an empty server. Often it doesn't, at least not yet. Several hosts publish exactly what they keep and for how long, and most of them will restore it if you ask and pay.

Then check your own backups, including the ones you forgot about

Owners routinely tell us they have no backup and then turn one up an hour later. Look in all of these before you accept that answer.

• A backup plugin's cloud folder. UpdraftPlus, Duplicator, WPvivid and the rest usually push copies to Dropbox, Google Drive or an S3 bucket. Search your cloud drive for a folder you don't remember creating.
• Your email. Search your inbox for the domain name plus "backup", "zip", or ".sql". Developers email these more often than you'd think.
• Old computers and external drives. The laptop the site was built on, the drive in a desk drawer, an old Time Machine or File History backup.
• A staging or development site. Sometimes still sitting on a subdomain or a different host, quietly running an older version of everything.
• Your web designer's file transfer link. Dropbox and WeTransfer links expire, but the files often survive in the sender's account.

If the person who built the site has stopped answering, that's a different and solvable problem. Our guide on what to do when your web developer disappears covers how to get access to accounts and copies without them.

Google's cache is gone, and so is Bing's

For twenty years the standard advice for a vanished page was to pull Google's cached copy. That advice is now wrong. Google removed the cached link from search results in late January 2024, and Google's own documentation changelog records that on 24 September 2024 they removed the cache: search operator documentation because the operator no longer works in Google Search. Bing followed: the Bing Webmaster team announced the removal of cache links from Bing results in December 2024.

Two useful leftovers. First, Google now links to the Internet Archive from the "About this result" menu on a search listing, a change the Internet Archive announced in September 2024, so the archive has effectively taken over the job. Second, Bing's own team has said site owners can still get to a cached view of their own pages through Bing Webmaster Tools' URL Inspection feature once the domain is verified. That's a narrow door, but it's a real one.

How to recover a website from the Wayback Machine

The Internet Archive's Wayback Machine holds captures of a huge portion of the public web going back decades, and for a site that had no backups at all it's frequently the difference between recreating your content from memory and copying it back off a screen.

1. 1Open the calendar view for your domain. Go to web.archive.org/web/*/yourdomain.com. You'll get a timeline of years with a calendar of captures.
2. 2Read the dots. The Archive documents its colour coding: blue means the page returned normally, green means a redirect, orange means the page was missing or blocked, red means a server error. Pick a blue capture from before things went wrong.
3. 3List every archived page, not just the homepage. Use the URL view at web.archive.org/*/yourdomain.com/* to see everything the crawler ever captured under your domain. This is where you find the service pages and blog posts you'd otherwise forget.
4. 4Copy the content out page by page. Text, headings, image files, and your page structure. For most small business sites this is a few hours of tedious but completely effective work.
5. 5Grab the images properly. Right-click and save each one from the archived page rather than screenshotting. The original files are usually there at full size.

Tools that rebuild a website from Wayback Machine captures

If the site had more than a handful of pages, copying by hand stops being sensible. The Internet Archive is honest that this is not something they do: their help page on rebuilding a website says several third-party services will help, names a few, and adds that they have no direct experience with any of them and you should investigate for yourself. Elsewhere they state plainly that their terms of use do not cover backups for the general public.

So everything in this category is third party and unaffiliated with the Archive. There are paid recovery services that advertise turning an archived site into a downloadable copy or a WordPress install for a small fee, and they work reasonably well for simple sites. There are also free command-line tools built for this, but they're for a developer to run, not something to install yourself if you've never used a terminal. Whichever route you take, treat the result as a content recovery, not a restore, and expect to clean it up afterward.

If you were on a website builder, there's a clock

Deleted builder sites usually sit in a recoverable state for a published window, which makes this the most time-sensitive scenario on the page.

Don't forget the email

If the website was deleted because a hosting account went away, the mailboxes on that account went with it. Restoring the site does not automatically restore mail, and messages sent to you in the meantime bounced rather than queuing. Check where your mail is actually routed before you declare the recovery finished.

When a rebuild is cheaper than a recovery

This is the honest part, and it's the advice we give more often than owners expect. Recovery is worth it when the site was large, when it had years of blog posts and rankings behind it, or when the pages carried detailed information that would take weeks to write again. In those cases, paying a host's restore fee or a recovery service is cheap.

Rebuilding is the better call when the old site was five or six pages, when it was already dated, when it was built on a platform or theme nobody supports any more, or when the recovered version would need rebuilding within the year anyway. Piecing a broken copy back together can cost more in hours than building fresh, and you end up with the same tired site. Pull your content out of the Wayback Machine, keep your page addresses the same so your search rankings survive, and put it on something current.

If you'd rather hand it to someone

Plenty of this is DIY. If you can open a support ticket and copy text out of an archived page, you can recover a small site yourself, and there's no reason to pay anyone for that. Where it's worth getting help is a site with a store, a database, or hundreds of pages, because that's where a half-recovery becomes a permanent mess. We handle recoveries and rebuilds for small businesses, and managed hosting inside a care plan from $99 a month is the version where this never comes up again, because daily off-site backups run whether or not anyone remembers them. The maintenance plan covers the ongoing upkeep.

If the deletion happened because the host went under, read what happens if your web host goes out of business, and if you're still in the first day of it, work the 24-hour rescue list.