Remove a Page From the Wayback Machine: How It Works
How to remove a page from the Wayback Machine: who can ask, what the Internet Archive says to include, what it will not do, and what stays elsewhere.
To remove a page from the Wayback Machine, you write to the Internet Archive and ask its team to review an exclusion or removal request. The Archive's help page on removal requests and its related pages describe one route for site owners (an exclusion request by email), one for copyright owners (a formal notice), one for people shown in intimate images shared without consent (a dedicated form), and a general email route for anything else. They also say the Archive makes no promise about the outcome of any request.
There is no button, no automatic deletion and no stated deadline. What you control is how clearly you identify the material, whether you can show a real connection to it, and whether you picked the route that fits who you are. This guide follows the Internet Archive's own help pages as they read on the day this was written, and it says plainly where a page could not be read.
Policies change, so check the live help page before you send anything. This is information, not legal advice.
- Site owners ask by email for an exclusion, giving the URLs, the time period to exclude and the period they controlled the site or account. The Archive says the request starts a review and that it does not promise the outcome.
- Copyright owners, people in intimate images and other third parties each have a different route. A third party with a different concern writes to the general address and explains what should go and why.
- Never claim a site you do not control. A request rests on facts the Archive can weigh, and a false claim of ownership is the fastest way to lose the request and create a worse problem.
- An exclusion affects the Wayback Machine only. Live pages, search results and other archives are separate files with separate owners.
Who can ask to remove a page from the Wayback Machine
The Archive's help page on removal does not set out strict eligibility rules, so the useful question is which route its pages describe for your situation. It separates copyright claims, which follow its Copyright Policy, from exclusion requests, which come from people who want their site or account archives removed from web.archive.org. It asks those requesters to state any period they controlled the site or account. Other removal requests go to the same general address with a clear explanation of what should be removed and why. Intimate images published without consent have their own page.
Related readRemove Old Forum Post About Me: Who to Ask FirstThe table sets the four routes next to each other, using only what those pages state.
| Who you are | Route the pages describe | What to state | What the page says about outcome |
|---|---|---|---|
| Site or account owner | Exclusion request by email | URLs, period to exclude, period you controlled the site or account | Starts a review, no promise of result |
| Copyright owner or authorized agent | Copyright notice to the Archive's copyright agent | The work, the exact location, contact details, good-faith and accuracy statements, signature | The Archive may remove content or disable access, at its discretion |
| Person shown in an intimate image shared without consent | The NCII takedown form | The form's own fields, which this guide could not read | No promise of removal, at the Archive's discretion |
| Anyone else with a concern | Email asking for removal | What should be removed and why, with URLs | Review, no promise of result |
Site owner versus third party
A site owner has the clearest case because the exclusion route was written for them. The help page for using the Wayback Machine notes that site owners may have asked for their sites to be excluded, which is one reason a site is missing from the archive. The request's reference to the period you controlled the site or account suggests a former owner can ask too, for the years they ran it.
A third party has no dedicated exclusion route on the pages read, but the help page invites other removal requests by email, as long as the message explains what should be removed and why. It does not say what grounds succeed, so expect a case-by-case review and lead with the strongest, most verifiable reason.
Why a page is or is not in the Wayback Machine at all
Check what is actually in the archive before you ask. The Wayback Machine is a service of the Internet Archive, a nonprofit research library that has been archiving the web since 1996, according to the Archive's FAQ on publishers blocking it. Its help pages explain that captures come from crawls: "Every day hundreds of web crawls contribute to the web captures available via the Wayback Machine."
The help pages read for this guide state several limits, and the same page adds that JavaScript is hard to archive, so a capture can look broken or incomplete even when it exists.
- The Archive says it does not archive pages that require a password. Pages on secure servers are also described as not archived, and the help page notes that crawlers do not enter queries in search boxes.
- A page may never have been crawled: a page with no links pointing to it may never be found.
- A page may be missing because of robots exclusions or a direct request from the site owner. The help page says a site's robots.txt document may have prevented crawling, and that sites excluded because of a robots.txt file or a site owner's request may be unavailable.
The same pages add a lag of "3-10 hours" between a crawl and the moment a capture appears, so a capture can appear hours after the crawl that made it, and a page you changed this morning may still show in a capture made earlier. Before asking, search the archive for the exact address and list the captures that matter. A request that names dates and addresses is easier to review than one that says "everything about me."
Related readDMCA takedown notice: contents, steps, limitsWhat to put in an exclusion request
The Archive's removal help page lists what an exclusion request should contain: the URL or URLs of the material, the time period you want excluded, the time period you controlled the site or account if that applies, and any other information that helps the team understand the request. Build the message around those four items and keep it short.
- List every addressWrite each URL exactly as it appears in the archive, including the host name with or without www and any path. If you want the whole site excluded, say so in one line and give the domain.
- Name the time periodState the dates or years to exclude. If you want every capture removed, write "all captures" and say so in plain words, so no one has to guess.
- State your connectionFor a site or account you own or owned, give the period you controlled it. For a third party, say that you are not the owner and explain your connection to the material.
- Give the reasonOne or two sentences on why the material should not be available, with the facts that support it. Attach documents only if they help a stranger verify the point.
- Send once, keep a recordEmail the address the help page gives, keep the sent message, and note the date. Do not send the same request several times in a row.
Wording that helps a reviewer
Write it the way a clerk would want to read it: who you are, what you control, the addresses, the period, the reason, and stop. A message that retells an entire dispute or attacks someone makes the review harder. The Archive's page asks for "a clear explanation of what should be removed and why" for non-owner requests. A skeleton that fits that wording, with placeholders in square brackets:
I controlled [domain] from [start year] to [end year]. I am asking that the captures of the addresses below be excluded from web.archive.org for [period]. Addresses: [list]. Reason: [one or two factual sentences]. I can provide further information if it helps your review.
Change the first sentence for a third party: "I did not own this site. I am writing about the page at [address], which [one factual sentence about how it affects you]." Then keep the rest the same.
The copyright route is a formal notice, not an email request
If the material in the archive infringes your copyright, the Archive's Wayback Machine general information page describes a formal notice. It says the Archive may, at its discretion, remove content or disable access when material appears to infringe. A complaint must include the identification of the copyrighted work, the exact location of the disputed material within the collections, the complainant's address, phone number and email, a good-faith statement that the use is not authorized by the owner, its agent or the law, a statement under penalty of perjury that the information is accurate and that the complainant owns the copyright or is authorized to act for the owner, and an electronic or physical signature. Notices go to the Archive's copyright agent, whose details are on that page.
Related readRemove Arrest Record From Google: The Right OrderThis route concerns the work, not your name or your reputation. A page can be accurate, lawful and unflattering, and none of that gives you a copyright claim. The perjury statement is a real commitment, so if the photograph, article or text is yours and was copied without permission, the notice fits. If it is not yours, use another route.
Intimate images published without consent have their own form
The Archive's help center has a separate page for people who believe material on the Archive contains a nonconsensual intimate visual depiction of them. It points to an NCII takedown request form and states that the Archive may remove content or disable access to it in appropriate circumstances, "at its discretion". It does not promise removal.
The page names the form's address as archive.org/forms/ncii-takedown. It does not say what the form asks for, whether there is an email route, or how long a reply takes, and the form page itself returned no readable fields when this guide tried it. Check it directly, and gather the exact addresses first. You are the person the form was built for, so use it rather than waiting to see whether a general email works. Our leak removal page describes how we approach these cases.
Robots.txt and the Wayback Machine: what the pages say and what they do not
Adding a line to robots.txt is often said to remove a site from the archive. The pages read for this guide support something narrower. The help page says robots.txt may have prevented crawling and that sites excluded for that reason may be unavailable. The general information page says pages may not be archived because of robots exclusions and does not explain how those rules are applied.
Related readRemove Google autocomplete suggestions: what worksA 2017 post on the Internet Archive blog goes further and shows why you should not rely on the trick. It says robots.txt files were designed mainly to guide search engine crawlers, that the Archive wants complete snapshots of pages, and that search-focused rules often conflict with that aim. It describes a practice in which a parked domain blocks everything through robots.txt and, historically, the domain's earlier pages vanished from the Wayback Machine, prompting near-daily complaints. The Archive says it had already stopped honoring robots.txt on U.S. government and military sites and planned to apply that approach more broadly. The same post says site owners can still ask the Archive to remove content by writing to it.
That post is from 2017, and the pages read for this guide do not state how the Archive applies robots.txt today. So do not treat a robots.txt line as a reliable removal method for pages already archived. Use it, if at all, as a statement of how you want future crawling handled, and make the explicit request by email.
If a robots.txt block or a login stops a crawler, do not look for a way around it. This guide describes only routes the Archive itself publishes.
What the Internet Archive will not do
Four limits stand out from the pages read.
- It makes no promise about the outcome of a request. The removal page says a request starts a review by the team and that the Archive does not make promises beforehand about the outcome.
- It gives no response time. None of the help pages read states a timeframe for review.
- It does not edit pages. The pages read describe exclusion, removal and disabled access, not corrections to an archived page.
- It sets a high bar for automatic takedowns. A 2017 Archive post argues that being forced to automatically remove material from the Wayback Machine "would irreparably harm the historical record", and its FAQ on publishers blocking the Wayback Machine says the service is widely used by journalists, fact-checkers, researchers, lawyers, courts and librarians. A request is weighed against that mission.
What stays after the Wayback Machine drops a page
The same material can sit in four places owned by four different parties. The table shows who controls each and what a Wayback exclusion does to it.
| Place | Who controls it | Your route | After a Wayback exclusion |
|---|---|---|---|
| The live page | Site owner and host | Ask the owner to change or remove it | Unchanged, still public |
| Wayback captures | Internet Archive | The routes in this guide | Excluded if the request is granted |
| Search results and snippets | Each search engine | That engine's removal tools | Unchanged until the engine updates or acts |
| Other archives and copies | Each service or person who made one | Their own policies, which this guide did not read | Unchanged |
Search results
Search engines keep their own index. Google's documentation on removing information says the permanent options are to remove or update the content on your page, password-protect it, or add a noindex tag, and that its Removals tool can hide a page you own from results within a day, for about six months. It adds that a noindex tag only blocks the page in Google, and that other search engines that do not support noindex can still access the page. Archive exclusion does not feed any of this.
Related readRemove images from Google Image search: what worksThe live page and the publisher
If the page is still live, the archive is the smaller problem. Only the party that controls the source can change or unpublish it, and a Wayback exclusion leaves that page as it was. Asking an editor or site owner for a change is a different letter.
Other archives and copies
Anyone can save a copy of a public page, and other archiving services have their own rules. No official page of another archive was read for this guide, so no claim is made about their policies. Search for copies under distinctive phrases from the page and treat each as a separate request.
A realistic sequence, and two invented scenarios
Fix the source first, then ask the Archive, then deal with search results, because each step depends on the one before. The timings below reflect our experience, not anything the Archive states.
| Stage | What you do | Usual timing (our experience) | What can go wrong |
|---|---|---|---|
| Day 1: audit | List live addresses and archived captures, and decide which route fits | An hour or two | Asking for everything when only some pages matter |
| Days 1 to 7: source | Change or remove the live page if you control it | Same day to a week | A new capture appears while the page is still live |
| Week 1: request | Send one clear request on the right route | Same day once ready | Wrong route or a vague message |
| Weeks 2 to 6: review | Wait, answer any follow-up, keep records | Often days to several weeks, and sometimes longer; no timeframe is published | Sending the same request again and again |
| After a decision | Re-check the archive and search results, then deal with copies | A day or two, then ongoing | Assuming one answer settles every copy |
Scenario one: a former site owner (invented)
A consultant closed a small advisory site and sold the domain. The old pages show a client list that no longer reflects the business. Assume the consultant has registrar records for the years they ran it. They list the addresses, ask for exclusion of captures for those years, state the period of control and send one email. The request is specific, truthful and limited to years they can prove. The Archive may still decline it, but a reviewer has nothing to chase.
Scenario two: a third party (invented)
A person is named in an old forum thread that the owner has deleted, yet it remains in the archive. The person did not own the site, so they write to the general address, say so, give the address and dates, and add one sentence on how it affects them, such as that it shows a home address. The limits are the same: review, no deadline, and the thread may persist in search snippets and in copies others made.
Related readRemove Bing Search Results: Every Microsoft RouteWhat to do now, and when to get help
Start with the source and a list of addresses, then choose the one route that fits who you are and send one request.
If the archived page shows private, outdated or unlawful material and you are unsure which route fits, a private review of the whole picture is usually faster than guessing: the live page, the archive, search results and copies. Start with a private audit.
At Reputation Partners we begin by separating what can be removed from what can only be outranked, and we say plainly when a route will not work. No one can promise that an archive will act on a request.
Questions people ask
Can I remove a page from the Wayback Machine if I do not own the site?
The Archive's pages describe no dedicated route for non-owners, but its help page says other removal requests can be sent by email with a clear explanation of what should be removed and why. Say you are not the owner, give the addresses and one factual reason. It starts a review, and the Archive does not promise the outcome or a timeframe.
Does deleting the live page remove it from the archive?
No. The archive holds captures made earlier, and the live site and the archive are separate. Deleting the live page leaves old captures in place, and the Archive's pages describe exclusion and removal as requests you have to make. If you want old captures excluded, ask.
How long does a Wayback Machine removal request take?
The pages read for this guide state no timeframe. In our experience a first reply usually takes days to several weeks, and some take longer. Send one clear message, keep a record, and do not repeat it in the meantime.
Will a robots.txt rule remove my old pages?
The Archive's help pages say robots.txt may have prevented crawling, but they do not explain how a rule affects pages already archived, and a 2017 Archive post describes the Archive moving away from relying on it. Treat robots.txt as a statement about future crawling, not as a removal tool, and make an explicit request by email.
Does the Wayback Machine remove intimate images shared without consent?
It has a separate help page and an NCII takedown form for people who believe material contains a nonconsensual intimate depiction of them. The Archive says it may remove content or disable access in appropriate circumstances, at its discretion, and does not promise removal. Use the form, not the general email, and also pursue the source and search results separately.
Will my page disappear from search results once it leaves the archive?
Not necessarily. Search engines keep their own index and snippets, and the archive is one of several copies. Google's documentation says the permanent options are to remove or update the content on the page itself, password-protect it or add noindex, and that noindex only affects engines that support it. Handle the archive, the source and search results as separate requests.
