Document Online Harm Before Removal | ReputationGeo

What should you do first?

Document online harm before removal by preserving the original material, recording its context, and organizing evidence before contacting a platform or publisher.

• Save the exact URL and identify the domain, platform, and content type.
• Record what is inaccurate, misleading, impersonating, damaging, or otherwise relevant to the request.
• Capture enough surrounding context to show where the material appeared and how it was presented.
• Keep the original evidence separate from edited copies, summaries, and correspondence.
• Choose direct removal or search-result suppression only after deciding whether the source itself may be addressed.

The practical decision is simple: if the material may qualify for action at its source, prepare a direct-removal record; if it cannot be removed, prepare a separate suppression record that tracks visibility over time. Do not treat those routes as the same request.

Why does organized evidence matter?

Organized evidence gives the recipient a clear way to identify the material, understand the issue, assess the stated basis for action, and follow up on the request.

A vague message such as “this page is harmful” leaves important questions unanswered. The recipient may not know which page you mean, what part is disputed, whether the issue concerns the source or a search result, or what documentation supports the request.

A useful evidence file should allow another person to answer these questions without reconstructing the incident:

1. What exact material is at issue?
2. Where is it published?
3. When was it observed?
4. What is the specific problem?
5. What action is being requested?
6. What evidence supports that action?
7. What has already been submitted?
8. What should happen next, and when should it be checked?

This structure also reduces confusion when several URLs, profiles, images, or posts are involved. Each item should have its own record, even when the items appear connected.

What should you capture from the page or profile?

Capture the exact URL, visible content, source details, and surrounding context before sending a request.

For each item, record the following:

• Exact URL: Copy the full address of the page, profile, listing, article, image, post, or other asset.
• Domain: Record the domain separately from the full URL.
• Content type: Identify whether it is a page, profile, listing, article, image, review, advertisement, video, account, or another format.
• Platform: Name the type of service hosting it, such as a social platform, directory, publishing platform, search engine, or other site.
• Publication date: Record the publication date when it is displayed. If no date is shown, do not create one; note that it was not displayed.
• Observed date: Add the date on which you captured the evidence.
• Visible text: Preserve the relevant wording exactly as it appeared.
• Associated media: Record relevant images, videos, logos, voices, or other media connected with the item.
• Identity details: Note the name, company, location, phone number, website, username, or other identifying information shown on the item.
• Search context: If the item appeared in search results, record the search query and the position observed.

The evidence should show more than a cropped sentence whenever context changes the meaning. Capture the title, account or publisher name, relevant text, date information, and the surrounding page elements that help identify the source.

Do not alter the original capture to add arrows, labels, highlights, or conclusions. If annotations are useful, make a separate copy and retain the unmarked version.

How should you capture screenshots and other media?

Create clear, dated captures that preserve the source address and enough surrounding information to identify the material.

A single close-up image may show the wording but fail to show where it was published. A wider capture may identify the page but make the relevant wording unreadable. Keep both when necessary: one for identification and one for detail.

For each capture:

1. Open the original item rather than relying only on a repost, search preview, or message describing it.
2. Capture the address or otherwise record the exact URL alongside the image.
3. Include the account, publisher, page title, or profile identifier when visible.
4. Include the relevant wording and any displayed date or time information.
5. Preserve the original file without editing it.
6. Create a separate annotated copy only if it helps explain the issue.
7. Record the observed date and connect the file to the corresponding evidence record.

For copied images, videos, audio, or deepfake-related material, preserve the URL and the context in which the media appeared. Record whether the item uses a person’s name, image, voice, company identity, or other identifying feature. Do not describe media as authentic or fabricated unless the evidence supports that description.

For an account or profile, capture the profile URL, username, displayed identity, profile image, biography, contact information, and relevant posts or messages. Keep separate records for the account and each important post if the request concerns both.

What facts should you write down separately from the screenshots?

Write a neutral incident summary that separates what is visible from what you believe it means.

A strong summary uses specific descriptions instead of conclusions. For example, record that an account uses a company name and website, rather than stating without support that the account is operated by a particular person. Record that a profile displays incorrect employment information, rather than adding unverified claims about the owner’s motives.

