- Learn
- De-listing vs Deletion: Why the Page Can Still Exist
Right to be forgotten
De-listing vs Deletion: Why the Page Can Still Exist
A calm, plain-language look at two actions people often blur together — having a search result hidden under your name, and having the underlying data deleted. Knowing the difference tells you which request to make, and what each one can realistically change.
In short
De-listing asks a search engine to drop a result from the list shown under your name; the original page stays online. Deletion asks the organisation that holds your data to erase it. They are different requests to different parties, and de-listing a link never removes the page it points to.
Two different actions, two different parties
The confusion starts because both actions feel like "making something go away," but they act on different things. De-listing is about a search engine's index — the list of links it shows when someone types your name. Deletion is about the data itself, held by whichever organisation collected or published it. One changes how easily a page is found; the other changes whether the data exists at all.
Because they act on different things, you ask different parties. A de-listing request goes to the search engine, asking it to stop showing a particular result under a name search. A deletion request — the right to erasure under UK GDPR (Article 17), the formal name behind the popular phrase "right to be forgotten" — goes to the organisation that actually holds the personal data, known as the data controller. Sending a deletion request to a search engine, or a de-listing request to the original site, aims the right ask at the wrong door.
Neither is a master switch over the whole internet. De-listing touches one search engine's results; another engine, a direct link, or a future crawl can still surface the page. Deletion runs against one organisation's records, not every copy that may exist elsewhere. Seeing them as two specific, limited tools — rather than one big eraser — is what makes them usable.
Why a de-listed page is still there
A search engine does not store the original page. It keeps an index — a record of what it found when it last visited a page that lives somewhere else. When a result is de-listed, the engine agrees to stop showing that link in the list under your name. The page on the other site is untouched: it still exists, still loads if you have the address, and can still be found through other engines or other search terms.
This is why people are surprised to see a "removed" page reappear. De-listing narrows one path to the information; it does not close the page. If the underlying site never changes, the data is still public — just a little harder to stumble on under a name search. An online identifier such as a username, email, or profile URL can also re-connect the page to you through a different route the de-listing did not cover.
Deletion is the action that addresses the page itself, because it asks the organisation holding the data to remove it at the source. When the source page changes or disappears, the search result that pointed to it tends to fade or update on its own the next time the engine crawls. So the durable change usually starts with the source, and de-listing is best understood as tidying the search path, not erasing the destination.
Choosing which request fits your situation
Start by separating the goal. If your worry is that a specific result is easy to find when someone searches your name, de-listing that result may be enough, and it can be the faster route. If your worry is that the data should not be held or published at all, deletion at the source is the action that addresses it — and once the source changes, the search result usually follows.
Remember that neither right is absolute and neither is guaranteed. A search engine weighs a de-listing request against the public interest in finding the information; an organisation can sometimes keep data despite an erasure request, for example where the law requires it or a legal claim depends on it. A clear, specific written request — naming the exact page or data and why it should be hidden or removed — is far more effective than a broad demand, and it gives the recipient something concrete to act on.
OSINTA helps you see and understand your own footprint and frame and route these requests with your own findings in front of you; it does not de-list, delete, or remove anything for you, and it cannot promise an outcome, because those decisions rest with the search engine and the organisation that holds the data. This is general information, not legal advice — for advice on your own situation, consider speaking to a qualified adviser or your data-protection regulator.
- De-listing → ask the search engine to drop a result under your name; the source page stays online.
- Deletion → ask the data controller to erase the data at the source; the search result then tends to fade.
- Neither right is absolute, and neither reaches every copy across the whole internet.
Frequently asked questions
If a search result is de-listed, why can I still open the page?
Because de-listing only acts on the search engine's index, not the page. The engine stops showing the link under your name, but the original site still hosts the page, so it loads if you have the address and can still be found through other engines or search terms.
Which should I request — de-listing or deletion?
It depends on your goal. If you only want a result to be harder to find under your name, de-listing the link may be enough. If you want the data itself gone, deletion at the source is the action that addresses it, and the search result usually fades once the source page changes.
Does de-listing a result delete the data behind it?
No. De-listing changes what a search engine shows; it does not touch the data on the original site. To remove the data itself, you make an erasure request to the organisation that holds it — the data controller — which is a separate request to a different party.
What if my de-listing or deletion request is refused?
Neither right is absolute, so the recipient should explain its reasons. If you are unhappy with the response, you can raise a complaint with the Information Commissioner's Office (ICO), the data-protection regulator, who can look at how the request was handled.
Related terms
This is general information, not legal advice. For guidance on your own situation, consider speaking with a qualified professional.
Reviewed by OSINTA's founding lawyer — 2026-06-27.
Want to frame your own request clearly?
OSINTA helps you understand your own footprint and frame your own de-listing or erasure requests — you stay in control of every step.