Start with the image's job

Classify important images as informative, functional, decorative or complex. An informative image explains something the text alone does not; a functional image acts as a link or control; a decorative image adds atmosphere without conveying unique information. That purpose determines how it should be described.

Before editing assets, check whether the image earns its place. A relevant diagram, original product photo or annotated screenshot can clarify a decision. A generic stock image that adds no context may increase page weight without helping the reader.

Write alternative text for people first

For an informative image, describe its meaningful content and relationship to the page. For a linked image, describe the destination or action where that is its function. Decorative images should generally use empty alt text so assistive technology can skip irrelevant filenames.

Do not turn alt text into a keyword list or repeat the caption when that adds no value. For a complex chart, provide concise alt text and put the important data or explanation in nearby text or an accessible table.

Choose formats and responsive delivery

Export at a size appropriate to the rendered dimensions, use modern formats where supported and retain sensible fallbacks. Responsive image markup helps smaller screens avoid downloading unnecessarily large desktop assets. Compress visually rather than applying the most aggressive setting blindly.

Prioritize the image that matters in the initial viewport, but do not lazy-load an image needed immediately to render the main content. For images lower on the page, lazy loading can reduce work before a visitor reaches them. Test on a real mobile connection.

Help search engines understand context

Use standard HTML image elements with crawlable source URLs, descriptive filenames where practical and placement near relevant text. Page titles, surrounding copy, captions and image content all establish context; no single attribute compensates for an irrelevant page.

Use structured data only when the page genuinely qualifies for the relevant feature, and validate it before release. Google's image guidance emphasizes a useful, discoverable landing page as well as appropriate image markup. citeturn0search0

Run a repeatable image QA pass

For important templates, test keyboard and screen-reader behaviour, check text alternatives, inspect dimensions and format, and confirm image URLs return successfully. Verify responsive crops preserve the subject and that essential labels are not embedded only in an image.

Keep an asset inventory with owner, source or licence, purpose, alt-text rationale and review date. That makes it easier to replace outdated screenshots and avoid inconsistent versions of the same visual across the site.

Measure outcomes realistically

Use Search Console to inspect image-search performance where relevant, then connect landing pages to engagement and business outcomes. More image impressions do not automatically mean more qualified visits, and a faster page can help usability even when image-search traffic is not a goal.

Use the title validator and SERP preview when improving the hosting page, and the schema tool only where structured data is appropriate. Pair image work with the SEO content brief and refresh-audit guides so it supports a clear page purpose.