# Remove Images of a Minor From Google Search

Google removes images of people under 18 from Search on request. Who can file, what qualifies, why requests fail, and host, platform and legal routes.

---


Yes. Google's policy lets a person under 18, or a parent or other representative acting for them, ask for non-explicit images of that person to be removed from Google Search. If the request qualifies, the images stop appearing in Google Image Search and as thumbnails in other Search features, but they stay on the website that hosts them.

That second half is where most families go wrong. The policy is narrow, it works on image URLs rather than whole pages, it carries an exception for newsworthy images, and it does nothing to Bing, to social platforms or to the original site. This guide explains what the policy covers, who can file, why requests are refused, and which other routes (the host, the platform, the law) fill the gaps. It describes the policy as the help page read for this guide states it, so check the page before you file.

Nothing here is legal advice. If the image is nude or sexual, skip to the section on explicit material: that is a different route.

<div class="box"><b>The short version</b>
<ul><li>Google's minors policy removes non-explicit images of someone under 18 from Search results at their request, or at the request of a parent or representative.</li><li>It only accepts image URLs, not pages that mix text and images, and it excludes images from accounts or pages the requester manages.</li><li>It removes the result, never the file: the host, the platform or a court order is what removes the image itself.</li><li>Newsworthy images and matters of public interest can be refused, and the policy page describes no timeline or appeal.</li><li>Nude or sexual images of a minor follow separate routes: Google's child sexual abuse imagery report and the NCMEC Take It Down service.</li></ul></div>

The three facts below decide most cases before any form is opened.

<figure class="keyfacts">
<div class="keyfacts-grid">
<div><b>Under 18</b><span>the person pictured must be under 18, or have died before turning 18</span></div>
<div><b>Image URLs only</b><span>pages that mix text and images are not eligible under this policy</span></div>
<div><b>Search only</b><span>Google cannot remove the image from the site that hosts it</span></div>
</div>
<p class="fig-src">Google Search Help, "Remove non-explicit images of minors from Google search results", as read for this guide.</p>
</figure>

## Which images does Google's minors policy remove from search?

It removes non-explicit images of a person under 18, from Image Search and from the thumbnails Google shows in other Search features. Google's announcement, published on October 27, 2021 by its Search liaison, introduced the policy; the help page is the document that now governs requests.

The help page sets four conditions, and a request has to meet all of them:

- The submission contains only image URLs. The page states that webpages with both text and images are not eligible under this policy.
- The image shows a person under 18, or someone who died before turning 18.
- The requester is the person in the image (a parent or relative can act as their representative).
- The image does not come from a social media account or a web page that the requester manages.

Two limits sit on top. Google says it may make an exception when an image is newsworthy or a matter of public interest. And the policy covers non-explicit images only: nude or sexual images of someone under 18 go through a separate reporting process, covered below.

The practical reading: the policy suits a photo someone else published, with no news value, reachable at its own image address. A local news article with the child's photo inside it does not fit, because the URL is a page, not an image.

## Who can file: the minor, a parent, or an adult looking back

A person under 18 can file for themselves, and a parent, relative or other representative can file for them. The help page says that if you are the subject of the content, you or a representative such as a parent or relative can start a request.

Two edge cases come up constantly, and the help page does not settle either.

### An adult asking about photos taken in childhood

The eligibility line reads in the present tense: the image depicts an individual who is under 18, or who died before reaching 18. The page does not say what happens when the person has since turned 18. We read the wording as aimed at people who are minors when they file, and we would not rely on it for an adult. An adult has the other routes in this guide: the host, the platform, and a data protection request where the law applies.

### A parent whose own account or site hosts the photo

The page excludes images from a social media account or a web page that "you" manage. It does not explain how that applies when a parent files for a child and the parent runs the page. Do not test this. If you control the page, you control the fix: delete or replace the image, then ask Google to refresh the result so the old thumbnail drops out. That is faster and certain.

