Image SEO: How to Optimize Images for Google Search

Why Image SEO Matters

Image SEO is the practice of optimizing images on your website so they rank in Google Images, contribute positively to page speed and Core Web Vitals, and enhance the overall search visibility of the pages they appear on.

According to SparkToro research, Google Images accounts for approximately 22% of all web searches, making it the second-largest search engine after Google's main web search. Yet many websites give image optimization minimal attention, treating images as purely decorative elements rather than discoverable assets.

Image optimization also has a direct impact on page speed. HTTP Archive data shows that images account for roughly 45% of the total weight of an average web page. Poorly optimized images are the number one cause of slow Largest Contentful Paint (LCP) scores, which directly affect rankings.

The three benefits of image SEO are:

• Direct traffic from Google Images: Users discovering your content through image search results
• Enhanced page rankings: Well-optimized images contribute to page quality signals including load speed and content richness
• Accessibility: Proper alt text ensures visually impaired users can understand your content, which also satisfies a Google quality criterion

Fast-loading, properly optimized images also improve engagement metrics. When pages load quickly with smooth visual rendering, users are more likely to stay and interact with content. Monitoring the relationship between image performance and user engagement through tools like the Sentinel Dwell Time Bot can reveal which pages benefit most from image optimization efforts.

File Names and Image Formats

Image file names are a direct ranking signal for Google Images. Google uses the file name to understand the image's content, especially when other signals are limited.

File Naming Best Practices

• Use descriptive, keyword-relevant names: blue-ceramic-coffee-mug.webp instead of IMG_4523.jpg
• Separate words with hyphens (not underscores or spaces)
• Keep names concise but descriptive (3-6 words)
• Include the primary keyword when relevant
• Use lowercase letters exclusively

Image Format Comparison for 2026

In 2026, WebP should be your default format for photographs and complex graphics. According to Google's WebP documentation, WebP images are 25-34% smaller than comparable JPEG images at equivalent quality. AVIF offers even better compression but has slightly lower browser support. Use the <picture> element to serve AVIF with WebP and JPEG fallbacks.

Alt Text Optimization

Alt text (alternative text) serves two purposes: it provides accessibility for screen reader users and it gives Google textual context about the image. According to Google's image best practices, alt text is one of the primary signals used to understand what an image is about.

Alt Text Rules

• Be specific and descriptive: Describe what is actually in the image, not what you wish the image represented
• Include keywords naturally: If the image is relevant to a target keyword, include it in the alt text where it fits naturally
• Keep it concise: Aim for under 125 characters. Screen readers may truncate longer alt text
• Do not start with "Image of" or "Picture of": Screen readers already announce that the element is an image
• Decorative images get empty alt: Images that are purely decorative should use alt="" so screen readers skip them

Alt Text Examples by Context

For more on integrating alt text into your overall page optimization, see the image section in our on-page SEO guide.

Image Compression and Performance

Image compression is the single biggest lever for improving page load times on image-heavy pages. The goal is to reduce file size as much as possible without visible quality degradation.

Compression Guidelines

Compression Tools

• Squoosh (by Google): Browser-based tool for manual compression with side-by-side quality preview
• Sharp (Node.js): Programmatic image processing for build pipelines
• ImageMagick: Command-line tool for batch processing
• Cloudflare Polish / Cloudinary: Automatic compression at the CDN level

Impact on Core Web Vitals

Unoptimized images are the most common cause of poor LCP scores. The LCP element (the largest visible content in the viewport) is frequently a hero image. According to Google's LCP documentation, a good LCP score is under 2.5 seconds. Compressing your LCP image alone can often bring a failing page into the "good" threshold.

Image optimization is a core component of the speed audit in our technical SEO audit checklist. Poorly optimized images not only hurt page speed but also degrade engagement metrics. The Sentinel Bounce Rate Bot can help you identify pages where slow image loading correlates with high bounce rates.

Responsive Images and Srcset

Responsive images ensure that every user receives an appropriately sized image for their device and viewport. Without responsive images, mobile users download full-resolution desktop images, wasting bandwidth and increasing load times.

The Srcset Attribute

The srcset attribute tells the browser which image sizes are available, allowing it to choose the best option:

<img
  src="product-800.webp"
  srcset="product-400.webp 400w, product-800.webp 800w, product-1200.webp 1200w"
  sizes="(max-width: 600px) 400px, (max-width: 1200px) 800px, 1200px"
  alt="Blue ceramic coffee mug on a wooden table"
  width="800"
  height="600"
  loading="lazy"
>

Image Size Recommendations

Always include explicit width and height attributes on image elements. This allows the browser to reserve the correct space before the image loads, preventing Cumulative Layout Shift (CLS), which is a Core Web Vital metric. For more on mobile-specific considerations, see our mobile SEO guide.

Lazy Loading Implementation

Lazy loading defers the loading of offscreen images until the user scrolls near them. This reduces initial page load time and improves LCP scores by allowing the browser to prioritize above-the-fold content.

