Google Removal Center / Mugshot Removal Assessment
Track a mugshot across separate locations
Webpage
Record each publisher and repost URL.
Image
Record the photo URL where available.
Search
Verify web and image results separately.
Each route requires its own evidence. Publishers and platforms decide requests.
An arrest photo can appear on a booking website, a social post, and Google Images at the same time. Start with a free review that distinguishes the original photo page from its search results and reposts.
When this assessment is useful
Mugshot publisher pages, outdated booking information, incorrect identity matches, and arrest photos appearing in Google Images.
What removal can—and cannot—change
An arrest is not a conviction. Removing a private mugshot page does not erase an official arrest record, and no single request covers every repost.
What to include
- The webpage URL and, where available, the image URL.
- The search terms showing the photo and any duplicate pages you found.
- Any publisher payment demand or factual error relevant to the request.
Send public links and a brief explanation. Leave out passwords, financial details, and identity documents.
How the review works
- Identify the source page, photo URL, and independent republications.
- Review publisher options and whether Google’s exploitative-removal-practices policy may apply.
- Recheck the source, web search, and image search separately after any action.
Your assessment and any next steps
The initial assessment is free and carries no obligation. It identifies the URLs to review, possible routes, key limitations, and any additional information needed. If paid help is appropriate, request a written scope, price, payment schedule, and definition of completion before proceeding. No universal success rate or deadline applies to every publisher.
Does paying a removal company guarantee Google will delete the photo?
No. Google makes its own policy decisions. Ask whether the provider is offering source deletion, search removal, or both, and get the scope and payment terms in writing.
Try it yourself or request help
Google’s official guidance · Read our detailed guide · Check your possible route
Build a complete mugshot URL inventory
Record the booking page, the image URL where available, and any independently published copies. Note which queries expose the image and whether the search result opens the same source you expected. Keep namesakes separate from your own records to avoid requesting changes to the wrong person’s information.
Do not assume that removing one publisher page also removes a social-media post, cached search snippet, or copied image. List each intended outcome in the scope: source page, image file, web result, and image-search result.
When a publisher asks for payment
Preserve the request, the amount demanded, the URL, and any claim about removal. Google has a policy addressing exploitative removal practices; review its current criteria before submitting. A payment demand should be documented rather than treated as automatic proof of eligibility.
Do not send money based only on an unsolicited promise. Verify who controls the website, what the proposed action covers, and whether the agreement concerns the original source or a search result.
How to verify a mugshot removal
Visit the original URL and check the image separately. Repeat the relevant web and image searches and record the date. If search still shows information that has been removed from the source, consider the appropriate refresh route through the Google Removal Center.
A private publisher’s action does not erase an arrest record or change a case disposition. For separately published legal summaries, use the court-record assessment. Request monitoring if you need agreed checks for republications.
Reviewed and expanded October 24, 2026 · Independent of Google.