How to Get My Old Website Back: 6 Ways, From Hosting Backups to the Wayback Machine

Short answer: To get your old website back, work through the sources in order of completeness: your hosting account’s backups, your registrar and domain status, cached copies from search engines and archive.today, the Wayback Machine at archive.org, any copy held by a developer or agency who worked on the site, and finally a rebuild from scratch. Most lost websites can be recovered from one of the first four, and the Wayback Machine is the fallback that works even when every backup is gone.

“How do I get my old website back?” usually comes up at a bad moment: the hosting lapsed, the domain expired, a developer disappeared, a migration went wrong, or a site was simply deleted and nobody kept a copy. The good news is that websites leave more traces than people expect. This guide lists six ways to recover a lost website, from the fastest and most complete to the slowest, with a decision table at the end to help you pick the right one for your situation.

First, work out what you actually lost

Before you start recovering anything, be precise about what is missing: the domain, the hosting, the files, the database, or all of them. Each one is recovered differently. A site that is “gone” because the domain expired may have perfectly intact files sitting on the old host, while a site whose hosting was deleted may still have a live domain pointing at nothing.

Three quick checks tell you most of what you need to know:

• Visit the domain. A registrar parking page or “domain for sale” notice means the domain lapsed. A hosting error page or a “this site can’t be reached” message points to the hosting side.
• Look up the domain’s WHOIS record. It shows the expiry date, the registrar, and whether the domain is in a grace or redemption period.
• Log in to the hosting control panel if you still can. If the files are there, you may not need any of the recovery methods below.

Way 1: Restore from your hosting provider’s backups

Most hosting providers keep automatic backups for anywhere from a few days to a few months, even on cheap shared plans, and many keep them for a while after an account is suspended or closed. This is the best source because it is a complete copy: files, database, email settings, and all.

Log in to the hosting panel (cPanel, Plesk, or the host’s own dashboard) and look for a Backups, JetBackup, or Restore section. If the account has been closed, contact support and ask whether a backup still exists; some hosts can restore a closed account for a fee within a limited window. Be specific about the date you want and the domain name.

If you are the one who deleted the site

Ask for the backup from before the deletion date. If the host offers daily snapshots, pick the most recent snapshot where the site was still working. Download the full backup to your own computer before restoring it, so you have an offline copy from now on.

Way 2: Check the registrar and domain status

If the domain expired, the website may be fine; it is just unreachable. Domains go through a grace period, then a redemption period, and only then are they released or auctioned. During grace and redemption you can usually renew or redeem the domain through the original registrar, although redemption typically carries an extra fee.

Log in to the registrar account, or use WHOIS to identify the registrar if you do not remember it. Once the domain is renewed and DNS points back to the host, the site comes back exactly as it was, provided the hosting is still active.

If someone else now owns the domain

If the domain was released and bought by someone else, you have two paths: contact the new owner to buy it back, or restore the website on a new domain. If the content is what matters, the methods below still work; you will simply publish on a different address and, where possible, set up redirects from any pages you still control.

Way 3: Google cache alternatives (Bing cache and archive.today)

Google removed its public cache links in 2024, so the old habit of clicking “Cached” in search results no longer works. Two alternatives still exist. Bing’s search results sometimes keep a cached copy of a page, accessible from the dropdown arrow next to a result. And archive.today (also reachable as archive.ph) stores user-submitted page snapshots that are often complete, including CSS and images, because they are captured on demand rather than by a crawler.

Both sources are page-by-page, so they are practical for recovering a handful of important pages rather than an entire site. They are especially useful for pages that were published or changed recently, since the Wayback Machine may not have crawled them yet.

How to use cached copies well

• Search for the exact page URL in Bing and check for a cached version.
• Search archive.today for the domain to list every saved page.
• Save each page’s HTML to disk, plus any images you can still download.
• Keep a list of which pages came from which source and date.

Way 4: Recover the site from the Wayback Machine

The Internet Archive’s Wayback Machine at archive.org has been crawling the web since 1996 and holds snapshots of billions of pages. For most sites that were publicly online for more than a few months, it has at least a partial copy, and for popular sites it often has hundreds of captures. This is the method that works when there is no backup, no cache, and no developer copy.

Enter the domain, pick a date from the calendar, and browse the captured site. If the pages you need are there, you can download them and rebuild. The archive serves pages with its own toolbar and rewritten links, so a usable restoration involves cleaning that up, fixing images and stylesheets, and either hosting the files as static HTML or rebuilding them in a CMS such as WordPress.

