Wrong Image in Google Search Results? How to Change the Thumbnail

Why is the wrong image in Google search results, and what should you do?

A wrong image in Google search results means the thumbnail Google picked for your page is not the one you wanted. Google chooses that image automatically from signals on the page. You can guide the choice by naming a preferred image, keeping it crawlable, and then waiting for a recrawl.

Do not panic, because this is usually a signal problem you can fix. However, you will not see the result right away. Google has to recrawl the page, process the image, and then update the search result.

Start with this short list:

1. Find out which image file shows up in the search result.
2. Check which signals on your page name a preferred image.
3. Confirm the image is not blocked by robots.txt.
4. Request a recrawl in Search Console and give it time.

The sections below explain each step. Our team sees this problem often in SEO consulting projects, and the fix usually comes down to consistent signals and patience.

Is a search thumbnail the same as a favicon or an image result?

No, these are three different surfaces. The thumbnail is the preview image shown next to some page results. The favicon is the small site icon shown in the result. Image results are a separate listing of individual images in Google Images.

This distinction matters, because the wrong fix wastes time. For example, if your logo looks wrong, you probably need the favicon side. Our favicon not showing guide covers that case.

This article focuses only on a wrong, unrelated, or outdated thumbnail next to a page result. For general image compression and speed, see our image optimization guide. We will not repeat it here.

• Thumbnail: the preview image next to a page result.
• Favicon: the small site icon in the result.
• Image results: the separate listing in Google Images.

Bear in mind that this problem hits corporate sites, online stores, and busy blogs most often. As the page count grows, templates start making image decisions for you. So fixing one page is not enough; you also need to understand how the template behaves.

How does Google choose the thumbnail for a page?

According to Google's image SEO best practices, the preview image comes from several sources, and Google selects it automatically. So no single tag guarantees the outcome. The prominent image on the page, its relevance to the content, and its quality all play a part.

Google can also consider your preference. The documentation names two ways: the primaryImageOfPage property from schema.org and the og:image value. Both let you say which image represents the page.

The key point is that these signals are hints, not commands. If Google finds the image inconsistent with the page, it may pick another one. Therefore you should point the hint at a representative image.

The documentation says Google favors relevant and representative images. It also suggests avoiding generic images, extreme aspect ratios, and text-heavy graphics.

Which signals tell Google your preferred image?

The official documentation lists two main ways. First, you can use the primaryImageOfPage property in the page's structured data. Second, you can define og:image in the head section of the page. For background on structured data, read our schema markup guide.

These two signals should not conflict. For example, if og:image shows a campaign banner and primaryImageOfPage shows a product photo, Google may hesitate. So point both to the same representative image.

A practical checklist:

• First, pick the main image of the page and choose one file name.
• Then make the social sharing value (og:image) and the structured data name the same file.
• Also use a full image address and keep it reachable from the page.
• Finally, actually use the same image inside the page content.

You do not have to write code. Most content management systems and SEO plugins let you fill these fields in a form. If you want a ready helper, try our meta tag generator.

What are the most common causes of a wrong thumbnail?

In our experience, the causes fall into a few groups. None of them is rare, and most are configuration mistakes. Still, you only learn which one applies to your site by checking.

• First, no preferred image is named on the page, so Google chooses from the content.
• The og:image value and the structured data point to different files.
• Your preferred image is blocked by robots.txt or cannot be crawled.
• Also, the image is added only as a background style, not as a standard image element.
• Sometimes the old image stayed at the same address, so Google shows a cached version.
• Then there are images that are too small, extremely tall or wide, or full of text.
• Finally, a theme or plugin may add the same default image to every page.

Check the last item carefully. On many sites, every page shares the same logo or placeholder image. In that case, Google has nothing else to pick.

How do you fix the wrong image in Google search results?

The fix runs in order. Do not skip ahead, because the problem usually shows up in the first three steps. The sequence below reflects the simple routine our team uses in the field.

1. Find the file address of the wrong image in the search result. You can right click the image and copy its address.
2. Look in the page source to see where this image appears. Work out whether the theme, a plugin, or a template adds it.
3. Choose one representative main image and define the same file for both og:image and primaryImageOfPage.
4. Check that the image address is not blocked by robots.txt.
5. Confirm the image sits on the page as a standard image element.
6. Publish the change, then inspect the URL in Search Console and request indexing.
7. Wait anywhere from a few days to a few weeks, then check the result again.

In short, the goal is to send Google one consistent message. After that, little else is in your hands; the rest depends on recrawling.

How do you check that the image is crawlable and indexable?

Google cannot choose an image it cannot see. So verify access first. If the image file is blocked by a robots.txt rule or sits behind a login, Google cannot use it as a preview. Our robots.txt guide explains the logic.

The official documentation also says Google crawls images in the source attribute of a standard image element, but it does not index CSS images. So if your main image is a background style, it may not be a thumbnail candidate. For responsive images, the documentation recommends keeping a fallback source attribute.

