Image SEO

TL;DR — Image SEOImage SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps. is making the pictures on your pages work for search: showing up in Google Images, and loading fast so they don’t slow your page down. The basics: use a descriptive filename, write good alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., compress images so they’re not huge, pick a modern format like WebP, and don’t make the big image at the top of the page “lazy loadLazy loading defers loading of off-screen or non-critical resources — usually images and iframes — until they're about to enter the viewport. The native way to do it is the loading=\"lazy\" HTML attribute, which needs no JavaScript..” There’s no magic ranking boost from any of this — it just helps your images get foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. and keeps your pages quick.

What image SEO is

When you put a picture on a web page, search engines can do two useful things with it. They can show it in image search (Google Images, Bing Images, Google LensMultimodal search lets you query and get results across more than one modality — text, images, video, and audio together. Instead of typing words, you can point your camera, circle something on screen, or combine an image with a question, and the system understands them jointly.), which sends people to your page. And they read the image as part of the page — mostly through its alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search. — to understand what the page is about.

The catch is that a search engine can’t “see” a photo the way you do. It relies on the clues you give it: the filename, the alt text, the words around the image, and the file itself. Image SEO is just giving good clues — and making sure the image doesn’t slow your page to a crawl.

The handful of things that matter

• Use a real format and compress it. WebP and AVIF are modern formats that make files much smaller than old JPEGs without looking worse. Smaller files = faster pages. Faster pages help your rankings (not because of the format itself, but because speed counts).
• Name the file something descriptive. golden-retriever-puppy.jpg tells Google more than IMG_0042.jpg. Do this for new images — don’t go back and rename all your old ones (more on that in the Advanced tab).
• Write good alt text. This is the short description of the image. It’s the main thing that helps your image show up in image search. It’s also required for accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all.. I cover it fully in the separate alt text guideAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search..
• Don’t lazy-load the big image at the top. “Lazy loadingLazy loading defers loading of off-screen or non-critical resources — usually images and iframes — until they're about to enter the viewport. The native way to do it is the loading=\"lazy\" HTML attribute, which needs no JavaScript.” delays loading images until you scroll to them — great for images down the page, bad for the main image at the top, because that’s the one Google times your page speed against.
• Use a unique image when you can. Stock photos are fine for normal search, but the same stock photo is on a thousand other sites, so it’s harder to stand out in image search.

The thing most people get wrong

There’s no SEO “boost” for using WebP or AVIF. People assume switching formats will lift their rankings. It won’t — Google has said so directly. What modern formats do is make your pages faster, and speed is what actually helps. Same with renaming files: helpful for new images, but renaming your whole library can do more harm than good.

Want the precise version — the exact Google quotes, format trade-offs, structured data, image sitemapsAn image sitemap is a sitemap (or an extension added to an existing sitemap) that lists the images on your pages using Google's image namespace, helping Google discover images it might otherwise miss., Discover, and the lazy-loading rules — switch to the Advanced tab.

TL;DR — Image SEOImage SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps. is two separate goals: (1) ranking in image search (Google Images / Lens / Bing), driven by alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., filenames, page context, and uniqueness; and (2) page performance, because images are usually the LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. element. Google indexes <img> (including inside <picture>) — not CSS backgrounds — and supports BMP, GIF, JPEG, PNG, WebP, SVG, AVIF. There is no direct ranking boost for WebP or AVIF (Mueller); the payoff is speed → Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data.. Don’t bulk-rename existing files. Native loading="lazy" is safe below the fold but never on the LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. image — that one gets fetchpriority="high". Since May 2025, reference the same image at the same URL everywhere. Structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. (ImageObject, Product/Article image arrays) unlocks rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show.; image sitemapsAn image sitemap is a sitemap (or an extension added to an existing sitemap) that lists the images on your pages using Google's image namespace, helping Google discover images it might otherwise miss. still help discovery. Alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search. gets its own deep dive.

Image SEO is two jobs, not one

This is the framing I keep coming back to, and almost every “image SEO checklist” blurs it. There are two distinct goals, and they call for different work:

