Google Confirms Image Thumbnails Update Slowly in Search Results

Google's John Mueller confirmed this week that image thumbnails in Search results are slow to update — and the situation gets even stickier when the old image is still living somewhere on your page. According to Google Search: It's Normal For Image Thumbnails To Be Slow To Update, the issue came to light after a recipe site owner reported that a new image, properly referenced in JSON-LD structured data, had still not replaced the old thumbnail in Search after two full weeks.

The site in question is Inspired Taste, and the page was their easy baked apples recipe. The site owner, Adam, replaced the primary recipe image with a newer version and updated the JSON-LD markup to point to it. Google kept showing the old one. He wrote on Bluesky: "A recipe card image is stuck. It won't update to a new image we give in JSON-LD markup. We've waited two weeks & it won't change."

Mueller replied on Bluesky and acknowledged the situation directly. His response: "I'll pass a note on to the team, but in general, this can happen. The image is still very prominent on the page & continues to exist on the site, so it's not unexpected to continue to be picked as a thumbnail." That one line tells you a lot about how Google's image selection actually works.

The Details: What Was Actually Going On

Here's the core of the problem. When Inspired Taste updated their primary image, the old image didn't disappear from the page entirely. It had been moved further down — still visible, still prominent, still crawlable. Google's systems saw it as a highly relevant image for the page and kept selecting it as the thumbnail.

This matters because it shows that Google's thumbnail selection isn't purely driven by what your structured data says is the primary image. Prominence on the page plays a real role. If an image is still there, still large, and still contextually related to the topic, Google may continue surfacing it regardless of what your JSON-LD markup declares.

To try to force the issue, Adam eventually removed the old secondary image from the page entirely — on or around September 11, according to the report. And here's the interesting twist: by the time Barry Schwartz was finishing the article on September 14, the thumbnail had already updated. Mueller's take on whether Google manually pushed a fix? "I imagine this is just the normal reprocessing that happens in search pipelines." Schwartz himself noted he doubts Google intervened over the weekend, and trusts that explanation.

So the resolution — removing the old image from the page entirely — appeared to work faster than waiting on structured data alone. That's the real lesson buried in this story.

Why It Matters for Your SEO

Recipe sites heading into the holiday season are particularly exposed here. A stale thumbnail on a high-traffic recipe page isn't just a cosmetic annoyance. It affects click-through rate. A more visually appealing image is one of the only levers you have in organic search results, especially in image-rich verticals like food, travel, and home decor.

But the lesson applies well beyond recipe sites. If you've ever updated a product image, swapped a blog header photo, or refreshed a service page visual and wondered why Google Search still shows the old one — this is your answer. Structured data helps, but it doesn't override what Google's crawlers find when they look at the actual rendered page. The page itself is still the ground truth.

And yes, this happens more than most site owners realize. I've seen teams spend time debugging their schema when the real fix was simpler: the old image was still sitting on the page somewhere, just lower in the layout. Google doesn't forget images the way we'd like it to.

There's also a broader takeaway here about how Google handles visual signals versus markup signals. Structured data is a strong hint. Page prominence is often the deciding factor. When those two conflict, page prominence frequently wins — at least in the short term.

What to Do Now

If you've updated an image and Google Search is still showing the old one, here's where to start:

1. Audit the full page for the old image — not just the hero or the structured data. Check inline content, galleries, related-post widgets, and anywhere the old image might still be referenced in the HTML. If it's there, Google can find it.
2. Remove the old image entirely from the page if it's no longer serving a purpose. Don't just demote it. Mueller's comments make clear that a prominent, still-present image will keep getting picked up regardless of what your schema says.
3. Update your JSON-LD to reference the new image URL explicitly, and make sure that new image is actually live, crawlable, and not blocked in robots.txt.
4. Request a recrawl via Google Search Console for the specific URL. This won't force an instant thumbnail update, but it signals to Google that the page has changed and gets you in the reprocessing queue sooner.
5. Be patient — and set realistic expectations with clients or stakeholders. Mueller confirmed that images update more slowly than text content by default. Two to four weeks is not unusual. If you're managing a content site at scale, site audit tools that flag stale image references across large page sets can save you a lot of manual digging.

Background and Context

This isn't the first time image thumbnail behavior in Google Search has confused site owners. Google's systems for selecting representative images from a page have always involved more than just structured data. The algorithm weighs image size, position on the page, contextual relevance, and historical association between an image URL and a page URL. That last one is the killer for fast updates — once Google's index associates a specific image with a page, breaking that association takes real recrawl cycles.

Recipe sites are a notable case because they rely heavily on visual engagement in Search. A rich result with a recipe image can be the difference between a click and a scroll-past. The structured data for recipes specifically includes an "image" property for exactly this reason — but as this situation shows, schema alone won't override what Google finds in the page body.

Mueller's transparency here is useful. He didn't dismiss the complaint, acknowledged it as a real pattern, and passed it to the team while also being honest that it's an expected behavior rather than a guaranteed bug fix. That kind of signal from Google is worth tracking — it tells you where to spend your troubleshooting energy and where to just wait it out.

If you're running an agency and managing sites where visual search presence matters, it's worth having a clear process for image updates — not just schema updates. Aergos flags technical issues like these during site audits so you're not discovering them weeks later when a client notices the wrong image in their search results.