Purpose

Create a complete, minimal evidence set that lets a reviewer locate the material and understand the policy mapping without needlessly duplicating sensitive data.

Applicable policy and verification date

Google requires specific content URLs and uses screenshots to locate relevant content. Depending on the detailed-form branch, it can request Search-results URLs, search terms, identifying text, and supporting files. Verified 2026-10-17. (Policy FAQ; form)

Audience

Affected people, authorized representatives, and case coordinators preparing a submission.

Before you begin

Assign a neutral case identifier. Do not use a full ID number, address, or password as the case name or filename.

Prerequisites

  • Correct route selected using the decision tree.
  • Permission to handle the evidence.
  • A secure storage location with access limited to the people working on the request.

Required inputs and evidence checklist

  • Case identifier
  • Specific source URL for each page or image
  • Google Search result context and result URL where applicable
  • Information category
  • Screenshot showing enough context to locate the material
  • Date and timezone observed
  • Affected-person ownership or representative authorization
  • Policy criterion mapped to observed facts
  • Submission date and confirmation/reference identifier
  • Current status and next action
  • Official source references used for the mapping

Download/copy the Markdown evidence case log.

Procedure

  1. Open the result and then the source page. Record both separately.
  2. Copy the specific page URL. If reporting an image, follow Google’s URL instructions to capture the appropriate image or Search-result URL.
  3. Record the information category without reproducing the sensitive value in the case log. Use a redacted notation such as phone ending 42.
  4. Capture a screenshot that includes the relevant content and enough page context to identify its location. Crop or redact unrelated personal data.
  5. For doxxing, preserve only the relevant threat/call or list the aggregated categories; distinguish quotation from analysis.
  6. Record the policy source and the exact criterion being mapped.
  7. Record authority: affected person, parent/guardian, lawyer, or another authorized role. Store proof only if necessary and requested.
  8. Before submission, verify that every URL opens and that each screenshot corresponds to it.
  9. After submission, record the date, channel, request identifier, status, and next action.

Expected result

A reviewer-ready package with enough context to locate and assess the submitted content, while the internal record contains no unnecessary full identifiers.

Privacy-safe storage and redaction

Limit access, avoid public shared links, encrypt devices or storage where available, and set a deletion review date. Redact unrelated people and unused identifier digits. Never store an exposed password in the evidence log; change it and use a category note. Preserve an unedited original only when necessary for the official submission, then apply the retention policy.

Troubleshooting and exceptions

  • A homepage is not a substitute for the exact content URL.
  • A Search-result URL is not always the source URL; label each.
  • Do not alter the evidence so heavily that the relevant content cannot be located.
  • If the page becomes inaccessible, record the response and use Troubleshooting.

Official references

Policy review record

  • Last policy review: 2026-10-17
  • Documentation version: 1.0.0