1. Ranking in image search. Getting your images foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. in Google Images, Bing Images, and Google LensMultimodal search lets you query and get results across more than one modality — text, images, video, and audio together. Instead of typing words, you can point your camera, circle something on screen, or combine an image with a question, and the system understands them jointly. for image-specific queries. This is driven by alt text, filenames, the text surrounding the image, structured data, and image uniqueness.
2. Page performance. Images are almost always the heaviest thing on a page — Google’s own docs say images are “often the largest contributor to overall page size.” That makes them the usual culprit for a slow Largest Contentful Paint (LCP), which feeds Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data., which is a web-search ranking signal.

Keep these separate and the whole topic gets clearer. Alt text and filenames are mostly an image-search play. Format, compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits., and loading strategy are a performance play. Both matter; they’re just not the same lever.

And the volume is real: image and visual search is a meaningful slice of all search activity, and Google Lens has grown fast. Optimized images aren’t just defensive — they’re a traffic source.

How Google discovers and indexes images

A few mechanics decide whether your images even make it into the index:

• Only HTML <img> gets indexed. Google: “Google parses the HTML <img> elements (even when they’re enclosed in other elements such as <picture> elements) in your pages to index images, but doesn’t index CSS images.” If an image lives only in a CSS background-image, it’s invisible to image search. Put anything you want found in an <img>.
• Always provide a fallback src. When you use srcset or <picture>, keep a plain src too — “some browsers and crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. don’t understand” the responsive attributes, and the src is the safety net Google relies on.
• Supported formats: BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF (AVIF support landed in August 2024). The file extension should match the actual file type.
• Context still matters alongside markup. Supported markup gets an image discovered; it’s the page’s surrounding text, captions, titles, and other metadata that Google combines with the image itself to understand what it’s about once found.
• URL consistency (May 2025 update). Google now recommends referencing the same image with the same URL every time it appears. A Google spokesperson put it as: “We updated the Google Image SEO best practices to clarify that URLs for images should be referenced consistently for easier crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. on larger websites.” This is a crawl-efficiency thing — same image, same URL, so Google can cache and reuse it instead of re-fetching the same picture under different CDN paths or query strings.

File formats: pick for speed, not for an SEO boost

Here’s the myth to kill first: there is no direct ranking boost for “next-gen” formats. Mueller confirmed there’s no “SEO boost” for AVIF, and the same logic applies to WebP — “WebP images are fine for Image Search,” but “fine” is not “better.” Google doesn’t reward you for the container.

What modern formats do is shrink your files, which speeds up the page, which helps Core Web VitalsWeb Vitals is Google's initiative (launched May 2020) for unified page-experience quality signals. Core Web Vitals — LCP, INP, and CLS — are the subset used in ranking; the rest (TTFB, FCP, TBT, Speed Index) are diagnostic, not ranking factors. — an indirect benefit. So choose on the merits:

• AVIF — best compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits. (often 50%+ smaller than JPEG). Use it where browser support is covered, with fallbacks.
• WebP — 25–35% smaller than JPEG with near-universal browser support. The safe default for photos today.
• JPEG — universal fallback for photographs.
• PNG — when you need transparency or sharp-edged graphics.
• SVG — logos and icons (vector, scales infinitely, tiny).
• GIF — avoid for anything non-trivial; use video or animated WebP/AVIF instead.

The clean implementation is <picture> with <source> elements for the modern formats and a <img src> fallback, so older browsers degrade gracefully and Google still has a src to index.

File names: descriptive for new images, don’t bulk-rename old ones

Filenames are a real (if minor) signal. Google’s own best practice is to use short, descriptive names — “the filename can give Google clues about the subject matter of the image” — so golden-retriever-puppy.jpg beats IMG00023.JPG, and anything generic like image1.jpg is a wasted opportunity.

But here’s the nuance that trips people up: don’t go back and rename your existing files. Mueller was clear that bulk renaming “is going to take a lot of time for Google’s systems to see” the new images, and that the effect is “minimal… maybe no visible effect at all” if your alt text and surrounding context are already good. Gary Illyes framed the signal loss from image URL migrations as “in line with web search results, which is a few weeks.” So: descriptive names on new images, yes; a site-wide rename project for marginal benefit and weeks of churn, no.

