If website thumbnails don’t show up, first identify which image is missing: a Google Search or Discover image preview, a favicon beside a search result, or a card image when someone shares a link. These are separate features, with different crawlers and display rules. For Google Search, start by checking whether Google can fetch both the page and its image, then inspect how the image appears in the page’s HTML and whether a preview directive limits it.
Why website thumbnails don’t show up
A thumbnail can be absent because a crawler cannot access the page or image, cannot discover the image in the way it expects, or is told not to show a preview. It can also be a selection issue: Google chooses images automatically, so providing a preferred image does not guarantee it will appear.
The right diagnosis depends on the surface. A Google Search image preview is not a favicon, and neither is necessarily the same as a social-sharing card. Search appearance can vary by device, country, language, query, and other context. Identify the affected surface before changing site-wide metadata.
- Google Search or Discover image: check page and image crawl access, rendered HTML, image signals, and preview directives.
- Favicon beside a Google result: check the home page’s icon reference and crawl access to both the home page and icon file.
- Shared-link preview: check the affected platform’s official guidance. Requirements, crawler behavior, and cache-refresh processes differ, and Google’s rules should not be assumed to control third-party previews.
How do I fix missing website thumbnails?
For a Google Search image preview, work through these checks in order. Change one relevant issue at a time, then inspect the rendered page and allow Google to recrawl it.
#1 Best Overall
1. Confirm the missing image and page URL
Record the exact page, image, and place where the image is missing. A Google Search result image is associated with an indexed image embedded on a page; a favicon is the small site-identity icon. If the issue occurs only in one search context, remember that appearance can vary. Don’t apply a favicon fix to a page image or assume an og:image change controls every share service.
2. Check that Google can access the page and image
Both the page and the image need to be publicly accessible to the relevant crawler. Review robots.txt, authentication, firewall rules, and other access controls for accidental blocks. Google recommends checking the page with Search Console’s URL Inspection tool and checking for unintended robots.txt restrictions when content is missing from Search (Google’s recrawl guidance).
Inspect both the page response and image URL. A page that loads for you may still present an access restriction to a crawler, and an image can be blocked independently of its page. URL Inspection can show the page Google received and its rendered output; use that evidence rather than relying only on what your logged-in browser displays.
3. Check preview controls
Review robots metadata and HTTP response headers for Google’s max-image-preview directive. Google documents three values for its Search surfaces: none prevents image previews, standard permits the default preview, and large permits a larger preview (Google robots meta tag documentation).
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If previews are intended, remove an unintended none restriction or use an allowed value consistent with the site’s policy. This directive concerns Google Search surfaces; do not treat it as a universal setting for social-sharing services.
4. Expose the image in crawlable HTML
For content images, use a standard <img src="..."> element. Google says it can discover image URLs in an image element’s src attribute, including an image inside a <picture> element, and does not index CSS background images as images (Google Images SEO best practices). A decorative CSS background may be appropriate for design, but it is a poor substitute when the image is content that should be discoverable.
If the page uses lazy loading, verify that the image loads without requiring a user action and that its URL appears in the rendered HTML’s src attribute. Use URL Inspection to examine what Google rendered, especially when JavaScript or a lazy-loading library fills the image URL after initial page load. An image sitemap can also help expose images that are otherwise difficult to discover.
5. Give Google a useful image signal
Where appropriate, identify a preferred page image with supported structured data or an og:image tag. Choose an image that represents the page rather than a generic site logo, and avoid an extreme aspect ratio. A high-resolution image gives Google a useful candidate. These signals influence selection; Google may draw on multiple sources and decides automatically which image, if any, to show.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Google describes image-preview selection as automated and based on multiple sources in its Image SEO Best Practices. That means correct metadata improves the information available to the system but cannot force a particular preview or guarantee one will display.
6. Treat a favicon as a separate repair
If the missing image is the small icon beside a result, add a supported <link rel="icon" href="..."> reference in the home page header. Make sure both the home page and favicon file are crawlable by Googlebot and Googlebot-Image. Google supports one favicon per hostname and says the icon should be square, at least 8 by 8 pixels; it recommends an image larger than 48 by 48 pixels. These are favicon eligibility guidelines, not dimensions for ordinary page thumbnails (Google favicon guidance).
Rank #3
Following the guidance still does not guarantee that Google will show the favicon. Do not use favicon dimensions as a supposed fix for a missing page image.
7. Request a recrawl and check again
Once you fix access, markup, or preview controls, inspect the rendered page again and use Search Console’s URL Inspection to request indexing of the home page where relevant. Google says favicon processing can take several days to several weeks, depending on when its systems refresh the content. That timing is specific to favicon processing; it is not a promised update window for other image features.
Recommended Free Tools
What to inspect in the rendered page
When the browser view and search result disagree, the rendered output is the useful point of comparison. In Search Console URL Inspection, check whether Google can fetch the page and whether the image URL is present after rendering. Compare that with the page source and the delivered image URL.
- Image URL present in rendered
src: confirm the response is accessible and the URL is not blocked. - Image appears only after a user interaction: revise lazy loading so the image can load without that interaction.
- Image is a CSS background: use a content-image element when it should be indexed.
- Page and image are accessible but no preview appears: verify preview controls and metadata, then allow for Google’s automated selection and recrawl.
Common failure modes and fixes
| Symptom | Likely issue | What to check or change |
|---|---|---|
| The image is visible to visitors but absent from Google’s rendered page. | It may be added only after user action or not exposed in a discoverable image element. | Inspect rendered HTML; expose the URL in an image src and load it without requiring a click. |
| The page appears, but its image cannot be fetched. | The image URL may be blocked or restricted separately from the page. | Check the image response and robots/access rules for the image URL. |
| No image preview appears on Google Search surfaces. | A preview directive may restrict it, or Google may choose not to display a preview. | Check metadata and headers for max-image-preview; remember selection is automated. |
| A logo or unrelated image appears instead. | Google may select another image from the page or its available signals. | Provide a representative preferred image through suitable metadata or structured data and ensure it is crawlable. |
| The small icon beside the result is missing. | This is a favicon issue, not a page-thumbnail issue. | Check the home page’s icon reference, file access, square format, and Google’s favicon guidance. |
| A link preview is missing only on one sharing platform. | The service may use its own crawler, metadata handling, or cache. | Consult that service’s official documentation; Google’s rules do not establish its behavior. |
Or skip the browser setup
If you need to inspect how a page renders without setting up your own browser automation, ScreenshotNeo can return a screenshot or PDF with one GET request. The API supports PNG, JPEG, or WebP screenshots, and its parameters include options such as full-page capture and custom waiting behavior. A screenshot can help you inspect the page’s visual rendering; it does not show what Google’s crawler received or guarantee that Google will select an image.
See the ScreenshotNeo API documentation. Example cURL request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhat Google’s guidance does—and does not—promise
Google’s documentation provides technical ways to make page images and favicons accessible and understandable, not a guarantee of search display. Its Search Essentials state that meeting requirements and best practices does not mean Google will necessarily crawl, index, or serve content (Google Search Essentials). Keep the distinction in mind: fixing a block or markup problem improves eligibility and discovery, while final appearance remains subject to crawling, indexing, and automated selection.
Frequently Asked Questions
Can I force Google to show a specific thumbnail?
No. Image metadata and structured data can signal a preferred image, but Google selects previews automatically and may not show one.
Does a missing thumbnail mean Google has not indexed my page?
Not necessarily. A page can be indexed while an image preview is not selected or cannot be fetched. Check the page and image separately in Search Console URL Inspection.
Will ScreenshotNeo tell me what Googlebot sees?
No. ScreenshotNeo captures a page for visual inspection; Google’s URL Inspection in Search Console is the relevant tool for examining Google’s rendered page.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
