Source removal changes the website publishing information. Google delisting concerns whether a link appears in specified search circumstances. One can happen without the other. Before making a request, decide whether you need a factual correction, less search visibility or an assessment of both. That choice determines what evidence to collect and which organisation to contact.
For the official figures behind the process, read our guide to Google’s European privacy Transparency Report, including what requests and URL totals actually measure.
Understand the two organisations involved
A directory controls its own profile and documents. A search engine helps users discover pages. Those roles overlap in what you see on screen, but they are not interchangeable. Clicking a result can move you from a Google page to a publisher's page without making the boundary obvious.
Record both addresses when investigating a concern. The destination URL identifies the publication. Your search notes explain how you found it, including the name or other terms used. A screenshot of results alone may not show enough to identify the content that needs review.
The CNIL's delisting explanation distinguishes search visibility from deletion at the source. Keep that distinction throughout the case. A message from a directory is not a decision by Google, and Google's response does not instruct every publisher to alter its records.
Fictional example: Elise discovers a directory result when searching her name. The source page describes a former appointment accurately but labels another panel incorrectly. She can ask the directory about the factual label while separately considering whether name-search visibility merits review. The two questions rely on related facts but seek different decisions.
Do not describe either organisation as controlling “your internet presence.” That phrase obscures other directories, direct links and different search queries. A bounded description makes it easier to recognise which change would actually address your concern.
Compare what changes in practice
| Action | Source page | Search discovery | Direct link |
|---|---|---|---|
| Correct a field | The specified fact changes | The displayed result needs separate checking | Page may remain available |
| Remove source content | The targeted content changes or disappears | Search appearance needs verification | Old URL must be checked |
| Delist a search result | Source may remain unchanged | Visibility changes within the decision's scope | Source may remain accessible |
Read a response against its stated scope. A result may be removed for certain searches without becoming undiscoverable in every context. Other engines and other websites require their own checks. Do not describe a limited observation as worldwide erasure.
Likewise, source removal needs a precise definition. The publisher might remove an address but retain the profile, replace a document or delete the page. Those outcomes are different from removing every reference to the business. Keep the actual change in your case record.
Search excerpts can also differ from the current page. If the source has changed, compare the live publication before assuming that an old-looking excerpt means the source refused. If the page remains unchanged, a missing result does not establish that the underlying information is gone.
Google explains source persistence in its personal-information removal guidance. Use the platform's current explanation to interpret its response rather than treating every “approved” label as the same technical or practical outcome.
Define the result you actually need
Write the concern in everyday terms. “This page wrongly says I am the current director” identifies a factual problem. “My home address appears when someone searches my name” identifies an exposure and discovery concern. “I want no record that I ever ran this company” is much broader and may face substantial limits.
Separate your desired outcome from the route you initially imagine. Someone may search for “Google removal” because Google is where they noticed the issue, even though correcting the source is their main need. Another person may have accurate historical information that requires a separate search assessment rather than a correction.
Ask what a useful partial outcome would look like. If the personal address disappeared but the company remained, would that address the concern? If the role were accurately labelled as former, would that solve the confusion? These questions help prevent an all-or-nothing request where a narrower change would be meaningful.
Do not invent the circumstances needed to support a route. An upcoming meeting can explain timing; it does not prove inaccuracy or make information automatically removable. A wish for privacy is relevant context, but the request still needs to identify the data and explain the basis for review.
Prioritise outcomes you can verify. A corrected label, absent address or specified search result can be checked. “Reputation repaired” cannot be established from one changed page. Define progress in terms of the publication and search context rather than predicting how every future visitor will think.
Coordinate the requests without a universal sequence
There is no single order that fits every case. If a clear factual error exists, correcting it may be a useful starting point. If the concern involves search discovery of personal information, review the relevant search route too. If an official source needs analysis, a directory-only request may leave a dependency unresolved.
Maintain one record linking the tasks, but keep separate status fields. For example: source correction requested, source reply received, source checked, search request assessed and search outcome checked. This prevents a completed step from concealing unfinished work at another level.
Use evidence consistently. If you explain a departure date to a publisher, do not describe it differently in a search request. Where the relevant question differs, explain the difference rather than copying a letter unchanged. A fact supporting correction and a circumstance supporting privacy review perform different roles.
Avoid parallel duplicate submissions merely because the first has not yet produced a visible change. Check acknowledgements and reference numbers. A follow-up should clarify or advance an existing matter instead of making it harder to identify which request a reply concerns.
Direct routes remain an option. If you purchase assistance, ask whether it covers source work, Google work or both. The service descriptions for directory assistance and Google delisting can help identify the distinction, but only a current written scope establishes what a provider will do in your case.
Read the outcome accurately
Fictional example: a directory changes “current director” to “former director.” That is a verified correction even if the page still appears in a name search. Calling the case a failure because the entire page remains would overlook the requested improvement.
In another fictional example, Google accepts a request affecting a result while the source page remains available through its direct URL. That is a search outcome, not source deletion. The final record should state the search context checked and the remaining source access without overstating the result.
A refusal also needs careful reading. The publisher may decline erasure but offer correction. Google may refuse under the route used. A request for more evidence is neither approval nor necessarily a final refusal. Keep the reason and scope of each answer.
Use a dated before-and-after comparison. Check the exact source, relevant attachment and original search context. If you cannot reproduce a previous result, record the observation rather than claiming a permanent outcome. Future checks may be appropriate, but a monitoring plan should have a defined purpose and scope.
The useful end point is a clear account: what changed, who decided it, where it was verified and what remains unresolved. From there you can decide whether to stop, make a focused follow-up or seek specialist advice. You do not need to describe a limited improvement as total disappearance for it to be worthwhile.
Keep continuity when moving between source and search work. Retain the original request references and a clear account of the relevant facts. A new surface does not require inventing a new history. The facts can remain consistent while the recipient, decision sought and way of checking the outcome change. If an item is partly resolved, say precisely what changed. This helps a recipient understand the remaining question and prevents you from submitting an inaccurate account in which every earlier action appears unsuccessful merely because another publication or search context remains visible.
Related reading: My home address appears on Google: which request should I consider?; Old text in Google after a page correction: what to check; How to choose a Google delisting service.