Alt text (the short version)

I’m not going to repeat the full treatment here because alt text has its own deep dive. The headline: alt text is the most important piece of image metadata, but its real payoff is image search and accessibility — not web-search rankings. Google reads it alongside computer vision and page context, so write for context, don’t keyword-stuff, and use alt="" for purely decorative images. The full rules, quotes, and audit workflow are in my alt text guideAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search..

Compression, lazy loading, and Core Web Vitals

Because images usually decide your LCP, this is where image SEO and Core Web Vitals overlap most:

• Compress everything. Right-size images to their display dimensions and compress them. This is the single biggest performance lever for most pages.
• Native lazy loadingLazy loading defers loading of off-screen or non-critical resources — usually images and iframes — until they're about to enter the viewport. The native way to do it is the loading=\"lazy\" HTML attribute, which needs no JavaScript. is safe — below the fold. loading="lazy" on the <img> is Google-endorsed and crawlable. The implementations that break are JavaScript ones that hide the real URL in data-src and never expose a src — those risk not being indexed. Stick to native loading="lazy" or IntersectionObserver, and make sure images load when visible, not on a click or swipe (“Google Search does not interact with your page”).
• Never lazy-load the LCP image. This is the one rule people break most. Your largest above-the-fold image (usually the hero) should load eagerly — loading="eager" and fetchpriority="high" — not lazily. Lazy-loading the LCP image can add hundreds of milliseconds to LCP for no reason.

TIP Audit the implementation, not just the file format

A page can use valid images and still miss the signals that matter for accessibility, discovery, and LCP. Treat the likely-LCP warning as a heuristic; confirm the real LCP element with field or lab performance data. Missing ImageObject markup is informational unless the page needs a structured-data feature.

Run the page through my checker to review its raw HTML image signals in one pass. Image SEO Checker Free

1. Enter a public page URL and run the check.
2. Review alt coverage, first-image loading and priority, source formats, and ImageObject detection.
3. Fix confirmed problems, then rerun the same URL to verify the rendered HTML changed.

Tap to enlarge

Responsive images

Use srcset + sizes (different resolutions for different viewports) and <picture> (art direction / format switching). Two things to keep straight:

• Always include a fallback src. As above — crawlers and older browsers need it.
• Every candidate needs to be reachable. Whatever access rules apply to your fallback src — not blocked, not behind auth, not a dead URL — apply to each srcset/<picture> candidate too. An undiscoverable candidate doesn’t help even when the fallback is fine.
• Keep your URLs consistent with the page. The image URL you put in an image sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. should be the same URL the page actually uses. Don’t serve a different image URL to mobile than to desktop — Google is a mobile-first crawler, and divergent URLs cause temporary image-traffic loss while Google rebuilds ranking history for the new URLs.

Structured data for images

Structured data is what unlocks image-related rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. and badges:

• ImageObject with a license property makes images eligible for the licensable badge in Google Images. The required fields are contentUrl plus at least one of creator, creditText, copyrightNotice, or license; add license
  • acquireLicensePage for the badge itself.
• Product and Article structured data want an image array with multiple aspect ratios (commonly 16:9, 4:3, 1:1). The image property is required for image-bearing rich results.
• Thumbnail control. Google’s thumbnail pick is automated, but you can influence it via primaryImageOfPage schema, the main entity’s image property, or the og:image meta tag — Google uses both schema.org markup and og:image for thumbnails in Search and Discover.

Eligible markup isn’t a display guarantee — Google still decides, page by page, whether to actually show the badge, image array treatment, or thumbnail your structured data makes possible.

This is also where image SEO overlaps with the broader structured data topic — the markup that powers product, article, and image rich results is the same machinery.

Image sitemaps

