Image SEO Checklist for Better Search Visibility
Images can make a page clearer, more trustworthy and easier to use, but they can also create slow loading, accessibility problems and crawl barriers. Image SEO is the discipline of publishing visuals so people receive genuine value while search systems can discover and understand the files.
The goal is not to insert a keyword into every filename or alt attribute. It is to connect a useful visual with the right page, descriptive context, efficient delivery and valid technical signals. A strong workflow begins before upload and continues through measurement.
. Confirm the image has a job
Every image should serve a defined purpose: demonstrate a process, show an object, compare options, summarize data, establish context or support a decision. Decorative images may improve visual rhythm, but they should not displace information or receive misleading descriptions.
Before using a visual, write one sentence explaining what a reader learns from it. If the sentence is vague, the image may be unnecessary. This simple test prevents stock-image clutter and makes later decisions about alt text, captioning and placement easier.
Verify reuse rights before publication. Record the creator, source URL, license, required attribution and any restrictions. A search-engine result is not a license. If the rights are unclear, commission an original image, use an established public-domain source or choose a verifiably licensed alternative.
. Make the file crawlable
Google recommends embedding important images with standard HTML image elements. Search crawlers can process images referenced in the src attribute of an img element, including images inside a picture element. Images used only as CSS backgrounds may not be treated the same way for image indexing.
Check that image URLs return a successful response, do not require a login and are not blocked by robots.txt. Avoid temporary, signed or session-bound URLs for public editorial images. Keep canonical page and image-host settings consistent when a content delivery network is used.
Do not hide the only version of a meaningful image behind a click, swipe or other user interaction. Search systems may not perform the interaction needed to reveal it. Important visual content should be present in the rendered page and discoverable without a visitor action.
. Use clear filenames and stable URLs
A descriptive filename helps humans manage assets and provides a small contextual clue. Use lowercase words separated by hyphens, such as red-brick-chimney-flashing.webp. Avoid camera defaults, long tracking strings and keyword repetition.
Name the file before upload because changing an image URL later may require redirects and cache updates. If an established image must move, preserve the old URL when possible or implement a permanent redirect to the new file.
A practical naming formula is subject-action-context-format. For example, window-weatherstrip-gap-test.webp tells an editor what the file contains without opening it. Keep the name accurate; do not add locations, products or claims absent from the image.
. Write alt text for the image’s purpose
Alt text communicates the image’s meaning or function when a person cannot see it and helps search systems understand its relationship to the page. The correct wording depends on context, not the file alone.
For an informative photo, describe the information readers need. For a functional image used as a link or button, describe the action or destination. For a chart, provide a concise alt description and place the underlying values or a longer explanation in nearby text. For a purely decorative image, use an empty alt attribute so assistive technology can skip it.
Do not begin with “image of” unless the medium itself matters. Avoid stuffing keywords, repeating the caption word for word or turning alt text into a hidden marketing message. A useful test is to remove the image and read the alt text in its place: the sentence should preserve the essential meaning without sounding unnatural.
. Place images beside relevant text
Google advises placing high-quality images near relevant text. The surrounding heading, paragraph, caption and page topic help establish meaning. A technically optimized image on an unrelated page is unlikely to satisfy search intent.
Lead with text that explains why the image matters. Captions are useful when readers need identification, interpretation, attribution or a key observation. They are not mandatory for every decorative visual.
Use one primary page for an important original image when possible. Reusing the same image across many loosely related pages can weaken context and complicate reporting. When reuse is necessary, adjust the surrounding explanation rather than duplicating the same caption everywhere.
. Choose the right dimensions and format
Start from the rendered size, not the camera’s original dimensions. A file displayed at 800 pixels wide rarely needs to be delivered as a 5,000-pixel image to every device. Create variants that match common layout widths while retaining enough detail for high-density screens.
Google supports common formats including JPEG, PNG, WebP, AVIF, SVG, GIF and BMP. Format choice should follow content and browser support. JPEG works well for many photographs; PNG suits transparency and crisp graphics; WebP and AVIF can reduce file size; SVG suits controlled vector artwork. Test quality because aggressive compression can destroy text, edges and product details.
Do not convert automatically just to follow a trend. Compare output size and visible quality. Keep the extension aligned with the actual file type, and strip unnecessary metadata when doing so does not remove required attribution or useful information.
. Deliver responsive images
Responsive image markup lets the browser choose an appropriate file for the viewport and display density. Use srcset with accurate width descriptors and a sizes attribute reflecting the real layout. The picture element can provide art direction or modern-format alternatives.
Test at narrow, medium and wide breakpoints. Confirm the browser is not downloading a desktop-sized asset for a small mobile slot. Also verify that crops do not remove meaningful content, labels or safety details.
Reserve image space with width and height attributes or an equivalent aspect-ratio rule. This reduces unexpected layout movement while the image loads. A stable page is easier to read and supports a better visual experience.
. Compress without making the image useless
Compression is successful when it reduces transfer size while preserving the detail a reader needs. Use visual inspection, not a single quality number. Photographs can tolerate different settings than screenshots, diagrams or text-heavy graphics.
Create a simple budget by role. A small inline photo can have a tighter size target than a detailed comparison diagram. Track final bytes, rendered dimensions and visual quality. If a file remains large, resize it before lowering quality further.
Avoid adding large images merely to reach a visual quota. The best byte is the one a reader never needs to download.
. Handle lazy loading carefully
Lazy loading can defer off-screen images and reduce initial work, but poor implementation can hide content from crawlers or delay a page’s most important visual. Google’s guidance emphasizes loading content when it approaches the viewport without requiring user actions.
Do not lazy-load the main hero or likely Largest Contentful Paint image by default. Give above-the-fold assets appropriate priority and explicit dimensions. Lazy-load lower-page visuals, then test with rendered HTML and performance tools.
Watch for placeholders that never swap, scripts that fail when JavaScript is delayed and data attributes that crawlers cannot interpret. Native browser loading behavior may be sufficient for many editorial pages, but it still requires testing.
. Use image sitemaps when discovery needs help
An image sitemap can help Google discover images, especially files loaded through JavaScript or hosted in ways that are otherwise hard to find. Images can be added to an existing sitemap or placed in a separate image sitemap.
A sitemap is a discovery aid, not an indexing guarantee. Include only canonical, accessible image URLs connected to valuable pages. Keep sitemap entries current when images move or are removed.
If standard crawlable markup already exposes every image, an additional image sitemap may have limited incremental value. Use it when the site’s architecture or rendering creates a real discovery problem.
. Connect images with structured data
Structured data can help search systems understand eligible page types such as products, recipes, articles and videos. Where a supported type requires or recommends images, provide representative, crawlable URLs that match the visible page.
Do not add markup solely to force an image result. Follow the specific structured-data documentation, keep the marked image visible and avoid misleading properties. Structured data does not guarantee a rich result.
For editorial articles, also review the preferred social-sharing image and the main image supplied to Article schema. Use a high-quality, relevant asset rather than a generic site logo.
. Build an image publishing checklist
Before publication, confirm:
- The image serves a reader need and has documented reuse rights.
- The filename and URL are descriptive, stable and free of unnecessary parameters.
- The image is embedded with crawlable HTML and is not blocked.
- Alt text matches the visual’s purpose; decorative images use empty alt text.
- Dimensions, format and compression fit the rendered slot.
- Responsive variants and aspect ratio work across breakpoints.
- The hero image is not delayed; lower-page images load reliably.
- Caption and attribution are present where needed.
- Structured data and sitemap entries are accurate when used.
- The page has been tested on mobile and desktop.
. Measure outcomes instead of guessing
Use Search Console performance data to review queries and pages receiving image-search impressions and clicks where that reporting is available. Combine it with analytics, page-speed data and an asset inventory. A fast image that attracts the wrong audience is not automatically successful; an instructional diagram that supports conversions may be valuable even with modest image-search traffic.
Track a small set of operational metrics: percentage of editorial images with verified rights, missing-alt rate, average bytes by image role, oversized-image rate, pages with layout shift tied to images and broken image URLs. These measures reveal workflow problems teams can fix.
Audit high-value pages first. Do not rewrite every alt attribute because a tool produced a score. Prioritize inaccessible images, blocked resources, oversized hero files, broken URLs and visuals attached to pages with meaningful demand.
The VISUAL framework
Use VISUAL as a final quality gate:
- V — Value: the image helps a person understand or decide.
- I — Indexability: the file is crawlable, accessible and attached to the right page.
- S — Semantics: filename, alt text, caption and surrounding copy agree.
- U — User experience: dimensions, quality and loading behavior suit the device.
- A — Authorization: ownership, license and attribution are documented.
- L — Learning: performance is measured and the workflow improves.
Score each dimension 0, 1 or 2. A total below eight should block publication until the responsible editor resolves the weak areas. This threshold is an internal workflow recommendation, not a Google ranking factor.
FAQ
How long should image alt text be?
Use the shortest description that communicates the image’s meaning in context. There is no universal ideal character count.
Should every image contain a keyword in its alt text?
No. Include relevant language naturally only when it describes the image. Decorative visuals should normally have empty alt text.
Is WebP always better than JPEG?
No. Compare file size, quality, workflow support and browser compatibility. The best format depends on the asset.
Do image sitemaps improve rankings?
They can help discovery, but they do not guarantee indexing or ranking.
Should the hero image be lazy-loaded?
Usually not when it is visible immediately or likely to be the page’s Largest Contentful Paint element.
ORIGINAL ELEMENT: VISUAL SCORECARD
Value + Indexability + Semantics + User experience + Authorization + Learning. Score each 0–2; require at least 8/12 and no zero in Authorization before publication.
