Infinite Scroll SEO

Infinite scroll SEO is the set of techniques that keep content crawlable when a page keeps loading more results as the user scrolls, instead of splitting them across numbered pages. The stakes: a crawler doesn't scroll. If your items only load in response to a scroll event, and there's no real URL behind them, Googlebot never requests them, and everything past the first screen is invisible to search.

This is the trap. Infinite scroll is a great UX pattern and a terrible default for discoverability, because the two goals pull apart. Users want a seamless feed; crawlers want distinct, requestable URLs. The fix isn't to abandon infinite scroll, it's to build crawlable paginated URLs behind the scroll, so the smooth experience is a progressive enhancement layered on top of a structure a bot can walk.

The pattern: real URLs under the scroll

Every "load more" chunk must correspond to a page a crawler can fetch on its own. You expose those pages with genuine, indexable, linkable URLs and let JavaScript stitch them together for humans.

<!-- Page 1 of a category feed -->
<div id="results">
  <!-- items 1–24 rendered server-side -->
</div>

<!-- A REAL crawlable link to the next page, always in the HTML -->
<a href="/category/shoes?page=2" rel="next" class="load-more">
  Load more
</a>

<script>
// Progressive enhancement: intercept the click, fetch page 2,
// append its items, update the URL — but the <a href> still
// works and is still crawlable if JS never runs.
document.querySelector('.load-more').addEventListener('click', async (e) => {
  e.preventDefault();
  const next = e.target.getAttribute('href');
  const html = await (await fetch(next)).text();
  appendItems(html);
  history.pushState(null, '', next); // /category/shoes?page=2
});
</script>

The non-negotiable line is the <a href="/category/shoes?page=2">. It exists in the server-rendered HTML whether or not JavaScript runs. A crawler follows it to a real page 2 that returns its own items server-side. Humans get the seamless scroll; bots get a paginated path. Both win. Note that rel="next"/rel="prev" no longer influence Google indexing, but the real href does all the work regardless.

Infinite scroll vs. crawlable pagination

How to check it on your own site

1. Disable JavaScript and scroll. With JS off, can you still reach page 2 via a clickable link? If the feed just stops, crawlers are stopping there too.
2. View source for a real next-page link. Search the raw HTML for an actual <a href> pointing to ?page=2 (or equivalent). An onClick handler with no href doesn't count.
3. Fetch page 2 directly. Load /category/shoes?page=2 in a fresh tab. It should return its own server-rendered items, not a blank shell or a redirect home.
4. Crawl with rendering off. Run a crawler with JavaScript disabled and confirm it discovers every paginated URL. The gap is what Google might miss.
5. Check Search Console coverage. Confirm your ?page=N URLs are indexed (or intentionally canonicalized), not lumped as "Discovered – not indexed."

Common mistakes and how to fix them

• Scroll events with no URL at all. Items append via JS and the address bar never changes, so there's nothing to crawl or share. Fix: back every chunk with a real ?page=N URL and update it with pushState.
• "Load more" as a button with no href. A <button onclick> that fetches via JS only. Fix: make it an <a href> to the next page so it degrades gracefully.
• Canonicalizing every page to page 1. Pointing ?page=2..N canonicals at page 1 tells Google to ignore deep items entirely. Fix: let each paginated URL self-canonicalize.
• Page 2+ returns a blank shell. The paginated URL exists but only renders client-side, so a bot fetching it directly gets nothing. Fix: render paginated results server-side. See JavaScript SEO.
• Relying on rel="next"/rel="prev" for indexing. Google stopped using those as an indexing signal. Fix: rely on plain crawlable links; keep rel tags only as harmless hints.

Frequently asked questions

Does Google crawl infinite scroll?

Not the scroll itself. Google won't trigger scroll events to load more. It only reaches deep content if there are real, crawlable paginated URLs behind the feed for it to follow.

Is infinite scroll bad for SEO?

Only when it's the whole mechanism with no crawlable fallback. Layer infinite scroll on top of genuine ?page=N URLs and you keep the UX without sacrificing discoverability.

Do rel=next and rel=prev still matter?

Google confirmed it no longer uses them as an indexing signal. They're harmless to keep, but real anchor links to each page are what actually get your content crawled now.

Should each paginated page be indexable or canonicalized to page 1?

Let each page self-canonicalize so its unique items can be indexed. Canonicalizing everything to page 1 hides your deep content from search.

What about "load more" buttons versus true infinite scroll?

Same rule applies to both: the control must be a real link to a real next-page URL. Whether it fires on click or on scroll, if there's no crawlable href, deep content is invisible. See Pagination.

Related reading: SEO-Friendly Pagination in 2026: Handling Page 2+, Load More, and Infinite Scroll.