Image sitemapsAn image sitemap is a sitemap (or an extension added to an existing sitemap) that lists the images on your pages using Google's image namespace, helping Google discover images it might otherwise miss. are a discovery tool, most useful for CDN-hosted images, large galleries, and JS-heavy sites where images might not be found through normal crawling. Two notes that catch people out: Google now supports only <image:image> and <image:loc> (it deprecated <image:caption>, <image:title>, <image:geo_location>, and <image:license> on May 6, 2022 — though Bing still uses them, so keep them in if you serve one sitemap to both). And image sitemaps are the one place you’re allowed cross-domain URLs in <image:loc>, which is handy for CDN hosting (verify the CDN domain in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.). The mechanics live in the image sitemaps article. None of this is a promise: an image sitemap can help Google discoverGoogle Discover is a personalized, mobile-first content feed built into the Google app, Chrome's mobile New Tab page, and google.com that surfaces articles and videos based on a user's interests and activity — not a response to a search query. There's nothing to 'rank' for in the traditional sense; eligibility is governed by Discover's content policies plus the same helpful-content, image, and page-experience signals Google Search already uses. images it might otherwise miss, but submitting one doesn’t guarantee crawling, indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., or ranking.

Discover and large images

To be eligible for large-format image previews in Discover and across Google surfaces, add <meta name="robots" content="max-image-preview:large"> and use big images — at least 1,200px wide, high resolution, ideally 16:9. Google’s own case study documented real CTR lift from enabling large previews (a food blog at +79% CTR from Discover; a news site at +30% CTR / +332% clicks over six months). This is one of the few image changes with directly measurable upside.

Stock vs. unique images

Mueller’s position is worth quoting plainly: stock photography “doesn’t matter for web search directly,” but “for image search, if it’s the same image as used in many places, it’ll be harder.” And separately: “uniqueness isn’t equivalent to higher quality” — taking the photo yourself doesn’t automatically rank it better. So: use stock freely if you only care about web rankings; use unique imagery when image-search visibility matters, because a one-of-a-kind image has nothing to compete with.

Emerging: AI-image labeling (C2PA / IPTC)

Worth flagging because it’s new and most guides miss it: Google reads IPTC copyright fields (which can show as attribution credit in Google Images — free brand visibility) and uses IPTC / C2PA metadata to identify AI-generated images, surfacing an “AI generated” label via the “About this image” feature. Camera EXIF (ISO, aperture, GPS) has no documented ranking effect — strip it for performance, but preserve the copyright fields. This space is still evolving.

Where to go next

This hub is the map. The deep dives and adjacent topics:

• Alt text — the full treatment of the alt attribute: why it’s image-search-not-web-search, accessibility/legal stakes, writing rules, decorative images, linked-image anchor textAnchor text is the visible, clickable text of a hyperlink. It tells readers what they'll find on the other end and gives search engines context about the linked page., and auditing at scale. It’s the one sub-topic deep enough to warrant its own article.
• Ranking in Google Images — the deep dive on visibility specifically in Google Images and Lens: indexing requirements, licensable images, and the myths top-ranking pages still repeat.
• Image formatsThe file encoding used to store an image (JPEG, PNG, WebP, AVIF, SVG, GIF) — it drives file size and Core Web Vitals, but carries no direct ranking weight. — JPEG vs. PNG vs. WebP vs. AVIF up close: what each format is actually good for, and why the format switch itself isn’t a ranking factor.
• Core Web Vitals — image SEO’s performance half lives here. Compression, LCP, and fetchpriority are really Core Web Vitals work wearing an image hat.
• Structured data — ImageObject, Product/Article image arrays, and og:image thumbnail control are part of the broader structured-data story.
• Image sitemaps — the discovery mechanics, the deprecated-by-Google-but-kept-for-Bing tags, and cross-domain CDN URLs.

AI summary

A condensed take on the Advanced version:

