the ITV case and Google’s technical response
Public Engagement > PUBLIC LEGAL NOTIFICATIONS
Forensic Style Report – ITV Source Code Comparison (2022 vs 2026) and GDPR Removal Events
Date: 02/06/2026
This forensic style report documents my technical analysis of the ITV News article “Sussex man who faked doctor’s letter to claim Blue Badge caught through ‘grammatical errors’”, originally published on 26 December 2022, and subsequently re‑served in 2026 following ITV’s migration to a new CMS. It also incorporates my GDPR removal correspondence with the Google Removal Team, which provides additional evidentiary context regarding the reappearance of URLs previously delisted under European data‑protection law.
1. Background of the ITV Publication (forensic style)
The original 2022 ITV News article associated my full name, “Riccardo Gresta”, with allegations of Blue Badge fraud, embedding both judicial data and special category health data directly into its metadata, social previews and structured data.
The 2022 source code shows:
- a
NewsArticleschema explicitly containing my name - a meta description stating that I “couldn’t walk further than 20 metres”
- Open Graph and Twitter Cards replicating the same health and judicial claims
- a publication timestamp of 26 December 2022
- no verification notes, no editorial caveats, and no contextualisation
This configuration ensured maximum visibility across search engines and social platforms, amplifying the reputational impact of inaccurate and unverified information.
2. ITV 2026 Source Code Re‑Serving (forensic style)
In 2026, ITV migrated its infrastructure to a Next.js‑based system. My forensic comparison of the 2022 and 2026 source code demonstrates that the article was re‑served, not revised.
The 2026 version retains:
- the same headline
- the same meta description
- the same Open Graph metadata
- the same JSON‑LD, including the 2022 publication date
- the same health and judicial data
- the same article body
The only significant technical change is the presence of a faulty canonical tag, now pointing to a generic
/news/article endpoint rather than the original article URL.This confirms that ITV performed a technical refresh without any editorial review, leaving all inaccuracies and sensitive data intact.
3. GDPR Removal Events and Google Correspondence (forensic style)
On 1 April 2026, Google granted my GDPR removal request, delisting the ITV article for name‑based queries. All affected URLs disappeared from the SERP.
However, in late May 2026, two URLs unexpectedly reappeared:
- An ITV topic‑hub URL displaying the original snippet
- A Facebook post linking to the original ITV article
I reported this to Google on 31 May 2026, following the exact procedure previously instructed by the Removal Team.
Google replied on 1 June 2026 confirming:
- both URLs would be removed again
- the removal would apply across all European versions of Google Search
- the underlying content remains online and accessible from the publishers
This exchange is critical for the forensic interpretation that follows.
4. Forensic Interpretation (forensic style)
4.1 Not a Propagation Delay
In my initial message to Google, I reasonably considered the possibility that the reappearance reflected incomplete propagation of the original GDPR removal.
If that had been the case, Google would have instructed me to wait for full propagation.
If that had been the case, Google would have instructed me to wait for full propagation.
They did not.
Google did not mention propagation delays.
Google did not describe the behaviour as temporary.
Google did not ask me to wait.
Google did not describe the behaviour as temporary.
Google did not ask me to wait.
Instead, they immediately removed the URLs again.
This behaviour is incompatible with a propagation issue.
4.2 Google Treated the URLs as Newly Surfaced Entries
Google’s immediate action is consistent with how they respond when:
- a publisher generates new URLs
- a site migration creates new indexable endpoints
- topic hubs or category pages begin exposing previously removed content
- social media posts reintroduce the same snippet through a different URL
In such cases, Google handles the URLs as fresh violations, not as remnants of the original removal.
This is exactly what happened.
4.3 Evidence of a Re‑Indexing Event Triggered by ITV
My forensic comparison of the ITV 2026 source code shows:
- a full migration to a new Next.js infrastructure
- regenerated topic‑hub pages
- altered internal navigation
- a faulty canonical tag
- new URL patterns
- updated asset paths
- unchanged article content and metadata
When a publisher performs a CMS migration of this scale, search engines often detect:
- new endpoints
- new hub pages
- new internal linking structures
- new freshness signals
These can unintentionally trigger re‑indexing, even for content previously delisted under GDPR.
Google’s immediate removal strongly suggests that the URLs which resurfaced were newly generated or newly exposed as a result of ITV’s technical changes.
5. Forensic Style Conclusion
The reappearance of the URLs was not caused by incomplete propagation of Google’s original GDPR removal.
If that had been the case, Google would have instructed me to wait.
If that had been the case, Google would have instructed me to wait.
Instead, Google acted immediately, which is consistent with:
- a re‑indexing event
- triggered by ITV’s CMS migration
- producing new or newly exposed URLs
- pointing to the same unlawful and inaccurate content
- previously removed under GDPR
This constitutes forensic style evidence that the resurfacing was caused by ITV’s technical actions, not by any delay or failure in Google’s propagation process.
The ITV case demonstrates how a legacy article, left uncorrected and structurally unchanged, can continue to generate reputational harm even after GDPR delisting. The forensic comparison of the 2022 and 2026 source code, combined with the documented Google correspondence, provides a clear evidentiary basis for assessing:
- the persistence of unlawful data processing
- the absence of editorial rectification
- the ongoing dissemination of inaccurate and sensitive data
- the structural role of ITV’s metadata in maintaining visibility
- the need for direct action by the publisher, not only by search engines
This forensic style report forms part of the evidentiary archive published on The Record Speaks.
Consolidation Paragraph (Forensic Style)
Across the different components of my archive — The ITV Case and Google’s Technical Response, The Argus Case and Google’s Technical Response, ITV – Digital Evidence Analysis, and Sussex Express – Digital Evidence Analysis — a consistent forensic pattern becomes evident. In each case, legacy articles containing inaccurate judicial and health data were initially removed by Google under GDPR, only to resurface later through newly generated or technically regenerated URLs. Google’s behaviour was identical in both the ITV and The Argus cases: the reappearing URLs were not treated as remnants of incomplete propagation, but as newly surfaced entries, requiring immediate removal. This confirms that the resurfacing was triggered not by Google reversing its decision, but by publisher‑side technical actions, such as CMS migrations, topic‑hub rebuilds, canonical inconsistencies and metadata replication. My ITV – Digital Evidence Analysis and Sussex Express – Digital Evidence Analysis both demonstrate that the underlying articles remain unchanged, uncorrected and structurally intact, while the surrounding technical frameworks continue to emit fresh indexation signals. Taken together, these cases show that the persistence of harm arises from publishers repeatedly re‑exposing the same unlawful and inaccurate content through evolving infrastructures, thereby necessitating renewed GDPR enforcement each time.
