Site approval
Does AdSense care about your images?
Yes, but almost never the way publishers think. There is no image requirement to get approved. Images matter in four other ways, and all four are downside to avoid, not a box to tick.
By Mario Bailey · Published
Search for image advice on AdSense and you will find confident rules: publish at least this many images, use stock photos to stay safe, more images means a richer page. None of that is Google policy. We read the actual pages, and the truth is both simpler and more useful: approval turns on original text, and images matter only where they can hurt you.
First, the folklore
Google's eligibility, page-readiness, and rejection pages set no image requirement. There is no minimum number of images, no rule preferring original photos over stock, and no image-quality standard for approval. The eligibility requirements list original, high-quality content, policy compliance, being of age, and site access, and never mention images at all. The page-readiness guide mentions an image once, as a layout consideration. If you have read that you must add a certain number of images or swap stock for original to get approved, that is publisher folklore, not a Google rule.
The four ways images actually matter
1. Too many images and too little text can get you rejected
This is the one real approval risk, and it is about the text, not the images. Google's rejection-reasons page says a site "found to have too little text" may not be approved, that pages made "mostly of images" are at risk, and that content "should contain complete sentences and paragraphs, not only headlines." Images cannot stand in for the text Google's crawler needs to understand the page. The Publisher Policies add the demonetization side: Google does not serve ads on screens without publisher content or with low-value content. Google publishes no minimum word count or text-to-image ratio, and the language is "may not," not "will not," so this is a risk, not a guarantee.
2. Certain images cut your RPM without banning you
Sexually suggestive and shocking or graphic images fall under Google Publisher Restrictions. This is a demand-side policy, not an account ban: the content is not a violation, but fewer advertising sources are eligible to bid on it, so it "will likely receive less advertising than other, nonrestricted content," and in some cases none at all. The effect is lower RPM on pages with that imagery, which is a revenue tax rather than a suspension.
3. How images sit next to ads is a placement rule
Google's ad placement policies say publishers "may not attempt to associate specific images with the individual ads appearing on their sites," may not place misleading images alongside ads, and should not align images with ads or make nearby content mimic their formatting. Separately, the ads-interfering policy warns against placing ads immediately next to interactive elements, naming an image in an image gallery, because it causes accidental clicks. Note the scope: this is about interactive galleries a reader clicks or swipes, not static article images. A page dense with ordinary images is not a violation.
4. Unsized images shift the page, and that costs you twice
Images without a reserved width and height are a leading cause of Cumulative Layout Shift, because the browser reserves no space and the text reflows when the image loads. Google's bar for a good CLS is under 0.1, and the web.dev guidance names both unsized images and ads as top contributors. This is where images and ads are the same defect: on a site we run, an ad that overrode its reserved height drove page CLS to 0.303, three times over the line, and the fix brought it to 0.013. CLS is a Search ranking signal and a viewability drag at once, so reserving space for images and ads protects rankings, experience, and bids together.
One more, labeled honestly
Copyrighted content is a confirmed violation: Google says ads "may not be placed on sites with scraped or copyrighted content," which can get ads disabled or an account closed. Google frames this as content generally, not images specifically, so applying it to copyrighted images is a reasoned inference from the copyright policy rather than a verbatim image rule. It is still the safe reading: do not build pages on images you do not have the rights to.
What to actually do
- Write real text on every page. Images enrich a page; they do not substitute for the sentences the crawler reads.
- Set width and height (or a CSS aspect ratio) on every image, and reserve height for every ad, so nothing shifts on load.
- Keep ads away from interactive image galleries and never dress an image up to look related to an ad.
- Expect lower RPM, not a ban, if a page carries restricted imagery.
- Use images you own or are licensed to use. Ignore the minimum-count and stock-versus-original folklore entirely.
The layout-shift study The low-value-content rejection
Sources, all Google primary pages read live in July 2026: Eligibility requirements; Make sure your pages are ready; Account not approved; Google Publisher Policies; Google Publisher Restrictions; Ad placement policies; Ads interfering with content; web.dev, Optimize CLS.