After a WordPress Move, Product Photos Won't Open Larger? A Short Triage
Brand promotion: this article introduces Guangsuan's Google SEO and WordPress hosting services.
After a WordPress move, a shop owner looks up a product photo in Google Images and finds only a small tile. Tapping it never brings a useful larger view. Before you pay for new exports or a gallery rebuild, sort out which layer failed. The screen in front of you and the moved site behind it need separate proof.
This checklist covers one public product post or gallery you intend to keep searchable. It does not cover a login-only catalogue, a staging duplicate, or a URL kept out of search with noindex. One lookup under one phrase, date, language and filter choice does not describe every shopper. For the screen-side routine used here, see Guangsuan's Google Images troubleshooting guide.
Start by naming the stall
If Google Images will not expand a result, say which piece is absent first: the small tiles, the larger preview that should follow, a specific open control, or the results you expected. An absent control and a broken file fetch call for different next steps. Either one alone cannot confirm your own pictures sit outside Google's stored set.
A tile, its overlay and the shop page can rely on different files or request rules. A compact listing card and an enlarged view often draw on different derivatives, so a small card shown in a large slot can still look small when bytes are otherwise correct. A compact tile by itself therefore does not show the master export was too small.
Record phrase, filters, SafeSearch position, device model, browser build, sign-in position and time before you alter anything.
Pass one: single-factor checks on this device
Keep the same phrase and alter only one factor between retests. Reload once, then try a neutral everyday phrase for contrast. Where a lone tile sticks, open its shop page where a link exists and try a second tile. Where the whole grid sticks, repeat the phrase in a second browser without changing the connection. A changed outcome narrows the area to inspect next without naming one cause by itself.
Repeat the phrase in a private window and note whether sign-in continued. Several settings shift together there, so avoid reading a difference as proof about stored data alone. A permitted add-on can still run in that mode.
- Pause one relevant blocker or page modifier, reload, retest, then restore it before touching the next.
- Review scripting behaviour under current troubleshooting guidance, then test content-blocking add-ons singly.
- On desktop Chrome, picture handling and script handling are separate site controls. Inspect the affected site instead of resetting every site. On a managed office or school machine, ask the administrator where the control is locked.
- Where another allowed network exists, hold browser and phrase steady and repeat the test there. Keep exact message text. A timeout, a reset and a filtered view are different notes.
A scripted preview can stay shut while the tile and the file still open. Where the shop page loads, keep that as one access note only; the overlay can depend on another file or request condition. Avoid clearing history, resetting the program and hopping networks in one move, because that destroys the trail.
Where an expand control is absent on this handset, use the controls actually shown. Follow the available shop-page link and find the picture there. Viewing a picture grants no reuse right; check shop terms and any licence before downloading for republication.
Pass two: page address, file address and delivery
Enter this stage only when repeated single-factor trials leave the identical small-tile pattern on each browser, network and sign-in mix. Confirm the exact page address, the review date, the recorded storage state, and which address Google selected as canonical. Where the selected address points elsewhere, the audit sits on the wrong page.
Redirects carry the strongest hint for canonical choice. Rel-canonical markup is also a strong hint, while sitemap listing is only a weak hint. For detail, see Google's canonical guidance. Use canonical only across duplicates or near-duplicates.
Keep the key product visual in ordinary image markup that points to a genuine file address. A visual that only materialises after gallery code runs, only as a styling backdrop, or only after sign-in is harder to count as a crawlable reference. Open rendered source rather than trusting a library thumbnail. Copy every file address seen in src, srcset, gallery links and downloads.
Fetch the exact file address while signed out and read status, type and body together. A success code beside a sign-in screen or error body is not a delivered photograph. Prefer a Google-supported type such as JPEG, PNG, WebP, SVG or AVIF. Keep title, caption and alternative wording faithful to the visible frame and brief rather than stuffed. Wording that aids readers cannot by itself unblock a refused request.
As a teaching sketch only, not a client outcome: picture a small soap shop with one product post, one card file named soap-card-600.jpg and one larger detail file named soap-detail-1600.jpg. The post URL loads, the card loads, and the larger detail file answers with a sign-in screen while signed out. That split points to access and delivery rather than export size. Log both rounds before ordering new derivatives.
When hosting and CDN notes are due
Stay with screen trials while results differ by machine, browser, network, sign-in or filter. Move to site duties when all screens stall together and signed-out fetches implicate paths, canonical selection, redirects, CDN or cache, or theme and gallery markup.
At that point check whether a wrapper page loads while a dated file under the uploads path fails. That pattern is a derivative gap rather than proof exports were too large. Review path rules for the file address and the agents they cover, page-level exclusion, hotlink or firewall screening, CDN retention and redirect chains. After any swap, confirm in network tools which derivative each slot actually received and whether an older variant is still served.
Seek build or hosting review when notes implicate template output, gallery markup, redirect or canonical output, or cache conduct that cannot be safely edited on a live shop. Guangsuan's WordPress hosting scope covers checks, backup, trial move and cutover without a separate migration charge; see Guangsuan WordPress hosting and optimization. Use an agreed secure route for access and keep passwords and customer data out of public channels. Keep enquiry and checkout routes working after any edit.
Keep reachability, eligibility for storage and query behaviour as three separate calls. A reachable file or a passing live check cannot by itself promise storage or placement. Absence from one phrase cannot confirm the file was never stored. Read the recorded state with its date instead of repeating the phrase. A viewer-side gap alone gives no ground to rewrite alternative wording.
Log to hand over
- Time, phrase, filters, device model, browser or app build and sign-in position.
- Whether tiles were blank, the preview stayed shut, a control looked different, or results were only thinner.
- What each isolated change produced, including second browser, private window, one add-on, site control or second network.
- Page address with review date and selected canonical; file addresses from source or network panel on phone and desktop, with signed-out status, type and body note.
- Path rules reviewed, CDN and cache notes, gallery or theme part name, redirect chain and placement of nearby copy.
That record offers another person a repeatable starting point rather than another unsupported clear-everything direction.
FAQ
Will a smaller export force small tiles to expand? No. Smaller bytes at fixed dimensions cannot by themselves make a file findable. Permission and eligibility still need their own confirmation.
Should a quiet preview trigger an alt rewrite? No. Settle the viewing cause first, then verify publishing separately. Description helps readers without unblocking a refused request.
One phrase finds nothing. Is the file unstored? Not proven. One view under one phrase, date, language and filter set cannot describe the full stored set. Check the recorded state with its date.