Lorixen.
EN

Lazy-Loaded Images and Googlebot: A Checklist for Small Sites

Short answer: Lazy loading is safe for search when images sit in the page's HTML as real <img> elements with a src (or srcset) value and load when they approach the viewport. It goes wrong when the real address only appears after a scroll, click or custom script event that Googlebot never triggers. Use the native loading="lazy" attribute below the fold, leave the main hero image eager, and test with the URL Inspection tool to confirm the rendered HTML still lists every image.

Why Googlebot cares

Googlebot renders pages with a tall virtual viewport rather than scrolling like a person. Images that load when they enter the viewport are generally picked up. Images that wait for a mouse movement, a tap or a scroll event handler that never fires are not. The risk is greatest with older plugins that store the true address in data-src and swap it in with JavaScript, because if that script fails, the page contains only a placeholder.

Missing images matter for two reasons: they drop out of Google Images, and for product or portfolio pages the pictures are part of what the page is judged on.

The checklist

Work through these in order. Tick each one for a representative page of each template: homepage, a service page, a product or project page, a blog post.

Markup

  • [ ] Every content image is an <img> element, not a CSS background on a div. Backgrounds are not treated as page content for image search.
  • [ ] Each image has a real src or a srcset with a valid URL in the delivered HTML, not an empty string or a 1 pixel placeholder with the real file only in data-src.
  • [ ] If a script-based loader is used, the <noscript> fallback contains a normal <img>.
  • [ ] Width and height attributes are set, so the layout does not jump when the image appears.
  • [ ] Alt text is present and describes the picture.
  • [ ] The picture is not wrapped in a link that only runs JavaScript when it is the only route to the full-size file.

Loading behaviour

  • [ ] The first large image on the page, usually the hero, does not carry loading="lazy". Delaying the largest visible element slows the Largest Contentful Paint measure.
  • [ ] Images below the first screen carry loading="lazy", which is built into current browsers and needs no script.
  • [ ] No extra script waits for scroll direction, hover or click before assigning a source.
  • [ ] Carousels expose their slides in the HTML, so later slides are not injected only after a swipe.
  • [ ] "Load more" galleries have paginated URLs or a plain link fallback for the later items.

Verification

  • [ ] The URL Inspection tool's live test shows the screenshot, and the rendered HTML lists the images you expect.
  • [ ] A site search (site:example.com) in Google Images turns up photos from several different pages after a few weeks.
  • [ ] Disabling JavaScript in the browser still shows an image or a placeholder with a usable fallback.
  • [ ] Mobile and desktop versions contain the same images, because indexing uses the mobile version.

How to test in five minutes

  1. Open Search Console and paste a page URL into URL Inspection.
  2. Choose "Test live URL", then "View tested page".
  3. Look at the HTML tab and search for <img. Count the elements against what you see in your browser.
  4. Check the screenshot. A lower-page image that is blank in the screenshot is not proof of failure, since the screenshot is limited, but the HTML should still list it with a real source.
  5. If images are missing in the rendered HTML, look at how your theme or plugin builds them, and test again after switching the option off.

Native or script: which to use

Approach Works for Google Notes
loading="lazy" attribute Yes Simplest, no script, supported by current browsers
IntersectionObserver script that sets src on scroll into view Yes, if the script runs without user input Test rendering, keep a noscript fallback
Loader waiting for scroll or click events Often not Googlebot does not interact
Background image set in CSS Not as image search content Fine for decoration only

For most small business sites the native attribute is enough. If a plugin on your WordPress or Shopify theme applies lazy loading as well, check it is not doing the work twice, since double handling sometimes leaves a placeholder in the delivered markup.

Illustrative example

A joiner in Auckland moves a portfolio of forty photographs to a lazy-loading plugin that stores each address in data-src. A month later the portfolio page appears in search, yet none of the photographs do. The fix is to switch off the plugin option and rely on the native attribute, keep the first photo eager, and give every image alt text. Within a few weeks, a handful of the photos begin appearing in image results.

FAQ

Should I lazy-load every image?

No. Leave the main visible image eager so the page paints quickly, and lazy-load what sits further down.

Does lazy loading hurt my rankings?

Done properly it tends to help by reducing the data a page downloads. It hurts only when it hides images or delays the main visual.

What about lazy-loaded text or reviews?

The same principle applies: content that appears only after a click or custom scroll event may not be seen. Put important text in the initial HTML.

Do I need an image sitemap?

Not for lazy loading. If images are normal <img> elements, they are discoverable. A sitemap can help for galleries loaded by script, but fixing the markup is better.

If you want us to review how your gallery and product pages load images, contact us through our enquiry page.

Sources

WhatsAppBook a call