Google indexes pages; it doesn't host your address. So removal almost always means getting the address off the source page first, then asking Google to refresh. Doing it the other way round — requesting removal while the page still shows your address — either fails or reverts at the next crawl. Google does offer a personal-information removal request for cases where the site won't cooperate, but it's the fallback, not the first step.
The order that works
- Find every page. Search your address in quotes. Try variations, and check Bing too — different index, sometimes different results.
- Get it off the source page. Contact the site owner and ask for removal. If it's your own page, edit it. This is the step that actually matters; everything else is cache management.
- Ask Google to refresh. Once the page no longer contains the address, use Search Console's removal tool if you own the site, or the public "Remove outdated content" tool if you don't. This clears the cached copy rather than the page.
- If the site won't remove it, use Google's personal-information removal request. Results vary; it's a policy decision by Google, not an entitlement.
- Re-check in a few weeks. Indexes update at their own pace.
Removing a URL from Google while the page still contains your address hides one route to it. The page is still live, still readable by anyone with the link, and still scrapeable by harvesters — who don't use Google.
You'd have improved your search results and changed nothing about your actual exposure. Source first, always.
Where addresses usually turn up
- Public code repositories — commit metadata contains an address, and it's indexed. Most platforms offer a no-reply address.
- Forum and community profiles, often from accounts you'd forgotten.
- CVs uploaded somewhere public, including on someone else's site.
- Conference and event listings, speaker bios, attendee lists.
- Company team pages from a previous job.
- PDFs — minutes, newsletters, planning documents. Frequently indexed and frequently forgotten.
- WHOIS records for a domain registered without privacy. Fixing that
What removal doesn't achieve
Being clear about the ceiling, because this is a place people expect too much:
- It doesn't reach harvesters. If a page was public for any length of time, the address has been scraped. Removing it now stops future collection; it doesn't recall past collection.
- It doesn't reduce existing spam. The lists already exist.
- It doesn't cover other search engines unless you repeat the process.
- It doesn't touch data brokers. Different mechanism entirely. People-search sites
So the honest framing is that this reduces ongoing exposure and does nothing about accumulated exposure. Worth doing, worth not overestimating. The general version of this limit
The version that doesn't need cleanup
If you need a contact address on a public page — and many people do — publish an alias you're prepared to burn rather than your real address. It gets harvested exactly the same way, and when the volume becomes unmanageable you switch it off and publish a new one.
That converts an irreversible exposure into a renewable one, which is the only durable answer for anything genuinely public. Reducing harvesting in the first place