Native Lazy Loading

Modern browsers support native lazy loading via the loading attribute. This is the simplest implementation and requires no JavaScript:

• loading="lazy" for below-the-fold images that should be deferred
• loading="eager" (or omit the attribute) for above-the-fold images that must load immediately

Critical Rule: Never Lazy Load the LCP Image

The most common lazy loading mistake is applying it to the hero image or the largest content element in the viewport. This delays the LCP measurement and directly hurts your Core Web Vitals score. According to Google's lazy loading guide, always load the first one to two images (above the fold) eagerly and only lazy load images further down the page.

Fetchpriority for LCP Images

For the LCP image specifically, add fetchpriority="high" to tell the browser to download it as a high-priority resource:

<img src="hero.webp" alt="description" width="1200" height="600" fetchpriority="high">

This is especially important for images loaded from a CDN or a different origin, where browser prioritization heuristics may not automatically assign high priority.

Image Sitemaps

An image sitemap helps Google discover images on your site, particularly those loaded dynamically via JavaScript or CSS that crawlers might miss during standard HTML parsing.

When Image Sitemaps Matter

Image sitemaps are most valuable for:

• E-commerce sites with thousands of product images
• Photography or portfolio sites where images are the primary content
• Sites using JavaScript frameworks that load images dynamically
• Sites with images served from CDN subdomains

According to Google's image sitemap documentation, you can add image information to your existing XML sitemap or create a separate image-specific sitemap. Include the image URL, title, caption, and geographic location if relevant.

Image Sitemap Structure

Add <image:image> tags within each <url> entry in your sitemap. Each page can declare up to 1,000 images. For most sites, including the primary images per page is sufficient. Do not include decorative background images or UI elements.

For e-commerce sites specifically, image sitemaps are crucial for ensuring that product images are indexed in Google Images, which can drive significant additional traffic. See our e-commerce SEO guide for more on product image strategies.

Structured Data for Images

Structured data can enhance how your images appear in Google search results. Several schema types include image properties that Google uses for rich results.

Image-Related Schema Types

When implementing schema that includes images, use high-quality images that meet Google's minimum requirements: at least 1200 pixels wide for Article schema and at least 600x600 pixels for Product schema. These requirements are documented in Google's structured data guidelines.

For a comprehensive overview of all schema types and their implementation, see the structured data section in our technical SEO audit checklist.

Image CDN and Delivery Optimization

An image CDN (Content Delivery Network) serves images from servers geographically close to the user, reducing latency and improving load times. Modern image CDNs also provide automatic format conversion, responsive resizing, and compression on the fly.

Image CDN Features

Implementation Considerations

When using an image CDN, ensure that Google can still crawl and associate images with your domain. Use a CDN subdomain (e.g., images.yourdomain.com) rather than the CDN's default domain to maintain brand association. Include images served from CDN subdomains in your image sitemap to ensure discovery.

For sites that rely on advertising revenue, image optimization has a dual benefit: faster-loading pages improve both ad viewability and user engagement. The Sentinel AdSense Clicker Bot can help you understand how image load performance affects ad revenue per page view.

Combine image CDN delivery with the responsive image and lazy loading techniques discussed earlier for the best possible image performance. Together, these techniques can reduce total image payload by 60-80% compared to unoptimized images, dramatically improving both Core Web Vitals and user experience.

FAQ

Does Google index images loaded via JavaScript?

Google can index JavaScript-loaded images, but it requires a second rendering pass which introduces delays. Images in the initial HTML are discovered and indexed faster. For critical images, include them in the HTML source. For dynamically loaded images (e.g., in carousels or galleries), ensure they are included in your image sitemap to aid discovery.

Should I use WebP or AVIF for my images?

WebP is the safer default choice due to broader browser support (97%+). AVIF offers better compression but has slightly lower support (92%+). The ideal approach is to serve AVIF as the primary format with WebP as a fallback using the HTML picture element, and JPEG as a final fallback for the oldest browsers.

How much does image optimization affect page speed scores?

Image optimization is typically the single largest factor in page speed scores. Properly optimizing images can improve PageSpeed Insights scores by 20-40 points. For image-heavy pages (portfolios, e-commerce, galleries), the impact can be even greater. Focus on the LCP image first, as it has the most direct impact on Core Web Vitals.

Do images with text in them get indexed by Google?

Google can use OCR (optical character recognition) to read some text within images, but it is far less reliable than HTML text. Never use images of text when HTML text would serve the same purpose. If you must use text in images (infographics, diagrams), ensure the same information is also available as HTML text on the page and describe the content in the alt text.

How many images should I include per page?

There is no maximum, but each image should serve a purpose, whether illustrating a concept, showing a product, or breaking up text for readability. For blog content, one image per 300-500 words is a common guideline. For product pages, four to eight images showing different angles and details is typical. What matters most is that every image is properly optimized so additional images do not significantly increase page load time.