How to remove personal information from search results

Removing a search result and removing the page behind it are two different jobs. A search engine can stop showing a URL, but that does not erase the page, image, or file from the website that published it. When possible, remove or correct the source first, then ask each search engine to update or remove its copy of the result.

Start by recording the exact exposure

Before changing anything, save only the evidence you may need to complete or appeal a request:

• the exact page URL, not just the website's home page
• the search query that produced it
• the result title and snippet
• the personal information shown
• the date and time you checked it
• a redacted screenshot that does not spread the sensitive information further

Copy the URL from the search result and the destination page. Images can have a separate image URL and a separate page URL; record both. If the same content appears under several URLs, each URL may need its own request.

If the page contains threats, stalking details, non-consensual intimate imagery, or information about a child, prioritize safety. Do not keep opening or sharing the material to build a perfect file. Use the platform's category-specific safety form, and contact an appropriate support service or emergency service if there is immediate danger.

Choose the layer you need to change

| Layer | What an action can do | What it cannot do | | --- | --- | --- | | Source website | Delete or edit the original page or file | Automatically clear every search index, repost, or archive | | Search engine | Remove or limit a result under policy or law | Delete the content from the source website | | Outdated-result tool | Refresh a result after the source changed or disappeared | Remove personal information that is still live on the source page | | Data-broker opt-out | Suppress a broker's listing or stop covered sale or sharing | Erase public records or unrelated copies |

This distinction prevents the most common failed request: submitting an outdated-content form while the sensitive text is still present on the live page.

Remove or correct the source first

If you control the account, post, or website, use its edit, privacy, or deletion controls. If someone else controls it, look for the publisher's Contact, Privacy, Report, or Remove my information route. State precisely:

1. which URL contains the information
2. which information belongs to you
3. whether you want deletion, redaction, correction, or account removal
4. the policy or legal right you are relying on, if applicable
5. how the publisher can confirm completion without collecting unnecessary data

Ask for a case number or written confirmation. Do not send a full identity document in an ordinary email merely because a page asks you to “prove” who you are. Use the official process and provide only the fields reasonably needed to match and verify the record. If identification is genuinely required, redact unrelated numbers and images where the process permits it.

Google's own guidance recommends contacting the website owner because only the publisher can remove the page from the web. If the owner has already changed or deleted the page, the search-refresh step becomes much simpler.

Use the correct Google route

Google has several removal routes with different purposes.

Personal contact information

Use Results about you, where available, to find results containing your home address, phone number, or email address, request removal, track decisions, and turn on notifications for new matches. Google also provides a detailed request form for people who cannot use the signed-in feature and for requests made on behalf of someone else.

Google may decline results it considers valuable to the public, including some government, educational, news, or business pages. An approved removal can be complete or limited to queries containing your name or identifier. In either case, the source page may remain online.

Other sensitive information and doxxing

Google's private-information policy also accepts requests concerning categories such as confidential government identifiers, bank or card numbers, signatures or identity documents, private medical records, and confidential login credentials. Its doxxing route covers qualifying pages that combine personal information with threats or aggregate a significant amount of personal information without a legitimate purpose.

Use the category that matches what is actually visible. Give the specific URL and a screenshot that helps the reviewer locate your information without exposing unrelated people.

A result that is now stale

Use Google's Refresh Outdated Content tool only when a page or image no longer exists or the source removed important content. It is not a privacy appeal for information that is still present on the live page. After approval, a vanished page can leave the results; a changed page may temporarily lose its old snippet until Google recrawls it.

A legal request

If a policy route does not cover the material but a law in your jurisdiction does, Google's Legal Help Center has a separate process. A legal theory is not a shortcut: identify the exact content, URL, right, and jurisdiction. For complex or contested cases, get advice from a qualified local professional.

Submit the equivalent request to Bing

Bing applies its own rules. Microsoft says it may remove sensitive personal information and other qualifying material after review, while balancing privacy, safety, law, and access to information. Use Microsoft's official Report a Concern flow for live content that fits a policy or legal category.

If the publisher has already deleted or changed the content but Bing still shows the old page or snippet, use Bing's Content Removal Tool instead. A Google approval does not automatically update Bing, and a Bing approval does not update Google or the source.

For any other search engine, start from its own current privacy, safety, legal, or outdated-result documentation. Do not send identity documents to a form reached through an advertisement or an unsolicited “removal service” message.

Keep a request ledger

A simple log makes follow-up reproducible:

| Field | Record | | --- | --- | | Exposure | Query, result URL, source URL, and information category | | Source action | Contact route, requested remedy, case number, date | | Search action | Engine, form category, request ID, date | | Outcome | Approved, partially removed, denied, changed, or pending | | Scope | All queries, name-based queries, one URL, one image, or source only | | Next check | The date you will verify the live page and each search engine |

Do not write “removed” when only one result disappeared for one query. Test the exact URL, a name query, an identifier query, image search where relevant, and the source page. Search from a signed-out or neutral context as well, because personalization and location can change what you see.

If the request is denied

Read the stated reason before resubmitting. Common mismatches include the wrong URL, information that is no longer visible in the screenshot, use of the stale content tool for a live page, or a public-interest exception.

Correct factual gaps and appeal through the official channel. Avoid repeatedly filing the same unsupported request or claiming a legal right that does not apply. If the publisher refuses a valid privacy request, use the complaint route of the relevant regulator or seek local legal advice rather than escalating to the publisher's unrelated vendors.

Know when the job is complete

The best outcome is usually a verified chain:

1. the source was deleted, corrected, or redacted
2. the relevant search results were removed or refreshed
3. image and alternate-URL copies were checked
4. the request IDs and outcome were saved
5. monitoring is in place for a new URL or listing

Search removal reduces discovery; it does not make a fact disappear from every copy of the internet. If the source is a people-search listing, continue with the data-broker opt-out directory and the reappearance monitoring workflow.