Posts by Someone Who Knows You

What decides this is not what you think it is

Something is up about you, and the person who posted it knows you. An ex-partner, a relative, someone you used to work with, a friend you fell out with badly. It names you, the people who matter can see it, and it is either untrue or true in the cruelest possible arrangement.

Here is the answer, and it is going to sound wrong. Whether it comes down depends on what the post breaks, not on how much it damages you and not on whether it is true. A platform keeps a list of written rules. A reviewer holds the post up against that list. If it crosses a line on the list, it goes. If it does not, it stays — regardless of what it has done to your job, your family, or your ability to sleep.

So there is a route here and it is real and it costs nothing. What there is not is a route that responds to harm. Understanding that on the first day saves months of writing letters that describe how bad this is to people who are not measuring that.

Why the rule is written that way, and what follows from it

Look across this whole subject and a pattern appears that explains almost everything.

Where there is a statute behind a category — sexual images shared without consent, imagery of children, copyright — every operator has a real form, published criteria, and staff who work through them. Where there is no statute, there is a feedback link, a general inbox, or nothing at all. That is the most reliable predictor of whether a request goes anywhere, and it has no relationship whatsoever to how badly the content is hurting the person it is about.

Which produces outcomes that feel arbitrary and are not. A cruel, false paragraph written by someone who knows exactly which detail will land can sit outside every policy. A clumsy post that happens to include your phone number is inside one. The second comes down and the first does not.

What follows is the whole method for this category:

• Stop arguing the damage and start finding the rule. “This has destroyed my life” is not a category. “This page publishes my home address” is.
• Read the post line by line rather than as a whole. One sentence in a long post can cross a line the rest of it never touches.
• File one thing at a time, against the policy it breaks. A report naming a policy is handled differently from one naming a feeling.
• Expect the decision to belong to somebody else. A reviewer applies a rule; usually there is no appeal and nobody to persuade.

What actually counts as a broken rule

The clearest published list belongs to the search engine rather than to any one platform, and it is worth knowing for two reasons: it shows the shape of what operators act on, and it is a route in its own right when the platform says no. The categories a search engine states it will remove from results:

• Contact details — a home address, a phone number, an email address.
• Government identification numbers, such as a Social Security number or a tax ID.
• Financial account numbers — bank accounts, card numbers.
• Images of identity documents, including a picture of a signature.
• Confidential medical records.
• Login credentials — usernames and passwords.

Doxxing is handled separately and carries a threshold. The policy covers a page containing:

“Your personal info along with explicit or implicit threats against you (or calls for others to harm or harass you)”

or

“A significant amount of aggregated personal info without a legitimate purpose”
— Google Search Help, “Remove your personal info from Google,” read August 15, 2026

Read the first half slowly, because this is where the ex-partner case usually fails. It requires a threat, or a call for other people to come after you. Hostile content that merely names you is not doxxing under that policy, however vicious it is. The second half turns on volume and on the absence of a legitimate purpose — a judgment somebody inside the company makes against criteria they do not publish.

And if what they posted is an intimate image, real or fabricated, stop reading here. That is a different category with far stronger rules and a deadline written into federal law.

Why “but it is a lie” does not open a door

This is the sentence people find hardest, so it should be said flatly rather than eased into. There is no policy category for untrue. There is none for unfair, embarrassing, disputed, or written specifically to hurt me. Content is not removed from search results for being negative, and the published route for content that violates no policy sends you back to the website:

“Google removes content from search results that violates our product and content policies. If there is content that you would like removed from search results but it doesn't violate our policies, you may have other options.”
— Google Search Help, “Remove content from search results outside of Google Search,” read August 15, 2026

Those other options begin with contacting the website owner, because a search engine does not operate the site and cannot delete anything from it.

Falsity does matter. It just does not matter to an operator. Whether something written about you is defamatory is a legal question with a legal answer, and I am not an attorney. What I can tell you is where the boundary sits: a platform reviewer does not decide what is true, and a court can. Those are two different systems, and a report to the first is not a step toward the second.

What to do today, before anything else

If the post is still up while you are reading this, do this part first. It is free, it takes about an hour, and it is what people most regret skipping.

