Your product photographs look sharp on the website, but you cannot find them in Google Images. Before commissioning another shoot or rewriting every filename, check whether Google can discover the pictures, fetch the files and understand the pages they belong to.
This matters most where appearance helps someone choose: furniture, interiors, landscaping, food, clothing or completed building work. Start with photographs that help a potential customer assess what you sell. A missing decorative background deserves less attention than a missing gallery of your work.
Start with three photographs and a clear baseline
Choose a small sample: one important product or project image, another using the same gallery template, and a photograph elsewhere on the site. For each, record the page address, the actual image-file address and when it was added or changed. A media-library attachment page is not the image file itself.
Note whether the problem began after a redesign, gallery replacement, image-optimisation change or move to a different image host. This gives your developer a useful comparison instead of an instruction to “fix image SEO” across the entire website.
Check the right search report
In Search Console, open the Search results performance report and change the search type to Image. Google’s performance report documentation confirms that this covers results in the Google Images tab. Review impressions and clicks over a useful period, then narrow the view to the relevant pages.
Keep the question precise. You are investigating discovery through Google Images. A missing thumbnail beside an ordinary web result is a different observation. Record which experience you checked so that everyone works on the same problem.
No impressions in your chosen period should prompt investigation; it does not identify the cause. Avoid replacing images merely because one search on your own phone failed to show them.
Check the page before the photograph
Open the page containing the picture while signed out. Can someone reach the product or project without an account? Does the page still exist at the address you recorded? Check the actual customer page, rather than its preview inside WordPress or another content management system.
Google’s technical requirements for Search include accessible content, a successful HTTP 200 response and indexable material. Meeting those requirements creates eligibility; Google does not guarantee indexing.
Ask your developer to establish whether the page has an access restriction, an unintended indexing block or an error response. Keep intended private content private. If the photograph belongs in a public portfolio, use the approved public version of the project rather than opening a private customer area to search engines.
Make sure the photograph is a discoverable image
A picture can fill the screen without being embedded in the way Google expects. Google’s image SEO guidance says it discovers images through the src attribute of HTML img elements and does not index CSS background images. It also recommends a fallback img with src when using responsive image techniques.
Ask your developer to inspect one affected photograph. Is it a content image, a CSS background, or a placeholder replaced later? If an important portfolio photograph is only a background, consider presenting it as a proper content image while retaining the intended design.
Do not rebuild every decorative section. Prioritise pictures that carry useful information about the product, service or completed work.
Test galleries and lazy loading without clicking
Check what happens before you swipe a carousel, open a lightbox or press “load more”. Does the page already contain the important photograph’s real address, or does that address appear only after an interaction?
Google’s lazy-loading guidance explains that Search does not interact with a page by clicking or scrolling. It recommends loading relevant content when it enters the viewport, using a suitable implementation, and testing the rendered HTML for the image URLs.
Give your developer a reproducible example: the page address, which photograph is missing initially, and the action that reveals it. Ask them to check both the first gallery image and a later one. A working cover photograph does not demonstrate that the rest of the gallery is discoverable.
The repair should preserve a usable gallery and sensible performance. Switching off every optimisation is a poor starting brief; identify the particular loading behaviour that needs changing.
Look for image-specific blocking
If the page is accessible, check the image host too. Your images may come from a separate content delivery network, commonly called a CDN, with its own rules.
Google’s documentation on excluding images from Search identifies several controls that matter here:
- Robots.txt restrictions: rules on the host serving the files can prevent Google from crawling them, including rules aimed at
Googlebot-Image. - An image response header: an
X-Robots-Tag: noindexheader can exclude the file. Google needs to fetch it to read that header. - A page-level instruction:
noimageindexprevents images being indexed from that page, although the same pictures may still be indexed through other pages.
Ask the person managing hosting or the CDN to inspect the affected file and its response headers. Remove only an unintended restriction. A blanket change to the whole uploads folder could expose material that was deliberately excluded.
Check what your sitemap actually contains
An image sitemap can help Google discover pictures it might otherwise miss. Google’s image sitemap documentation permits either a separate sitemap or image entries within an existing one. Its image-location entries identify the image-file URLs.
Check a real entry for your sample page. Does it list the intended photograph, or an old file that the website no longer uses? If the images sit on another domain, follow Google’s verification guidance for both domains and check that the image host allows crawling.
Use this as an additional discovery route after investigating access and loading. Do not buy another sitemap plugin before checking what your current setup already produces.
Give useful photographs useful context
Google’s image guidance also recommends placing images near relevant text and keeping references to the same image URL consistent. Review whether your project page explains what the photographs show. For an illustrative fitted-kitchen project, describe the layout and materials accurately rather than repeating a list of towns.
Write alternative text for the image’s purpose. The W3C alt-text decision tree distinguishes informative photographs, functional images and decoration. Informative photos need a brief meaningful description; purely decorative images can have an empty alt attribute.
“Oak cabinet doors with brushed brass handles” is a useful description when that is what the photograph shows. Do not add a location, product specification or claim that you cannot verify. Ask your editor to review the examples individually before making bulk changes.
Verify the repair in two stages
First, prove the implementation works
Use Search Console’s URL Inspection tool on the containing page. Compare Google’s indexed information with a live test. Inspect the tested page’s rendered HTML, screenshot and resource information where available.
For your sample, ask for evidence that the intended image address appears in the rendered page and that the image can be fetched. Test a second page using the same template and check the gallery on mobile. Confirm that the repair has not removed useful pictures or broken the customer journey.
Then, review search visibility
A successful live test checks the current implementation; it does not prove that Google has indexed the individual photograph. Record the repair date, retain the before-and-after evidence and review subsequent Image search performance for the affected pages.
Keep the handover practical: which pages were affected, what prevented discovery or access, what changed, and what remains uncertain. Where no technical fault is found, reassess whether the pictures and their pages genuinely help a customer choose. Avoid promising a particular ranking or a fixed date for their appearance.
Image discovery belongs within the wider technical SEO work on your website. If valuable product or project photographs are missing, talk to BuzzBoost about checking the page, image delivery and search evidence together. Bring a few affected URLs so the investigation starts with a concrete example.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
