Investigate the landing page and image file as two related resources, then fix the first demonstrated discovery or access failure.
An image can look correct on your website while being undiscovered, inaccessible or unselected for image search. Trace the exact image file and its landing page separately. Start with an observed failure instead of assuming that a new filename, extra keywords or another sitemap submission will make it appear.
First define what missing means. Not seeing an image for one query is not proof that Google has never indexed it. Record the query, date and expected page, then investigate the publication and access evidence available to you.
Identify the two resources
Write down the public page that contains the image and the image URL actually delivered there. In WordPress, the attachment record, original upload, generated sizes and article address can all be different resources. A Media Library item existing in an administrator view does not establish that a public page introduces it.
Open the saved article signed out. Check the visible subject and use the browser’s image inspection to locate the source. If responsive selection chooses another file, record both the declared fallback and the selected candidate. Our responsive-image diagnostic covers that distinction.
Keep the investigation attached to one intended image. A page with a header, logo, decorative background and gallery can make a vague report impossible to reproduce. Note where the image appears and what the surrounding article explains.
Can a crawler discover the image?
Google’s image guidance says it discovers images through an img element’s src and does not index CSS background images. It recommends a fallback src when responsive markup is used. A picture visible only as a background therefore needs a different publishing decision from an ordinary article image.
Inspect the delivered or appropriately rendered page rather than the editor’s settings. A gallery may reveal images only after a visitor opens a panel. An animation can paint the picture without supplying an ordinary image reference. Ask the maintainer to identify how the intended image becomes discoverable; do not infer that from visual appearance.
A meaningful content image should also make sense on the landing page. Check its caption and nearby explanation. A standalone diagram placed beside an unrelated promotion gives the reader less context, even if the file can be fetched.
Can the image file be fetched publicly?
Open the exact image URL in a fresh signed-out browser. Record the final destination, status and returned content. An image-looking URL can redirect to sign-in, return an expired-link message or serve a challenge. A successful administrator session can hide those differences.
Ask the authorized maintainer to inspect relevant robots rules and delivery restrictions at the actual image hostname. Images on a CDN can have a different access policy from the article. Record a demonstrated block before changing firewall or hotlink settings; never remove broad protections merely because an image is absent from search.
For intermittent failures, retain the time and requested URL and compare appropriate server evidence privately. A successful later fetch does not erase an earlier access problem. Equally, one failed request from an unrelated tool is not proof that Google receives the same response.
| Observation | Focused next check | What it does not establish |
|---|---|---|
| Only a CSS background references the file | Choose appropriate discoverable content markup | The visual design must be removed |
| Signed-out file request is denied | Inspect its delivery and access policy | All site security should be disabled |
| Article is excluded from search | Confirm its intended indexing role | An image sitemap overrides that role |
| Public page and file are healthy | Review discovery and later indexed evidence | The chosen query must show the image |
A fictional catalogue’s diagram disappears
Consider a fictional catalogue article explaining how to measure a shelving unit. The diagram appears on desktop and mobile. The owner expects people searching for the measurement process to discover it, but cannot find it in image results.
Inspection shows that the article uses the diagram as a theme background while a separate thumbnail is an ordinary image. The owner records that difference. A proposed correction is to publish the instructional diagram as meaningful article content with an actual image source, leaving purely decorative backgrounds to their visual role.
In a protected preview, the maintainer would check the new markup, public image response and surrounding explanation. After an authorized release, the owner would retain the output and release date and inspect later search evidence. This example identifies a discovery weakness; it does not claim a guaranteed indexing result or a measured ranking gain.
Check the landing page’s own status
Use the exact article address in the authorized Search Console property. URL Inspection distinguishes Google’s indexed information from a live test. Keep the reported crawl time beside the date of any correction. A live success today does not prove that the stored version already includes the new image.
Review redirects, the preferred page address and deliberate exclusions. Use the page-indexing workflow when the article itself is missing. Do not create duplicate articles solely to give the same image more URLs.
Inspection is page evidence, not an inventory certificate for every image on that page. State that limitation in a handover. A green page status can coexist with an unresolved question about a particular resource.
Use an image sitemap for discovery gaps
The image sitemap specification describes listing image locations, including images that may otherwise be difficult to discover. Review the actual generated entry: it should connect the correct landing page with the intended file, rather than list an obsolete original or private upload.
For a separate delivery domain, review the documented ownership and access considerations with the person who controls it. An image sitemap does not grant access, repair an expired URL or force selection. Keep one maintainable generation path rather than uploading several inconsistent lists.
Finish with a proportionate change
Fix the first supported fault, then repeat the affected page and file checks. Preserve source originals before replacing media and use the Media Library workflow for sizing and presentation. That is a separate decision from discoverability.
If no fault is demonstrated, keep the uncertainty. Improve the image’s usefulness and page context where needed, monitor the relevant search type and avoid promising a result for an exact query. Your next step is an evidence pair: the article response and the exact image response, each with its observation time and intended public role.
Sources and verification
Editorial review 2026-10-17. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- Google image SEO best practicesChecked HTML image discovery, CSS background limitation, fallback src and landing-page context.
Limits: Eligibility does not guarantee indexing or a result for a chosen query. - Google image sitemapsChecked Image sitemap purpose, image URL relationship and CDN-domain considerations.
Limits: A submitted image location is a discovery aid, not indexing proof. - Google URL Inspection toolChecked Indexed versus live page evidence and inspection limits.
Limits: Inspection of a landing page does not independently prove that every embedded image is indexed.