Analysis of Google’s Removal Decision
Public Engagement > PUBLIC LEGAL NOTIFICATIONS
This page presents the official decision issued by Google LLC on 1 April 2026 concerning the removal of several URLs associated with my name from European search results. To ensure full transparency and to allow independent verification of the procedural steps taken, the decision is published here in redacted form, with personal email addresses and any non‑essential identifiers obscured in accordance with the UK GDPR and the principles of data minimisation and proportionality.
Immediately below, I have also included the redacted copy of my formal escalation to Google’s Legal Department, which preceded and informed the decision reproduced above. This document is likewise published for the same reasons of transparency, accountability, and public documentation. It provides the legal and factual context that led to Google’s reassessment, including the withdrawal of the primary source by East Sussex County Council, the removal of derivative content by multiple platforms, and the ongoing judicial proceedings notified to the competent authorities.
Both documents are reproduced without substantive alteration, save for the redactions required to safeguard privacy and comply with data‑protection obligations. Their publication forms part of the broader effort to document, in a verifiable and responsible manner, the institutional steps taken to correct the unlawful dissemination and indexing of judicial and health‑related data.
Analysis of Google’s Removal Decision (1 April 2026)
Google’s decision of 1 April 2026 to remove all URLs associated with my name from European search results represents a significant step in restoring accuracy, proportionality and data‑protection compliance.
Based on the documentation available and on Google’s established criteria for de‑indexing, the following analysis outlines the most plausible factors that contributed to this outcome.
Based on the documentation available and on Google’s established criteria for de‑indexing, the following analysis outlines the most plausible factors that contributed to this outcome.
1. Withdrawal of the Primary Source by East Sussex County Council (ESCC)
A key element in Google’s assessment was the official removal of the original ESCC press release, which now returns a 404 error and is no longer validated by the issuing authority.
When a public body withdraws a publication, Google typically considers the information:
When a public body withdraws a publication, Google typically considers the information:
- no longer reliable,
- no longer verifiable,
- no longer suitable for continued indexing.
This aligns with Google’s long‑standing approach to outdated or withdrawn public‑sector content.
2. The Content Was Based on a Non‑Judicial Document
The ESCC Subject Access Request confirms that the original article was drafted using a Prosecution Summary, not a court judgment.
Such documents:
Such documents:
- are not final,
- are not judicially validated,
- are not intended for permanent public disclosure.
Google generally treats non‑judicial and non‑final materials as unsuitable for long‑term indexing, especially when the original source has been withdrawn.
3. The Conviction Was “Spent” Under UK Law
The documentation shows that the conviction had been “spent” for over a year under the Rehabilitation of Offenders Act 1974.
Spent convictions:
Spent convictions:
- cannot be treated as public information,
- cannot be republished without a lawful basis,
- cannot be indexed indefinitely.
This directly engages Article 10 GDPR, which imposes strict limitations on the processing of judicial data.
4. Removal of All Snapshots by the Internet Archive
The Internet Archive removed every stored version of the original page, including:
- historical captures,
- cached versions,
- archived snapshots.
Google typically interprets such removals as evidence that the content is no longer reliable or appropriate for public preservation, reinforcing the case for de‑indexing.
5. Removal and De‑Indexing by PressReader
PressReader, a professional news aggregator, also removed the derivative article.
When multiple independent platforms withdraw the same content, Google tends to view this as confirmation that:
When multiple independent platforms withdraw the same content, Google tends to view this as confirmation that:
- the information is outdated,
- the source is no longer authoritative,
- continued indexing would be disproportionate.
This cross‑platform consistency is a strong indicator of the content’s unreliability.
6. Presence of Judicial and Health‑Related Data (Articles 9 and 10 GDPR)
The URLs contained:
- judicial data,
- health‑related information,
- material not validated by a court.
Google cannot process such data without:
- a lawful basis,
- accuracy,
- necessity,
- proportionality.
With the primary source withdrawn, these conditions were no longer met.
7. Existence of “Orphaned Snippets”
Google likely detected that some snippets displayed my name even though:
- the underlying pages no longer contained it, or
- the pages were no longer accessible.
Orphaned snippets constitute unlawful processing of personal data, and Google typically removes them promptly to restore accuracy.
8. Documented Risk of Name Collision
The presence of multiple individuals with the same surname increases the risk of:
- algorithmic confusion,
- misattribution,
- reputational harm to uninvolved third parties.
Google treats name‑collision scenarios as a significant risk factor, particularly when the underlying content is no longer verifiable.
9. Consistency Across Platforms
Google observed that:
- ESCC removed the source,
- Internet Archive removed all captures,
- PressReader removed the derivative article,
- other aggregators also withdrew their versions.
When the wider ecosystem surrounding a piece of content collapses, Google typically aligns its indexing accordingly.
Conclusion: The Most Probable Interpretation of Google’s Decision
Google’s removal of all URLs was likely driven by the convergence of the following elements:
- the primary source was withdrawn by the issuing authority,
- the content was based on a non‑judicial document,
- the conviction was spent,
- major platforms had removed their copies,
- the information was no longer verifiable,
- the URLs contained judicial and health‑related data,
- orphaned snippets were present,
- there was a risk of name collision,
- no lawful basis remained for continued indexing.
In essence:
Maintaining the URLs posed a higher legal and reputational risk than removing them.
This decision aligns with Google’s obligations under the GDPR, the Rehabilitation of Offenders Act 1974, and established case law on the right to be forgotten.
Note: Certain URLs previously associated with my name no longer appear in Google’s European search results. Their removal follows Google’s assessment of accuracy, relevance, and data‑protection requirements under the GDPR.
- http://www.itv.com/news/meridi
an/2022-12-26/man-caught- faking-doctors-letter-to- claim-blue-badge - https://www.itv.com/news/merid
ian/2022-12-26/man-caught- faking-doctors-letter-to- claim-blue-badge - https://www.sussexexpress.co.u
k/news/crime/eastbourne-man-gi ven-suspended-prison-sentence- after-faking-medical-letter- for-blue-badge-application- 3965025 - https://www.theargus.co.uk/new
s/23213516.eastbourne-man-sent enced-hove-council-blue-badge- fraud/ - https://www.whatsoninbrighton.
net/eastbourne-man-sentenced-i n-hove-after-council-blue-badg e-fraud/