• Image SEOImage SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps. is two jobs: (1) ranking in image search (Google Images / Lens / Bing) — driven by alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., filenames, page context, and uniqueness; and (2) page performance, because images are usually the LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. element feeding Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data..
• Discovery mechanics: Google indexes <img> (including inside <picture>), not CSS backgrounds; always keep a fallback src; supported formats are BMP, GIF, JPEG, PNG, WebP, SVG, AVIF.
• Formats give no direct ranking boost (Mueller, on AVIF; WebP is “fine”). The win is speed. Pick AVIF/WebP for compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits., PNG for transparency, SVG for icons.
• Filenames: descriptive names help new images; don’t bulk-rename existing ones (minimal/no effect, weeks of churn — Mueller; signal loss ~“a few weeks” — Illyes).
• Alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search. primarily helps image search, not web rankings — covered in its own article.
• Lazy loadingLazy loading defers loading of off-screen or non-critical resources — usually images and iframes — until they're about to enter the viewport. The native way to do it is the loading=\"lazy\" HTML attribute, which needs no JavaScript.: native loading="lazy" is safe below the fold; JS that hides the URL in data-src is risky; never lazy-load the LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. image — use fetchpriority="high".
• URL consistency (May 2025): reference the same image at the same URL everywhere; match mobile and desktop URLs.
• Structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.: ImageObject + license = licensable badgeImageObject is the schema.org type that describes an image as structured data. It's rarely used alone — its main job is as the value of an image or logo property nested inside another type (Product.image, Article.image, Recipe.image, Organization.logo). You upgrade a plain image URL to a full ImageObject when you want to attach metadata: who owns the image, how it can be licensed, its caption, or its dimensions. Adding the license property is what makes an image eligible for Google's Licensable badge.; Product/Article want multi-aspect-ratio image arrays; primaryImageOfPage / og:image influence thumbnails.
• Image sitemapsAn image sitemap is a sitemap (or an extension added to an existing sitemap) that lists the images on your pages using Google's image namespace, helping Google discover images it might otherwise miss. aid discovery (CDN, big galleries, JS sites); Google kept only <image:image> / <image:loc> (deprecated the rest in May 2022 — Bing still uses them).
• Discover: max-image-preview:large + 1,200px / 16:9 images; documented CTR lift.
• Stock vs. unique: stock is fine for web search, harder for image search; uniqueness ≠ higher quality. AI-image labeling via C2PA/IPTC is emerging; EXIF doesn’t rank.

Official documentation

Primary-source documentation from the search engines.

Google

• Google Images best practices — the core reference: discovery via <img>, supported formats, descriptive filenames, alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., responsive images, URL consistency, preferred-image selection, and opting out of inline linking.
• Image sitemaps — the supported <image:image> / <image:loc> tags, cross-domain URLs for CDNs, and the 1,000-image-per-URL limit.
• Image license structured data — ImageObject, required/recommended fields, and the licensable badgeImageObject is the schema.org type that describes an image as structured data. It's rarely used alone — its main job is as the value of an image or logo property nested inside another type (Product.image, Article.image, Recipe.image, Organization.logo). You upgrade a plain image URL to a full ImageObject when you want to attach metadata: who owns the image, how it can be licensed, its caption, or its dimensions. Adding the license property is what makes an image eligible for Google's Licensable badge..
• Article structured data — the recommended image array and aspect ratios (16:9, 4:3, 1:1).
• Product snippet structured data — product image recommendations.
• Fix lazy-loaded content — native loading="lazy" / IntersectionObserver, and why interaction-triggered loading hides content from Google.
• Robots meta tag — max-image-preview — unlocking large image previews in Search and Discover.
• Large images case study — Google’s own CTR-lift data from enabling large previews.
• Prevent images appearing in search — robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. (Googlebot-Image), X-Robots-Tag: noindex, and the Removals toolA Google Search Console feature for verified owners to manage how their URLs appear in Search. A Temporary Removal hides a URL for about six months — it does not delete the page from the index..
• Mobile-first indexing best practices — matching image URLs, alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., and filenames across mobile and desktop.

Bing / Microsoft

• Being a part of the Bing Image Search ecosystem — Bing’s image discovery and the metadata it uses (note: Bing still uses the image-sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. tags Google deprecated).
• Bing Visual Search — object-level visual searchMultimodal search lets you query and get results across more than one modality — text, images, video, and audio together. Instead of typing words, you can point your camera, circle something on screen, or combine an image with a question, and the system understands them jointly. and what helps Bing match images.

Quotes from the source

On-the-record statements from Google. Where a page exposes the text, the link is a deep link that jumps to the quoted passage.

Google docs — discovery and filenames