1. Save copies, dated. Full-page captures showing the address, the account, the date and the whole text. Posts get edited. Accounts get deleted. What you can show later is what you captured now.
2. Write down exact addresses. Every route that exists asks for a page address, and several also ask for a screenshot showing where on the page the problem sits. A description of the problem is not a request anyone can act on.
3. Look for the copies before you act on the original. Screenshots travel and threads get quoted, and if the original disappears first the copies are harder to trace.
4. Do not reply in public. Whatever you write becomes part of what people find, and it keeps the thing alive.
5. Note who can actually see it. A post visible only inside a closed group is a different problem from one that surfaces when your name is searched, and the second has more routes than the first.

One thing worth knowing about preserving evidence: anyone can permanently archive a public page on demand. That is useful to you, and it is equally useful to the other side, who can preserve a page minutes before it comes down.

What a request that gets read looks like

The difference between a report that gets actioned and one that vanishes is usually not the merits. It is the form.

• One issue per report. Name the single policy the post breaks and point at the exact line that breaks it.
• Addresses, not descriptions. The exact page address for each item, plus a screenshot showing where on the page it appears.
• Nothing about the history between you. It does not help, and it invites a reviewer to file the whole thing as a personal dispute.
• Do not bundle categories. If a post carries your address and also calls you a criminal, report the address under the policy that covers addresses, on its own.
• Keep your own record. What was sent, when, to whom, and what came back. Not for the operator — for you, if this ever becomes something a lawyer handles.

Expect one of three answers from a search engine even where the request is a good one. The address stops appearing for every search; or it stops appearing only for searches of your name and keeps showing for other queries; or it is refused. That middle outcome is common and rarely mentioned by anyone selling this. For many private people, a name-query removal is exactly what they wanted. If your worry is that the thing is findable at all, it is not.

When they delete it themselves

The strongest outcome here is usually not an operator's decision at all. It is the person taking it down — because the heat went out of it, because somebody with authority over them required it, or because a lawyer wrote to them. That last route is not mine, and whether it is available to you is a question for an attorney.

Two things to know for the day after. A stale search result can linger after a page changes, and a free tool exists for asking a search engine to refresh one — but it only does something once the page has actually changed at the source. Filed against a live post it achieves nothing, which is why a service whose whole deliverable is filing those forms has not done removal work.

And a deleted page may already exist as an archived copy. The main public archive decides those requests at its own discretion, builds its request process around whether you controlled the site, and states its position plainly:

“This will initiate a review by our team. We do not make any guarantees beforehand about the outcome of a request.”
— Internet Archive Help Center, “How do I request to remove something from archive.org?” read August 15, 2026

Someone merely written about by another person does not fit that framing well.

The things that do not work

Four of them, all common, and each expensive in a different way.

• Mass reporting. Getting twenty friends to report the same post does not add weight to it. It is one post, measured once, against one rule.
• Responding, publicly or privately. A reply gives the post a second life, and it gives the person a reaction, which for some of them is the entire point.
• Paying somebody to get it removed. A reviewer applies a policy to content. If the content does not break the policy, no fee changes that answer, and nobody has a relationship that changes it either.
• Waiting to see whether it settles down. The one thing that reliably degrades with time is your evidence. Save first, decide afterward.

What I can honestly offer here

An assessment on this kind of post is a sorting exercise, and it comes down to one question asked line by line: is there anything in this that crosses a written rule? Contact details, an identity document, medical information, credentials, a threat, an aggregation of personal information serving no purpose. Where the answer is yes, the work is preparing each report properly, filing it in the form the operator asks for, keeping a dated record, and re-checking when copies surface.

Where the answer is no — and it often is no — the honest statement is that no removal route exists, and the question changes into what a search for your name returns instead. That is slower work with no promised outcome, and it belongs on a different page rather than being sold to you as a removal.

I will not tell you a post will come down. A reviewer decides that against a rule, and the rule was not written about you. What I will tell you, before you spend anything, is which of those two situations you are actually in — and that answer is usually available within a day.

Frequently Asked Questions

Published 2026-08-15