Image SEO: useful pictures and understandable files

Image SEO helps a search engine understand an image and its page, while helping people decide whether the page answers their need. A descriptive file name and alt text matter, but they cannot rescue an irrelevant stock image or a page with no useful context. Start with the role of the picture in the reader's task, then make it discoverable, accessible and fast.

Choose images that answer a question

For a product, show the item from angles that reveal size, material, controls, packaging or what arrives in the box. For a tutorial, show the exact step that is hard to explain in words. For a comparison, use a diagram that makes the difference visible. A decorative image may support the page's tone, but it should not be the only visual evidence.

Write down the question each important image answers. “What is included?” may call for a photograph of all components. “How does it fit?” may need a scale reference or dimensions. “Where is this setting?” may need an annotated screenshot. If the answer is already obvious without the picture, the image may be decorative.

Use images you have the right to publish. Record the source, creator, license or permission and any required credit. Do not download a competitor's product photo because it appears in search results. If a product changes, replace images that no longer show what buyers receive.

Make images crawlable

Google recommends standard HTML <img> elements with a src URL. It does not index CSS background images as content images in the same way; its image SEO guidance explains discovery and rendering. A responsive <picture> or srcset setup should still provide a usable src fallback.

Test the page as a logged-out visitor. The image URL should return successfully, avoid authentication, and load on mobile. Check whether lazy loading actually loads an image when it approaches the viewport. Images hidden behind a click-only interface may be harder to discover and less useful to readers who never open it.

An image sitemap can help surface images that are otherwise difficult to discover, but it does not make a poor page valuable. Check the page and image first. If you use a CDN, keep URLs stable where practical and verify that the server does not block crawlers unexpectedly.

Write alt text for the image's purpose

Alt text is an alternative for people who cannot see the image and a clue to its subject. Describe the relevant information in context. “Red ceramic mug with lid beside a laptop” may be useful for a product photo. “Image of product” is vague; a repeated list of keywords is frustrating and can look manipulative.

For a screenshot, explain the control or state the reader needs to find. For a chart, include the conclusion in nearby text and use alt text that identifies the chart. Complex information may require a text explanation or data table. A purely decorative image may need empty alt text so assistive technology skips it; the decision depends on its role, not on a desire to fill every field with a keyword.

Google's image guidance specifically recommends descriptive alt text and warns against keyword stuffing. Filenames also provide a light clue, so blue-linen-shirt-front.jpg is more useful than IMG_4027.jpg, but renaming a file alone is unlikely to change a weak page.

Add surrounding context and a useful landing page

Place the image near the paragraph it explains. Give the page a clear title and relevant copy. A photo of a tool on a page about a different topic gives conflicting signals. Captions can add context when they explain something beyond the alt text, such as a dimension, a step or a limitation.

The landing page matters after the click from image results. Show the image at a useful size, answer the query and let the visitor navigate to related information. A search result leading to a page dominated by ads or an unrelated offer wastes the image's discoverability.

For products, keep the picture, variant name, price and availability consistent. If a color variant changes the photograph but the URL and copy still describe the previous color, the visitor may mistrust the listing. Test both the visual and the buying path.

Balance quality with load time

Use an image large enough to show detail without serving the full camera original to every phone. Modern formats and responsive sizes can reduce transfer, but inspect the result for blur or artifacts, particularly around text and product details. Set dimensions to prevent layout jumps where possible and reserve priority for the main image rather than lazy loading it indiscriminately.

Measure a representative page on a mobile connection. Look at image transfer size, when the main visual appears and whether scripts or sliders delay it. Do not compress every image until details needed for a purchase disappear. The goal is a fast, legible image.

Audit a small image set

Select the homepage hero, one article illustration, a category image and three product images. For each, record its question, rights, filename, src, alt text, surrounding copy, mobile rendering and file size. Fix missing or wrong images on valuable pages first.

After a change, open the public page, inspect its HTML and repeat the mobile test. Search Console can show image-search performance over time, but a sitemap or alt-text edit does not guarantee impressions. Keep the image useful to the person who clicks it.

For an existing catalog, export image URLs and identify repeated placeholders, files that fail to load and variants sharing the wrong photograph. Compare the export to public product pages instead of trusting the media library alone. A missing image on an important product is an immediate buying obstacle. An attractive but inaccurate image can be worse, because it creates a false expectation that may lead to returns and distrust.