Product Brief Shipped, Images Still Small? Check Viewing First
GetPhoto ecommerce teams see new PDP photos as small tiles in Google Images: name the symptom, run single-change browser checks, then verify PDP address, file access and eligibility before compress or reshoot.
Brand promotion: this article introduces Guangsuan's image-indexing checks for ecommerce photo teams.
Your team sends a product photo brief, approves PDP heroes plus paid-social crops, publishes the product page, then hears that Google Images shows only compact tiles that do not expand. Pause asset work at this point. A control that looks absent on one screen and a file that cannot be fetched need different repairs, and neither observation alone proves your pictures sit outside Google's index. This note covers a public PDP you intend to keep searchable. It does not cover a login-gated catalog, a staging duplicate, or an address that carries noindex.
What the team should name before touching assets
Write one line that states which gap you actually see. Empty tiles across many results, tiles that render while tapping opens nothing larger, an expand control you cannot locate on this handset, and a thinner or blurred set under present filters are four separate states. A layout that hides a control on your phone does not prove the file request failed. One odd lookup under one date, language, and filter set does not describe the whole index state.
If shoppers can otherwise use Google Images normally while your own PDP pictures stay small, shift attention toward your own address and file. If the odd display follows only one laptop, one browser profile, or one login state, keep the work on the viewing side and leave masters untouched.
Pass one: confirm the viewing path with single changes
Run the same wording in a fresh tab, note hardware, browser build, and login state, and vary only one factor per round. Test browsers while the connection stays fixed, then test connections while the browser stays fixed, and write the outcome after each round. A changed display narrows where to look next without naming a single root cause by itself.
- Reload once, then run a plain everyday phrase for contrast. When one tile stalls, open its publisher page where a link exists and compare a second tile. When most tiles stall, repeat the same phrase in a second browser over the same connection.
- Repeat the phrase in a private window and record login state. A private window can still run permitted add-ons, so a different view there points jointly at add-ons, stored data, account state, and settings rather than proving stored data is damaged.
- Pause one script-related or content-blocking add-on, reload, retest, then restore it before testing the next. A tile and its origin file can still open while the scripted overlay stays shut.
- In desktop Chrome, picture access and script access sit in separate site switches, so inspect the affected site instead of resetting every site. On a managed work device, ask an administrator where permission is locked.
If the publisher page loads, file that as one access note. The overlay preview may draw on another asset or meet another request rule, so one successful load does not close the case. Do not clear history, reset the browser, and swap networks in one move, because that combination erases the trail you need.
Note wording, filters, and SafeSearch position before you remove anything. There is no fixed tile count per screen, and a filtered view does not show that origin sites deleted files. For the viewer-side method, see Guangsuan's Google Images troubleshooting guide.
Pass two: confirm the PDP address and file can be fetched
Start this pass only when pass one leaves the same small-tile gap on every device and connection. Confirm the exact PDP address, the date you checked, the recorded index state, and which canonical Google picked. When the picked canonical points elsewhere, you are auditing the wrong address.
Key visuals should sit in ordinary image markup that points to real file addresses. A picture that appears only after gallery logic runs, only as a styling backdrop, or only after sign-in is harder to treat as a crawlable reference. Fetch the file address while signed out and read status, content type, and body together. A success status with a login screen or error body inside is not a delivered picture.
Review robots rules for the image path, page-level exclusion, hotlink or firewall screening, CDN cache, and redirect chains, plus surrounding copy and loading behavior. Keep reachability, eligibility for indexing, and query performance as three separate judgments. A reachable file or a passing live check does not promise indexing or placement, and absence from one phrase does not prove the file was never indexed. An absent viewer control on its own is not grounds for rewriting alternative text.
Brief fields and diagnosis log to keep for next time
For a photo team, the fastest fix is a short handover that links the shoot brief to the web check. Keep the master file, list the card and zoom derivatives built from it, and record which PDP address uses which file. After any swap, open network tools, reload, and confirm file name, bytes, and type that truly arrived, then purge an image service or CDN derivative when it still sends an older copy.
Teaching example, hypothetical and not a customer result: assume a team links twelve refreshed PDPs from one new-arrivals page, each with a listing card plus a larger detail file. Office laptops show tiles that never grow while a phone on mobile data opens larger views from the same wording. That split keeps the task in pass one. When every device shows the same gap and the log shows Google knows the addresses but has not retrieved the diagram files, the task shifts to pass two. The story only shows how the two passes part.
Keep below-fold gallery items deferred, but let the first-view picture load without delay. Save new photography for depiction faults such as missed focus, wrong color or material, absent scale cue, or too few pixels for the detail slot. Encoding work cannot restore detail that was never captured.
For a site-side review, Guangsuan's Google SEO service can look at technical and content questions within its published scope. If you want a check on one page, send the address plus a dated symptom log so the team can confirm what needs testing. Include page addresses with check date and chosen canonical where it differs, file addresses copied from the network panel, device builds with second-browser and private-window outcomes, and robots, CDN, cache, and hotlink rules for the image path. Share access through an agreed secure route and keep passwords and buyer data out of public channels.
FAQ
Will squeezing files open small tiles?
No. Squeezing trims transfer bytes at set dimensions. Findability, permission, and eligibility need their own checks first.
Should a silent preview trigger an alternative-text rewrite?
No. Settle the viewing layer first, then verify publishing separately. Descriptive text aids readers without unblocking a failed request.
One phrase returns nothing. Is the file unstored?
Not proven. One look under one phrase, date, language, and filter set cannot prove full index state. Check the recorded state with its date.
Ship your first image in 24 hours.
Flat $9 per asset. No shoot fees. No retouching upcharges.