<aside class="callout">
<span class="callout-label">Rule</span>
<h4>If you can delete the image yourself, do that first</h4>
<p>Google's policy excludes pages and accounts the requester manages. Remove the image at the source, then use Google's refresh outdated content tool so Search stops showing the old version.</p>
</aside>

## What a request needs, and what happens after you submit it

You submit through Google's removal request form with the image URLs, the URLs of the search results pages where the images appear, and the search terms that surface them. Google's announcement lists those three items, and the help page adds that screenshots help Google find the content. The page says to take screenshots on the same device you use to submit, and that you may edit them so only the face is visible.

Google's announcement says its teams review the request, may ask for more information to verify it, and notify the requester once an image is taken down. Neither the announcement nor the help page, as read for this guide, states a review timeline, and neither describes an appeal or a resubmission process. In our files a decision usually takes days to a few weeks, which is experience, not a promise.

<figure class="fig">
<figcaption><b>Filing the request, in order</b></figcaption>
<ol class="fig-steps">
<li><b>Check the image is a standalone image URL</b>Open the result and confirm you can copy the image address itself. If the only address is a page that also carries text, this policy will not accept it.</li>
<li><b>Check who controls the page</b>If the image sits on an account or page you manage, delete it there and request a refresh instead.</li>
<li><b>Gather URLs, search terms and screenshots</b>Record the image address, the results page address and the query that finds it, on the device you will file from.</li>
<li><b>Submit the removal request form</b>Choose the removal option that matches the images and attach the evidence. Give a contact address you check daily.</li>
<li><b>Answer any follow-up</b>Google may ask for more information. Respond the same day, because a slow reply stalls the file.</li>
<li><b>Recheck the results and log the outcome</b>Search the same terms in a private window, note the date, and keep Google's reply for any later request.</li>
</ol>
</figure>

## Why requests fail and what to change

Most refusals trace to a small set of causes, and each one has a different fix. The table maps what we see to the policy conditions above.

<div class="tablewrap"><table><thead><tr><th>Cause</th><th>Policy condition</th><th>What to do</th><th>Likelihood</th></tr></thead><tbody>
<tr><td><strong>URL is a full page with text</strong></td><td>Image URLs only</td><td>Find the direct image address, or go to the host</td><td>Common</td></tr>
<tr><td><strong>Image is on a page or account you run</strong></td><td>Not from a page you manage</td><td>Delete at source, then request a refresh</td><td>Common</td></tr>
<tr><td><strong>Image appears in a news report</strong></td><td>Newsworthy exception</td><td>Ask the publisher, or use a legal route</td><td>Fairly common</td></tr>
<tr><td><strong>Person is now an adult</strong></td><td>Under 18 condition</td><td>Use host, platform or data protection routes</td><td>Possible</td></tr>
<tr><td><strong>Image is nude or sexual</strong></td><td>Non-explicit only</td><td>Use the explicit-material routes below</td><td>Wrong form</td></tr>
</tbody></table></div>

A refusal is not always the end, but the policy pages read for this guide do not describe a resubmission process, so follow whatever Google's reply says. File again only after changing something real, such as a direct image URL or a clearer description of who is pictured.

## Removing the image from the web: the host, then the platform

Google's removal ends at its own results. The help page says Google can take images out of its results but cannot remove them from the source website, and tells requesters to contact the site owner. A second Google page, content removal options outside Google Search, says the same and points social media content to that platform's own help center.

This is why the host is the first stop in most cases, not the last. When the file is deleted at the source, it leaves every search engine, not just Google.

### The site owner

Write to the owner or the site's contact route, name the image address, say a child is pictured, and ask for deletion or replacement. In our experience, schools, clubs and photographers often act once they understand the subject is a minor. If the owner will not answer, the hosting provider's abuse route is the next step, and a WHOIS lookup of the domain usually shows who that is.

### The platform

