Hitivi · Field Notes
Episode Stills Stay Small in Google Images? Check Viewing First, Then Page and File
For broadcast and OTT episode pages: how to separate a local viewing fault from a page and still-file eligibility fault before you re-export or order new stills, and what log to send for help.
Brand promotion: this article introduces Guangsuan's Google SEO services for broadcasters and OTT operators.
A catch-up editor publishes episode pages with gallery stills for the week's programmes. In Google Images the new stills sit as small tiles and do not open into a larger view. For a public episode address that should remain searchable, do not rebuild the gallery yet. Confirm the screen in front of you first, then confirm the page and the still file itself, and leave file work until both are settled. A sign-in catalogue, a staging address, or a page marked noindex needs its access status corrected before this sequence applies.
What this title asks you to decide
When a Google Images entry does not enlarge, record which element fails: empty tiles, tiles present but the larger view does not react, an expected control you cannot locate, or a result set that looks filtered. A vanished control and a blocked file request point in different directions, and neither on its own shows that your stills sit outside Google's index. Use the same query in a new tab, write down handset or desktop type, browser build, and sign-in condition, and alter a single variable between retries.
If other people can browse Google Images without trouble while your programme stills stay small, move the inquiry to your own publishing side. For that split, see Guangsuan's Google Images troubleshooting guide.
First confirm it is not only this screen
Remain with viewing comparisons while behaviour shifts across machines or browsers.
- Reload a single time, then run a neutral everyday query. Where one tile misbehaves, follow its source-page link when offered and open a second tile for contrast. Where the whole grid misbehaves, repeat the query in another browser on the same connection.
- Open a private window and log whether sign-in persists. A changed view there reflects several things at once, including add-ons, retained data, account condition, and settings, so it does not by itself convict stored data.
- Test add-ons and script behaviour singly. The larger view can stay shut while the tile and the underlying file both respond, so pause one relevant add-on, reload, and retry before touching a second setting. Because an add-on may be allowed inside private mode, that mode is no clean control.
- Inspect permission for the affected site only. On desktop Chrome, picture access and script access sit in separate site switches, so leave global settings alone. A workplace machine may need its administrator.
- Note query wording, filters, and who controls SafeSearch before clearing. No fixed tile count applies to every viewport, and a single lookup under one date, language, and filter set cannot speak for every viewer. An opened source page counts as one access note only; the preview may draw on another asset or meet another request rule.
Do not wipe history, reset the program, and swap networks together. That bundle destroys the trace you need.
Then confirm the episode page and still can be kept
Enter this stage only when every screen shows the same gap. Write down the exact episode address, the date of the lookup, the stored state on record, and the canonical Google has chosen. If that canonical aims elsewhere, later file work will target the wrong address.
- Keep principal stills inside ordinary image markup that cites genuine file addresses. A still visible only through gallery interaction, as a styling backdrop, or behind sign-in is difficult to treat as a reference a crawler can reuse.
- Fetch the file while signed out and read status line, media type, and body together. A success code means little when the body holds a sign-in screen or an error document.
- Read robots entries for the picture path, page-level exclusion, hotlink or firewall screening, CDN retention, and redirect chains, alongside surrounding copy and loading behaviour.
- Hold access, eligibility for retention, and query performance as separate verdicts. A reachable file or a passing live probe does not assure retention or placement. The reverse also stands: absence from one result list does not show the file was never retained.
A control absent from your own screen is no ground for an ALT rewrite. Leave ALT brief and faithful, and repair the layer that truly failed.
Illustrative desk case, hypothetical
Teaching example, hypothetical and not a customer result: suppose a night desk posts four catch-up pages under one series hub, each with a card tile plus a wider still. The gallery desk on the office link sees tiles that never expand, while an editor's handset on mobile data from the same wording opens the larger view. That divergence keeps attention on viewing. If all handsets and desktops instead show the same small tiles, and the log records Google aware of the episode addresses yet the still files unfetched, attention shifts to page and file eligibility. The sketch only separates the two routes.
When a new export or a new still makes sense
Rework files only after the two stages above settle. Treat extent, encoding, and selection as separate choices. Extent sets pixel size. Lossy encoding shrinks bytes by dropping picture data. Selection decides which derivative a slot receives. A lighter file does not by itself become discoverable.
- Where the right derivative arrives yet the page drags, inspect delivered bytes, pixel width, format, and load sequence first. Preserve a high-quality master and derive card, listing, and detail variants from it.
- Where the right file arrives soft, blocky, or with mistaken hue or fabric rendering, inspect source sharpness and lighting. Fresh encoding cannot recover dropped detail or correct a misleading depiction.
- After any swap, ask the browser what it fetched and whether an image service still hands out a stale cached derivative. Defer below-fold gallery items, but leave the first-view picture without delay.
- Book fresh photography only for depiction faults: missed focus, wrong colour or material, absent scale cue, or too few pixels for the detail slot.
What to include when you contact Guangsuan
For site-side review, Guangsuan's Google SEO service can examine technical and content causes inside its stated scope. Share the episode address plus a symptom note so the team can confirm the next check.
- Episode addresses, stored state with lookup date, chosen canonical where it differs, and file addresses taken from the network panel.
- Machine, browser or app build, sign-in condition, and outcomes from the second-browser and private-window contrasts.
- Robots entries, CDN and cache handling, hotlink or firewall rules for the picture path, plus gallery builder or plug-in name.
- Routes that must survive edits: playback, on-site search, enquiry form, and contact mail. Pass access by an agreed secure channel and keep passwords and audience data out of public threads.
FAQ
Does shrinking files force small tiles to open?
No, not alone. Shrinking alters transfer weight at the exported extent, while discovery, permission, and eligibility call for their own checks.
Should a silent preview prompt an ALT rewrite?
No. Resolve the viewing contrast first, then verify publishing separately. ALT wording serves readers and search; it does not unblock a request.
One lookup returns nothing. Is the still unretained?
No. One lookup under one query, date, language, and filter set cannot settle full retention. Consult the recorded state and its date.