Image SEO with DAM: file names, alt text, formats and sitemaps

Image SEO starts in the DAM, because the DAM is where file names, alt text, rights metadata and renditions are created once and reused everywhere. When these signals live as governed fields on each asset, every website, shop and marketplace inherits them automatically. When they are typed by hand in each CMS, quality drops with every channel and every language.

Why image SEO belongs in the DAM

The DAM is the only system that sees every image before it reaches a page, so it is the right place to enforce search signals. Google extracts the meaning of an image from the page around it, its alt text, file name, structured data and embedded metadata. Four of those five can be managed as DAM fields and published through integrations. The table maps each signal to Google guidance and to its owner in the DAM.

File names and URLs that describe the image

Descriptive file names give search engines context and cost almost nothing to automate. Google recommends short, descriptive names and warns against generic ones such as image1.jpg. Keep internal file names (with SKU, shoot ID and version) inside the DAM and generate public names at delivery, for example oak-dining-table-180cm-front.webp, built from product name and view metadata. Generate names per language for localised storefronts. Use stable URLs so search engines keep ranking signals when the asset gets a new version.

Alt text: write for accessibility first, search second

Alt text serves screen reader users first, and good accessible alt text also satisfies search engines. Google describes alt text as the most important attribute for image metadata and explicitly warns against stuffing it with keywords. The European Accessibility Act, Directive (EU) 2019/882, applies from 28 June 2025 and makes text alternatives a compliance requirement for many e-commerce services; see European Accessibility Act: alt text and accessible assets. Store alt text as a mandatory, per-locale field in your DAM metadata model, and use AI auto-tagging only for drafts that a person approves.

Image formats for SEO and speed: WebP, AVIF and fallbacks

Modern formats improve page speed, which supports rankings, and Google indexes them without special handling. Google lists WebP and AVIF among its supported formats, and Can I use reports AVIF support in Chrome 85, Firefox 93, Safari 16.4 and Edge 121 onwards. Serve AVIF or WebP through format negotiation and always keep a fallback src URL, which Google recommends because some crawlers ignore srcset and picture. Place images in img elements: Google does not index CSS background images. The delivery side is covered in dynamic media and image CDNs, offered by vendors such as Cloudinary, Scaleflex and Adobe Experience Manager Assets.

Image sitemaps, structured data and licence metadata

Image sitemaps and structured data help Google find and badge images that templates alone may hide. Google accepts image URLs on other domains in an image sitemap, so a DAM delivery CDN works, and verifying that domain in Search Console exposes its crawl errors. For licensing, Google reads IPTC Creator, Credit Line, Copyright Notice and Web Statement of Rights, or the equivalent schema.org ImageObject properties creator, creditText, copyrightNotice and license; the licence field makes images eligible for the Licensable badge. For products, Google's merchant listing guidance recommends multiple high-resolution images of at least 50,000 pixels (width multiplied by height) in 16x9, 4x3 and 1x1 ratios, which a DAM can generate from one master.

What to do next

1. Audit 100 top-traffic images for file name, alt text, format and indexability.
2. Add mandatory per-locale alt text and rights fields to the DAM metadata model.
3. Generate SEO file names and stable URLs at delivery from product and view metadata.
4. Enable AVIF and WebP negotiation with a JPEG or PNG fallback.
5. Publish an image sitemap from DAM delivery URLs and verify the CDN domain in Search Console.