After a WordPress Move, Images Stay Small? What to Check First
Brand promotion: this article introduces Guangsuan's Google SEO services for WordPress publishers.
After a WordPress move or hosting change, you open Google Images and see small tiles that never open a larger view. Before you recompress uploads or rebuild the gallery, pause. The break can sit in two different places: how this screen shows results, or how the moved site serves pages and files for retrieval. Those tracks need different evidence.
This note fits one public WordPress post or gallery you plan to keep searchable. It does not fit a signed-in library, a staging copy, or a page marked noindex. One test under one wording, date, language and filter set cannot speak for all visitors. For the viewer-side method used here, see Guangsuan's Google Images troubleshooting guide.
Name what you actually see
If Google Images will not show the full page or enlarge a result, identify what is missing first: the thumbnails, the interactive preview, a particular viewing control, or the results you expected. A missing button is not the same problem as a failed image request, and neither proves that your own site's images are absent from Google's index.
- Blank or broken tiles on many results on this machine
- Tiles load but selecting one never reveals a larger view
- An expand or visit-page action you expect on this handset is absent
- A set that looks thin or softened under present wording and filters
Write down wording, filters, SafeSearch state, device, browser build, sign-in state and time before you change anything.
Thumbnails open but the original will not open: check the browser first
When thumbnails open but the original will not open, check the browser first. Start with the same query in a fresh tab, note the device and sign-in state, and change one thing at a time.
- Reload once, then try a plain everyday phrase for contrast. If only one result fails, open its source page where a link exists and compare a second tile.
- If many results fail, repeat the same wording in a second browser while the connection stays fixed. A different outcome narrows the investigation; it does not identify one cause by itself.
- Repeat the wording in a private window and record whether you stayed signed in. Do not read a difference there as proof about cache alone. Several conditions can change together, and private browsing is therefore not automatically an extension-free control.
- Pause one relevant blocker or page modifier, reload, retest, then restore it before testing the next. Check JavaScript using Google's troubleshooting guidance, then test content-blocking extensions one at a time.
- On desktop Chrome, Images and JavaScript appear as separate site switches. Check the affected site's settings rather than resetting every site's permissions. On a managed work or school machine, an administrator may own that switch.
- Where available, hold the browser fixed and try another permitted network with wording fixed. Keep exact error text. A timeout, a reset and a filtered view are different records.
An interactive preview can fail while the thumbnail and source file remain usable. Where the publisher page opens, log it as one access note only; the overlay may use another asset or another request rule. Do not wipe history, reset the program and change networks together, because that erases the trail.
When full-screen or view-image control is missing, work with the controls present on your device. Google's image-search help explains searching and selecting images, but it does not promise a permanent grid or list switch or a full-screen button in a fixed corner. Follow the available source-page link and locate the picture there. Viewing a picture grants no reuse right; check publisher terms and any license before downloading for publication.
File too small or display limit? Check the file address
A small derivative on screen does not prove the original export was too small. Keep size, encoding and delivery apart. A listing card and a zoom view often need different derivatives; a small card file will look small in a full-screen slot even if bytes are correct.
- Confirm the key visual sits in ordinary image markup that points to a real file address. Under Google's image SEO guidance, key images should be discoverable through standard HTML image elements with real resource URLs.
- Open rendered source and copy each address seen in src, srcset, gallery links and downloads. Do not guess behavior from file names.
- After round one still stalls on every browser and connection, fetch the exact file address while signed out and read status, content type and body together. A success code paired with a sign-in screen or error body is not a delivered photograph.
- Use a supported type such as JPEG, PNG, WebP, SVG or AVIF. Keep title, caption and alt wording faithful to the visible frame. Alt wording describes the picture; it does not open a blocked path.
As a teaching sketch, not a customer result: suppose a post links a card image plus a larger detail file. The card opens, the larger file returns a login screen while signed out. That split points to access and delivery, not to export size. Do not order new derivatives until both rounds are logged.
After a move: check attachment pages, redirects and CDN separately
Move here only when every machine and connection keeps the same small-tile result after round one. Confirm the exact page address, the check date, the recorded storage state, and which canonical Google selected. If the selected canonical points elsewhere, you are auditing the wrong address.
- Attachment pages: confirm whether the wrapper page loads while the dated file under the uploads path fails. The wrapper can load while a phone-size derivative answers missing. That is a derivative gap, not proof that exports were too large.
- Redirects and canonical: copy redirect chains for the page and for each file address. Apply canonical only across duplicates or near-duplicates. For scope and handoff where theme or redirect output cannot be safely edited live, see Guangsuan's onsite technical SEO.
- CDN and cache: review path rules for the image address and the user-agents they cover, page-level exclusion, hotlink or firewall screening, CDN cache and whether an older variant is still served. After any swap, confirm in network tools which derivative each slot actually received.
Separate resource access, indexing eligibility and search performance; an accessible file or a passed live test does not guarantee indexing or ranking. Conversely, not seeing an image in one query does not prove it has never been indexed. A stored-state label such as crawled but not indexed names what was observed. It does not name the cause. A viewer-side control gap alone is no reason to rewrite alt text.
Keep a log you can hand over
Time, wording, filters, device model, browser build and sign-in state. Whether tiles were blank, the preview stayed shut, a control looked different, or results were only fewer. What each lone change produced. Page address with check 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, CDN and cache notes, gallery or theme part name and redirect chain. This gives someone a reproducible starting point instead of another unsupported clear-everything instruction.
FAQ
Will smaller exports force tiles to widen?
No. Smaller bytes at fixed dimensions do not by themselves make a file findable. Permission and eligibility still need their own checks.
Should a silent preview trigger an alt rewrite?
No. Settle the viewing layer first, then verify publishing separately. Descriptive text 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.