New researchTechnical SEO & AI Search · 2027Explore the framework

Lazy loading and SEO: keep content and links visible to Google

Learn when lazy loading helps performance, when it hides content from Google, and how to test images, product lists and infinite scroll safely.

Part of the JavaScript SEO series. For the full picture, start with JavaScript SEO: the complete rendering and indexing guide.

Lazy loading is a sensible way to avoid downloading content nobody has reached yet. It becomes an SEO problem when the next product row, article section or link appears only after a person scrolls or clicks. Google’s lazy-loading guidance is precise: relevant content should load when it is visible in the viewport, without depending on user actions.

Does lazy loading hurt SEO?

Not by itself. It hurts discoverability when important content or links never reach the HTML Google renders. Google does render JavaScript, but its crawler does not interact with the page by scrolling and clicking to reveal more. If a page needs those actions before it loads a product or a link, a crawler may not find it.

Separate three situations:

What loads later Main risk Better implementation
Below-the-fold images Image is absent from rendered HTML or has no real src Native loading="lazy" with a real src, dimensions and a fallback
Text or cards entering view Important content appears only after manual scrolling Load on viewport visibility, or render the essential text in initial HTML
More products via a button or infinite scroll Later products have no crawlable route Link to persistent paginated URLs with <a href>

The first screen is different. An above-the-fold hero image or key answer is already needed, so do not postpone it merely because a CMS offers a site-wide lazy-loading switch. web.dev’s LCP guidance explains why lazy-loading the LCP image delays its discovery. See the separate image optimization guide for image size, priority and layout stability.

What does Google need to discover lazy-loaded images?

Use an ordinary <img> with a real src, optionally inside <picture> with srcset. Google’s image SEO documentation says it finds images in an <img src> and recommends a src fallback for responsive images. If a library keeps the real address only in data-src until someone scrolls, inspect what appears in Google’s rendered HTML instead of assuming it was loaded.

For below-the-fold images, native loading="lazy" is a simple default. Include width and height so their space is reserved. Do not rely on a click-to-load gallery if the images themselves must be discovered in Search.

How should infinite scroll work for SEO?

Give every later chunk a stable URL and a crawlable link to it. Google’s infinite-scroll guidance recommends persistent, unique URLs, sequential links between chunks and History API updates when a new chunk becomes the primary view. A URL such as /shoes/?page=3 is stable; “the next 20 products after today’s newest item” is not.

An infinite-scroll interface can sit on top of normal pagination. Users keep scrolling, while crawlers and people with JavaScript disabled can follow Next links. Do not make the only route to page three a button with an onclick handler. Google’s link guidance says an <a href> is the reliably crawlable form. The pagination SEO guide covers canonicals and page-number URLs in detail.

How do you audit a lazy-loaded template?

  1. Pick an article, category page and product list that use lazy loading. Include a deep item that appears only after scrolling in a normal browser.
  2. View the raw HTML, then the rendered HTML. Look for the key text, product links and image src values in each. The raw-versus-rendered guide shows the comparison.
  3. Inspect the same URL in Search Console. Check the rendered HTML, not just a screenshot. Google’s guidance explicitly recommends this test.
  4. Open a deep page URL directly, without first visiting page one. Confirm it returns the intended products, a 200 response and usable links onward.
  5. Re-run the crawl after fixing the template. Crawlens flags links only in rendered HTML, content dependent on JavaScript and pages that failed to render. These are review signals; Search Console confirms what Google received.

If the crawler finds the page only when rendering is enabled, serving important links in initial HTML is usually a sturdier fix. If a deep product appears in neither crawl, inspect the pagination or navigation path before changing its metadata.

Lazy loading SEO checklist

  • First-screen content and likely LCP image load eagerly
  • Below-the-fold images have real src values and reserved dimensions
  • Important text becomes available without a click or manual scroll
  • Infinite scroll has persistent page URLs and <a href> links
  • Deep paginated URLs work when opened directly
  • Search Console rendered HTML contains representative items and links

The goal is to delay optional downloads, not discovery of the pages and content you want in search.

Frequently asked questions

Can Google index lazy-loaded content?

Yes, when it loads as the content becomes visible in the viewport during rendering. Google does not scroll or click to trigger content, so anything that requires those actions can be missed.

Should I lazy-load the hero image?

Usually no. The hero is visible on initial load and may be the LCP element. Delaying it can slow the first screen; reserve lazy loading for below-the-fold images.

Is infinite scroll bad for SEO?

Infinite scroll can work for users, but search engines need persistent URLs and crawlable links to later chunks. Use paginated pages underneath the scrolling experience.

How do I test lazy loading for SEO?

Inspect a representative URL in Search Console and check its rendered HTML for the important text, links and image src attributes. Also compare raw and rendered HTML with a crawler, and test deeper pagination URLs directly.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows