To remove leaked content from Google, match each URL to the right request: intimate images you never sold and deepfakes of you go through Google's personal sexual content form, copies of paid posts you own go through the copyright form for Search, and exposed contact details go through Results about you. An approved request only delists the URL from Google Search. The page stays online until its host removes it, so send the host a report as well and repeat the process on Bing.
This page covers search delisting only. Getting the file taken down by the website that holds it is covered in the copyright takedown evidence pack, and Australian escalation through eSafety and police sits in the Australian leak response plan. Everything here is general information, not legal advice.
Delisting is not deletion
Google is direct about this. Its page on removal options outside Google Search says it can keep content out of results but cannot remove it from the sites that host it, and that the best option is usually to remove content at its source. Bing's content removal help makes the same point: search engines cannot delete content from any website. A delisted page can still be reached through a shared link, a social post or another search engine.
Approval also comes in two strengths. Google describes a full removal, where the URL stops appearing for any search, and a partial removal, where it stops appearing for searches containing your name or identifier but may surface for other queries. Partial removals tend to happen when a page mixes the violating material with content about other people or with information Google considers valuable to the public. Record which one you received, because a partial removal still needs the host route.
Form picker: which request, what proof
Pick the row that describes what you found. One page can need more than one request, for example a leak post that also shows your phone number.
| What you found | Request to use | What to have ready | Source |
|---|---|---|---|
| An intimate image of you that was never sold or published commercially | Google personal sexual content removal | Page and image URLs, plus a screenshot edited so only your face shows if asked | Google policy |
| A fake nude or sexual deepfake in which you are identifiable | The fake sexual content option on the same Google request | URLs and a short statement that the image is fabricated and shared without consent | Google policy |
| Your stage name or handle tied to adult pages or ads that have nothing to do with you | Google request for results associating you with sexual material | The query you searched and each result URL it returned | Google policy |
| Copies of paid posts in which you own the copyright | Google copyright removal form for Search | Where the original lives, each copied URL, and your authority to act | Google DMCA form |
| Your home address, phone number or email on a leak page | Results about you, or the personal information form | The details typed exactly as the page shows them | Results about you |
| A page publishing your details next to threats or calls to harass you | The doxxing route in Google's personal information policy | The URL and a capture showing the threat beside your details | Google personal info policy |
| A page the host already deleted that still shows in results | Google refresh outdated content | The page URL, or the copied link address for an image result | Google refresh help |
| Intimate images of you in Bing results, real or generated | Microsoft Report a Concern, non-consensual intimate imagery | URLs, and confirmation you were an adult when it was made, per the Helpline's walkthrough | Microsoft form |
| A dead link or stale snippet still showing in Bing | Bing Content Removal Tool | A URL that now returns 404 or 410, or a word found only in the old version | Bing help |
| Copied paid content appearing in Bing results | Bing infringement notice for search results | The same copyright details you prepared for Google | Bing notice form |
Filing Google's personal sexual content request
Start from Google's personal sexual content page, or for pictures use the removal option inside Google Images, which Google calls the Image Viewer flow. You or a representative can file as long as you are the subject. List every page URL and image URL you want reviewed, because Google reviews only the addresses you supply. If the form asks for screenshots, Google suggests taking them on the device you are filing from and editing them so only your face shows. Never include imagery of anyone under 18; Google has a separate reporting process for that.
The detail creators miss is the commercial condition. Google's policy covers intimate imagery you did not consent to, and imagery you did consent to only where it is not commercialised online or elsewhere, and it points copyright concerns to its DMCA form instead. So posts you sold behind a paywall usually belong on the copyright route below. Deepfakes are assessed differently: you need to be identifiable, the content must be fake and falsely depict you nude or in a sexual situation, and it must have been distributed without your consent, with no commercial test.
For sexual imagery Google says it tries to find and remove duplicates as standard, with an opt-out on the form if you prefer to handle copies yourself. It weighs public interest before deciding, and it emails you when a URL is removed.
Copied paid content: the copyright route
The copyright form for Search is for the copyright owner or someone authorised to act for them. Google's copyright transparency FAQ notes that a DMCA notice needs a good-faith statement that the use is unauthorised and an affirmation, under penalty of perjury, that the sender is authorised to represent the owner. It also says Google declines URLs where it lacks information, cannot find the material, or sees the process being misused.
Think about privacy before you file. The same FAQ explains that Lumen, a research project that collects takedown notices, publishes the requests it receives, and that Google may link from its results to the published notice in place of the removed content. Decide in advance which name appears as the copyright owner and which contact details you include. Google's legal removals page adds that content in several Google products needs a separate notice for each product, so a leak hosted on a Google service is a different request from the search result pointing to it.
Bing and Microsoft: the parallel requests
Bing needs its own requests. Microsoft's Digital Safety Content Report says anyone can ask for removal of a nude or sexually explicit image of themselves shared without consent, including synthetic imagery, and that once a report is confirmed it removes the reported links from Bing results globally. Microsoft's May 2026 update adds that it has piloted StopNCII hashes in Bing since September 2024, which is one reason to read how StopNCII works if your images are private rather than commercial.
For pages that are already gone, Bing's Content Removal Tool handles dead links and stale snippets. Bing only updates a result after it recrawls the page, so confirm the host has actually removed or changed the content before you submit. If the content is still live, Bing's help says to go to the site owner first.
Delisting tracker
Keep one row per URL per search engine. A spreadsheet works; what matters is that every column is filled before you call a URL closed.
| Column | What to write | Why it matters |
|---|---|---|
| URL | The full page address, plus the image address if it differs | Google only reviews the addresses you list |
| Engine and request | For example, Google personal sexual content or Bing intimate imagery report | Each engine and each form is a separate case |
| Submitted | The day and clock time you sent it, with your time zone | Shows the order of events if anyone asks later |
| Reference | Request ID or the confirmation email's subject line | You will quote it when following up or refiling |
| Host action | Whether a host notice went out, and what the host replied | A delisted page can still be online at the source |
| Outcome | Full removal, partial removal, denied, or more information requested | A partial removal still appears for some searches |
| Recheck | The date you will search again while signed out | Catches re-indexing and copies at new addresses |
| Next step | Refresh request, refile with new facts, legal request, or close | Stops open rows from going quiet without a decision |
Keeping results clean after approval
- Turn on notifications in Results about you so Google tells you when new results show your address, phone number or email.
- Add alerts for your stage name and handles, as set out in how to check if your content is leaked.
- Treat every new address as a new request, and mention your earlier reference so the reviewer sees the history.
- When a host deletes a page, file a refresh on Google and use the Content Removal Tool on Bing so stale snippets disappear sooner.
- If the copy sits on a US platform covered by the Take It Down Act, send that platform a request too, using the Take It Down Act request guide.
- If the volume outgrows what you can track, read how to compare leak removal services before paying anyone to file for you.
Limitations of delisting
Google and Microsoft decide every request under their own policies, may weigh public interest, and may approve only a partial removal. Other search engines run their own processes, and none of these requests removes the source page. Forms, labels and policies change, and this guide reflects them as published on 1 October 2026. Contact police if a page carries threats or blackmail, or if anyone shown is under 18. Talk to a lawyer if ownership of the content is disputed, a counter-notice arrives, or you want to rely on a local law that Google's policies do not cover, which Google handles through its legal removals route.