Evidence guide · visual discovery · Cross-stream operating guide

Image SEO fundamentals: meaningful visuals, accurate metadata, and fast delivery

A practical guide to image filenames, alt text, visual context, responsive delivery, and metadata for teams that want discoverability without turning accessibility into keyword stuffing.

Diagram showing ARM Agency's five image SEO foundations: truthful visual, descriptive asset name, contextual alt text, appropriate delivery, and accurate metadata.
Image SEO Foundations — an original ARM Agency visual explaining the standards described in this guide.
The decision this supports

Use this guide when deciding whether an image improves a buyer’s understanding, accessibility, performance, or public discovery—and what should be true before it is published.

Start with an image that earns its place

A visual should explain, evidence, orient, or support a decision on the page. Decorative imagery can be appropriate, but it should not be used as manufactured proof, a substitute for a clear offer, or a stock visual that implies a client outcome that did not occur.

Name assets for people and systems

Use concise, lowercase, hyphen-separated names that truthfully describe the visual, such as arm-agency-founder-professional-headshot.webp. Avoid generic camera names, revision clutter, keyword lists, or claims the image cannot substantiate. A filename is a light contextual clue, not a ranking mechanism.

Write alt text for the context, not a keyword field

Alt text should describe the meaningful visual content or function in its page context. A useful description supports people using screen readers and helps clarify the image subject. Decorative images should use empty alt text; keyword strings and redundant phrases create a worse experience.

Ship the right image, not simply the newest format

Choose the format, dimensions, compression, and responsive approach based on the placement and measured experience. WebP or AVIF can reduce bytes for suitable raster images; SVG is often a better fit for logos and line diagrams. Include intrinsic width and height, use an img fallback within picture patterns, and avoid serving oversized hero assets to small devices.

Use image metadata only when it is representative

A page may benefit from a preferred preview image through accurate Open Graph or structured metadata. The image must be relevant to the page and visible content. Metadata can inform a platform’s selection, but it does not guarantee an image preview, rich result, ranking, or AI citation.

Readiness questions

  • The visual helps a buyer understand the page or is deliberately decorative.
  • The filename is concise, factual, lowercase, and hyphen-separated.
  • The alt text describes meaningful content or correctly uses an empty value for decoration.
  • Dimensions, loading strategy, format, and compression match the placement.
  • Any caption, metadata, and visible claims accurately represent the asset and page.

What a scoped next step can deliver

  • Image inventory and placement review
  • Filename and alt-text standards
  • Responsive-format and performance recommendations
  • Preferred-image and structured-data accuracy review
  • Future asset intake and quality-assurance workflow
A bounded next step

Need help applying this to your operating context?

We begin by clarifying the decision, scope, ownership, and constraints. The appropriate next step may be a diagnostic, a workshop, a bounded implementation, or a respectful no-go decision.

Review image SEO readiness

Sources