The documentation lists the supported formats too: BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF. Matching the file extension to the real format is a good habit.

Check these points:

• First, does the image address open in a browser, or does it ask for a login?
• Also, is the image blocked by robots.txt?
• Then, is the image added as a standard image element?
• Finally, is the file type one of the supported formats?

For indexing problems, our guide on finding unindexed pages also helps.

Which image should you pick as the thumbnail?

The right image explains the page topic at a glance. The documentation asks for relevant and representative images. So on a product page, choose the product itself. On a blog post, choose an image that illustrates the topic. A generic stock photo or a logo is a poor choice.

We do not give exact size or ratio numbers, because Google does not publish them as fixed values. The general principle is to avoid extremely tall or wide images, keep the resolution reasonably high, and skip text-heavy graphics.

An original image also builds trust. A real photo of your product, team, or service gives a more lasting representation than a generic picture. Moreover, you can use that image consistently on social networks and in ads.

Ask yourself these questions:

• First, does the image explain the page topic on its own?
• Second, is it still readable when shrunk?
• Third, is the main subject centered, or does it vanish when cropped?
• Finally, is the same image reused on many other pages?

To resize and convert files, use our image resizer. For writing descriptions, our alt text guide helps.

How does max-image-preview affect the thumbnail?

The max-image-preview setting is one of the robots directives. It limits how large an image preview may be in search results. According to the official documentation, it takes three values: none, standard, and large. None shows no preview, standard may show a default preview, and large may show a bigger preview up to the viewport width.

So if no thumbnail appears at all, check this setting. A theme or SEO plugin may add the none value to your page. In that case, even the right image will not show as a preview.

The documentation also notes that the setting does not apply where a publisher separately granted permission through structured data or a license agreement. See the robots meta tag documentation for details.

This setting does not fix a wrong image. It only controls how big the preview may be. Manage image choice and preview size separately.

When will the wrong image change in Google search results?

We cannot give an exact time, because Google does not promise one. The change depends on Google recrawling your page and processing the new information. Recrawl frequency differs from page to page.

In its favicon documentation, Google says crawling can take anywhere from several days to several weeks. There is no separate promise for thumbnails. Still, a similar expectation is realistic. See the favicon documentation for the wording.

Two things help while you wait. First, ask for indexing of the page with the URL Inspection tool in Search Console. Second, strengthen the page's internal links, because frequently visited pages tend to be crawled sooner.

Results can also look different depending on the device and the type of search. So do not judge from one search. Try several queries, a private window, and another device.

Checking once a week is enough. If nothing changed after that long, review your signals again.

Why does the old image still show in search results?

There are a few logical reasons. The first is that Google has not recrawled the page yet. The second is that you replaced the old image with a new one under the same file name. In that case, Google may keep showing the cached version for a while.

The third is a content delivery network (CDN) or server cache. The cache may keep serving the old file. Review your image loading setup as well; our lazy loading guide can help.

The safe approach is to use a new file name whenever you swap an image. That way Google sees the new address as a separate image and nothing gets mixed with the old record. If the old address stays on the page, remove it.

• First, give the new image a new file name.
• Then clear the cache.
• Next, ask for a recrawl of the page.
• Finally, remove the old image address from the page.

Do URL parameters and SafeSearch affect the thumbnail?

Sometimes, but they are separate topics. Parameter versions of the same page can look different in search results. In that case, check which address got indexed. For parameters, read our srsltid parameter article.

Filtering by SafeSearch is a completely different process. If parts of your site are filtered by mistake, read our SafeSearch article.

Do not confuse these cases with a wrong thumbnail. A wrong thumbnail means Google represents your page with the wrong image. Parameter and filter problems affect the result itself.

Here is a short comparison:

Is a social sharing preview the same as the search thumbnail?

No, they are not the same, but they are connected. Social networks also read the og:image value and show it in the share card. Google treats the same value as a hint for the page's representative image. So one field serves two different surfaces.

For that reason, a card that looks right on social media does not guarantee the right image in search. Google makes its own choice. Still, if you see the wrong image on the social card, you probably gave a wrong signal in search too.

There is a small trap here: social platforms keep cards in their own cache. After you change the image, you may keep seeing the old card. That is independent of Google, so check both separately.

A practical tip: if you prepare a special sharing image for a campaign, use it only on the campaign page. On permanent core pages, keep a lasting, representative image.

How does image choice change on product, blog, and category pages?

The right image depends on the page type. On a product page, a clean and recognizable product photo is the safest choice. Meanwhile, a blog post works well with a cover that illustrates the topic. A category page, in contrast, needs one image that best represents the category.

Category pages cause the most trouble. They hold dozens of product images, and it is unclear which one is representative. Google may pick one at random. Therefore define a deliberate representative image for each category.

