Image SEO: How Google Finds and Ranks Your Pictures
Google can't see a photo the way you do. It reads the words around the picture, the filename, the alt text, and the caption, then makes a guess about what the image shows. Get those signals right and your pictures earn traffic from Google Images. Get them wrong and a great photo sits invisible.
That's the whole game. Image SEO is the practice of giving Google enough text-based clues to understand a picture it cannot actually look at, plus making that picture load fast enough that it doesn't drag your page rankings down. This guide walks through every signal that matters, in plain language, for a business owner who isn't a developer.
Quick Navigation
- How Google Finds and Understands Your Images
- Why Alt Text Matters Twice Over
- Filenames, Captions, and Surrounding Text
- Image Speed: Format, Compression, and Size
- Lazy Loading Without Hurting Rankings
- Structured Data for Product and Recipe Images
- Image Sitemaps and Google Images as Traffic
- Common Image SEO Mistakes
- Frequently Asked Questions
How Google Finds and Understands Your Images
Google understands an image through text, not vision, relying on the filename, the alt text, the caption, and the words surrounding the image on the page. Google's own image SEO documentation states it uses page content and these supporting signals to determine an image's subject and relevance. A picture with no descriptive text around it is, to a search engine, a blank.
Discovery comes first. Googlebot crawls your page, finds the <img> tag, and follows the src to the image file. If the image is loaded by JavaScript that never runs, or buried behind a click, Google may never reach it. The simplest way to get an image found is a plain <img> tag with a real src pointing at a real file.
Then comes understanding. Google reads the alt text first as its primary description. It weighs the filename. It looks at any caption directly beneath the image. And it reads the paragraph the image sits inside, because a photo of a copper kettle inside an article about brewing tea is almost certainly a brewing kettle, not a decorative object. Context resolves ambiguity.
You can check what on-page elements a given page exposes. The Brass-SEO Page Audit button crawls a single URL and reports its on-page SEO elements, so you can see how a page presents itself before worrying about whether each picture is described well. Run an audit on your top pages and start there. The page audit feature gives you that snapshot in under a minute.
Why Alt Text Matters Twice Over
Alt text serves two audiences at once: screen readers that read it aloud to blind and low-vision users, and search engines that use it as the main description of the image. Google's accessibility guidance and its image SEO documentation both point to alt text as the single most important attribute on an <img> tag. Write it once, satisfy both.
Good alt text describes what's in the image, specifically, in a short phrase. For a photo of a blue ceramic mug on a wooden desk, write alt="blue ceramic coffee mug on a wooden desk". Skip the phrase image of or picture of, because a screen reader already announces that it's an image. Keep it under roughly 125 characters so screen readers don't truncate it.
Don't stuff keywords. alt="coffee mug coffee cup best coffee mug buy coffee mug cheap" reads as spam to Google and as gibberish to a screen reader. One honest description beats a pile of keywords every time.
Decorative images get empty alt text. A divider line or a background flourish that carries no meaning should use alt="" (empty, but present), which tells screen readers to skip it. Leaving the attribute off entirely is different and worse, because some screen readers then read out the filename instead.
The accessibility payoff is real and legal in many places. The U.S. Web Accessibility guidelines (WCAG 2.1) require text alternatives for non-text content, and missing alt text is one of the most common accessibility failures flagged in automated audits. SEO and accessibility pull in the same direction here.
Filenames, Captions, and Surrounding Text
A descriptive filename is a free ranking signal that most sites waste. Google's image documentation explicitly recommends descriptive filenames because the URL path of an image is one of the clues it uses to understand the content. IMG_4821.jpg tells Google nothing. blue-ceramic-coffee-mug.jpg tells it plenty.
Name files in lowercase with hyphens between words, the same convention Google recommends for page URLs. Underscores work less reliably as word separators, so red_running_shoes.jpg is weaker than red-running-shoes.jpg. Set the filename before you upload, because renaming after the fact can break links to the image.
Captions earn extra attention. The visible text directly below an image gets read more often than body copy, and Google treats a caption as a strong relevance signal for the picture above it. Not every image needs a caption, but for charts, product shots, and anything a reader might study, a caption helps both people and search engines.
Surrounding text closes the loop. Place an image near the paragraph it illustrates, and write that paragraph as if the image weren't there. A photo of a finished deck inside a paragraph about cedar decking inherits the topic of that paragraph, which is exactly the association you want Google to make.
Image Speed: Format, Compression, and Size
Heavy images are the most common cause of slow pages, and slow pages rank worse on mobile. Google's Core Web Vitals threshold for Largest Contentful Paint (LCP) is 2.5 seconds, and on most content pages the largest element is an image. A 4 MB hero photo can blow that budget single-handedly and pull your whole page down in mobile rankings.
Format comes first. Modern formats like WebP and AVIF compress far smaller than old JPEG or PNG files at the same visual quality, and Google has recommended WebP for years. Most image tools and content systems can export WebP directly. Use JPEG as a fallback for photos, PNG only when you need transparency, and avoid uploading raw camera files straight to your site.
Compression comes second. A photo straight off a phone can be several megabytes; compressed for web it might be 150 KB with no visible difference. Run images through a compression tool before uploading, or let your platform do it. The goal is the smallest file that still looks sharp on a retina screen.
Dimensions come third, and they're the step people skip. Don't upload a 4000-pixel-wide image and let the browser shrink it to 600 pixels with CSS. The browser still downloads the full 4000-pixel file. Resize the actual file to roughly the size it displays, then let responsive srcset markup serve smaller versions to phones. Right-sizing dimensions often cuts more weight than compression alone.
To learn how page weight ties into ranking, our guide on Core Web Vitals breaks down LCP and the other speed metrics Google measures. If you suspect images are dragging a page down, the walkthrough on whether your website is slow shows how to find the culprit.
Lazy Loading Without Hurting Rankings
Lazy loading delays image downloads until the user scrolls near them, which speeds up the initial page load when used correctly. The browser-native attribute loading="lazy" on an <img> tag handles this with no JavaScript, and Google fully supports it. Apply it to images below the fold.
One rule prevents a self-inflicted wound: never lazy-load your largest above-the-fold image. The hero image at the top of the page is usually your LCP element, the thing Google times for Core Web Vitals. Lazy-loading it delays the very pixel Google is measuring, making your LCP score worse, not better. Mark above-the-fold images with loading="eager" (or leave the attribute off) and reserve lazy loading for everything further down.
Set explicit width and height attributes on every image, lazy-loaded or not. Without them, the page reflows as each image arrives, jumping the text around and hurting your Cumulative Layout Shift score. Width and height let the browser reserve the right space before the image loads. It's a one-line fix with an outsized payoff.
Structured Data for Product and Recipe Images
Structured data is hidden code that labels an image's role so Google can show it in rich results, and certain result types require an image to qualify. Google's Product and Recipe rich-result documentation both list image as a required property. No image, no rich result.
A product page using Product structured data must include a product image, which makes the listing eligible for the rich product cards in search that show price, rating, and a photo. A recipe page using Recipe structured data must include a dish image to appear in the recipe carousel with a thumbnail. The image isn't decoration in these cases; it's a gatekeeper for the enhanced listing.
Provide high-resolution images for structured data and make sure they're crawlable, not blocked by robots.txt. Google recommends images at least 1200 pixels wide for the best presentation in rich results and Discover. The image URL you put in the structured data has to return a real, indexable image when Google fetches it.
If you want the broader picture on how this hidden labeling works, our post on schema markup explains structured data without the jargon. Image properties are one piece of a larger system that helps Google display your pages richly.
Image Sitemaps and Google Images as Traffic
Google Images is a genuine search surface, and a picture that ranks there sends real visitors to your page. An image sitemap, or image entries inside your regular XML sitemap, helps Google discover pictures it might otherwise miss, especially those loaded by scripts or galleries. Google's sitemap documentation supports image extensions for exactly this reason.
Most modern content systems generate a sitemap automatically, and many include image entries without you lifting a finger. If your platform does, you're covered. If you run a custom site or a heavy JavaScript gallery where images don't appear in plain <img> tags, adding image sitemap entries gives Google a direct list of every picture worth indexing.
Tapping that traffic still depends on the fundamentals above. An image that ranks in Google Images got there because its filename, alt text, caption, and surrounding text told Google what it shows, and because it loaded fast enough to satisfy mobile users. The sitemap helps discovery; the on-page signals earn the ranking. Both have to be in place.
Common Image SEO Mistakes
The most expensive image SEO mistake is uploading full-resolution photos straight from a camera or phone, which buries fast pages under megabytes of unnecessary weight. A single uncompressed hero image can push a page past Google's 2.5-second LCP threshold by itself. Fixing image weight is often the fastest page-speed win available to a small site.
Here are the errors that show up most often, and the fix for each:
- Missing alt text — add a short, specific description to every meaningful image; use
alt=""only for purely decorative ones. - Generic filenames — rename
IMG_4821.jpgtoblue-ceramic-coffee-mug.jpgbefore uploading. - Oversized dimensions — resize the actual file to its display size instead of shrinking a giant image with CSS.
- Lazy-loading the hero — never apply
loading="lazy"to your largest above-the-fold image. - No width and height — set both attributes to stop layout shift as images load.
- Keyword-stuffed alt text — write one honest description, not a string of keywords.
Work through that list on your highest-traffic pages first. The pages already earning visits have the most to gain from images that load fast and rank in Google Images.
You don't need to memorize every rule to get started. Brass-SEO connects to your Google Search Console and Google Analytics 4 data and answers plain-English questions about your pages, including which pages load slowly and which on-page elements need work. You can run your first SEO analysis and ask where to focus.
Frequently Asked Questions
Does Google actually read alt text for ranking?
Yes. Google's image SEO documentation names alt text as the primary attribute it uses to understand an image's subject. Alt text feeds both image rankings and accessibility for screen-reader users, so a single good description serves two purposes. Write it for a person first, and the SEO value follows.
What's the best image format for SEO?
WebP and AVIF are the strongest choices because they compress much smaller than JPEG or PNG at the same visual quality, which means faster pages. Google has recommended WebP for years and most platforms can export it directly. Keep JPEG as a fallback for photos and use PNG only when you need transparency.
How big should my images be?
Resize the actual file to roughly the size it displays on the page, not larger, then compress it for web. A hero image displayed at 1200 pixels wide should not be a 4000-pixel file shrunk by CSS, because the browser downloads the full file regardless. For structured-data and Discover eligibility, Google recommends source images at least 1200 pixels wide.
Will slow images hurt my Google rankings?
Yes, on mobile especially. Images are usually the largest element on a page, so a heavy image directly worsens your Largest Contentful Paint, which Google measures as a Core Web Vitals signal with a 2.5-second threshold. Compressing and right-sizing images is one of the fastest ways to improve page speed and protect mobile rankings.
Should I add structured data to my images?
If you sell products or publish recipes, yes, because Google's Product and Recipe rich results both require an image to qualify. Structured data labels the image's role so Google can show it in enhanced search listings with photos, prices, or ratings. For ordinary blog and informational images, descriptive alt text and a good filename are usually enough.
Can Brass-SEO check my image SEO?
Brass-SEO crawls individual pages with the Page Audit feature and reports on-page SEO elements, and it answers questions about page speed using your Google Search Console and Google Analytics 4 data. It requires both GSC and GA4 connected and costs $25/month with a 3-day free trial. Use it to find which pages are slow or weakly described, then fix the images on those pages first.
Image SEO rewards the basics done consistently. Descriptive filenames, honest alt text, compressed and right-sized files, careful lazy loading, and structured data where it qualifies. None of it requires a developer, and most of it takes minutes per page. Start with the pages that already earn traffic and work down from there.