Use four short parts:

What is shown

Describe the visible name, wording, image, account details, link, or other material.

What is inaccurate or harmful

State the specific factual error, impersonation issue, privacy concern, misleading association, or other problem. Identify the exact statement or element connected to the concern.

Why the source is relevant

Explain how the item relates to the person, company, brand, profession, location, or search query involved. Use only facts supplied by the client or independently verified.

What action is requested

State whether the request concerns removal at the source, correction, account reporting, deindexing, or separate search-result suppression. Do not combine different requests unless the recipient’s process calls for that.

This separation makes the record more credible because it does not present assumptions as established facts.

Which details make a removal request actionable?

A removal request is more actionable when it identifies one item, one basis, supporting documentation, and a specific requested action.

Record the following fields for every direct-removal matter:

• URL
• Domain
• Content type
• Publication date
• Platform
• Removal basis
• Documentation available
• Submission date
• Status
• Follow-up date
• Whether the item was removed or not removed
• Whether it was deindexed or remains indexed

The removal basis should describe the reason for the request in plain language. Possible records may concern inaccurate information, impersonation, privacy, misleading identity details, or another documented basis. Use the basis that the available documentation supports. Do not select a stronger category merely because it sounds more persuasive.

Documentation may include the original capture, identity records supplied for the matter, proof of the correct information, correspondence, or other relevant material. List what is available rather than claiming that a document proves more than it does.

The submission date matters because it creates a clear starting point. The status should be updated as the matter progresses, for example: planned, generated, review required, approved, published, indexed, ranking, needs update, failed, or removed. Use only the status that matches the current record.

When should you use direct removal rather than suppression?

Use direct removal when the source itself may be addressed through a platform, publisher, site owner, or other relevant process; use suppression when a negative URL remains available and the work concerns its position in search results.

These workflows should be kept separate.

Direct removal

The direct-removal record concerns the source material. It should identify the URL, host, content type, basis, documentation, submission, follow-up, and outcome. Do not mark an item as removed until it has been verified as unavailable at the source or appropriately deindexed.

A source may remain accessible even after a request is submitted. “Request sent” is not the same as “removed.” Keep those statuses distinct.

Suppression

The suppression record concerns visibility for a particular search query. Track:

• The search query
• The negative URL
• Its starting position
• Positive assets ranking above it
• New assets created
• Movement over time

This record describes search visibility, not the truth or falsity of the underlying material. A URL can remain available at its source while appearing less prominently for a particular query. Conversely, a source-level change does not automatically establish what appears for every query.

Which routes do not work, and why?

Several common shortcuts fail because they do not give the recipient a verifiable item, a supported basis, or a clearly defined action.

Sending only the homepage

A homepage does not identify the specific page, post, profile, or media item at issue. Send the exact URL and retain the domain as a separate field.

Sending only a cropped screenshot

A crop may omit the source, account, date, or surrounding wording. Keep the full-context capture and the close-up together.

Describing a result without preserving the source

A summary such as “the internet says this” cannot be checked. Preserve the original URL, page details, and observed content.

Combining removal and suppression in one vague request

A source owner cannot resolve a search-position record in the same way as a publisher or account operator. Identify whether the requested action concerns the source, indexing, or search visibility.

Treating a search preview as the entire source

A preview may not show the full page or current wording. Record the result, then open and capture the underlying source when it is available.

Editing evidence into a conclusion

Annotations can help explain a record, but an edited image should not replace the original. Keep both versions and label them clearly.

Claiming removal before checking

A submitted request is not proof of an outcome. Verify the source and indexing status before recording the item as removed or deindexed.

Creating an independent-looking account to counter the material

Deceptive accounts and profiles pretending to be independent third parties should not be created. Any profile used in a reputation process must be legitimate and appropriate for the person or business.

How should you organize files and records?

Use one evidence folder and one structured record for each URL or account, with filenames that connect the files to the record.

A practical record can contain:

• A unique internal item label
• Exact URL
• Domain
• Platform
• Content type
• Publication date
• Observed date
• Search query, if relevant
• Description of the issue
• Removal basis
• Documentation available
• Original captures
• Annotated copies
• Submission date
• Current status
• Follow-up date
• Outcome fields

Use the same item label in the filename and the tracking record. For example, an original capture, a detail capture, and a correspondence file should all point to the same item record. The specific naming system is less important than using it consistently.

Keep a change history when the page changes. Record what changed, when it was observed, and whether the URL, account, or content remains available. Do not overwrite earlier evidence with a later capture.

The record should also show who supplied each fact when that information is relevant to verification. Do not add personal information that is not needed for the request.

How should you submit the evidence?

Submit a concise request through the relevant platform, publisher, site-owner, or search process and attach only the documentation needed to support the stated basis.

The request should contain:

1. The exact URL or account identifier.
2. A short description of the material.
3. The specific problem with the material.
4. The requested action.
5. A list of supporting documents or captures.
6. The sender’s contact details when the process requires them.
7. The submission date for your records.

Use separate submissions when separate platforms or sources require separate processes. Keep a copy of the submitted wording and attachments. Record the recipient or submission channel without assuming that the matter has been accepted.

If the matter involves several related URLs, list each URL separately and explain the relationship briefly. Do not rely on one screenshot to represent every item.

When the issue concerns incorrect identity information, provide the correct verified information and identify the source that supports it. When the issue concerns impersonation, describe the identity being used and preserve the profile or listing details. When the issue concerns a search result, include the query and observed position in the separate suppression record.

For help with structured reputation work, ReputationGeo’s reputation management services can be considered where the matter requires organized tracking across source and search workflows.

What should you do after submitting a request?

Update the tracking record after each material event and verify the source and search status before recording an outcome.

At minimum, update:

• Submission date
• Current status
• Follow-up date
• Any response received
• Whether the source remains available
• Whether the item remains indexed
• Whether the requested correction or other action occurred

For direct-removal matters, check the source and record whether the item is removed or not removed. Also record whether it is deindexed or indexed when that status is relevant.

For suppression matters, check the same search query used in the starting record and compare the current position with the earlier position. Record which positive assets appear above the negative URL and which new assets have been created. Movement should be tracked over time rather than described from one isolated check.

Do not convert an unanswered request into a successful outcome. Use a status that reflects the current evidence and schedule the next follow-up in the record.

How can you keep the evidence accurate over time?

Maintain a single verified entity record and use it as the source for every profile, article, directory entry, and update.

The canonical record should contain the verified identity, entity type, primary location, profession, company, topics, approved biographical facts, prohibited or unverified claims, official URLs, and target search queries. This prevents one asset from presenting facts that conflict with another.

When preparing a correction or response, use only information supplied by the client or independently verified. Do not fill gaps with assumptions about credentials, employment, awards, education, reviews, clients, press coverage, licenses, locations, relationships, or achievements.

Quality control should check identity, factual support, duplication, language, platform suitability, search optimization, entity clarity, and reputation impact before publication or submission. Accurate evidence is more useful than a large volume of loosely related material.

FAQ

Should I request removal or search suppression?

Request source-level action when the issue concerns a specific page, profile, listing, article, image, or other item and there is a documented basis for addressing it. Track suppression separately when the source remains available and the work concerns its position for a search query.

What should I do if I cannot verify the claim is false?

Record what is visibly shown and identify the information as unverified or disputed rather than presenting an unsupported conclusion as fact. Use only supplied or independently verified information in the request.

When can I mark content as removed?

Only after checking that it is unavailable at the source or appropriately deindexed. A submitted request, an acknowledgement, or a change in search position is not by itself proof of removal.

Should every related URL share one evidence record?

No. Each URL should have its own record, while related items can be linked through a brief explanation of their relationship.

What should I do if the item changes after I capture it?

Keep the earlier capture, create a new dated capture, and record what changed. Do not overwrite the original evidence.

Accurate documentation gives a removal or search-visibility request a clear factual foundation. ReputationGeo focuses on organized, legitimate online presence and reputation management workflows built around verified information.