Why takedown notices fail quietly, and what a notice has to carry

A takedown notice is a claim: this page carries material that belongs to someone else and should not be in the results under their name. The person reading that claim did not write it, does not know the brand, and is processing a queue. Whether the page comes down depends far less on how strongly the claim is put than on whether it can be checked without effort.

The failure nobody sees

The common picture of a failed notice is a refusal: a reply that says the request was reviewed and declined. That happens, and it is the better outcome, because a refusal tells you what was missing.

The usual outcome is nothing. The form is submitted, an automatic acknowledgement arrives, and the page stays where it was. No reason is given because no decision was made; the notice went into the queue and came out the other side unactioned. From the outside this looks identical to a notice still being processed, and weeks pass before anyone concludes it is not.

This is why the failure is quiet, and why it repeats. The next notice is written the same way as the last one, because nothing said the last one was wrong.

What the reader has in front of them

Put yourself at the other desk. The notice names a URL and says the page infringes. To act on it, the reader has to open the page, work out which part of it is the complainant's, confirm the page is still up, and satisfy themselves that the complaint is not mistaken or malicious. Every one of those steps is work, and the reader has a queue.

A notice that leaves all of that work to the reader competes against notices that do not. It loses, not on merit, but on cost.

A claim that takes work to verify is the one that gets refused — or, more often, the one that gets left.

The four things a notice has to carry

What turns a claim into something the reader can act on is a record that answers the questions before they are asked.

• The page as it appeared. A screenshot taken at the time the page was found, not a description of it. Pages change; a description of a page that has since been edited is an argument, a capture is a fact.
• The passages that match. The exact text on the page that corresponds to the complainant's material, quoted so the two can be compared side by side. This is the part most notices omit, and the part the reader needs most: it turns "this page infringes" into "this paragraph is that paragraph".
• The query and the market. Which search produced the page, in which country, in which language, on which device. Without this the reader cannot reproduce the result, and a result that cannot be reproduced is an opinion.
• The time. When the capture was made, so that the record is demonstrably older than any change to the page.

None of these is about tone. Politeness and legal vocabulary make no measurable difference. Reproducibility does.

Why the order matters

Notices are usually written after the fact: the page is noticed, someone drafts a complaint, and then, if anyone thinks of it, a screenshot is taken. By then the page may already differ from what was seen, and the screenshot documents the wrong thing.

The order has to be reversed. The record is made the moment the page is found, before anyone decides what to do about it. The notice is written from the record, not the other way round. A page that is edited, moved or taken down in the meantime cannot be captured afterwards, and an uncaptured page is one you can no longer prove existed.

The page that shows the reader nothing

There is a second reason a well-formed notice can fail, and it is worth naming because it looks like a mistake on the complainant's side. Some pages show one thing to the search crawler and another to a person who opens the link. The listing promises the material; the page the reader sees contains nothing of the sort. The notice is closed as mistaken.

The only defence is to record both versions: the page as the crawler sees it and the page as a visitor sees it, and to put the discrepancy itself into the notice. A reader who is shown the two side by side understands what happened. A reader who is shown only the visitor's version does not.

What follows the notice

Removal is the host's decision, and a notice, however complete, does not force it. What a complete notice does is get read, and a notice that is read is usually answered.

After that the work is not over. A page taken down under one address has a way of returning under another, in the same market, for the same query. The search that found it has to keep running, so that the return is found as quickly as the original was. Filing is not the outcome; removal is, and removal is something you check, not something you assume.