{"id":14879,"date":"2026-04-23T21:14:07","date_gmt":"2026-04-23T19:14:07","guid":{"rendered":"https:\/\/shortpixel.com/blog\/?p=14879"},"modified":"2026-04-23T21:14:08","modified_gmt":"2026-04-23T19:14:08","slug":"how-image-optimization-impacts-your-websites-visibility-in-ai-overviews","status":"publish","type":"post","link":"https:\/\/shortpixel.com\/blog\/how-image-optimization-impacts-your-websites-visibility-in-ai-overviews\/","title":{"rendered":"How Image Optimization Impacts Your Website’s Visibility in AI Overviews"},"content":{"rendered":"\n

Google’s AI Overviews don’t just pull text from web pages. They pull images too.<\/p>\n\n\n\n

If you search for “best running shoes for flat feet” or “how to repot a monstera,” the AI-generated summary at the top often includes product photos, diagrams, or step-by-step visuals, sourced directly from websites. And the pages those images come from get cited as sources, with a link back.<\/p>\n\n\n\n

That’s the part a lot of site owners haven’t connected yet. Your images aren’t just decoration. They’re content that AI systems evaluate, interpret, and sometimes feature in their responses. How well those images are optimized, their size, format, metadata, visual clarity, plays a direct role in whether your pages show up in AI Overviews.<\/p>\n\n\n\n

AI Overviews are multimodal<\/strong><\/h2>\n\n\n\n

This is the starting point most image optimization guides miss.<\/p>\n\n\n\n

AI Overviews launched in May 2024 and have been expanding steadily. Some industry data suggests they now appear on a large share of searches, particularly informational and product-related queries.<\/p>\n\n\n\n

But the important detail isn’t just that they exist, it’s that they include images. Product comparison queries often show photos sourced from review sites or stores. How-to queries pull in diagrams and screenshots. Recipe searches include food photography. When your image gets selected, your page gets cited.<\/p>\n\n\n\n

Google hasn’t published a formal spec on how images get chosen (they rarely do), but based on how AI Overviews behave in practice, a few patterns are clear. The AI tends to favor images that are visually sharp and easy to interpret. It favors images on pages that load fast and have proper structured data. And it checks whether the image actually relates to the query and to the content around it.<\/p>\n\n\n\n

Image clarity and computer vision<\/strong><\/h2>\n\n\n\n

Modern AI crawlers, Googlebot, GPTBot, and others, use computer vision to analyze your images at a pixel level. Same class of technology behind facial recognition and visual search.<\/p>\n\n\n\n

What does that look like in practice? A crawler can look at your product photo and identify “stainless steel water bottle” or “blue running shoe” without reading your alt text. It can read text embedded in infographics through OCR. And it can evaluate whether the scene in your image matches the topic of the page.<\/p>\n\n\n\n

This matters for AI Overviews because the system needs to understand what an image shows before deciding whether to include it in a response. The clearer your image, the more confidently the AI can classify it. Higher confidence means a better chance of being selected.<\/p>\n\n\n\n

And here’s where over-compression becomes a problem. If you’ve crushed a JPEG down to quality level 30, the artifacts, blurring, blockiness, color banding, don’t just look bad to humans. They make the image harder for AI vision systems to interpret. The crawler sees something, but it’s not confident about what it’s seeing.<\/p>\n\n\n\n

Modern lossy compression avoids this. Tools like ShortPixel Image Optimizer are designed to reduce file size significantly while preserving the visual details that both users and AI systems rely on.<\/p>\n\n\n\n

File size and the speed connection<\/strong><\/h2>\n\n\n\n

Image file size also connects to AI visibility through page speed.<\/p>\n\n\n\n

AI crawlers work on time budgets, often just a few seconds to fetch and process a page. If your page loads slowly, crawlers may not fully process it. Content that doesn’t get processed can’t get cited.<\/p>\n\n\n\n

Images are typically the heaviest elements on a page. On more than half of all websites, the main image determines the LCP (Largest Contentful Paint) score, the Core Web Vital that measures how fast your above-the-fold content appears. Google considers anything under 2.5 seconds “good,” but according to 2025 Web Almanac data, around 38% of mobile pages still don’t meet that threshold.<\/p>\n\n\n\n

Pages with poor LCP tend to rank lower, and pages that rank lower are less likely to be sourced by AI Overviews.<\/p>\n\n\n\n

We ran 11,000 images<\/a> through ShortPixel’s compression recently, real photographic content, mixed subjects, and saw a 46.5% reduction, from 536.6 MB down to 287.2 MB. For a WordPress site with a similar library, that’s potentially hundreds of megabytes of unnecessary weight removed.<\/p>\n\n\n\n

Practical target: most web images under 150KB. Hero images under 200KB.<\/p>\n\n\n\n

Does your image match your content?<\/strong><\/h2>\n\n\n\n

AI Overviews evaluate whether images on a page actually relate to the surrounding text. This is called multimodal analysis, the AI processes text and images together, not separately.<\/p>\n\n\n\n

If your page is about cleaning a cast iron skillet and your photos show that process, the visual and text content reinforce each other. Strong match, strong signal.<\/p>\n\n\n\n

If the same page uses a generic stock photo of a kitchen, no skillet in sight, the AI notices the gap. That mismatch can reduce the page’s relevance score, making it less likely to be cited.<\/p>\n\n\n\n

You don’t need professional photography for every post. Screenshots, diagrams, even a phone photo of the actual thing you’re writing about, all of these work, as long as they’re clear and genuinely relevant. What doesn’t work: dropping in unrelated stock imagery just to fill space.<\/p>\n\n\n\n

Alt text has a new job<\/strong><\/h2>\n\n\n\n

Alt text used to be the main way crawlers understood images. Now crawlers can see images on their own through computer vision. So alt text has shifted from primary descriptor to confirmation layer.<\/p>\n\n\n\n

The AI looks at your image, forms its own interpretation, then reads your alt text. If the two match, say it sees a walnut dining table and your alt text says “walnut dining table with visible grain”, that reinforces confidence. Good match, strong signal.<\/p>\n\n\n\n

If there’s a mismatch, the AI sees a table but your alt text says “image” or is blank, that weakens the signal. And something like “best dining table 2026 buy now free shipping”, that’s not alt text, that’s a keyword dump, and crawlers can tell the difference.<\/p>\n\n\n\n

Write alt text that describes what’s actually in the image. Plain, specific, honest. That’s it.<\/p>\n\n\n\n

Filenames and structured data<\/strong><\/h2>\n\n\n\n

A file called cast-iron-skillet-seasoning.jpg gives crawlers useful context before they even look at the image. IMG_4823.jpg gives them nothing. Worth renaming before you upload, doing it afterward in WordPress means dealing with URLs and redirects.<\/p>\n\n\n\n

Structured data is a bigger lever. When you add Schema.org markup, Product schema for product photos, Recipe schema for food images, HowTo schema for tutorials, you’re giving AI systems a machine-readable shortcut to understand what each image represents. Instead of the AI guessing “is this a product photo or a lifestyle shot?”, the schema tells it directly. Particularly useful for AI Overviews, where the system needs to categorize images quickly before deciding whether to feature them.<\/p>\n\n\n\n

Format matters: WebP and AVIF<\/strong><\/h2>\n\n\n\n

WebP produces files roughly 25\u201335% smaller than JPEG at similar quality. Every modern browser supports it, AI crawlers handle it natively, and there’s no real downside to making it your default.<\/p>\n\n\n\n

AVIF compresses even further, usage roughly quadrupled between 2022 and 2024, though browser support still has some gaps.<\/p>\n\n\n\n

If you’re still serving only JPEG or PNG, switching to WebP as your baseline (with JPEG fallback) is one of the simpler improvements you can make. Serving next-gen formats means less data per request, which directly improves how fast your page becomes usable, both for visitors and crawlers.<\/p>\n\n\n\n

On WordPress, tools like ShortPixel handle this automatically during compression.<\/p>\n\n\n\n

The WordPress thumbnail blind spot<\/strong><\/h2>\n\n\n\n

When you upload an image to WordPress, the system creates multiple resized versions, often 5 to 15 per upload, depending on your theme. A site with 1,000 uploads might have 10,000+ image files on disk.<\/p>\n\n\n\n

Here’s the thing: on most pages, it’s the thumbnails and medium sizes that get displayed, not the originals. If you’ve only compressed your originals, all those generated variants are still unoptimized, and they’re the ones actually affecting your page speed and crawler experience.<\/p>\n\n\n\n

Make sure compression covers every generated size. ShortPixel Image Optimizer<\/a> does this by default, processing all WordPress-generated variants automatically.<\/p>\n\n\n\n

Don’t lazy-load your hero image<\/strong><\/h2>\n\n\n\n

Lazy loading is great for below-the-fold images. WordPress enables it by default, and that’s generally the right call.<\/p>\n\n\n\n

But your hero image, the big one at the top of the page, is almost always your LCP element. If it’s lazy-loaded, the browser waits to request it, which makes your LCP worse instead of better.<\/p>\n\n\n\n

Fix: add fetchpriority=”high” to your hero image and exclude it from lazy loading. Everything else below the fold can stay lazy. Surprisingly common issue on WordPress sites, and one of the quicker wins for both page speed and AI visibility.<\/p>\n\n\n\n

Practical checklist<\/strong><\/h2>\n\n\n\n

Compress your full media library.<\/strong> All sizes, including thumbnails. Expect 50\u201370% savings. ShortPixel handles all sizes in one pass.<\/p>\n\n\n\n

Use clear, sharp images.<\/strong> Don’t over-compress to the point of blurriness. AI vision systems need visual detail to classify images confidently.<\/p>\n\n\n\n

Match images to content.<\/strong> Screenshots, diagrams, product photos, anything that genuinely illustrates the topic. Ditch unrelated stock.<\/p>\n\n\n\n

Serve WebP by default.<\/strong> JPEG\/PNG as fallback. Consider AVIF for modern-browser audiences.<\/p>\n\n\n\n

Write accurate alt text.<\/strong> Specific, plain descriptions. Confirms the AI’s own interpretation.<\/p>\n\n\n\n

Rename files before uploading.<\/strong> Cast-iron-skillet-cleaning.jpg, not photo_final_v2.jpg.<\/p>\n\n\n\n

Add structured data.<\/strong> Product, Recipe, HowTo, Article schema \u2014 whatever fits your content.<\/p>\n\n\n\n

Fix your hero image.<\/strong> Under 200KB, fetchpriority=”high”, not lazy-loaded.<\/p>\n\n\n\n

Use a CDN.<\/strong> Faster delivery for humans and crawlers.<\/p>\n\n\n\n

Check robots.txt.<\/strong> Don’t block GPTBot, ClaudeBot, or PerplexityBot.<\/p>\n\n\n\n

Monitor Core Web Vitals.<\/strong> Check images first when LCP is flagged.<\/p>\n\n\n\n

Image optimization won’t get you into AI Overviews on its own.<\/p>\n\n\n\n

But it removes one of the biggest blockers.<\/p>\n\n\n\n

Smaller images mean faster pages. Faster pages are easier to crawl. And pages that are easier to crawl and understand are more likely to be cited.<\/p>\n\n\n\n

That’s the part most sites still get wrong.<\/p>\n\n\n\n

FAQs<\/strong><\/h2>\n\n\n
\n
\n
\n

How do images actually appear in AI Overviews?<\/strong><\/h3>\n
\n\n

Google’s AI pulls images from third-party websites and shows them alongside the generated text summary. The source page gets a citation with a link. This happens most often for product queries, how-to searches, and visual topics where an image adds real value to the answer.<\/p>\n\n<\/div>\n<\/div>\n

\n

Does image quality affect whether my images get selected?<\/strong><\/h3>\n
\n\n

It seems to, yes. AI Overviews tend to feature sharp, well-lit images. Heavily compressed images with visible artifacts are harder for AI vision systems to interpret, which likely reduces their chances of being picked.<\/p>\n\n<\/div>\n<\/div>\n

\n

Is Alt text still important?<\/strong><\/h3>\n
\n\n

More than before, actually, but its job has changed. Crawlers now interpret images on their own through computer vision. Alt text serves as confirmation. Accurate alt text strengthens the signal; vague or missing alt text creates a mismatch that can work against you.<\/p>\n\n<\/div>\n<\/div>\n

\n

What file size should I target?<\/strong><\/h3>\n
\n\n

While there’s no specific recommendation, it’s best to keep it as low as possible without damaging the quality. Image filesizes usually determine your LCP score, which affects both rankings and how AI crawlers process your pages.<\/p>\n\n<\/div>\n<\/div>\n

\n

Should I switch all my images to AVIF?<\/strong><\/h3>\n
\n\n

Yes, but keep this in mind. AVIF compresses better than anything else available, but browser support isn’t universal. WebP is the safer default. Serve AVIF to browsers that support it and fall back to WebP or JPEG for the rest. ShortPixel Image Optimizer does this for you automatically.<\/p>\n\n<\/div>\n<\/div>\n

\n

I have thousands of images on WordPress. Where do I start?<\/strong><\/h3>\n
\n\n

Bulk compression across your entire media library, including all the thumbnail sizes WordPress generates. That single step makes the biggest immediate difference. ShortPixel Image Optimizer handles all generated sizes automatically.<\/p>\n\n<\/div>\n<\/div>\n

\n

Can image optimization alone get me into AI Overviews?<\/strong><\/h3>\n
\n\n

Honestly, no. You also need useful content, site authority, structured data, and solid technical health overall. But images are a smart starting point, fixing them improves several signals at once, and AI Overviews actively feature images, not just text.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n

\n

Try ShortPixel on WordPress for free!<\/h3>\n\n\n\n

Easily optimize your pictures and lower the filesize in bulk using ShortPixel Image Optimizer.<\/p>\n\n\n\n

\n
Get Started<\/a><\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Google’s AI Overviews don’t just pull text from web pages. They pull images too. If you search for “best running shoes for flat feet” or “how to repot a monstera,” the AI-generated summary at the top often includes product photos, diagrams, or step-by-step visuals, sourced directly from websites. And the pages those images come from […]<\/p>\n","protected":false},"author":37,"featured_media":14881,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-14879","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-world-of-wordpress"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/posts\/14879","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/comments?post=14879"}],"version-history":[{"count":1,"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/posts\/14879\/revisions"}],"predecessor-version":[{"id":14880,"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/posts\/14879\/revisions\/14880"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/media\/14881"}],"wp:attachment":[{"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/media?parent=14879"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/categories?post=14879"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/shortpixel.com\/blog\/wp-json\/wp\/v2\/tags?post=14879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}