Make the image discoverable and the page useful
Google can discover an image through the src attribute of an HTML img element, including an image within picture. It does not index CSS background images. Google's image guidance distinguishes these delivery patterns.
Review the landing page alongside the file. A clear product photograph helps a visitor inspect the product, while a diagram needs an explanation of what its parts mean. Putting an unrelated image beside a keyword-rich paragraph does not make the information useful.
Give the image meaningful context
Google combines page content, alt text and computer vision to understand an image. A descriptive filename provides a light clue, not a promised ranking change. Place the image near relevant explanation and describe what is actually shown. The primary documentation covers these signals.
Text alternatives depend on purpose. An informative photograph needs its relevant meaning conveyed; a functional image needs its action or destination. A decorative HTML image can correctly use an empty alt. Use W3C's decision tree for that review rather than filling every image with keywords.
Compare the actual file and loading behavior
| Review area | Inspect | What the check establishes |
|---|---|---|
| Discovery | The rendered img src and returned file. | Whether the intended asset can be found and fetched. |
| Context | The actual image, its alternative and nearby text. | Whether the information fits this page. |
| Delivery | The selected file, dimensions and loading/render timing. | Where to investigate unnecessary transfer or delay. |
Google supports formats including JPEG, PNG, WebP, SVG and AVIF. That list does not choose the best export for your particular asset. Compare visual quality and delivered file weight using the actual image, and check the fallback src when implementing responsive versions. Google documents supported formats and responsive markup.
If an image is the Largest Contentful Paint candidate, investigate both loading and rendering. A smaller file may reduce transfer time while another delay still holds back the paint. web.dev's LCP guidance explains that distinction and warns against lazy-loading the LCP image.
Illustrative markup for a product photograph
Assume the photograph really shows a standing desk with its desktop raised. The following filename and asset are illustrative, not a working file or a customer implementation:
<img src="example-desk.webp"
alt="Standing desk with its desktop raised">Before using that description, inspect the real photograph and the surrounding product information. If the photograph conveys a different feature, change the alternative. Then review responsive delivery separately; the alt wording does not select which image file the browser downloads.
Review a real image from page to file
- Open the published page and identify the image's purpose.
- Inspect the image markup and final asset response.
- Compare the actual image with its filename, alternative and nearby explanation.
- Check the chosen responsive file at relevant screen sizes.
- If loading is slow, diagnose the transfer and render sequence before changing formats.
- Retest after publishing the revised asset or markup.
Keep visual quality and meaning in the review. A smaller export that makes product details or diagram labels unreadable has lost useful information. Choose images because they explain the page, rather than filling an article to meet an image quota.
Questions readers ask
Can an image sitemap reference files on a CDN?
Yes. Google permits image URLs from other domains in image sitemap entries, including files hosted on a CDN. Check that the intended files are accessible; the sitemap is a discovery aid, not an indexing guarantee.
Should the same image file have a different URL on every page?
Google recommends consistently referencing the same image with the same URL so it can cache and reuse it. Review unnecessary duplicate asset URLs separately from responsive variants that are actually different files.
Related concepts
alt text, Core Web Vitals, page speed, on-page SEO, the image SEO implementation guide.
Primary references
Guidance checked on October 12, 2026. Examples are illustrative. This revision does not claim customer results or human expert approval.