Image SEO checklist: 10 fixes that help images rank
Short answer Google's image advice comes down to ten checks: real img tags, images beside related text, descriptive alt text, plain file names, a supported format, files resized and compressed, width and height set, lazy loading only below the first screen, a chosen preview image, and a sitemap for images Google can't find. Most take minutes per page.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callThe 10-point image SEO checklist
Work down this list one page at a time, starting with your busiest service pages. Each line is from Google's image guidance (Google Search Central: Google image SEO best practices) unless another source is named.
| # | Fix | Quick check |
|---|---|---|
| 1 | Put images in normal image tags, not CSS backgrounds | Right-click the photo: "Save image as" should appear |
| 2 | Place each image next to text about it | The heading or paragraph beside it names what it shows |
| 3 | Write alt text that describes the image | Every meaningful image has one plain sentence |
| 4 | Rename files before upload | No IMG_4021.jpg on the live site |
| 5 | Use a format Google reads, matched to the image | Photos JPEG, WebP or AVIF; logos SVG or PNG |
| 6 | Resize to display size, then compress | No photo much wider than it shows on screen |
| 7 | Set width and height | Page doesn't jump as images load |
| 8 | Lazy-load only images below the first screen | Top photo loads right away |
| 9 | Choose the page's preview image | Shared link shows a real photo, not your logo |
| 10 | Make every image findable | Image sitemap if photos load by script; one URL per image |
The fixes fall into two groups. Fixes 1 to 4 and 9 to 10 help Google find and understand images. Fixes 5 to 8 make pages faster, and speed is where images hurt most: Google says images "are often the largest contributor to overall page size."
1. Use real image tags
Google finds images in the standard HTML image element (the `img` tag) and says plainly:
"Google doesn't index CSS images." (Google Search Central: Google image SEO best practices)
A CSS image is one a designer set as a background. Big banner photos with text on top are often built this way. They look the same to visitors but are invisible in image search. If a photo matters, ask your web person to make it a normal image.
2. Put images near related text
Google reads the page around an image to learn what it shows, "including captions and image titles," and asks that images be "placed near relevant text and on pages that are relevant to the image subject matter." A photo of a finished bathroom belongs on the bathroom remodel page, under a heading about it, with a caption such as "Walk-in shower, Plano, 2026."
3. Write alt text that describes the image
Alt text is a short description in the page code that screen readers speak aloud and that shows if the image fails to load. Google calls it "the most important attribute" for image metadata. Its own example shows the scale from bad to best:
| Alt text | Google's verdict |
|---|---|
| (none) | Bad |
| A long list of dog words | Bad: keyword stuffing, "may cause your site to be seen as spam" |
| "puppy" | Better |
| "Dalmatian puppy playing fetch" | Best |
Describe what is in the picture and where, in the words a customer would use. Google sets no length limit; one short sentence is enough. Images that only decorate, such as a divider line or a background pattern, get an empty alt text (`alt=""`) so screen readers skip them, per the W3C's accessibility tutorial. Leaving the alt text out entirely is not the same thing.
4. Rename files before you upload
Google says a file name gives "very light clues" about an image. Light, but free: `kitchen-cabinet-refinishing-before-after.jpg` beats `IMG00023.JPG`. Use short, descriptive names with hyphens. Don't stuff them; the gain is small either way. If your site is in a second language, Google suggests translating the file names too.
5. Use a supported format
Google Search reads images in "BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF," and suggests the file extension match the real file type.
| Image | Format to use |
|---|---|
| Photos of jobs, team, premises | JPEG, or WebP or AVIF for smaller files |
| Logo, icons | SVG (stays sharp at any size), or PNG |
| Screenshots with text | PNG or WebP |
If you serve WebP or AVIF with a fallback, Google asks that the fallback be a normal image with a `src` address, which is how the HTML `picture` element is meant to work.
6. Resize, then compress
A phone photo is often 4,000 pixels wide. Shown in an 800-pixel box, the visitor still downloads the full file. Google's Lighthouse audit flags any image whose shown size is at least 4 KiB smaller than the file, and says pages should "never serve images that are larger than the version that's rendered on the user's screen" (Chrome for Developers: Properly size images).
Resize first, then compress. Squoosh, a free browser tool from Google's Chrome team, does both and lets you compare quality before saving. For many screen sizes, a `srcset` attribute lets the browser pick a smaller copy on phones; Google recommends keeping a plain `src` as the fallback.
7. Set width and height
When an image has no size set, text jumps down as it loads. That jump counts against Cumulative Layout Shift (CLS), one of Google's Core Web Vitals.
"Always include width and height size attributes on your images and video elements." (web.dev: Optimize Cumulative Layout Shift)
Most site builders do this for you. Check by loading a page on a slow phone connection and watching for jumps.
8. Lazy-load only below the first screen
Lazy loading means an image downloads only as the visitor scrolls near it. It saves data on long pages. Used on the top photo, it slows the page:
"Don't lazy-load images that are likely to be in-viewport when the page loads, especially LCP images." (web.dev: Browser-level image lazy loading for the web)
The LCP image is usually the large photo at the top. Largest Contentful Paint (LCP) is how long it takes to appear, and Google calls 2.5 seconds or less good (web.dev: Largest Contentful Paint). Google also warns against lazy loading that waits for a click or a scroll, because "Google Search does not interact with your page" (Google Search Central: Fix lazy-loaded content). WordPress has skipped lazy loading on the first few images of a page by default since version 6.3 (Make WordPress Core, 2023).
9. Choose the page's preview image
Google picks the thumbnail for a search result or Google Discover on its own, but you can suggest one with the `og:image` tag or schema markup (structured code that labels page content). Google's rules for that image: relevant to the page, not a "generic image (for example, your site logo)," no image with text in it, no extreme shapes, and high resolution if possible. The same `og:image` is usually what Facebook and text messages show when someone shares your link.
10. Make every image findable
Two cases need extra help:
- Photos loaded by script, such as some galleries and sliders. An image sitemap lists them so Google finds images "we might not otherwise find," for example ones "your site reaches with JavaScript code" (Google Search Central: Image sitemaps). A site with plain image tags usually doesn't need one.
- The same photo on many pages. Use one address for it everywhere, so Google can reuse it instead of fetching copies.
If your images sit on a separate image server (a CDN), Google suggests verifying that domain in Search Console so you hear about crawl errors.
How to check the checklist worked
- Speed: run the page through PageSpeed Insights. Its suggestions name the exact images to resize, compress or stop lazy loading, and it shows your LCP against the 2.5-second mark.
- Image search traffic: in Search Console's Performance report, set the search type to Image. It "Includes search traffic from results shown in the Google Images tab" (Search Console Help: Performance report). Searches made with a camera, such as Google Lens, are counted separately under Web: multimodal.
Give Google a few weeks to recrawl before you judge.
Example
Illustrative cases with invented numbers.
A landscaper in Austin (US dollars)
Project photos come straight off a phone: 5 MB each, named IMG_ numbers, no alt text, ten on the home page. PageSpeed shows a slow LCP. The owner resizes them to 1,200 pixels wide in Squoosh (about 200 KB each), renames them like `flagstone-patio-austin.jpg`, adds one-sentence alt text and turns off lazy loading on the top photo. The page loads noticeably faster on a phone.
A dental office in Toronto (Canadian dollars)
The services page uses a CSS background for its hero photo and the clinic logo as the sharing image. A $300 developer fix makes the hero a normal image with alt text and sets a photo of the treatment room as `og:image`. Links shared in texts now show the room, not the logo.
FAQ
Do images help SEO at all?
Yes. They can bring visitors from Google Images and the thumbnails beside text results. Badly handled images mostly hurt by slowing the page.
How long should alt text be?
Google sets no limit. One short sentence that says what the picture shows is enough. Screen reader users hear every word, so skip "image of."
Should I use stock photos?
Google doesn't ban them. But real job photos show customers your work, and Google warns against generic images as the page's preview.
Do I need an image sitemap?
Usually not. You need one when images load through scripts or forms that Google may not run, per Google's image sitemap page.
Different for you?
- Your whole site is slow, not just the images: Core Web Vitals and site speed.
- You want the rest of the service page right too: on-page SEO for service pages.
- You need alt text for accessibility rules, not only search: ADA website compliance.
- You want to read the Image traffic numbers in context: Google Search Console for a small business.
- You'd rather have every image on the site fixed and kept that way: SEO & GEO Agent.