In short. Google Search does not scroll or click, so lazy-loaded content needs viewport-based loading or accessible linked pages, checked in rendered HTML.
Definition: Lazy loading defers loading offscreen or non-critical content. As of 17 October 2026, Google Search does not scroll or click to trigger loading, so content that requires those actions can remain unavailable to Search.
Key facts
- Google's lazy-loading documentation lists native image and iframe loading, the IntersectionObserver API, and libraries that load data when it enters the viewport, the browser's visible area.
- Google's browser-level image guide documents
loading="lazy"for offscreen images and recommends ordinary loading for images visible when the page opens. - Google's URL Inspection help distinguishes the indexed page report from a live test that fetches the current URL.
Which lazy-loading approaches work without a scroll event?
Google's implementation guidance requires relevant content to load whenever it is visible in the viewport. Loading must work without waiting for a scrolling or clicking action.
For images, the web.dev guide gives this browser-native example:
<img src="image.png" loading="lazy" alt="…" width="200" height="200">
The src attribute contains the image URL. The browser defers loading until the image approaches the viewport. The guide recommends width and height so the browser can reserve space for images while they load. Images visible when the page opens use default loading or loading="eager".
How should infinite scroll expose additional content?
Infinite scroll adds chunks of content as a reader moves down a page. Google's lazy-loading guide calls for each chunk to have a persistent, unique URL with consistent content. Its example uses ?page=12.
Pagination provides links between those pages. Google's pagination documentation recommends links from each page to the following page using <a href> elements. Google generally crawls these URLs. Its crawlers do not click buttons and generally do not trigger JavaScript functions that require user actions. Page numbers belong in distinct URLs; Google ignores URL fragments, the portion after #. The documented URL pattern can appear in an ordinary link:
<a href="?page=12">Next page</a>
How can the loaded content be checked?
In Search Console, Google's URL Inspection instructions describe inspecting a URL, selecting Test live URL, and opening View tested page for response details. The panel includes page HTML, a screenshot, loaded resources, and JavaScript console output. More info exposes resource and diagnostic information.
Google's lazy-loading test instructions say to search rendered HTML, the page HTML after rendering, for expected content. Image or video URLs should appear in the src attributes of <img> or <video> elements.
Related terms
- Infinite scroll
- JavaScript rendering and AI crawlers
- How do I inspect the HTML Google renders for a page?
- Googlebot
FAQ
Can I rely on a Load more button?
Google's pagination guide says its crawlers do not click buttons. Provide linked page URLs for the additional content.
Should I lazy-load an image visible when the page opens?
The browser-level image guide recommends default eager loading for these images. You can omit the loading attribute or use loading="eager".
Does a successful live test confirm indexing?
Google's URL Inspection help says the live test confirms whether its inspection crawler can access the page for indexing. Check the indexed report for Google's stored page information.
Sources
- Google Search Central, "Fix lazy-loaded content", updated 10 December 2025
- Google web.dev, "Browser-level image lazy loading for the web", updated 13 August 2024
- Google Search Central, "Pagination, incremental page loading, and their impact on Google Search", updated 10 December 2025
- Google Search Console Help, "URL Inspection tool", accessed 17 October 2026
Check how a page reads to answer engines. Open the GEO score analyzer