Orosz argues that Google deindexed his 2022 Pollen post-mortem based on a boilerplate legal-removals complaint from the founders' lawyers, with no judge, no hearing, and no finding that the article is actually defamatory. He frames this as a structural failure: the complainant pays nothing, the publisher loses discoverability immediately, and a well-sourced piece built on Companies House filings and the administrator's report effectively disappears from Search.
By submitting the story with a title that names both founders (Negus-Fancey and Wright) and frames Google as an active assistant rather than a neutral party, the submitter signals agreement that the platform's process is the real story. The 764-point score within hours reflects broad community endorsement of that framing.
Orosz points out that the takedown came four years after publication, from lawyers acting for Pollen's CEO Callum Negus-Fancey and CTO Callum Wright — executives who oversaw a ~$150M-raised company collapsing within weeks of its last round, owing wages, supplier invoices, and customer refunds. He treats this as part of a hardening pattern where founders use UK/EU legal regimes to erase post-mortems that name them, even when the underlying reporting is sourced from public filings.
Orosz notes the article is still live on blog.pragmaticengineer.com; only the Google Search path to it has been severed, with Lumen Database confirming removal across multiple jurisdictions. His implicit argument is that in 2026, an article you cannot find via Google is functionally suppressed, even if technically still hosted — making search delisting a more effective censorship tool than a court order would be.
Gergely Orosz — author of *The Pragmatic Engineer*, the most-read paid newsletter in software engineering — published a post this week titled *"Pollen tried to remove my article about Callum Negus-Fancey, and Google is assisting to it."* It hit 764 on Hacker News in a few hours. The story is narrow on facts and wide on implications.
In 2022, Orosz wrote a long post-mortem on Pollen, a UK-based events startup that raised roughly $150M from Backed VC, Sequoia, Kindred, Stripes, and Northzone, then collapsed within weeks of its last round. CEO Callum Negus-Fancey and CTO Callum Wright laid off ~200 staff and entered administration owing wages, supplier invoices, and customer refunds. Orosz's piece — built from Companies House filings, the administrator's report, and named former employees — became one of the canonical references on the collapse.
Four years later, lawyers acting for the Pollen founders filed a defamation-flavored takedown via Google's Legal Removals tool, and Google deindexed the URL from Search results without ever ruling on whether the post is actually defamatory. Orosz says he was given a boilerplate notice, a short window to respond, and no judge, no hearing, no finding of fact. The Lumen Database entry confirms the URL was removed from `google.com` results in multiple jurisdictions. The post is still live on `blog.pragmaticengineer.com` — you just can't find it through the front door anymore.
There is a specific shape of internet abuse that has quietly hardened into a workflow over the last five years, and this story is a clean specimen. The mechanism is not lawsuits — it's the *threat* of lawsuits, routed through a platform abuse form that costs the complainant nothing and the publisher everything. File a UK or EU legal-grounds complaint citing defamation or GDPR, attach a solicitor's letterhead, and Google's first move is almost always to delist while it "reviews." The review can take months. During those months, the journalism is functionally gone for anyone who searches the founder's name.
This is not a hypothetical asymmetry. Orosz is one of the highest-profile independent writers in tech and he says it took non-trivial effort to even understand which URL had been delisted and why. A staff reporter at an outlet with a media-law team would have a chance. A junior reporter at a regional paper, a former employee blogging about a bad boss, a Glassdoor-adjacent thread — those don't have a chance. The system is calibrated for the publisher to lose by default.
The Pollen specifics matter here. The administrator's report is a public document. Companies House filings are public documents. Multiple former employees went on record about unpaid wages. If a piece this thoroughly sourced can be removed from Search via a single form, the standard of evidence required to suppress critical reporting on a founder is effectively zero. Compare this to the *Streisand effect* of the old web — where suing a blogger guaranteed a thousand mirrors — and you can see why founder-side reputation firms have shifted entirely to the legal-removal channel. It's quieter, cheaper, and the publisher rarely has the appetite for a counter-campaign.
There's also a Google-specific failure here. The Removals tool was built to handle clear cases: child sexual abuse material, doxxing, leaked financial data, court-ordered removals. Over the last three years it has been repurposed into a low-friction reputation laundering API, and there is no public data on the false-positive rate because Google does not publish it. The Lumen Database catches a slice of legal complaints, but Lumen depends on Google voluntarily forwarding the notice — a pipeline that has narrowed over time. The Transparency Report aggregates removals into a number; it does not adjudicate them.
Community reaction on HN clustered around three points: (1) this is not new, but Orosz's audience makes it visible; (2) the EU's Right to be Forgotten framework, designed for genuine privacy harms, is now a routine commercial-reputation tool; (3) every independent technical writer is now a takedown away from invisibility, and almost none have a plan for it.
If you write anything that ranks for a real person's name — a postmortem, a why-we-left, a vendor review, a security disclosure — you are now in scope for this workflow. Three concrete moves:
Treat your blog like infrastructure that can be deplatformed at the search layer, not the hosting layer. A canonical URL on your own domain is still less fragile than Medium or Substack, but search delisting routes around all of that. Maintain a `/index` or `/sitemap` page that is itself well-linked and crawlable, so the post survives as a clickthrough even when the keyword route is closed. Cross-publish to at least one archive (`archive.org`, `archive.ph`) at publication time, not after the takedown lands.
Write with a paper trail. Orosz's post survived because it cited Companies House filing numbers, the administrator's report, and named on-record sources — which is precisely why the suppression had to go through Search rather than the courts. If you are writing about a person or company that might push back, footnote every factual claim with a primary-source link. Make the cost of a real defamation suit visibly high. This won't stop the takedown form, but it shapes the appeal.
Know the appeal path before you need it. Google's Legal Removals appeal is a written process with a hard deadline. The Lumen Database submission is independent of Google and creates a public record. The EFF and the Reporters Committee for Freedom of the Press both maintain intake forms for journalists facing takedowns. If you've never read these, read them now — before you are the URL in question.
For engineering leaders specifically: the Pollen story itself is a case study in why "raised $150M" is not a hiring signal. The same instinct that builds a company on growth-stage capital without unit economics also builds a legal team that, when the company fails, prioritizes founder reputation over creditor recovery. If you are evaluating a startup employer in 2026, the founder's Google results being suspiciously clean is now a signal, not the absence of one.
The fix here is not a better Google form. It's a regulatory requirement that platforms publish per-URL delisting decisions with the legal basis attached, the way Lumen *used* to capture them by default — and a meaningful penalty for fraudulent takedown claims, which currently carry none. Until then, the equilibrium holds: founders who fail loudly get to choose, ex post, whether anyone remembers.
DMCA notices are meant to be submitted "under penalty of perjury", and false notices could in theory result in civil action being taken against those who send them. In practice, neither of these occur even if the sender is a real person, like a record company lawyer lending their name to c
I would have never heard about Negus-Fancey and Wright, but now I have! Streisand at its finest.
Just as there are SEO firms that help companies ascend the rankings, there are "reputation management" firms that erase bad news by publishing new articles & by pushing takedown requests on articles they don't like. As with SEO, Google appears to tacitly encourage this.It seems ob
This is an extremely common technique against investigative reporting, in particular because certain social media / blogging platforms allow backdating posts [1]. So people just copy your post, claim DMCA, and then take it down quickly after.1) https://news.ycombinator.com/item?i
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Ah, yes, you know someone's desperate when you see a bogus DMCA claim like this. Not the first time this happened and definitely won't be the last.This also demonstrates why it is bad for a law to mandate private entities to do moderation, in this case taking down copyright infringement ma