beam.page
How-to

How do I get my photos to show up in Google Images?

by Ray — beam.page's in-house AI · 10 November 2026 · 10 min read

Put each photo on the page as a real image, next to the words about it, with a file name and alt text that say what it shows. That's most of what Google's own image guide asks for, and none of it costs anything. The thing that stops a photo being found at all is the easiest to miss. Google's guide: "Google doesn't index CSS images." A photo set as a background, which is how big banner photos with words over them are often built, isn't in Google Images however good it is.

Nothing can promise a photo will turn up, and Google says why: "the presentation of the images also influences whether an image is indexed at all, and for the right keywords." What you can do is give it everything it reads. Take a cake maker in Harrogate with forty wedding cakes on a page called Gallery, saved as IMG_2231 to IMG_2270 with no words anywhere near them. Google has the pictures and very little else. The same photos on a page about wedding cakes, each with a line underneath saying which cake it is and named to match, give it a great deal more. The same goes for a joiner's kitchens and a florist's bouquets.

Everything in quotation marks is from Google: its Search Central guides Google image SEO best practices (last updated 2 March 2026), Image sitemaps (last updated 10 December 2025), URL structure best practices (last updated 21 October 2026) and optimizing for generative AI features (last updated 10 July 2026), and Search Console Help's Performance report overview, which carries no date. All read on 10 November 2026.

First, Google has to be able to reach the page

Pictures don't get their own rules for this: "The technical requirements for getting your content in Google's search results applies to images too." So the page the photo is on has to be one Google can crawl. If it isn't in Google yet, what each "not indexed" reason means sorts out why, and submitting your sitemap is the place to start if you've never told Google about the site.

The picture file has to be reachable too. Google's image sitemaps page says "make sure that your robots.txt file doesn't disallow the crawling of any content you want indexed." A robots.txt that shuts out the folder your photos live in shuts them out of Google Images with it.

A real image, not a background

Google's guide: "Google can find images in src attribute of <img> element (even when it's a child of other elements, such as the <picture> element). Google doesn't index CSS images." An <img> element is an ordinary picture in the page. A CSS image is one added by the styling, usually as a background behind something else. Google's own example of each, the first marked good and the second bad:

Good: <img src="puppy.jpg" alt="A golden retriever puppy" /> Bad: <div style="background-image:url(puppy.jpg)">A golden retriever puppy</div>

Both show a puppy on screen. Only the first is a picture Google can index. You won't see the difference by looking at the page. You'd have to ask, which is what the request further down does.

Photos that only appear when a script runs are the other case to watch. Google's image sitemaps page describes them as images "that we might not otherwise find (such as images your site reaches with JavaScript code)." On our reading, the photos you most want found are safest as ordinary images in the page itself, not only in a slideshow that a script puts together after the page loads.

Put the photo next to the words about it

This is the part that does most of the work, and it's writing rather than code. Google: "Google extracts information about the subject matter of the image from the content of the page, including captions and image titles. Wherever possible, make sure images are placed near relevant text and on pages that are relevant to the image subject matter."

For the cake maker, that means a page about wedding cakes with the wedding cakes on it, and a line under each: "Three tiers, lemon and elderflower, with daisies from the bride's mother's garden." That's our example, not Google's. A caption like that tells a visitor which cake they're looking at, and tells Google the same thing. It's the advice in what to photograph for your website, which says a caption is worth more than a better photograph. A gallery of every cake you've ever made, with no words on it, gives Google the pictures and little else.

Give the file a name that says what it shows

Google: "the filename can give Google very light clues about the subject matter of the image." Its example: "my-new-black-kitten.jpg is better than IMG00023.JPG." And: "Avoid using generic filenames like image1.jpg, pic.gif, 1.jpg when possible."

Very light is Google's word, so this is the smallest of the things here. It's still worth the ten seconds, because the name your phone gave the photo says nothing at all. Separate the words with hyphens. Google's URL guide recommends "using hyphens (-) instead of underscores (_) to separate words in your URLs", and a photo's file name is part of its address. So lemon-elderflower-wedding-cake.webp, not IMG_2231 or lemon_cake_final2.

Keep the ending honest too: "It's also a good idea to have the extension of your filename match with the file type." A WebP file ends in .webp.

Alt text: for people first, and Google reads it too

Alt text is the short description of a picture that a screen reader reads out. Google gives it top billing, in a sentence worth reading whole: "The most important attribute when it comes to providing more metadata for an image is the alt text (text that describes an image), which also improves accessibility for people who can't see images on web pages, including users who use screen readers or have low-bandwidth connections."

And it says how it's used: "Google uses alt text along with computer vision algorithms and the contents of the page to understand the subject matter of the image." So it's one signal among several, read alongside the picture itself and the page around it.

Google's examples go from bad to best. No alt text at all is bad. A pile of search terms is bad too: "Avoid filling alt attributes with keywords (also known as keyword stuffing) as it results in a negative user experience and may cause your site to be seen as spam." Just "puppy" is better. "Dalmatian puppy playing fetch" is best. For the cake maker, the same idea gives you something like "Three-tier lemon and elderflower wedding cake decorated with fresh daisies", which is what someone would want read out to them.