On a social platform, use that platform's own report tool and look for its rules on images of minors. We do not summarize individual platform rules here: they change often and were not read for this guide, so read the platform's current help page before filing. Platform reports also work when the image is not in Google at all.

### Other search engines

Google's removal does not carry to other search engines. Each runs its own request process, so check Bing and any other engine that shows the image.

<aside class="callout">
<span class="callout-label">Limit</span>
<h4>A Google removal is not a deletion</h4>
<ul><li>The image stays on the host and can be found through direct links.</li><li>Other search engines keep showing it until they act or the file is deleted.</li><li>A re-upload to a new address is a new URL and needs a new request.</li></ul>
</aside>

## When the image is nude, sexual or being used to threaten a minor

Do not use the non-explicit form. Nude or sexual imagery of a person under 18 follows a separate path, and the first rule is not to copy or screenshot it.

Google's help pages say that anyone can report nude or sexual pictures of people under 18, and warn against sharing child sexual abuse imagery, even as a screenshot. Google's child sexual abuse imagery page says Google will consider removal when a URL shows a person under 18 in nude or sexual conduct, or offers or advertises such material. If Google confirms apparent child sexual abuse material, it removes the content from Search and makes a report to NCMEC's CyberTipline. The same page says anonymous reports are possible: log out of your Google account and leave the optional contact fields blank, with the trade-off that Google cannot send status updates. It also says that if a child is in immediate danger you should contact the police.

For images that exist on someone's device and may be shared, the National Center for Missing and Exploited Children runs Take It Down. It helps remove or stop the online sharing of nude, partially nude or sexually explicit images or videos taken of a person under 18, and it works through hashes, so the file never leaves your device. It only reaches participating platforms, may not be able to remove content already posted, and applies when the image was taken under 18. For an image taken at 18 or older, the Take It Down page points to StopNCII.

If a minor is being threatened with publication, our intimate and leaked content service at <a href="/leak-removal">leak removal</a> handles the search side, but the first calls are to the police and to the platform.

## Legal routes when the policy does not fit

When the image is part of a page, the person is now an adult, or the policy was refused, a data protection request is the main legal lever in the UK and EU. It works differently from Google's minors policy.

### Google's data protection delisting request

Google runs a separate data protection delisting request for EU style claims. Its page says the affected person or an authorized representative can file, and that the request needs the specific URLs, how the content relates to you and why it should go, and the search query, usually your full name. Google says it balances the public interest against your data protection rights, weighing factors such as your role in public life, the source, how old the content is, and whether it involves sensitive data. Delisting applies to searches of the person's name, so the content can still appear for other queries. The page covers EU law and does not address UK data protection law, so read the form's own wording for your country.

### The right to erasure against the host

GDPR Article 17 lists grounds for erasure, including (in point f) personal data collected in relation to the offer of information society services, with exceptions in Article 17(3) such as freedom of expression and information. The UK Information Commissioner's Office says that where a request involves a child's data it places emphasis on erasure, and that a controller must respond within one month, extendable by two months for complex requests. The ICO page does not discuss search engines, so this route is aimed at the site holding the data, not Google. We have not read Article 8, which sets the child consent rules, so we do not rely on it here.

### Courts and other laws

Countries and US states have their own rules on images of minors. We did not read a primary source for them in this session, so we make no claim about them. If the host refuses and the image does harm, a lawyer in the relevant country decides whether a court order is available.

## Choosing the route: a decision table

Start with what the image is and where it sits. The table compares the routes on the same criteria.

