After a WordPress Move, Google Images Won't Enlarge? Separate Screen Checks From Site Checks
Brand promotion: this article introduces Guangsuan's Google SEO and WordPress hosting services.
After a host change, a WordPress owner searches Google Images for a recent post and finds every thumbnail locked at a small size. Tapping yields no useful larger view. Before paying for fresh compression or a theme rebuild, pause and separate two places where the break can sit: the way this device shows results, and the way the moved site serves files and pages for retrieval.
This walkthrough fits a single public post or gallery you plan to keep searchable. It does not fit a signed-in media area, a staging clone, or an address blocked by noindex. A single test under one phrase, date, language and filter set cannot speak for all visitors. For the screen-side approach used below, see Guangsuan's Google Images troubleshooting guide.
Start from what you actually see
Write down which shape appeared: blank tiles across many results, loaded tiles that never open a larger pane, an expected open or visit action that is absent on this handset, or a set that feels thin under present filters. An absent control and a broken file fetch need different follow-up, and either one alone cannot confirm your files sit outside Google's stored set. Keep phrase, filters, SafeSearch setting, hardware, browser build, sign-in position and time with the note.
Stay on this screen first
Hold the phrase steady and alter only one setting between retests. Reload once, then try an ordinary phrase for contrast. When one tile alone stalls, open its publisher page where a link exists and test a second tile. When the whole grid stalls, repeat the phrase in another browser without changing the connection.
Repeat the phrase in a private window while noting whether sign-in persisted. A changed result there reflects several altered factors at once, so avoid reading it as proof about cache alone; a permitted add-on may still run there. Pause one relevant blocker or page modifier, reload, retest, then bring it back before touching the next one. Check scripting under current troubleshooting guidance.
On desktop Chrome, image handling and script handling live as separate site controls, so review the affected site rather than resetting all sites. On a managed office or classroom machine, ask the administrator where that control is locked. Where possible, hold the browser steady and repeat the phrase on another allowed network, saving the exact message. A timeout, a reset and a filtered view deserve separate notes.
Avoid clearing history, resetting the program and hopping networks in one move, because that erases the trail. Where the publisher page opens, log it as a single access note; the overlay may depend on another file or request rule. Viewing a picture gives no reuse permission, so review publisher terms and any licence before downloading for publication.
Move to files and markup only when every screen agrees
Enter site-side review only after repeated single-change trials leave the identical small-tile pattern on each browser, network and sign-in mix. At that point confirm the exact page address, the review date, the recorded storage state, and which address Google selected as canonical. When 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. Apply canonical only across duplicates or near-duplicates, not across unrelated pages. For detail, see Google's canonical guidance.
Keep the important picture in plain image markup that points to a real file. A frame 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 the 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 photo. Choose a Google-supported type such as JPEG, PNG, WebP, SVG or AVIF. Then review path rules for that file address and the agents they cover, page-level exclusion, hotlink or firewall screening, CDN retention, redirect chains, nearby wording and loading conduct. Keep title, caption and alternative wording faithful to the visible frame and brief rather than stuffed with terms; wording that aids readers cannot by itself unblock a refused request.
A reachable file or a passing live check cannot by itself promise storage or placement. Keep reachability, eligibility for storage, and query behaviour as three separate calls. 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.
As a teaching sketch only, not a client outcome: picture a cooking blog that links four refreshed guides from one start page, each with a card plus a larger method photo. A home PC on broadband and a phone on mobile data show the same small-tile pattern under one phrase, and a signed-out fetch of the larger method photo returns a path-rule refusal. That shared pattern shifts effort from screen trials to path, markup and cache notes. Had the two machines disagreed, screen trials would have continued and theme files would have stayed untouched.
Hosting review or new files: how to choose
Remain with screen trials while results differ by machine, browser, network, sign-in or filter. Move to site work when all screens stall together and signed-out fetches implicate paths, canonical selection, redirects, CDN or cache, or theme and gallery markup.
Seek hosting or build review when notes implicate template markup, gallery output, redirect or canonical output, or cache conduct that cannot be safely edited on a live publication. Guangsuan's WordPress hosting scope covers checks, backup, trial move and cutover without a separate migration charge. For duties and handoff, 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 paths working after any edit.
Avoid ordering fresh derivatives only because tiles look compact. Smaller bytes at fixed dimensions cannot by themselves make a file findable. Permission and eligibility still need their own confirmation.
Keep a log you can hand over
- Time, phrase, device model, browser or app build, and sign-in position.
- Whether tiles were blank, the pane stayed shut, a control looked different, or results were only thinner.
- What each isolated change produced: second browser, private window, one add-on, site control or another 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.
- Image-path rules reviewed, CDN and cache notes, gallery or theme part name, redirect chain, and placement of nearby copy.
This record offers another person a repeatable starting point rather than another unsupported clear-everything direction.
FAQ
Clicking a thumbnail does nothing. Does that point to the screen or to storage?
A quiet preview beside working tiles points to screen-side work: scripting, one add-on at a time, site controls, second browser and second network. A file that will not fetch while signed out, a canonical pointing elsewhere, a path refusal, or a blocked gallery file points to site-side work. Either pattern alone cannot confirm absence from storage.
After a move, which layer comes first?
Begin with this screen, then the exact file address, then page markup and delivery. Complete single-variable screen trials first. Only when each screen shows the identical gap, confirm page address, canonical, image markup, file response, path rules, exclusion, CDN retention, redirects and nearby copy.
Should I compress again or request hosting help?
Compress again only after both passes are logged and delivery is confirmed. Request hosting or build help when evidence implicates template output, gallery markup, redirect or canonical output, or cache conduct that cannot be safely altered live. Send the page address plus dated notes so the team can confirm what needs testing.