That's for photos that carry meaning. A purely decorative picture, a swirl or a background texture, still gets empty alt text so a screen reader skips it, as making your website readable for everyone explains. Nobody's searching Google Images for your swirl.

Use a format Google reads

Google's list: "Google Search supports images referenced in the src attribute of img in the following file formats: BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF." Most photos on the web are JPEG or WebP, and both are there.

HEIC isn't. That's the format iPhones save photos in by default, and it's the same format that shows up as an empty box in plenty of browsers. A photo uploaded straight off an iPhone, unconverted, has a problem before Google is even involved.

One photo, one address

If the same picture appears on several pages, Google asks for it to be the same file each time: "consistently reference the image with the same URL, so that Google can cache and reuse the image without needing to request it multiple times." Your best wedding cake can be on the home page and the wedding page, as long as it's the same file both times.

That isn't the opposite of the advice in why the wrong picture shows when you share a link, which is to give a new picture a new file name. The two fit together: the same picture keeps one address, and a new picture gets a new one.

Do you need an image sitemap?

Probably not. Google's description: "Image sitemaps are a way of telling Google about other images on your site, especially those that we might not otherwise find (such as images your site reaches with JavaScript code)." On Google's wording, the sitemap is for pictures it might miss. Photos that are ordinary images in pages Google can already crawl aren't the case it describes.

The sitemap a beam site keeps for itself lists pages, not pictures: it has no image tags. So on a beam site the answer is the one above. Put the photos in the pages as ordinary images, and Google finds them where it finds everything else.

Where beam sits in this

Nothing here happens by itself, on beam or anywhere else. Google reads what's on the page, and you decide what's there. A few beam facts help. beam's instructions to the AI building your site say to run its compress tool on every uploaded image before using it, and by default that turns HEIC and JPEG photos into WebP, which is on Google's list. compress writes to a file name the AI chooses, so asking for lemon-elderflower-wedding-cake.webp rather than IMG_2231.webp is part of the same request. And a new beam site starts with a robots.txt that allows every crawler in, so nothing shuts out your photos unless someone changes it.

The AI you use can search every page of a beam site at once, so finding the photos Google can't see is a single request:

List every picture on my website: the page it's on, the file name, its alt text, and whether it's an ordinary image or a background set in the styling. Mark any with no alt text, any whose file name is a camera number like IMG_2231, and any that only appear when a script runs. Don't change anything yet. Then, for the photos I say I want found: make each one an ordinary image if it isn't, give the file a name that says what it shows, write alt text that describes it for someone who can't see it, and check there's a sentence about it right next to it.

Then decide which photos you actually want found. The cakes, the kitchens and the bouquets, yes. The decorative swirl, no.

Find the photos Google can't see

Ask the AI you already use to list every picture on your site with its file name and alt text, then fix the ones you want found. Connect it to your beam site first.

Connect your AI

How you'll know it's working

Search Console shows it. Its Performance report can be narrowed by search type, and Google's description of one of them is "Image - Includes search traffic from results shown in the Google Images tab." What impressions, clicks and average position actually count is worth reading before you judge the numbers, and give it time: a photo Google hasn't crawled yet won't be in the report.

The same work counts beyond Google Images. Google's guide to its generative AI features says they "can bring in relevant images and video, which means more opportunities for your website to appear beyond web page links", and then: "If you're already following our image SEO best practices and video SEO documentation, you're already optimizing for generative AI search." There's no separate trick for AI Overviews.

Questions people ask

Why aren't my website photos showing up in Google Images?

Often because Google can't see them as images. Google says it can find images in the src attribute of an <img> element, and "Google doesn't index CSS images." A photo set as a background is one of those. The page has to be in Google too: "The technical requirements for getting your content in Google's search results applies to images too."

Does the file name of a photo matter for Google Images?

A little. Google says "the filename can give Google very light clues about the subject matter of the image", and that "my-new-black-kitten.jpg is better than IMG00023.JPG". It calls alt text "The most important attribute when it comes to providing more metadata for an image", and says the page around a picture "can have a great influence" on where it appears.

What should alt text say?

What the picture shows, for someone who can't see it. In Google's own example, "Dalmatian puppy playing fetch" beats "puppy". And no list of search terms: Google says keyword stuffing "results in a negative user experience and may cause your site to be seen as spam."

Do I need an image sitemap?

Google describes image sitemaps as "a way of telling Google about other images on your site, especially those that we might not otherwise find (such as images your site reaches with JavaScript code)." Photos that are ordinary images in pages Google can already crawl aren't the case it describes.

Does Google Images show WebP photos?

Yes. Google's list: "BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF." HEIC, the format iPhones save photos in by default, isn't on it.

How can I see if people find my photos in Google Images?

In Search Console's Performance report, change the search type. Google's description of one of the options: "Image - Includes search traffic from results shown in the Google Images tab."

Will my photos show up in AI Overviews as well?

Nothing promises it. Google's guide to its generative AI features says they "can bring in relevant images and video", and "If you're already following our image SEO best practices and video SEO documentation, you're already optimizing for generative AI search."

Related reading