• “Google parses the HTML <img> elements (even when they’re enclosed in other elements such as <picture> elements) in your pages to indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. images, but doesn’t index CSS images.” Jump to quote
• “The filename can give Google clues about the subject matter of the image.” Jump to quote

Google spokesperson — URL consistency (May 2025)

• “We updated the Google Image SEOImage SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps. best practices to clarify that URLs for images should be referenced consistently for easier crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. on larger websites.” Coverage

John Mueller, Google — formats give no SEO boost

• On AVIF: there is no “SEO boost” for using AVIF files — the benefit is indirect, via page speed. Coverage
• On WebP: “WebP images are fine for Image Search.” Coverage

John Mueller, Google — don’t bulk-rename files

• “If you change all of the filenames across the website, then it’s going to take a lot of time for Google’s systems to see” the new images — and the effect is “minimal effect, maybe no visible effect at all” if alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search. and surrounding context are already in place. SEJ coverage

John Mueller, Google — stock vs. unique images

• Stock photography “doesn’t matter for web search directly,” but “for image search, if it’s the same image as used in many places, it’ll be harder.” Coverage
• “Uniqueness isn’t equivalent to higher quality” — taking a photo yourself doesn’t necessarily make the page or image rank higher. Coverage

John Mueller, Google — image streaming

• EmbeddingEmbeddings are dense numerical vectors — lists of floating-point numbers — that represent the meaning of text in a high-dimensional space. Semantically similar content lands close together, so search and AI systems can match by meaning, not just keywords. images via streaming is “a great way to prevent your images from being foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. through search engines” — i.e. it’s not SEO-friendly. Coverage

Gary Illyes, Google — image migration signal loss

• Signal loss from image URL migrations is “in line with web search results, which is a few weeks.” Coverage

Image SEO cheat sheet

The factors — what each does and the best practice

Fast facts

• Supported formats: BMP, GIF, JPEG, PNG, WebP, SVG, AVIF (AVIF since Aug 2024).
• Google indexes <img> (incl. inside <picture>) — not CSS background-image.
• No direct ranking boost for WebP/AVIF — the benefit is speed → Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data..
• EXIF (ISO/aperture/GPS): no ranking effect; IPTC copyright fields can show as credit.
• C2PA/IPTC: used to label AI-generated images in Google (“About this image”) — emerging.

The mental model

Image SEOImage SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps. is two jobs, not one. Almost every “image SEO checklist” blurs this together, and blurring it is exactly why the myths (rename your files! switch to WebP for rankings!) keep spreading. Split it into the two goals it actually is, and each piece of advice sorts itself into the right bucket:

1. Ranking in image search. Getting your images foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. in Google Images, Bing Images, and Google LensMultimodal search lets you query and get results across more than one modality — text, images, video, and audio together. Instead of typing words, you can point your camera, circle something on screen, or combine an image with a question, and the system understands them jointly. for image-specific queries. The levers here are alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., filenames, the text surrounding the image, structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., and image uniqueness. None of this touches how fast the page loads.

2. Page performance. Images are almost always the heaviest thing on a page, which makes them the usual culprit for a slow Largest Contentful PaintLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. (LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good.) — and LCP feeds Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data., a web-search ranking signal. The levers here are format, compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits., and loading strategy. None of this touches whether the image shows up in Google Images.

Why the split matters in practice:

• It kills the format myth. WebP and AVIF don’t rank you higher in image search — that’s not what they’re for. They’re a performance-bucket lever (smaller files → faster LCP → Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data.), not an image-search-bucket lever. Expecting a ranking boost from a format switch is applying a performance tool to an image-search problem.
• It kills the bulk-rename myth. Filenames are an image-search-bucket signal, and a minor one at that. Renaming your whole existing library doesn’t touch the performance bucket at all, and Mueller’s read is that the image-search payoff is “minimal… maybe no visible effect” if your alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search. and context are already solid — so it’s weeks of churn for a small win in only one of the two buckets.
• It tells you where lazy loadingLazy loading defers loading of off-screen or non-critical resources — usually images and iframes — until they're about to enter the viewport. The native way to do it is the loading=\"lazy\" HTML attribute, which needs no JavaScript. belongs. loading="lazy" is a performance-bucket decision (defer off-screen images to help load time), and it has one hard exception at the intersection of both buckets: the LCP image. Lazy-load that one and you’ve made the performance bucket worse for no gain in the image-search bucket.
• It explains why alt text and compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits. aren’t interchangeable advice. Alt text is almost entirely an image-search-bucket lever (plus accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all.); compression is almost entirely a performance-bucket lever. A page can have perfect alt text and still have a terrible LCP, or a blazing-fast LCP image with no alt text and zero image-search visibility. Fixing one doesn’t fix the other.

