Image SEO: how Google finds, picks and describes your images
Help Google discover and describe images through HTML, metadata, filenames and useful alt text without promising search visibility.
Images can appear in Google's text results, Google Images and Discover. This article summarises Google's "Image SEO best practices" page as read on 15 November 2026 (the page says it was last updated 2026-03-02). Google says the general recommendations are the same across those features. It covers Google only. Read the page before you act.
Help Google find the images
- Use normal HTML image elements. Google says it finds images in the src attribute of an img element, even when the img sits inside another element. It says Google does not index CSS images. If a designer puts your product photos in as CSS backgrounds, they are not in this route.
- An image sitemap can give Google image URLs it might not otherwise find. Unlike regular sitemaps, it can list image URLs on other domains, which suits a CDN. Google encourages verifying ownership of the CDN domain in Search Console so it can report crawl errors.
- Responsive images: Google says some browsers and crawlers do not understand srcset or the picture element, so always give a fallback URL in src. With picture, include an img element with a src as the fallback. Our article on responsive images covers the markup.
- Formats: Google Search supports images in the src attribute in BMP, GIF, JPEG, PNG, WebP, SVG and AVIF, and it is a good idea for the file extension to match the type. Images can be inlined as data URIs, but the page warns this can considerably increase page size.
- Speed and quality: the page says sharp images are more appealing in thumbnails, that images are often the biggest part of page size, and points to PageSpeed Insights.
Help Google choose and describe the right image
- Preferred image: Google says choosing the preview image is fully automated, but you can influence it with the schema.org primaryImageOfPage property, an image property attached to the main entity, or an og:image meta tag. It advises choosing a relevant, representative image, avoiding a generic one such as your logo or one with text, avoiding extreme aspect ratios, and using high resolution where possible.
- Title and description: Google generates the title link and snippet from several sources including the title and meta tags; see our title and meta description article.
- Structured data: the page says it can make images eligible for certain rich results, including a badge in Google Images, and that the image attribute is required for those types. Guidelines for the markup type must also be met.
- Filenames, captions, alt text: Google takes information about the subject from the page, including captions and image titles, so images should sit near relevant text. Filenames give light clues; it prefers short descriptive names such as my-new-black-kitten.jpg over IMG00023.JPG and generic names such as image1.jpg. If you localise images, translate the filenames, keeping URL encoding in mind.
- Alt text is described as the most important attribute for image metadata. It also helps people who use screen readers or have low bandwidth, and works as anchor text when an image is a link. Google asks for useful, information-rich text in context, and warns that stuffing keywords into alt text is a bad experience and may make the site look like spam. For inline SVG, the page shows a title element referenced by aria-labelledby.
- Same URL: if an image appears on many pages, reference it with the same URL each time so Google can cache and reuse it.
Controls
- Inline linking opt-out: you can stop the full-size image from showing on the Google Images results page by checking the referrer on image requests and answering requests from a Google domain with 200 or 204 and no content. Google says it will still crawl the page and show a thumbnail created at crawl time, and that this is not cloaking and will not cause manual actions. The page says you can also keep the image out of search results entirely, and links to how.
- SafeSearch: the page says to make sure Google understands the nature of your site so SafeSearch filters can be applied if appropriate.
Omnistu advice for a site or app project (not from the source)
- Ask the developer how product and article images are embedded. If they are CSS backgrounds, ask whether the important ones should be img elements.
- Write alt text for the image's purpose in context, not just its appearance. Decorative images normally need empty alt text; functional images need their action or destination conveyed. It is also an accessibility requirement for many sites.
- Name files when you export them, not after they are live and linked.
- Choose one representative image per page and set it deliberately, rather than leaving the choice to chance.
- Do not buy mass "alt text keyword" work; Google's page names this as a risk. See our article on Google's spam policies for the broader list.
Limits
One Google page, read in full on 15 November 2026, with its code examples partly lost in our fetch. We did not read the pages it links to (image sitemaps, structured data types, SafeSearch, removal). We tested nothing and make no claim about how image changes affect rankings or traffic. Google only; other search engines were not read.
By Omnistu.