Why Google Does Not Index Infinite Scroll Product Lists — and the Fixes
Key takeawayInfinite scroll puts everything below the second screen into DOM nodes inserted on scroll events. Googlebot typically does not scroll and does not trigger those load buttons, so products beyond the second screen simply do not exist for the index.
When this applies
- Stores whose product listings use "load more" buttons or infinite scroll
- Category pages where the first screen shows only a dozen products and the rest load on scroll
- Cases where GSC shows many product URLs with no crawl records at all
- Sites that had paginated pages indexed before a redesign, then lost most indexing after switching to infinite scroll
| Implementation | Crawler-visible range | Risk level | Recommended approach |
|---|---|---|---|
| Pure JS scroll loading | Usually first screen only | High | Switch to crawlable paginated links |
| Button-triggered loading | First screen plus a few clicks | High | Switch to pagination links |
| Infinite scroll with ?page= URLs | Depends on implementation | Medium | Keep indexable paginated URLs |
| Server-side rendering with client enhancement | Full | Low | Keep it and monitor |
| Fully static generation | Full | Low | Best option |
Step-by-step diagnosis
- Fetch a category page with curl, count the products in the HTML source, and compare against how many are visible after scrolling.
- Use URL Inspection's live test in GSC to see what Googlebot actually receives and confirm whether second-screen products exist.
- Count product URLs that were once indexed but now only load on scroll, to size the loss.
- Option A (recommended): restore crawlable pagination links — keep the ?page=N form and make the links clickable in the source.
- Option B: keep infinite scroll but additionally output an indexable "all products" page and point a canonical to it.
- Ensure content beyond the second screen is rendered server-side, not injected client-side.
- Request recrawling in GSC and watch recovery over 2-4 weeks.
Common mistakes
- Assuming Google will scroll the page automatically — Googlebot does not perform scroll interactions.
- Making "load more" an <a href="?page=2"> and expecting indexing — the content must genuinely exist in the source.
- Not requesting recrawling after the fix — old pages stay in the broken state for a long time.
- Keeping pagination only on the client while the server still returns just the first screen — nothing has changed for the crawler.
- Ignoring filters: infinite scroll combined with filters makes the URL set completely unmanageable.
FAQ
Is infinite scroll always a bad idea?
You can use it, but pair it with server-side rendering and crawlable links. Products loaded purely by JS scrolling are essentially invisible to the index.
Does switching back to pagination hurt user experience?
Modern e-commerce widely uses pagination or "view more" buttons combined with infinite scroll. The key is having crawlable URL entry points, not just the visual scrolling effect.
Can lost indexing be recovered?
Usually yes. After restoring crawlable links and requesting recrawling, most product pages re-enter the index within 2-4 weeks.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Common hreflang Errors on Multilingual Sites: The Full ListCanonical Tag Conflicts Causing Duplicate Indexing: How to Fix ThemXML Sitemap Errors: Types and Fixes ComparedWhy Breadcrumb Schema Errors Make Rich Results DisappearOn-Site Duplicate Content: Judgment Criteria and a Prevention ChecklistNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.