Back to blog

Image SEO: How to Optimize Images for Google, Image Search and AI Answers

Image SEO: How to Optimize Images for Google, Image Search and AI Answers
Table of contents

Good image SEO comes down to four things: a modern format, a sensible file size, honest alt text and an image tag Google can actually find in your HTML. Get those right and you’ve covered classic rankings, Google Images and AI Overviews in one pass, because Google feeds all three from the same index.

  • Use AVIF with a WebP or JPEG fallback, since AVIF reaches roughly 93 to 97% of browsers.
  • Write alt text as one plain sentence, like Google’s alt=”Dalmatian puppy playing fetch” over alt=”puppy”.
  • Skip image sitemaps and schema unless images load via JavaScript or you want Image Search badges.
  • AI Overviews and ChatGPT need no separate image rules, and no study proves alt text raises citations.

Format and Compression: What Actually Keeps Images Fast

Serve AVIF as your main format, keep WebP or JPEG as fallback, and resize every image to the width it’s actually displayed at before you upload it. That combination handles most of what PageSpeed complains about, and it stays inside the formats Google can process.

That last part matters more than it sounds. Google Search supports exactly seven formats in an image’s src attribute: BMP, GIF, JPEG, PNG, WebP, SVG and AVIF. Anything else, like an HEIC file straight off an iPhone, simply doesn’t get processed. Convert first, then upload.

On AVIF itself: global browser support sits at roughly 93 to 97% in 2026, depending on whose methodology you trust, and Safari has fully supported it since version 16.4 in March 2023. The gap is mostly older iPhones on iOS 15 or earlier and outdated Android browsers. Small, but real, which is why the fallback stays.

FormatBest useFallback needed?
AVIFPhotos, hero images, anything largeYes, WebP or JPEG
WebPPhotos and graphics when you skip AVIF, plus the usual AVIF fallbackRarely, only JPEG for very old browsers
JPEGUniversal fallback for photosNo
PNGScreenshots with sharp text, images that need transparencyNo
SVGLogos, icons, simple line illustrationsNo

Technically, the fallback lives in a picture element: your AVIF and WebP versions go in source tags, and a plain img tag with a src attribute sits at the end. Google asks for img fallback because some browsers and crawlers don’t understand picture or srcset at all.

For compression, skip the hunt for a magic quality number. Export at the largest width the image is rendered on the page (roughly double that if you want it crisp on high-density screens), then lower the quality setting until you spot artifacts at 100% zoom and step back up one notch. A 4,000 px stock photo squeezed into a 700 px column by CSS is the single most common reason a blog feels slow.

Writing Alt Text That Works for Screen Readers and Rankings

Good alt text describes what’s in the image in one plain sentence, the way you’d describe it to someone on the phone. Google’s own documentation spells out the step-up: an empty alt is bad, alt=”puppy” is better, alt=”Dalmatian puppy playing fetch” is best.

The penalty fear has a simple fix. Google states that stuffing the alt attribute with keywords creates a bad user experience and can get your site flagged as spam. Describing honestly keeps you safe. A reusable pattern: what it is + what’s happening + the one detail that matters. Here’s how bad alt text turns into good alt text:

  • For a blog header, swap alt=”seo tips images” for alt=”Marketer comparing original and compressed photos on a laptop”.
  • For a product photo, alt=”boot” becomes alt=”Black leather Chelsea boot with elastic side panel, side view”.
  • For a chart, alt=”chart” becomes alt=”Bar chart comparing one photo’s file size as JPEG, WebP and AVIF”.
  • For a decorative swirl, alt=”decorative blue swirl background” becomes alt=”” so screen readers skip it.

For charts and screenshots, repeat the key numbers in the text nearby too. The empty alt for decorative images comes from W3C guidance that Google points to. For purely decorative inline SVGs, Google recommends a title element instead of alt. And if an image is a link, its alt text works as the anchor text, so a linked logo or button image without alt is a link with no label.

File Names, Captions and Context: Signal or Folklore?

Google documents four signals beyond the image itself: alt text, captions and image titles, file names, and surrounding text. They’re not equal, and knowing the ranking among them saves time.

Alt text is most important in Google’s documentation. Google also pulls information about the image’s topic from captions and image titles on the page, combining all of this with computer vision and the page content to work out what the image shows. So even without perfect alt text, Google isn’t blind. Your text just removes the guesswork.

File names are where folklore creeps in. Google calls them “very light clues“. So my-new-black-kitten.jpg beats IMG00023.JPG, but stuffing a file name with keywords does nothing a clean descriptive name wouldn’t.

Surrounding text is a documented signal that gets underrated. Google recommends placing images near relevant text because context helps it understand the image within the page. A chart dropped between unrelated paragraphs is harder to place than the same chart under the paragraph it explains.

Easy win for templates: If you reuse the same stock photo or author image across many posts, reference one stable image URL everywhere. Google can cache it once instead of requesting a dozen copies, which saves crawl budget on larger sites.

Do You Need an Image Sitemap or ImageObject Schema?

For standard blogs, you can skip both. An image sitemap exists to tell Google about images it wouldn’t otherwise find, like ones loaded via JavaScript. If you do need one, only image:image and image:loc are required, with up to 1,000 image tags per URL entry. The deciding question is whether Google can find your images on its own.

