Brand promotion: this article introduces Guangsuan's Google SEO services for B2B SaaS content teams.
Your team ships updated dashboard screenshots, links them from release notes and help pages, then opens Google Images and sees only small tiles that will not grow larger. The instinct is to recompress everything or book another capture session. Hold that work. A tile you cannot open and a file Google cannot use point to different layers, and the repair is different. This guide covers a public help or changelog page you want indexed. It does not cover a gated app, a staging host, or a page that carries a noindex directive.
What stuck-small can mean
Write one line before you touch settings. Tiles never render, tiles render but tapping does nothing, you cannot locate the larger-view control on this device, or the result set feels thinner than expected each behave differently. A control that is absent on your phone layout is not proof the file request failed. A single odd query under one language, date and filter set is not proof of the whole index. Naming the gap decides whether you start with your browser or with your own pages.
- Tiles stay blank: confirm the same phrase elsewhere, then look at local image permission and connection faults.
- Tiles show but tapping stalls: look at script permission and add-ons, and open a second tile for comparison.
- No larger view where you expect it: use whatever source-page path this layout offers and find the picture there.
- Thin or softened set: write down phrase, filters and SafeSearch mode before you clear anything.
Path A: rule out your viewing setup
Run the same phrase in a fresh tab, note hardware, browser build and login state, and vary a single factor per round. Keep the connection fixed while you swap browsers, then keep the browser fixed while you try another permitted connection. Note each result. A changed outcome trims the search area without naming one root cause on its own.
- Reload once, then run a plain everyday phrase. When a single tile stalls, open its publisher page where a link exists and check a second tile. When most tiles stall, run the same phrase in a second browser on the same connection.
- Open the same phrase in a private window and note login state. A private window can still run some add-ons, so a change there does not by itself prove stored data is damaged. List what else moved together: add-ons, stored data, account state, options.
- Pause one script-related or content-blocking add-on, reload and retry. In desktop Chrome, picture permission and script permission sit in different switches, so inspect the affected site instead of wiping every site. On a managed work laptop you may need an administrator.
- When the publisher page loads, file that as one access note. The overlay preview may still use another asset or hit another request rule, so one load does not close the case. Avoid wiping history, resetting the browser and swapping networks in one move, because that erases the trail.
For the viewer-side method, see Guangsuan's Google Images troubleshooting guide.
Path B: check page and image eligibility
Start here only when Path A leaves the symptom unexplained. You are now asking whether the address and the file can be located, fetched and kept eligible.
- Confirm the exact help or changelog 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 with real file addresses. A shot that only appears after gallery logic runs, only as a styling background, 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. A success code with an HTML login or error body is not a delivered picture. Review robots rules for the image path, page-level exclusion, hotlink or firewall rules, CDN cache, and redirect chains.
- Keep access, eligibility and ranking apart. A reachable file or a passing live check does not promise indexing or a position. Missing from one phrase does not prove the file was never indexed. Read the recorded state and its date rather than repeating the same search.
Teaching example, hypothetical: suppose a docs team links twelve refreshed feature pages from one release note, each with a listing card graphic plus a larger annotated screenshot. Office laptops show tiles that never grow, while a phone on another connection opens larger views. That split keeps the work in Path A. When every device shows the same gap and the log shows Google knows the addresses but has not retrieved the image files, the work shifts to Path B. This story is invented only to show how the two paths part.
Files: compress or shoot again
Touch files after Path A and Path B are settled. Keep three choices apart. Size sets pixel dimensions. Encoding sets how data is stored and, for lossy options, how much detail is dropped. Delivery picks which file a screen gets. A listing card rarely needs the same asset as a zoomable annotation.
- Keep a high-quality master and build derivatives for listing, help body and zoom uses. Judge any export against the master at real phone and desktop widths, especially small labels, thin lines, colour steps and feature edges that decide identification. Writing an already damaged JPEG into a lossless wrapper does not bring lost detail back.
- After a swap, ask the browser what arrived. Open network tools, reload and confirm name, bytes and type. When a CDN or image service still sends an older variant or an oversized file, purge and retest before calling the swap done. A filename suffix alone does not convert data.
- A smaller file on its own does not make Google discover the picture. Smaller transfer may help loading without promising a ranking move or fixing a misleading visual. Keep below-fold graphics deferred, but let the first-view graphic load without delay. Describe meaningful shots with short accurate alt text and nearby context.
- Book new captures only for depiction faults: soft focus, wrong colour or material, missing scale cue, or too few pixels for the zoom slot. Encoding cannot restore detail that was never captured.
For the file-side method, see Guangsuan's image compression guide for SEO, which separates size, encoding and delivery and explains how to confirm the fetched asset.
What to send if you ask Guangsuan
For a site 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 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 and browser builds with second-browser and private-window outcomes, and robots, CDN, cache and hotlink rules for the image path. List pages that must keep working after edits, such as help search, contact and signup. Share access through an agreed secure route and keep passwords and customer data out of public channels.
FAQ
Will compression turn small tiles into large previews? Not alone. Compression trims bytes at set dimensions. Findability, permission and eligibility need their own checks.
Should a stalled preview trigger an alt-text rewrite? No. Settle the viewing layer first, then verify publishing. Alt text describes the picture for readers and search; it does not unblock a failed request.
One phrase returns nothing. Is the file unindexed? Not proven. One look under one phrase, date, language and filter set cannot prove full index state. Check the recorded state with its date.