Google Images is one of the largest search engines in the world. For industries where visuals drive decisions, like e-commerce, travel, interior design, food, and fashion, image search represents a real traffic channel that most sites completely ignore.
The basics of image SEO are straightforward: descriptive file names, useful alt text, modern formats, and fast loading. But the gap between knowing these things and actually implementing them across a site with hundreds or thousands of images is where most teams fall short.
This guide covers what works, what does not, and the common mistakes that quietly kill your image search visibility.
Why image SEO matters
Google Image Search accounts for a significant share of all Google searches. For product-oriented queries, image results often appear in the main search results through image packs, pulling users into a visual browsing experience.
If you sell physical products, the path from image search to purchase is short. Someone searches "mid-century modern desk," sees your product image, clicks through, and buys. For service businesses and publishers, the path is longer but still valuable: image clicks bring users to your site, where they discover your content and brand.
Image SEO also feeds into broader SEO performance. Optimized images load faster, which improves Core Web Vitals. Proper alt text helps Google understand your page content. And image sitemaps ensure Google discovers visual content it might otherwise miss.
File names: the first signal Google reads
When you upload an image, the file name is one of the first things Google uses to understand what the image shows. A file named IMG_4392.jpg tells Google nothing. A file named blue-running-shoes-nike-pegasus.jpg tells Google exactly what it is looking at.
File naming best practices
Use descriptive, lowercase words separated by hyphens
Include the primary subject of the image
Keep it concise: three to six words is ideal
Avoid keyword stuffing: best-cheap-blue-running-shoes-2026-buy-now.jpg hurts more than it helps
A ChatGPT SEO audit is a manual site review where you feed page data, crawl output, or Google Search Console exports into ChatGPT and use targeted prompts to identify technical issues, content gaps, and ranking opportunities. It works best for analysis and pri
The "duplicate content penalty" is one of the most persistent myths in SEO. Site owners panic when they find identical text on two URLs, convinced that Google is about to punish their entire domain. That is not how it works.
Google does not have a penalty for
React applications have a reputation for being invisible to search engines. That reputation is outdated, but the underlying concern is valid: if your content is rendered entirely in the browser with JavaScript, Google has to execute that JavaScript to see it.
Bad examples:
IMG_0847.jpg
screenshot-2026-02-15.png
image1.jpg
product-photo-final-v3-EDITED.jpg
Rename images before uploading them. Doing this retroactively across an existing library is painful but worth it for your highest-traffic pages.
Alt text: describe the image, not your keywords
Alt text serves two purposes. First, it provides a text description for screen readers, making your images accessible to visually impaired users. Second, it gives Google another signal about what the image contains.
Good alt text describes what the image actually shows in plain language. It is not a place to dump your target keywords. You can analyze your page's meta tags and alt text to catch missing or poorly written attributes.
Writing effective alt text
Do this: Write as if you are describing the image to someone who cannot see it.
alt="A person running on a forest trail wearing blue Nike Pegasus shoes" (descriptive, natural)
alt="Sliced chocolate layer cake on a white plate with raspberries" (specific, useful)
alt="Comparison table showing pricing for three CRM platforms" (describes the content)
Do not do this: Stuff keywords or write generic descriptions.
Decorative images that add no informational value, such as background patterns, divider lines, or purely aesthetic elements, should have empty alt text (alt=""). This tells screen readers to skip them. But if an image communicates anything meaningful, it needs descriptive alt text.
Image formats: WebP, AVIF, and JPEG
Choosing the right image format is a balance between quality, file size, and browser support.
JPEG
The workhorse format. Excellent compression for photographs. Universal browser support. Use JPEG when you need maximum compatibility and the image is photographic (not graphics or text).
PNG
Best for images with transparency, text overlays, or sharp edges (logos, icons, screenshots). File sizes are larger than JPEG for photographs, so avoid PNG for product photos or landscape images.
WebP
Developed by Google. Offers 25 to 35 percent smaller file sizes than JPEG at equivalent visual quality. Supports transparency. Browser support is now nearly universal. WebP should be your default format for most web images in 2026.
AVIF
The newest contender. Even better compression than WebP, often 30 to 50 percent smaller than JPEG. Support is growing: Chrome, Firefox, and Safari all support AVIF. The trade-off is slower encoding times, which matters for sites that process images on the fly.
What to use in practice
Serve WebP as your primary format with JPEG as a fallback. If your build pipeline supports AVIF, serve AVIF to browsers that accept it, WebP to those that do not, and JPEG as the final fallback. The <picture> element handles this gracefully:
<picture> <source srcset="product.avif" type="image/avif" /> <source srcset="product.webp" type="image/webp" /> <img src="product.jpg" alt="Blue running shoes on white background" /></picture>
Responsive images with srcset
Serving a 2400px wide image to a phone on a 375px screen wastes bandwidth and slows the page. The srcset attribute lets you provide multiple image sizes so the browser picks the appropriate one.
The browser evaluates the viewport width and pixel density, then downloads the smallest image that fits. This is one of the highest-impact performance optimizations you can make, and it directly affects your Core Web Vitals scores.
Lazy loading: stop loading images users never see
Native lazy loading tells the browser to defer loading images until they are about to enter the viewport. One attribute does the job:
Apply loading="lazy" to every image that is not visible in the initial viewport (below the fold). This includes product grids, blog post images, gallery thumbnails, and sidebar content.
When not to use it
Never lazy load your largest contentful paint (LCP) image. The LCP image is typically the hero image or main product photo at the top of the page. Lazy loading it delays the LCP metric and hurts your performance score. For above-the-fold images, use loading="eager" (the default) and consider adding fetchpriority="high".
Image SEO for Next.js developers
If you build with Next.js, the next/image component handles several optimization steps automatically:
Automatic format conversion: Serves WebP (or AVIF with configuration) when the browser supports it
Responsive sizing: Generates multiple sizes at build time or on demand
Lazy loading by default: Images below the fold are automatically deferred
Width and height enforcement: Prevents layout shift by requiring dimensions
import Image from "next/image";<Image src="/images/product-blue-shoes.jpg" alt="Blue running shoes on white background" width={800} height={600} priority={false}/>
Set priority={true} for your LCP image. For everything else, the default lazy loading behavior is correct.
The key thing next/image does not do for you is write good alt text or choose good file names. Those are still your responsibility.
Image sitemaps
Google discovers images primarily through crawling your HTML. But if you have images that are loaded via JavaScript, served from a CDN with a different domain, or embedded in ways that Googlebot might miss, an image sitemap ensures they get found.
For most sites using server-rendered HTML with images in <img> tags, a dedicated image sitemap is unnecessary. Google finds the images during its normal crawl. But for JavaScript-heavy sites or sites with large image libraries loaded dynamically, image sitemaps close the gap.
Common image SEO mistakes
Missing alt text entirely
This is the most common issue. Pages go live with dozens of images and not a single alt attribute. Screen reader users get nothing, and Google gets no text signal about the image content. Run your site through the Ooty SEO Analyzer to catch missing alt text across your pages.
Oversized images killing page speed
A 4000px wide JPEG at full quality can be 3 to 5 MB. Put six of those on a product page and you have a 20 MB page that takes seconds to load on mobile. Compress images before upload. Aim for the smallest file size that maintains acceptable visual quality. Tools like Squoosh, Sharp, or your CMS's built-in image processing can automate this.
Keyword-stuffed alt text on decorative images
Some SEO guides suggest adding keyword-rich alt text to every image on the page, including decorative borders, background textures, and spacer images. This is counterproductive. It clutters the screen reader experience and looks spammy to Google.
Using CSS background images for content
Images loaded via CSS background-image are invisible to Google's image index. If an image is part of your content (a product photo, an infographic, a team headshot), it belongs in an <img> tag with proper alt text, not in a CSS background.
Ignoring image dimensions
Omitting width and height attributes causes layout shift as images load. The browser does not know how much space to reserve, so content jumps around when images pop in. This hurts your Cumulative Layout Shift (CLS) score and frustrates users.
Structured data for images
For certain content types, structured data helps Google understand and display your images in richer ways.
Product schema with image properties helps Google show your product images in shopping results and image search with price and availability overlays.
Recipe schema with image properties triggers the rich recipe cards in both regular and image search results.
Article schema can include images that Google uses for the article's visual representation in Discover and Top Stories.
The connection between images and structured data is often overlooked. Adding the right schema to pages with strong visual content can increase the ways Google surfaces your images. For a deeper look at schema types, see our schema markup guide.
Building an image SEO workflow
Image optimization is not a one-time project. It needs to be part of your content workflow.
Before upload: Resize to the maximum display size needed. Convert to WebP or AVIF. Rename the file descriptively. Compress with a quality setting of 75 to 85 percent for photographs.
During content creation: Write descriptive alt text for every content image. Set decorative images to alt="". Add width and height attributes. Apply lazy loading to below-the-fold images.
After publish: Audit image performance in PageSpeed Insights. Check that images are not the largest contentful paint bottleneck. Verify images appear in Google Image Search for target queries within a few weeks.
Quarterly audit: Scan your highest-traffic pages for missing alt text, oversized images, and outdated formats (still serving only JPEG when WebP is available). Fix issues in batches, starting with your most valuable pages.
Image SEO is not glamorous work. But for sites in visual industries, it is one of the most underused traffic sources available. The sites that get the basics right, descriptive names, useful alt text, modern formats, fast loading, consistently outperform those that treat images as an afterthought.