Use the split as a diagnostic: when an image “isn’t working,” first decide which job it’s failing at. Not showing up in Google Images? Look at alt text, filename, and uniqueness. Page is slow? Look at format, compression, and lazy-loading choices. Trying to fix an image-search problem with a performance lever (or vice versa) is the most common wasted effort in this topic.

The standing KPIs: image-search visibility and image-driven page speed

Because image SEOImage SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps. is two jobs, the health checks split the same way — one set for image-search visibility, one set for the performance/Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. side.

Image-search impressions and clicks (Search Console)

• Metric — Impressions and clicks specifically from Google Images, tracked over time as a share of total Search traffic.
• What it tells you — Whether your alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., filenames, page context, and image uniqueness are actually earning visibility in image search — the first of the two jobs. A flat or falling Images share while overall traffic grows is a sign the image-search side is being neglected relative to the web-search side.
• How to pull it — Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. → Search results report → filter by Search type: Image. Compare impressions/clicks/CTR/position against the default Web filter for the same pages and date range.
• Benchmark / realistic range — There’s no universal target share — an image-heavy site (recipes, product photography, stock/portfolio sites) should expect a meaningfully larger Images share than a text-heavy B2B blog. Establish your own baseline the first time you check, then watch the trend rather than chasing a fixed number.
• Cadence — Quarterly as a standing check; re-check within a few weeks of any large-scale image change (bulk rename, CDN migration, new alt-text pass) — Illyes’ read on migration signal loss puts the re-settling window at “a few weeks.”

Core Web Vitals pass rate, filtered to image-heavy templates

• Metric — The share of real-user page loads passing LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. (and CWV overall), specifically for templates where the LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. element is typically an image (product pages, blog hero images, galleries).
• What it tells you — Whether the performance half of image SEO — compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits., format choice, and correct lazy-loading — is actually holding up under real-world conditions. This is the field-data proof that the never-lazy-load-the-LCP-image rule and format/compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits. choices are working.
• How to pull it — PageSpeed InsightsPageSpeed Insights (PSI) is a free Google tool at pagespeed.web.dev that reports two kinds of data for a URL: real-user field data from the Chrome UX Report and a single Lighthouse lab run with the 0–100 Performance score. Only the field Core Web Vitals are what Google uses for ranking. or the Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. report in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. (CrUXChrome User Experience Report — Google's public dataset of real-world (field) performance data from eligible Chrome users. It's the official field-data source behind the Core Web Vitals program.-backed), segmented by template/page group rather than site-wide averages, which can hide a badly performing template behind well-performing ones.
• Benchmark / realistic range — Google’s published “good” LCP threshold is 2.5 seconds or faster at the 75th percentile — that’s a real, documented number, not a guess. Treat it as the pass/fail line; there’s no honest “typical” number beyond it since it depends entirely on your image weight and hosting.
• Cadence — CrUXChrome User Experience Report — Google's public dataset of real-world (field) performance data from eligible Chrome users. It's the official field-data source behind the Core Web Vitals program. field dataPerformance metrics captured from real users, not lab tests. is a rolling 28-day window, so check monthly; re-check immediately after any change to image formatThe file encoding used to store an image (JPEG, PNG, WebP, AVIF, SVG, GIF) — it drives file size and Core Web Vitals, but carries no direct ranking weight., compression pipeline, or lazy-loading implementation.

Resources worth your time

My related writing