The full process is covered step by step in our guide on how to restore a website from the Wayback Machine. If you want to know whether the archive has enough for a rebuild before you spend any time on it, the free checker at Can My Website Be Restored? reports coverage for any domain.

What the Wayback Machine can and cannot give you

• Usually recoverable: page text, HTML structure, navigation, most images, CSS, blog posts, and the URL structure.
• Sometimes recoverable: PDFs and downloads, fonts, JavaScript-driven layouts, images hosted on CDNs.
• Not recoverable: databases, user accounts, form submissions, order history, content behind a login, and anything the site blocked from crawling.

If the archive has nothing for your domain, the options are more limited; our page on recovery options when a website was never archived walks through them.

Doing it yourself versus hiring it out

A Wayback rebuild is manual work: cleaning archive URLs from every page, replacing missing assets, and reconstructing the site in a form you can edit. Wayback Restore does this by hand at fixed per-site starting prices: HTML from $29, WordPress $79, and Elementor $149, with other platforms listed on the pricing page. The archive is checked for free before payment, the rebuilt site is editable after delivery, and the old URLs are kept so bookmarks and backlinks keep working.

Way 5: Ask the developer or agency for their copy

Anyone who built, redesigned, or maintained the site probably still has a copy. Developers keep local working folders and Git repositories; agencies keep staging sites and project archives; theme and plugin customizers often keep the full theme folder. Even an old freelancer from years ago may have a ZIP in a backup drive.

Ask politely and be specific: the domain, the approximate dates they worked on it, and whether they have the database export as well as the files. A developer copy from two years ago combined with recent pages from the Wayback Machine can add up to a nearly complete site.

Other places a copy might be hiding

• Your own computer: FTP client download folders, old “website” folders, and Downloads.
• Email: hosts and developers often email backup links or ZIP attachments.
• Cloud storage: Dropbox, Google Drive, and OneDrive folders shared during a project.
• Staging or test subdomains that were never deleted.
• Site builder accounts (Wix, Squarespace, Shopify) that still hold the project even if the plan lapsed.

Way 6: Rebuild from scratch (with whatever you can salvage)

If nothing above produces a usable copy, the last option is to rebuild. This is rarely a total loss: even a few recovered pages, a logo, the old navigation structure, and a list of the URLs that used to exist give you a far better starting point than a blank page. Keeping the same URL paths matters here too, because any backlinks and bookmarks pointing at the old site will resolve again.

Use a page list from the Wayback CDX index or from your backlink tool as the site map. Recreate the most important pages first, set up 301 redirects from any old URLs you cannot bring back, and submit a sitemap in Google Search Console so the rebuilt site gets recrawled. If you want to modernize the design at the same time, Wayback Restore’s redesign and restore option starts from $299 and combines the recovered content with a new layout.

Decision table: which recovery method fits your situation

Use this table to go straight to the method most likely to work for your case. Start with the row that describes you and move down the list if that method fails.

After you get the site back: stop it happening again

Once the site is live again, set up a backup routine that does not depend on the host: a scheduled off-site backup to cloud storage, a periodic full download to your own computer, and auto-renew on the domain with a current payment card. Keep the registrar login, hosting login, and CMS admin login in a password manager that more than one person can access. Most lost websites are lost because a single renewal email went to an old address.

Frequently asked questions

Can I get my old website back if I no longer own the domain?

You can recover the content and publish it on a new domain, using hosting backups, a developer copy, or the Wayback Machine. Getting the original domain back means renewing it during the grace or redemption period, or negotiating with the new owner if it has already been resold.

How long do hosting companies keep backups after an account is closed?

It varies widely, from a few days to several months, and some hosts keep nothing after closure. Contact support as soon as possible and ask specifically whether a backup from before the closure date still exists.

Is Google cache still available for recovering a website?

No. Google removed public cache links from search results in 2024. Bing still shows cached copies for some pages, and archive.today holds on-demand snapshots. For whole-site recovery, the Wayback Machine at archive.org is the main public source.

Can a website be recovered from the Wayback Machine if it was a WordPress site?

Yes. The archive stores the rendered HTML pages, not the WordPress database, so the site is rebuilt by recreating pages and posts in a fresh WordPress install and restoring the theme appearance. Wayback Restore does this manually from $79 for WordPress and $149 for Elementor sites.

How do I know whether the Wayback Machine has enough of my site to restore?

Check the calendar on archive.org for the number and spread of captures, and open a few inner pages to see whether they render. For a quicker answer, run the domain through the free checker at waybackrestore.com/can-my-website-be-restored/, which reports which pages have usable snapshots.