Should images be lazy-loaded if it risks them not being indexed?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 63
Lazy-load the images below the first screen, load the ones at the top normally, and use a method that loads each image when it enters the viewport rather than when someone scrolls or clicks. Done that way, the method itself removes the main indexing risk, though an implementation can still hide an image, so test the result rather than assume it. Google’s guide to fixing lazy-loaded content recommends lazy-loading for content that is not visible yet, and warns against it for content likely to be visible as soon as the page opens.
Which images to lazy-load
| Image | Lazy-load? | Why |
|---|---|---|
| The main image at the top of the page, which can be the largest element on first view | No | Delaying it slows the moment the page looks loaded, which Largest Contentful Paint measures |
| Logos and images in the first screen | No | They are visible on arrival, the case Google's guide advises against |
| Images further down an article or product page | Yes | They are not needed until the visitor reaches them |
| Gallery and carousel images beyond the first | Yes, if each loads when it becomes visible | Loading them on a click hides them from Google |
The indexing risk, and how to avoid it
Google does not scroll, click or type on a page. An image that loads only after a scroll event or a click on “show more” may never load for Google, and an image Google never sees cannot be indexed. The guide names three methods that avoid this, because they load content when it is visible in the viewport rather than on a user action:
- the browser’s built-in lazy-loading for images and iframes, through the
loadingattribute; - the IntersectionObserver API, with a polyfill for older browsers;
- a JavaScript library that loads content as it enters the viewport.
Checking an implementation
- Run the page through URL Inspection and open the rendered HTML.
- Confirm that each lazy-loaded image appears with its real image address in
srcorsrcset, not a placeholder. - For galleries and carousels, confirm that the images beyond the first are in the rendered HTML without a click.
- Confirm that the first-screen images carry no lazy-loading attribute.
- After the change, watch how the page’s group moves in the Core Web Vitals report.
Before spending more on image indexing, ask whether image search is worth it for the site at all: when image SEO is worth the effort. Lazy-load what sits below the fold, through the viewport, and leave the top of the page to load at once.
Add a comment