Why website thumbnails don’t show up depends on where you expect the image. A Google Search result image, a Google Images or Discover preview, a favicon beside a result, and a social-link card are different features fetched by different systems. The reliable fix starts by naming the surface, then checking crawler access, the HTML that crawler receives, image metadata, preview directives, and recrawl timing.
This guide answers How do I fix missing website thumbnails? with a Google-focused diagnostic sequence, separate favicon instructions, social-preview boundaries, and a browser-free capture option using ScreenshotNeo.
First identify the missing image
Do not apply one fix to every “thumbnail” problem. Record the exact page, device, country or language context, query, and surface where the image is absent. Search appearance can vary by those factors, and automated image selection can change even when your code is unchanged.
| Surface | What you are looking for | Primary checks |
|---|---|---|
| Google Search text result | A larger image or preview associated with the result | Page and image crawl access, HTML image exposure, preview directives |
| Google Images or Discover | An indexed image or page preview | Discoverable image URL, rendered HTML, representative image signals |
| Favicon beside a result | Small square site identity icon | Home-page and icon crawlability, supported icon link, square dimensions |
| Social-link card | Image shown when a URL is shared | That platform’s own crawler, metadata and cache rules; verify with its current official documentation |
Google’s rules do not automatically describe every social network. Avoid assuming that an og:image tag, a particular pixel size, or a cache-refresh trick works everywhere.
#1 Best Overall
Why website thumbnails don’t show up
The crawler cannot fetch the page or image
A search engine must fetch both the document and the image. Accidental robots.txt disallow rules, authentication, firewall rules, geoblocking, hotlink protection, server errors, or a URL that works only in your logged-in browser can prevent a preview. A page that loads for you is not proof that Googlebot or Googlebot-Image can load it.
The image is not exposed in crawlable HTML
Google documents an image URL in an <img> element’s src attribute as discoverable, including an image inside <picture>. It does not index CSS images such as background-image. A visually perfect hero background can therefore produce no indexed image.
JavaScript or lazy loading hides the URL
Some implementations put the real URL only in a custom attribute, insert it after a click, or require scrolling. Verify that the relevant image is loaded without user action and that its URL appears in the rendered HTML’s src. URL Inspection in Search Console lets you compare the rendered page Google received with your source code.
Preview controls suppress the image
The max-image-preview directive applies to Google Search surfaces. none blocks image previews, standard permits the default preview, and large permits a larger preview. Check both a robots meta tag and the HTTP response header; either can carry the directive.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsGoogle selected another image—or none
Google’s selection is completely automated and can use several sources, such as an image embedded on the page, structured data, and page context. Metadata influences the choice but does not guarantee that a preview appears. A result can therefore have valid code and still show a different image or no image.
How do I fix missing website thumbnails? Follow this sequence
1. Reproduce and document the exact case
- Copy the precise URL and search query.
- Note whether the failure is in Search, Images, Discover, a favicon slot, or a shared link.
- Check another device or signed-out browser, but treat differences as context—not proof of a code failure.
2. Test public access to the page and image
Open the page in a private window and request the image URL directly. Confirm a successful response, the intended content type, and no login or consent gate that blocks a crawler. In Search Console, use URL Inspection on the page and inspect the rendered result. Check robots.txt for rules affecting Googlebot or the image path, and check server or CDN logs for denied requests.
3. Inspect the HTML Google receives
In the rendered HTML, find the intended image and confirm a usable absolute or resolvable URL in src:
<picture>
<source type="image/webp" srcset="https://example.com/hero.webp">
<img src="https://example.com/hero.jpg" alt="Product dashboard">
</picture>Keep the meaningful fallback in img src. Do not rely solely on CSS backgrounds, a JavaScript click, or a custom attribute such as data-src. If you use lazy loading, make sure the image URL is present and loads as the crawler renders the page.
4. Add representative image signals
Choose an image that explains the page, is high resolution, and has a sensible aspect ratio. Avoid using a generic logo as the only candidate. Where your page type supports it, provide a preferred image through supported structured data and an og:image tag:
<meta property="og:image" content="https://example.com/images/article-hero.jpg">These are signals, not commands. Google can select another image, and meeting best practices does not guarantee crawling, indexing, or serving.
5. Check preview directives
Search your HTML and response headers for a restrictive setting:
<meta name="robots" content="max-image-preview:none">If you want Google’s normal preview, use standard; if you permit a larger preview, use large. Apply the setting deliberately and ensure a CDN or framework is not injecting a conflicting header.
Recommended Free Tools
Rank #3
6. Expose hard-to-find images with an image sitemap
An image sitemap can help expose image URLs that are otherwise difficult to discover. It does not override blocking, authentication, or a missing src; it is an additional discovery path.
7. Request a recrawl and wait
After deployment, inspect the page again and request indexing for the home page or affected URL where appropriate. Processing is not immediate. Google’s favicon guidance says updates can take several days to several weeks; do not promise a fixed time for other image features. Recheck after the systems have had time to recrawl rather than changing five variables at once.
Fixing a missing favicon (not a page thumbnail)
A favicon is a separate site-identity feature. Put one supported icon reference in the home page’s <head> and make both the home page and icon crawlable by Googlebot and Googlebot-Image:
<link rel="icon" href="https://example.com/favicon.png">- Use a square file at least 8 × 8 pixels; Google recommends more than 48 × 48 pixels.
- Keep the icon URL available without authentication or blocking.
- Google supports one favicon per hostname, so changing multiple competing declarations can create ambiguity.
- A valid implementation still does not guarantee that a favicon will appear.
Use URL Inspection on the home page after publishing the change, then allow the documented recrawl window.
Social sharing cards: what you can and cannot infer
An og:image tag is a useful, widely recognized signal, but current official documentation for each social service does not establish crawler rules, image dimensions, cache lifetimes, or debugger workflows here. Diagnose the affected network separately: confirm its crawler can fetch the page and image, inspect the HTML it receives, and follow that service’s current official documentation. Do not treat Google’s max-image-preview directive as a universal social-card control.
Or skip the browser setup
ScreenshotNeo returns a PNG, JPEG, WebP, or PDF from one GET request. Before capture it accepts consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and whether it was billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo documentation for all options, including full-page and selector captures, device and retina settings, waits, custom CSS or JavaScript, request blocking, cookies, headers, geolocation, signed links, asynchronous webhooks, bulk capture, caching, and PDF controls.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 shots each month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan. Create a free ScreenshotNeo account.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, 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 minuteTroubleshooting symptoms and fixes
| Symptom | Likely cause | Next action |
|---|---|---|
| Image works in your browser but not Search | Crawler block, authentication, or rendered-HTML gap | Use URL Inspection, review robots rules and logs, and verify rendered img src |
| Only a CSS hero is absent | Background images are not indexed as image content | Add a meaningful img src element |
| Wrong image appears | Automated selection or weak page signals | Use a representative image, structured data and og:image; accept that selection is not guaranteed |
| No preview anywhere in Google | max-image-preview:none or access failure |
Check meta and headers, then test page and image fetchability |
| Favicon remains absent after a valid change | Recrawl delay or eligibility decision | Inspect the home page, request indexing, and wait days to weeks |
Performance, reliability, and cost considerations
- Serve stable image URLs and avoid expiring, signed URLs that a crawler cannot refresh.
- Keep image responses reasonably sized and available over HTTPS; a slow or failing origin can prevent fetching even when markup is correct.
- Do not rebuild metadata on every request in a way that changes the preferred image unpredictably.
- Test the rendered page, not only server source, whenever a framework performs hydration or lazy loading.
- Separate “not displayed” from “not billed” when using a capture service: ScreenshotNeo reports verdict and billing status in response headers, while Google’s appearance remains an independent indexing decision.
What Google still does not guarantee
Google states that image-preview selection is completely automated. It also states that a favicon is not guaranteed even when all guidelines are met, and that meeting Search best practices does not mean Google will crawl, index, or serve content. Treat fixes as making the page eligible and understandable—not as a promise of a particular result for every query, device, or country.
Frequently Asked Questions
Should I put the thumbnail in CSS or HTML?
Use a normal <img src> for important content images. Google says it does not index CSS background images as image content.
Does og:image force Google to show that picture?
No. It is a preferred-image signal. Google’s selection is automated and may use other sources.
How long should a favicon fix take?
Google’s favicon guidance describes processing that can take several days to several weeks. There is no fixed display time for other preview types.
Can ScreenshotNeo make Google display a thumbnail?
No. ScreenshotNeo captures a clean rendering for your own workflows; Google’s crawling, indexing, and preview selection remain separate systems.
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.
