Image SEO in 2026: Format, Size, Filenames, Alt Text and Loading — What Matters

Page speed is a confirmed ranking consideration (as Core Web Vitals, a tiebreaker at the margin), and images are the slow part of most pages. The measurable chain, in order of size: serve next-gen formats (AVIF/WebP beat JPEG by 30-60% at equal quality), size the file to the actual display dimensions (a 4000 px photo into a 800 px slot wastes ~90% of its bytes), compress with the image compressor (quality 80-85 is visually identical for web photos — the compression guide walks the slider), and set width/height or aspect-ratio on every <img> so the page does not jump while loading (that jump is Cumulative Layout Shift, a CWV metric itself).

The single most damaging image mistake on modern sites is lazy-loading the hero image. The loading="lazy" attribute tells the browser to defer until the image nears the viewport — for the LCP element that defers the very thing being measured, costing hundreds of milliseconds and turning a green CWV page amber. Rule: loading="eager" (or no attribute) plus fetchpriority="high" on the hero; loading="lazy" on everything below it.

Alt text's job is to make the page complete when the image cannot be seen — screen-reader users reading the page linearly, sighted users on broken images, and machines that infer content from it. The working standard is the read-aloud test: if the alt phrase would sound bizarre read aloud in the sentence around the image, rewrite it. 'Blue widget mounted on a DIN rail, shown with the included cable gland' is good alt; 'blue widget | best blue widget | widget reviews 2026' is alt text that hurts your conversion-free readers and does literally nothing extra for rankings.

Choose alternative text by the image's role: informative, decorative, or functional. Decorative images normally use an empty alt attribute; linked icons need an accessible name that explains their action. Put important image text into accessible page content instead of relying on OCR. The alt-text decision guide includes contextual examples and explains charts, linked logos, and when repeating nearby text becomes unhelpful.

The myth: hyphenated keyword filenames are a major ranking lever. The reality: Google's own statements over the years are that filenames are a minor contribution ('blue-widget.jpg' beats 'DSC_0481.jpg' in roughly the way a sensible URL beats a query-string mess) and keyword-stuffing them is ignored at best. So: descriptive, short, hyphen-separated, done — then spend the saved minutes on bytes, which are measured.

One filename practice with a real upside that is not about rankings: unique filenames. 'logo.png' overwritten twelve times makes debugging and cache behaviour a nightmare; versioned or content-named files ('widget-front-45deg.png') keep a site's image inventory intelligible to the humans maintaining it, which is the actual reason to think for ten seconds before upload.

When images are the content — product listings, portfolios, recipe galleries, real-estate photos — machine-readable discovery pays: an image sitemap (or the ImageObject in existing product/recipe/Article schema) tells Google which images represent which pages, with captions and titles that can surface in image search with a click back to the source. For a page where images are illustrative only, an image sitemap is optional overhead.

The rich-results angle that matters more in 2026 than the image sitemap itself: if your page type supports structured data (products, recipes, articles), matching the schema image to the on-page hero gives eligibility for layouts that display large image thumbnails in results — the visual real estate that actually moves click-through, and the one image SEO task with a directly measurable payoff.

Choose a format after comparing representative outputs. Match source widths to the actual layout with the responsive image guide, using the retina sizing guide to assess density without enlarging weak originals. Reserve layout space, keep the likely LCP image discoverable and eagerly loaded, and evaluate the page's total transfer budget. Confirm alt text, caching, and actual delivered dimensions; no single byte target is right for every website. The image is only one line of the search result, though — the page's title tag and meta description decide the headline and snippet above it, and the title and meta description guide covers that text half of on-page SEO.

And the one-line test that catches most mistakes without any tooling: open the page on a throttled connection, right-click → inspect the hero, and read its actual delivered dimensions and weight against the slot it fills. A 3 MB 3840 px image in an 800 px frame is visible in the HTML itself — the fix is the compressor and the resizer, and it is the biggest win on the page.

For layout prototypes, the placeholder-image workflow helps establish realistic slots before final artwork arrives. On a WordPress site, the WebP publishing guide covers thumbnail generation and media migration. Keep descriptions useful to readers and test the delivered page: better metadata and smaller files cannot guarantee indexing or rankings.