A business owner’s guide to removing personal information from Google Search

Start by separating personal information from business information

A business owner may use the same address, telephone number or email address for both personal and commercial purposes. That overlap does not make every result automatically removable. Google may preserve information that it considers valuable to the public, including material on government, educational, newspaper or business websites.

Identify exactly what is private and why its exposure matters. A home address used only for correspondence presents a different case from the public address of a customer-facing premises. A director's private mobile number is different from a published sales line. Describe the individual risk accurately rather than calling all company information confidential.

• Home address or precise residential location
• Personal mobile or home telephone number
• Private email address
• Government, financial, medical or login information
• Personal details aggregated with threats or calls for harassment
• Outdated profiles that still connect private details to the individual

Protect safety before starting a removal request

If the exposure includes a credible threat, stalking, blackmail, account compromise or an immediate risk to someone at the address, treat safety as the first workstream. Contact the appropriate police or emergency service where necessary, secure affected accounts and tell relevant people not to circulate the material further.

Preserve evidence without creating new exposure. Record the exact page and search-result URLs, publication date, search query and a screenshot showing the context. Redact unrelated personal details when sharing evidence. Do not send passwords, identity documents or unredacted financial information by ordinary email unless a verified process specifically requires them.

• Record the source URL and the Google result URL
• Capture the visible information, date and search query
• Note threats, harassment or connected accounts
• Secure email, domain, social and business-profile access
• Keep an incident log with one accountable owner

Map every place where the information appears

Removing one result does not address copies on other pages, subdomains, PDFs, image URLs, directory profiles or quoted snippets. Search the person's full name with the exposed detail, then search relevant variations such as an old company name, previous address, job title or commonly used telephone format.

Create one row for each distinct source URL. Record whether the information is still visible on the live page, appears only in Google's result snippet, or survives in an image result after the source changed. This distinction decides which tool is appropriate.

• Exact source URL and website owner
• Search query that reveals it
• Type of personal information
• Live page, snippet, cached description, PDF or image
• Duplicate and republished URLs
• Source contact, opt-out or correction route
• Request status and follow-up date

Choose the correct removal route

There are four main routes. Remove or correct the information at the source when possible. Use Google's personal-content process when qualifying private information remains live. Use the Refresh Outdated Content tool when a third-party page or image has already been removed or materially changed but Google still shows the old version. If the information is on a website you control, remove or protect it and use Search Console where a temporary block is needed quickly.

These routes solve different problems and can run together. Google can restrict a result without deleting the source page. A publisher can remove a page while an old search snippet remains temporarily visible. Track source action and search action separately.

• Live third-party page: source request and, where eligible, Google personal-content request
• Changed or deleted third-party page: Refresh Outdated Content
• Page on your own site: permanent technical removal plus optional temporary Search Console block
• Possible legal or data-protection issue: qualified advice and the relevant legal route

Request removal of an address, phone number or email from Google

Google accepts requests concerning certain personally identifiable information, including a person's home address, phone number and email address. The affected person or an authorised representative can submit a request. Google reviews the exact URLs provided and considers whether the information falls within its policy and whether there is a public-interest reason to keep the result available.

Google's Results about you feature can help eligible adult users find results containing their contact information, request removal and receive notifications about new matches. Availability and options vary by market and result type. A detailed personal-content removal form is also available, including for representatives or people who do not want to use the signed-in feature.

Approval may remove the URL for all searches or only for searches containing the person's name. In either case, the source page may remain online, so source removal is still important when practical.

• Submit the exact URL shown in the result
• Identify the information as it appears on the page
• Explain who is affected and your authority to act
• Provide only the evidence requested
• Save the confirmation and monitor the decision

Understand when exposed information becomes doxxing

Doxxing is more than finding an address in an ordinary business record. Google describes doxxing content as personal information shared to cause harm. Its policy may apply when a URL combines personal information with explicit or implicit threats, calls for others to harm or harass the person, or a significant collection of personal details without a legitimate purpose.

Document the relationship between the information and the threat. Preserve surrounding text, connected posts, timestamps and copied versions without amplifying them publicly. Avoid emotional accusations in the request; show the exact facts that establish the risk.

A search-removal request is not a substitute for immediate safety action. Where threats are credible, preserve evidence for the relevant authorities and obtain appropriate security or legal support.

Remove outdated directory and profile information at the source

Old company profiles, people-search databases and directories often repeat information from historic public records, previous websites or data suppliers. Begin by finding the profile's claim, correction, privacy or opt-out process. Ask for the specific field or page to be removed rather than sending a broad demand with no URL.

Where a UK organisation controls the personal data, an individual may be able to make a written request for rectification or erasure. The right to erasure is not absolute. Freedom of expression, legal obligations, public-interest work, archiving and legal claims can justify continued processing. Current ICO guidance says organisations generally need to respond without undue delay and within one month, subject to permitted extensions and identity checks.