• Product page: a plain-background image, because it shows the product itself.
• Blog post: an image that explains the topic, with little text on it.
• Category page: one consistent image that sums up the category.
• Service page: an original image of the team or the service.

An original image always beats a stock image. Stock images appear on other sites too, so they do not set your page apart.

What should you check when preparing the image file?

The official documentation recommends descriptive file names. So instead of a generic name, choose one that describes the subject. Place the image near the relevant text and use it on a page that fits the topic. Also write alt text that is short, informative, and not stuffed.

According to the documentation, alt text helps Google understand the image and improves accessibility. Keyword stuffing, on the other hand, hurts the user experience.

Speed matters too. A very heavy image slows the page, but an over-compressed image looks blurry. Use our image optimization guide above to find the balance.

A short preparation list:

• First, give the file a descriptive name.
• Also keep the file extension consistent with the real format.
• Then write short alt text that fits the topic.
• Finally, place the image next to the related text.

Does an image sitemap help the thumbnail?

It does not pick the thumbnail directly, but it helps Google discover the image. According to the official documentation, image sitemaps help Google find image addresses it might otherwise miss. Moreover, you can include image addresses from another domain, which matters for sites that use a CDN.

So if your images load through JavaScript or sit on a CDN, an image sitemap can be useful. On an ordinary site you often do not need one. For the general idea, see our XML sitemap guide.

Remember that a sitemap is a hint, not a guarantee. Keeping the image address crawlable matters more than listing it. Think about access first, then the sitemap.

Which mistakes keep the wrong image in Google search results?

Some habits prolong the problem. The most common mistake is expecting a result right after a single change. Next comes leaving several conflicting signals on one page. Third, adding the image only through CSS.

Another mistake is using placeholder images on every page. In that case, Google finds the same image everywhere and cannot make a distinctive pick. Also, text-heavy graphics become unreadable when shrunk, yet Google may still pick them.

Avoid these:

• First, waiting for Google to choose without giving any preference signal.
• Also, blocking the image with robots.txt but still expecting a preview.
• Then adding the same placeholder image to every page.
• Next, replacing the old image under the same name and expecting an instant result.
• Finally, using an image from another site without permission.

On the last point, mind copyright. This is not legal advice; ask a specialist about licensing questions.

How do you monitor the page in Search Console?

Search Console is the most reliable way to see how Google views your page. With the URL Inspection tool, you can check whether the page is indexed, its last crawl status, and your indexing request. For access, read our Search Console guide.

Menu names and interface texts can change over time. So find the relevant section in the panel and compare the screen with the official help page. You do not need to memorize each label.

To try a preview yourself, our Google SERP preview tool simulates how the title and description look. It does not show the thumbnail, but it lets you check the text side.

After every change, keep a note for the page: which image, on which date, with which signal. That way you can tell more easily what affected the result.

What does the full checklist look like in order?

The list below puts the whole article into one flow. If you follow the same order for every page, you can see which step blocks you. Most of the time, the problem sits in one of the first five steps.

1. Note the file address of the image in the search result.
2. Find where this image comes from on your page.
3. Define one representative image for the page.
4. Point og:image and primaryImageOfPage to the same file.
5. Verify the image is crawlable and not blocked by robots.txt.
6. Check that the image is a standard image element.
7. Make sure the max-image-preview value is not none.
8. Give the new image a new file name.
9. Publish the change and request a recrawl in Search Console.
10. Check weekly and update your notes.

This list fits any site, but nobody can guarantee how long the result takes.

Which example scenarios produce a wrong thumbnail?

The scenarios below are not real clients. They are examples of patterns our team sees often. In each one the problem comes from a different place, yet the fix still relies on consistent signals.

Scenario one: on a corporate site, every page uses the same default sharing image. The same image shows next to every result. The fix is to define original representative images for the key pages.

Scenario two: a store replaces last season's banner with a new one under the same file name. The old banner keeps showing for a while. The fix is to use a new file name and ask for a recrawl.

Scenario three: a blog adds its cover only as a background style. Google cannot see it as a candidate and picks another image from the content. The fix is to add the cover as a standard image element.

• Same default image: instead, define original representative images.
• Same name after a swap: then give the image a new file name.
• Background style image: also switch to a standard image element.

These examples are stories, not calculations; we give no numbers or success rates.

When should you get expert help?

In most cases you can solve this yourself. However, if several weeks pass with no change, or many pages show the same problem, you need a technical review. Template level mistakes do not end with page by page fixes.

Our team first checks the signals, then image access, and finally how the template works. Once we find the root cause, a single fix can affect hundreds of pages. This is not a guarantee, only the method we follow.

If the template itself is the problem, our web design service can help. For ongoing technical checks, see our SEO consulting service. In every case, beware of anyone who asks for unauthorized access to your site or accounts; that is never a safe solution.