Wayback Machine Not Showing Your Website? 8 Reasons and Fixes

You type your old domain into web.archive.org, hit enter, and get an empty calendar, a redirect loop, or a page with every image broken. If the Wayback Machine is not showing your website, it rarely means your content is gone — it usually means you are looking at the wrong URL, the wrong date, or a snapshot that was blocked from crawling.

Here are the eight causes we see most often, and what to do about each one.

1. You searched the wrong version of the URL

The archive treats example.com, www.example.com, http:// and https:// as different addresses. A site can have hundreds of captures under one and none under another.

Fix: try all four variations. Then open the archive’s URL search with a wildcard — web.archive.org/web/*/example.com/* — which lists every captured path under the domain rather than just the homepage.

2. The snapshot you picked is after the site went down

Archive crawlers keep visiting a domain after it expires, so the most recent captures are often a parking page, a 404, or a host suspension notice.

Fix: use the calendar view and step back to the last date with a full-size capture. Snapshot file size is a useful signal — a 2 KB capture is a parking page, a 60 KB one is a real page.

3. robots.txt blocked the crawler

If the site had a restrictive robots.txt while it was live, whole directories may never have been crawled. A staging site left on noindex, or a WordPress install with “discourage search engines” ticked, produces exactly this result.

Fix: nothing can be recovered from a path that was never crawled, but check neighbouring paths — blog posts are often archived even when a blocked /wp-admin/ or /shop/ is not. Third-party archives such as Bing’s cache or archive.today sometimes hold what the Wayback Machine missed.

4. The domain owner requested removal

If a domain changes hands, the new owner can ask the Internet Archive to exclude the whole domain — which retroactively hides snapshots from the previous owner too. You will see a message saying the page is not available rather than an empty calendar.

Fix: if you still own the domain and the exclusion is not yours, contact the Internet Archive directly and explain. If the domain has been sold, the archived copy is effectively closed to you.

5. The site was JavaScript-rendered

Single-page applications built on React, Vue or Angular load their content after the page renders. The crawler saves the HTML shell and often misses the API responses that fill it, so the snapshot opens to an empty layout.

Fix: view the snapshot’s page source rather than the rendered page. Content is sometimes present in inline JSON. Otherwise, check whether the site had server-rendered or AMP versions at different URLs.

6. Images and CSS load from a domain that was not archived

A snapshot renders unstyled or image-less when assets sat on a CDN, a subdomain or a third-party host that the crawler treated separately.

Fix: search the asset domain in the archive as its own URL. Media files are frequently captured under cdn.example.com even when the main domain looks incomplete.

7. The site was too new or too small to be crawled often

The Internet Archive prioritises linked, trafficked pages. A site that launched weeks before it went offline, or one with no inbound links, may have only one or two thin captures.

Fix: check whether the pages exist in Google’s index, an old sitemap.xml capture, or your own Search Console export. A sitemap snapshot gives you the full URL list even when individual pages were not captured.

8. You are hitting rate limits, not missing data

Heavy requests to the archive trigger temporary throttling, which looks like timeouts, blank pages or “Hrm” error screens. It is a traffic limit, not a missing snapshot.

Fix: wait fifteen minutes and retry, and avoid running aggressive bulk download tools against the archive.

How to confirm what is genuinely recoverable

Before you write a site off, run this checklist:

Search all four URL variations of the domain
Run the wildcard URL list to see every captured path
Open the last three captures from before the site went offline
Look for an archived sitemap.xml to get the full page inventory
Check the CDN or media subdomain separately for images
Cross-check anything missing against archive.today

If paths appear in the wildcard list, the content exists — the rendering problems above are solvable. Our walkthrough on recovering a deleted website from the Wayback Machine covers the extraction process once you have confirmed what is there.

Still seeing nothing?

We run a free archive check before any restoration: send us the domain and we will tell you which pages survived, which did not, and what a rebuild would actually include. Start on our contact page, or read what a full rebuild covers on our services page.

Frequently asked questions

Why is my website not in the Wayback Machine at all?

Most often the crawler was blocked by robots.txt, the site was never linked from anywhere the crawler visits, or you are searching a different URL variant than the one that was captured. Try the wildcard URL search before concluding it was never archived.

Can deleted Wayback Machine snapshots be restored?

If a domain has been excluded at the owner’s request, the snapshots stay hidden until that exclusion is lifted. If you are the current domain owner, you can ask the Internet Archive to review it.

Why do archived pages look broken?

Broken layouts almost always mean the CSS, fonts or images lived on a different host that was archived separately — or not at all. The text content is usually intact in the page source.

How far back does the Wayback Machine go?

Captures date from 1996 onwards, though coverage of small sites before roughly 2005 is thin. A site that was live and linked for several years usually has dozens of usable snapshots.