Provide enough information to locate the record, but do not send more identity evidence than is reasonably necessary. Keep the request, response and any reference number. If the publisher corrects or deletes the page, check all duplicate URLs before moving to Google's outdated-content route.

• State your name and the exact URL
• Quote the specific data to correct or erase
• Explain why it is inaccurate, unnecessary or creating a personal risk
• State the outcome requested
• Ask for written confirmation
• Record the deadline and any reason given for refusal

Use Refresh Outdated Content only after the source changes

Google's Refresh Outdated Content tool is for pages or images you do not control that no longer exist or have removed important information. It does not remove a live page simply because the information is inaccurate, harmful or private.

Copy the exact URL associated with the search result. If the information appears through multiple URLs, parameters, PDF files or image locations, submit each relevant version. For an image, use the image-result link specified by Google's instructions rather than only the page that once displayed it.

A successful refresh updates Google's result; it does not delete content from the web. If the source still contains the information, return to the source, personal-content or appropriate legal route.

If the personal information is on a website you control

Remove the information from the page, delete the file, restrict access with authentication or apply an appropriate noindex directive. For a permanently deleted page or file, configure the server to return a genuine 404 or 410 response. Do not rely on robots.txt: blocking crawling can prevent Google from seeing the instruction that the content should leave the index.

Search Console's Removals tool can temporarily hide a page or clear an outdated snippet while Google processes the permanent change. Google says a temporary URL block normally lasts about six months, so it must be paired with a lasting action. Check variants such as uppercase URLs, query parameters, PDFs, image files and development copies.

• Remove or update the exposed content
• Return 404 or 410 for content that is permanently gone
• Password-protect genuinely private material
• Use noindex where the page must remain public but should not appear in Google
• Use Search Console removal as a temporary acceleration step
• Confirm that URL variants and files are also protected

Handle an outdated Google Business Profile correctly

A Google Business Profile is designed to publish business information. If it shows a home address, personal number or old location, first check whether the profile is claimed and whether the details can be edited through the authorised account. Service-area businesses may be able to hide an address where customers are not served at that location, subject to Google's profile rules.

Do not submit a personal-information request as a substitute for correcting a Business Profile you control. Update the source profile, verify the change and then monitor Search and Maps. If an old third-party profile still repeats the details, address that source separately.

Write a removal request that is easy to assess

A strong request is concise, specific and supported. Identify the exact information, where it appears, who is affected and the policy or right that may apply. Explain the practical risk without including unrelated history. One well-organised request is usually easier to evaluate than repeated submissions with changing explanations.

Do not claim that information is private if it is intentionally published as current business contact information. Do not alter screenshots, invent threats or use several policy categories without evidence. If a request is rejected, read the reason, correct any URL or evidence problem and resubmit only when you can address the issue or provide meaningful new information.

• One-sentence description of the problem
• Exact URLs and search queries
• Information that identifies the affected person
• Evidence of threats, aggregation, inaccuracy or source removal where relevant
• The specific action requested
• A safe contact address for the decision

Monitor after removal and reduce reappearance

A result can disappear while copies remain discoverable elsewhere. Re-run a controlled set of searches after the decision, check images and PDFs, and monitor directories that previously republished the information. Google's Results about you notifications may help eligible users detect new matches.

Reduce unnecessary exposure at the source. Separate personal and public business contact details, review domain-registration privacy, remove old staff biographies and downloadable files, secure social profiles and maintain accurate company listings. Do not publish replacement pages containing the same private information merely to push an unwanted result down.

• Check the approved URL and query scope
• Search for copied text, number and address formats
• Review images, PDFs and cached descriptions
• Recheck high-risk sources monthly until stable
• Maintain a private evidence and decision log

Common mistakes that delay personal-information removal

Most delays come from using the wrong route or supplying an incomplete URL map. A request to Google will not erase a page from another website, and an outdated-content request will not work while the information remains live.

Be realistic about outcomes. Google, publishers, platforms and data controllers make their own decisions. A result may remain when the information is current, professionally relevant, published for a legitimate purpose or protected by public-interest and expression considerations.

• Reporting the search page instead of the exact source URL
• Using the outdated-content tool while the information is still live
• Ignoring PDFs, images, URL parameters and copied profiles
• Publishing sensitive evidence in a public complaint
• Submitting a broad legal claim without identifying the data or requested action
• Assuming business contact information always qualifies as private
• Treating temporary Search Console removal as a permanent fix

When specialist support is appropriate

Specialist help is useful when private information is spread across many sources, doxxing involves threats, a publisher is unresponsive, the correct policy route is unclear or removal needs coordination across source websites, platforms and search engines. High-risk cases should also involve appropriate legal, security or law-enforcement support where needed.

FirstRank maps the exposure, preserves proportionate evidence, separates source and search routes, and provides realistic expectations about what each process can achieve. We do not guarantee a decision controlled by Google or another publisher, and we do not use privacy processes to conceal legitimate public-interest information. This guide provides general practical information and is not legal advice.