Brand promotion: this article introduces Guangsuan's Google SEO services.
You added new product photos to your shop site, then opened Google Images and saw only small tiles that would not open larger. Before you pay for recompression or book a new shoot, work through two layers in order. This guide is for a public product page that you want indexed. It does not cover login-gated catalogues, staging copies, or pages that carry a noindex directive.
The short answer for a busy shop owner
Name the missing piece before you change files. A tile, an interactive preview, a viewing control, and the set of results are four different things. A viewer-side display difference alone does not show that your product file is missing from Google's index.
If shoppers can use Google Images normally but cannot find your products, move to your own page and file. If the odd display happens only on one of your devices, stay on the viewing side first. Repeat the same search in a new tab, write down the device and login state, and adjust only one factor per test.
First check: viewing setup
Keep the network the same while you test the browser, then keep the browser the same while you test the network. Write down what you changed and what happened after each single change.
Reload once, then run a plain query that you have not filtered. When one tile fails, open its source page where a link exists and open a second result for comparison. When many tiles fail, run the same query in a second browser on the same connection. A different result narrows the area to examine. It does not name a single cause by itself.
Look at site permissions in a narrow way. Desktop Chrome keeps image permission and script permission as separate switches. Inspect the setting for the affected site instead of resetting all sites. On a managed school or work device, you may need an administrator.
Run a private-window comparison and note whether you are signed in. When the private window behaves differently, list what else changed at the same time: extensions, stored data, account state, and settings. A private window is not automatically free of extensions, because an extension can hold permission to run there.
Test script behaviour and extensions one by one. A preview can stop responding while the tile and the source file still open. Pause one relevant extension, reload, and test again. Then try a different tile, because a single-result failure needs different evidence than a page-wide failure.
Write down query text, filters, and SafeSearch state before you remove anything. A locked filter setting and an absent viewing control do not prove that source sites deleted their files. Work with the controls shown on your device and follow the source-page link where one is offered.
Changing history, browser reset, and network together erases clues, so avoid that combination. When the source page opens, log it as one access observation. The preview may still use another resource or face another request condition, so one open does not complete the check.
Second check: publishing side
Start this part only when the viewing checks do not explain the symptom. You are now asking whether your page and file can be found, fetched, and kept eligible.
Confirm the exact product address, the date you checked, the index state, and the canonical that Google selected. When the selected canonical points elsewhere, you are checking the wrong address.
For Google to find a product picture, the page should reference it with a normal image tag pointing to an actual file. A file that appears only after a gallery script runs, only as a style background, or only after login is harder to treat as a crawlable reference. Keep a high-quality master, then build smaller derivatives for cards, listings, and zoom views.
Request the exact file address while signed out and read the status, the content type, and the body. A success code alone does not prove the picture was delivered if the body is a login screen or error page. Check robots rules for the image path, page-level exclusion, hotlink rules, firewall or bot checks, CDN cache, and redirect chains.
An accessible file or a passed live check does not promise indexing or a position. Missing from one query does not prove the file was never indexed. Read the recorded state with its date rather than repeating the same search.
Hypothetical teaching example: assume a boutique publishes 12 new product pages linked from one collection page, each with a 900-pixel card image. The owner sees small tiles without enlargement on a shop laptop, while the same query opens larger on a phone. That split points to the first check. If instead every device shows the same gap and the recorded state says Google knows the addresses but has not fetched them, the work moves to the second check. This example is hypothetical and is used only to show how the two paths diverge.
File work: when compression helps and when a new photo is needed
Handle files after the two checks are clear. Keep three ideas apart. Size sets pixel dimensions. Encoding sets how data is stored and, for lossy choices, how much detail is dropped. Delivery picks which file a screen receives. Making a file smaller does not by itself make it discoverable by Google.
Compare any new export against the master at the real phone and desktop sizes. Read small labels, edge lines, colour shifts, and product features that decide identification. A new suffix alone does not change the file; the converter must write a new file.
After you publish a replacement, ask the browser what it fetched. Open network tools, clear cache for the test, reload, and confirm the file name, size, and type. When a CDN or image service still sends an older derivative or an oversized version, purge that cache and test again before you call the change published.
Keep below-the-fold pictures deferred, but keep the first-view picture loading without delay. Do not mark every image as high priority. When another delay controls first paint, a smaller file will not move that mark by itself.
Choose reshoot only for representation faults: soft focus, wrong colour or material, missing scale cue, or too few pixels for the zoom slot. Encoding work cannot bring back detail that was already dropped or fix a misleading presentation.
For the file-side method, see Guangsuan's image compression guide for SEO, which separates dimensions, encoding, and delivery and shows how to confirm the fetched resource.
What to bring if you ask Guangsuan for help
Guangsuan can look at technical and content questions for an export-oriented independent site. It suits a shop owner who can supply page addresses and approve content changes, and who wants the scope, deliverables, and review method stated before work starts. Collect one page of notes so the team can confirm what needs checking:
Product page addresses, recorded index state with check date, selected canonical where it differs, and file addresses copied from the network panel on phone and desktop. These decide which address is examined.
Device, browser or app version, sign-in state, and the outcome of the second-browser and private-window tests. These show whether the fault stays with viewing.
Robots rules, CDN and cache settings, hotlink or firewall rules for the image path, and the gallery builder or plugin name. These show whether the request reaches the file.
Pages that must keep working after any edit: cart, checkout, enquiry form, and order mail on a shop site. Send access through an agreed secure route and keep passwords and customer data out of public channels.
For the viewing-side separation, read Guangsuan's Google Images troubleshooting guide. If you send the page address plus the symptom log, Guangsuan's Google SEO service can address technical and content issues within its published scope.
FAQ
Will compression make my images appear?
Not by itself. Compression changes transfer size at set dimensions. Discoverability, access permission, and eligibility need separate checks.
Should a missing preview trigger an ALT rewrite?
No. Settle the viewing cause first, then verify the publishing side. ALT text describes the picture for readers and search; it does not repair a blocked request.
One query shows nothing. Is the file unindexed?
No. One observation under one query, date, language, and filter set does not prove the full index state. Check the recorded state with its date.