Image SEO

Images and SEO in 2026: The Practical Guide to Better Rankings

You've compressed your images, chosen WebP, enabled lazy loading, and your pages aren't moving up. The problem is often not speed. It's the entire set of signals Google expects from your images, in the right order.

9 min read

Why images weigh on your rankings

Images typically represent 50 to 70% of the total weight of a page containing visuals. This weight has a direct impact on Largest Contentful Paint, the Core Web Vitals signal Google uses to measure perceived page speed.

But performance is only one of two reasons to optimize images for SEO. The other is indexation. Google can analyze your images, read their context, classify them in Google Images, and have them appear in visual search. An image without alt text, without a descriptive filename, without structured data: that’s an image Google treats as visual noise.

These two dimensions are often treated separately. In 2026, they are inseparable.

For more on the link between images and Core Web Vitals, see: Optimize your images for Core Web Vitals and LCP.

Naming files: the basics often overlooked

The name of an image file is read by Google before it even analyzes its content. IMG_4832.jpg transmits no semantic signal. compress-image-webp-lossless.webp transmits several.

The rules are simple, and rarely applied systematically:

• Use hyphens as separators (-), never underscores or spaces
• Include the main keyword or a factual description
• Stay concise: 3 to 5 words are sufficient
• Lowercase, no accents

In practice, the filename is not a major ranking signal taken in isolation. Combined with alt text and the page’s textual context, it strengthens the semantic coherence that Google attributes to the image. It’s the accumulation of these coherent signals that matters.

Alt text: the golden rule and mistakes to avoid

The alt attribute serves two functions: accessibility (read by screen readers) and SEO (text signal for Google). Both goals converge on the same best practice — describe precisely what the image shows.

The golden rule: describe the image as if you were explaining it to someone who can’t see it.

An effective alt text looks like: "Comparison of image weight JPEG vs WebP — 34% reduction for identical visual quality". Factual, descriptive, natural.

Depending on context, including the main keyword in the alt text of the most important image on the page — usually the one that triggers LCP — is a coherent practice. Without making it a mechanical rule applied to every image.

Format and compression: WebP, AVIF and the 100 KB rule

The choice of image format has a direct impact on LCP, and therefore on the signal Google receives to evaluate your page’s performance.

WebP is supported by 95.6% of modern browsers (caniuse.com, May 2026). It’s the reference format for most web uses: photos, illustrations, screenshots. It offers weight reduction of 25 to 35% compared to JPEG for equivalent visual quality.

AVIF compresses even better — on the order of 40 to 50% compared to JPEG — but its browser support reaches 94.3%, slightly below WebP. In practice: AVIF is the best technical choice, WebP remains the most universal choice.

PNG retains relevance for images with transparency or screenshots requiring perfect text sharpness. For photos, its weight is structurally superior to WebP — to be avoided in that case.

The “100 KB rule” is not an official Google standard. It’s a practical benchmark: an image content under 100 KB generally allows maintaining LCP under 2.5 seconds, the “good” threshold for Core Web Vitals.

One last often-ignored point: the srcset attribute allows serving different-sized images depending on screen resolution. A mobile visitor shouldn’t download the same image as a 4K screen visitor. Implementing responsive images via srcset reduces average perceived weight — and improves LCP on mobile, the segment where Google prioritizes evaluation.

Lazy loading and CLS: avoiding pitfalls

Lazy loading (loading="lazy") defers loading images off-screen. It reduces initial load time and can improve LCP — provided you don’t apply it to the main image on the page.

CLS related to images has a simple cause: an image whose dimensions are not declared in the HTML. The browser cannot reserve the necessary space, which causes a visual jump when the image loads.

The fix is straightforward: always declare width and height on every <img> tag. The browser calculates the ratio and reserves space, even before the image loads.

Google Images: capturing visual traffic

Google Images is a traffic channel often overlooked. For sites publishing original images — tutorials, e-commerce, photography — it’s a second distinct acquisition channel measurable in Google Search Console, distinct from text traffic.

For an image to appear in Google Images meaningfully, several conditions must be met:

Text context — Google reads the text around the image to understand what it’s about. An image surrounded by relevant content is indexed better than an image isolated on an empty page.

ImageObject structured data — The ImageObject schema from schema.org allows you to explicitly convey the title, description, and license of an image to Google. Particularly useful for original images, infographics or brand visuals.

Stable URL — An image accessible via a permanent URL is more easily indexed than an image whose path is dynamically generated or changes regularly.

Sufficient resolution — Google Images favors images with resolution suitable for display. A 200×150 pixel image has little chance of appearing in visual results for generic queries.

Images in background-image CSS are harder to index: they don’t carry alt text and their semantic context is less readable to the crawler. For images you want to appear in Google Images, prefer <img> tags in the HTML.

Image sitemap: create, submit, verify

An image sitemap explicitly lists your site’s images for Google. It doesn’t guarantee indexation — but it accelerates discovery, especially for images outside the HTML body: images loaded via CSS, JavaScript, or advanced lazy loading.

Minimal structure of an entry:

<url>
  <loc>https://example.com/blog/my-article/</loc>
  <image:image>
    <image:loc>https://example.com/images/articles/my-image.webp</image:loc>
    <image:title>Descriptive image title</image:title>
    <image:caption>Short description</image:caption>
  </image:image>
</url>

For submission: Google Search Console → Sitemaps → Add URL. Then verify in the console that it’s processed without format errors.

Most CMSs automatically generate a sitemap including images if the configuration provides for it. For static sites — Astro, Next.js, Eleventy — plugins like astro-sitemap can be configured to include image:image entries.

For sites with few images directly accessible in HTML, the impact of an image sitemap is marginal. It becomes relevant once important images aren’t naturally crawled.

SEO images checklist: 10 points to audit

GlitchGhost

Independent Developer

Independent developer specializing in web performance tools and image optimization.

Web DeveloperPerformance SpecialistCreator of Impmage