Your situationWhat to do
Images sit in regular img tags in the page HTMLSkip the image sitemap
Images load via JavaScript, galleries or slidersAdd an image sitemap with image:image and image:loc
You want to control the thumbnail in Search and DiscoverSet og:image or primaryImageOfPage markup, using a specific image, never your logo or an image with text
You want badges in Google Images (products, recipes and similar)Use the matching structured data type, whose image property is required for the badge
You’re adding schema only to show up in AI OverviewsSkip it, since Google says no special markup is needed for AI search

If you do build a sitemap, check what your SEO plugin puts into it.

Outdated advice: Older guides still tell you to add image:caption, image:title, image:geo_location or image:license to your sitemap. Google has deprecated all four. If a plugin generates them, they’re harmless but useless.

Do AI Overviews and ChatGPT Actually Read Your Images?

No separate AI index for Google. AI Overviews draw on the same ranking and quality systems as regular Search, grounded in the normal index Googlebot builds. If not indexed for Search, it isn’t available for AI Overviews either. Google recommends high-quality visuals that support your text, so every fix in the sections above is your AI Overview image strategy. No extra AI rules to learn.

Good to know: Google-Extended, the token people block to “opt out of AI”, only controls whether your content is used for training and grounding Gemini models. It has no effect on Search rankings or AI Overview inclusion. Blocking Googlebot, by contrast, removes you from both at once.

ChatGPT works differently because OpenAI runs its own crawlers. OpenAI documents four of them, and each can be allowed or blocked separately in robots.txt:

  • GPTBot collects content for model training.
  • OAI-SearchBot indexes pages for ChatGPT search.
  • ChatGPT-User fetches a page when a user’s request triggers it.
  • OAI-AdsBot checks ad landing pages.

One technical detail matters a lot for images: GPTBot processes only raw HTML from the first page load, without running JavaScript, and AI crawlers tend to work with tight timeouts of one to five seconds. JavaScript images can be invisible to them, and a slow page may get skipped entirely. Server-rendered img tags with real alt text are the safe bet.

No verified study measures alt text’s effect on AI citations. The “156% higher selection rate” number comes from an industry blog analysis without public methodology. It’s also not documented whether Perplexity, Gemini or AI Mode run real computer vision on page images during crawling. What you can defend: text signals like alt text, captions and surrounding text are the documented entry ticket.

Your One-Afternoon Priority Order

Start with your top 10 posts and above-the-fold images. That’s where speed and alt text pay off first, and the long tail of old posts can wait.

  1. Resize each top post’s hero image, convert it to AVIF with a fallback, and never lazy-load it.
  2. Write alt text for every meaningful image on those posts, using the sentence pattern above.
  3. Set alt=”” on purely decorative images so screen readers skip them.
  4. Add width and height attributes to every image, and use loading=”lazy” only below the fold.
  5. Check that key images sit in server-rendered img tags rather than JavaScript-only sliders.
  6. Agree on a descriptive file naming convention for every upload from today on.

Width and height attributes let the browser reserve space before the image arrives, preventing layout shift. Responsive images via srcset and sizes, or a CDN that resizes on the fly, take care of serving the right size to phones versus desktops.

Largest Contentful Paint (LCP): The Core Web Vital that measures when the biggest visible element finishes loading, usually your hero image. Lazy-loading it tells the browser to wait, which is the fastest way to tank your LCP score.

While you’re in there, watch for quiet mistakes: the same alt text pasted on every image, keyword-stuffed file names, huge uploads scaled down by CSS, important text baked into images where Google and screen readers can’t use it, and linked images without alt. Ignore sitemaps, schema and old file names for now.

If you’d rather not do this by hand, there are options for recurring hygiene. Claire’s GEO Audit checks a site on more than 70 points across technical setup, content, authority and brand to assess visibility in ChatGPT and similar tools. For ongoing publishing, Claire’s AI Blog Writer (from €199) finds topics, writes SEO articles in your voice and publishes them to WordPress, Webflow or Shopify, up to 30 per month.

Image SEO Is a Checklist You Can Finish

Image SEO is tedious, not hard, and nothing here needs a new tool or redesign. Google publishes the whole list itself. Pick your 10 highest-traffic posts this week, run the priority order on those, and handle the rest as a habit on every new upload instead of one giant backlog.

FAQ

Does my CMS need to support AVIF before I switch formats?

Usually, yes. Your CMS or image plugin has to accept AVIF uploads and output the WebP or JPEG fallback for you. If it can’t, convert the files yourself and add the picture element by hand, at least for your hero images.

Can I reuse the same alt text when one image appears in several posts?

Usually, yes, if the image shows the same thing in the same role on each page. Keep one stable image URL as well so Google caches it once. Rewrite the alt only where a page uses the image to make a different point.

How do I check in Search Console that my image fixes worked?

Filter the Performance report by search type “Image” for Image Search impressions and check the Core Web Vitals report. PageSpeed Insights shows lab improvements immediately, while field data in Search Console follows a rolling 28-day window, so expect a few weeks.

byClaire

Content marketing like this article?

AI search already answers your customers’ questions. The only question is: with whom?

Discover moreTry it for free
Trusted by 500+ DACH users