<div class="tablewrap"><table><thead><tr><th>Route</th><th>What it removes</th><th>Speed</th><th>Fits when</th></tr></thead><tbody>
<tr><td><strong>Google minors policy</strong></td><td>Image from Google results</td><td>Days to weeks</td><td>Standalone image of a person under 18, no news value</td></tr>
<tr><td><strong>Site owner request</strong></td><td>The file itself, everywhere</td><td>Days, if they answer</td><td>Any image you can trace to a person</td></tr>
<tr><td><strong>Platform report</strong></td><td>The post or image on that platform</td><td>Days</td><td>Image is on a social or sharing site</td></tr>
<tr><td><strong>Data protection request</strong></td><td>Name-based results, or the data at the host</td><td>Often weeks; one month is the UK limit for a host</td><td>UK or EU link, or the person is now an adult</td></tr>
<tr><td><strong>Explicit-material reports</strong></td><td>Nude or sexual imagery of a minor</td><td>No timeline stated by the sources</td><td>Any nude or sexual image of a person under 18</td></tr>
</tbody></table></div>

Timing is our experience in usual cases, not a sourced figure, and no route is certain. Run the host and Google routes in parallel: one fixes the source, the other clears the results meanwhile.

## A worked scenario: a club photo that keeps appearing

This is an invented scenario with generic parties, used to show the order of operations.

A parent finds that a search for their 15-year-old daughter's name returns a team photo on a regional club's results page and the same photo on an image-sharing site. We would sort it like this:

1. On day one, the parent records every address. The club results page mixes text and images, so it is a page URL and does not meet the "image URLs only" condition. The route is a message to the club's webmaster, asking for the photo to be removed or the name taken off the caption.
2. The image-sharing copy has its own image address. It is a standalone image on a site the family does not run, so it should fit the Google minors request, unless Google treats it as newsworthy.
3. The same day, the parent files the request for the image-sharing copy and, in parallel, reports it to that site under its own rules.
4. Usually within days to a couple of weeks, the club deletes the page photo, and the parent then asks Google to refresh the result so the old thumbnail does not linger.
5. About a week after each step, the parent searches the name again in a private window and lists what remains.

The same photo took three routes because it lived at three kinds of address.

## What to do before you file anything

Record first, ask second. Save the addresses and dates of every place the image appears before anything changes, because a later search may not show what you saw. Then work the host route and the Google request together, and keep every reply.

Do not repost the image to complain about it, and do not message the poster in anger. Both raise the image's profile and slow cooperation. A measured first message is worth more than a fast one.

<div class="box hot"><b>If this is happening to you now</b>
<p>If a child's image is in search results and you are not sure which route fits, Reputation Partners can sort the addresses, send the host and platform requests, and file Google's request in the right order. Start with a private review of what is showing.</p>
<p><a href="/audit">Request a private audit</a></p></div>

## Questions people ask

### Can I ask Google to remove a photo of my child that I posted myself?

Google's policy excludes images from pages or accounts that the requester manages. If you posted the photo, deleting it at the source is the dependable fix. After that, request a refresh so Search stops showing the old thumbnail. Parents managing a family account should not count on the minors form for their own uploads.

### Does a removal also happen in Bing, Yahoo and other search engines?

No. Google's page says it can remove images only from its own results. Each other engine has its own process. If the file stays on the host, any engine can show it again. Deleting it at the source is the only action that works across them all.

### Will Google remove a photo of a minor that appeared in a news story?

It may not. The help page says Google may make an exception when an image is newsworthy or a matter of public interest, and the policy only takes image URLs, so a news article page is not eligible anyway. The practical route is to ask the publisher directly, or to use a data protection request if the law applies.

### How long does Google take to decide?

The help page as read for this guide gives no timeline. Google's announcement says teams review the request, may ask for more information and notify the requester when an image is removed. In our files, decisions usually arrive within days to a few weeks. Treat that as experience, not a promise.

### What if I am an adult and the photo was taken when I was a child?

The policy wording refers to a person under 18, and the page does not say how it treats adults. Do not count on it. Contact the host, report to the platform, and consider a data protection request if the UK or EU rules apply to you. Name-based delisting is possible under that process.

### Can a family ask for a photo of a child who has died?

The eligibility list covers a person who died before turning 18, and the help page says a representative such as a parent or relative can start a request. The other conditions still apply: image URLs only, no pages the requester manages, and the newsworthy exception.