• Image SEO: 12 Actionable Tips for More Organic Traffic — Ahrefs’ image SEOImage SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps. guide (filenames, alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., formats, compressionCompression (HTTP content encoding) shrinks text-based responses — HTML, CSS, JS, JSON, SVG, XML sitemaps — before they're sent over the network, using an algorithm like Gzip, Brotli, or Zstd, so the browser or crawler downloads fewer bytes. It's not a ranking factor, but it speeds up page loads and helps pages stay under crawler fetch limits., sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., responsive images, schema, lazy loadingLazy loading defers loading of off-screen or non-critical resources — usually images and iframes — until they're about to enter the viewport. The native way to do it is the loading=\"lazy\" HTML attribute, which needs no JavaScript., CDN).
• The Beginner’s Guide to Technical SEO — where images and Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. fit into the broader technical picture.
• JavaScript SEO Issues & Best Practices — the renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. side, plus blank alt attributes left behind by JS frameworks.
• Ahrefs Site Audit Study — the 1M+ domain study where missing alt attributes were the single most common technical issue (80.4% of sites).

My speaking

• “Image SEO” (Visme webinar, 2021) — my dedicated talk on optimizing images for search.

Official

• Google’s Google Images best practices — the canonical reference for everything on this page.
• Google’s Large images case study — real CTR-lift data from enabling large image previews.

From around the industry

• Google on Image Filenames & a Surprising SEO Mistake (Search Engine Journal) — Mueller’s recorded session advice: bulk-renaming has “minimal, maybe no visible effect at all” if alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search. is already good.
• Google Shows How to Use Alt Text for SEO (Search Engine Journal) — Mueller on alt text as primarily an image-search signal, not a direct web-ranking factor.
• Google Updates Image SEO Best Practices: URL Consistency (Search Engine Land) — coverage of the May 2025 update clarifying same-URL-for-same-image guidance.
• Google Uses Schema.org + og:image for Thumbnails (Search Engine Land) — March 2026 update on preferred-image signals in Search and Discover.
• Fetch Priority API (web.dev) — the canonical explainer for fetchpriority="high" on LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. images; the reference behind “never lazy-load your hero.”
• Let’s Talk Image SEO (Search Off the Record, Google, Oct 2022) — Lizzi Sassman and John Mueller discussing image naming, alt text, and crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. directly.
• Image SEO: Multimodal AI (Search Engine Land) — how AI-powered visual understanding is shifting image-search optimization.
• Image Migrations and Lost Signals (GSQI) — Gary Illyes on the ~few-weeks signal-loss window when image URLs change.

Test yourself: Image SEO

Five quick questions on the myths and mechanics this hub covers. Pick an answer for each, then check.

Image SEO

Image SEO is optimizing the images on your pages so search engines can discover, crawl, index, and rank them — in Google Images and visual search, and as part of standard web results. It spans file format, filenames, alt text, compression, responsive markup, structured data, and image sitemaps.

Related: Alt Text, Image sitemap, Core Web Vitals, Structured Data

Image SEO

Image SEO is the practice of optimizing the images on a web page so search engines can find, understand, and rank them — both in dedicated surfaces like Google Images, Google LensMultimodal search lets you query and get results across more than one modality — text, images, video, and audio together. Instead of typing words, you can point your camera, circle something on screen, or combine an image with a question, and the system understands them jointly., and Bing Images, and as the images that appear inline in standard web results, Discover, and AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index..

It covers two distinct goals that need different work. The first is ranking in image search — getting your images foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. for image-specific queries, which is driven mostly by alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., filenames, surrounding page context, and image uniqueness. The second is page performance — images are usually the largest thing on a page, so how you format, compress, and load them feeds directly into Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. (especially Largest Contentful PaintLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good.), which is a web-search ranking signal.

A few things are worth getting right up front. Google indexes images referenced in HTML <img> elements (including inside <picture>), not CSS background images. The supported formats are BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF — and choosing a “next-gen” format gives no direct ranking boost; the benefit is purely faster pages. Descriptive filenames help, but you shouldn’t bulk-rename images on a live site. And alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search. — covered in depth in its own article — primarily helps image search, not web rankings.

Related: Alt Text, Image sitemap, Core Web Vitals, Structured Data

Changelog