Any of the three can work for Google, as long as every item can also be reached through an ordinary link. Google says its crawlers generally follow URLs in the href of <a> links and don't "click" buttons, so a "load more" button or infinite scroll with no linked pages behind it can leave older blog posts, projects or products undiscovered (Google Search Central, pagination and incremental page loading, last updated 10 Dec 2025, checked 9 Nov 2026). Numbered pages are the safest default for a small site. If you prefer "load more", make sure real page links exist underneath.

The three patterns in plain terms

  • Pagination: page 1, 2, 3 and "next" links. One batch at a time, each on its own URL.
  • "Load more": a button that adds the next batch to the same page.
  • Infinite scroll: the next batch appears automatically as you reach the bottom.

Google notes that "load more" and infinite scroll are "generally implemented using JavaScript". That's not a problem in itself. The problem is when the only way to reach item 13 onwards is to press a button or keep scrolling, because a crawler does neither.

Where this bites small business websites

You don't need an online shop for this to matter. Common places we see it:

  • A blog or guides listing that shows 12 posts and a "load more" button.
  • A projects or portfolio gallery with infinite scroll.
  • A product or menu page built with a page builder's "load more" widget.

If those older posts are also linked from elsewhere on your site, or listed in your XML sitemap, Google can still find them. If they aren't, they may sit undiscovered, and a page Google hasn't found can't rank or be used in AI answers.

What Google recommends

From Google's pagination guidance (checked 9 Nov 2026):

  • Link each page to the next one with <a href> links. Linking every page back to the first can hint that page 1 is the best landing page.
  • Give each page a unique URL, for example ?page=2.
  • Give each page its own canonical. Google says "Don't use the first page of a paginated sequence as the canonical page." Pointing page 2 and 3 at page 1 tells Google to ignore the very pages that link to your older items. Our guide to canonical tags explains how canonicals work.
  • Don't put page numbers in a # fragment. Google ignores fragment identifiers, so /blog#page=2 looks the same as /blog.
  • Don't rely on rel="next" and rel="prev". Google no longer uses them, though other search engines may.
  • Same titles are fine. Google says you can use the same title and description across the sequence.
  • Keep filters and sort orders out of the index if they create endless URL variations, using noindex or robots.txt rules.

Google also suggests a sitemap (or, for shops, a Merchant Center feed) to help it find items that aren't reachable through links.

Which pattern should you choose?

Your situation Sensible choice
Blog or guides list, under a few hundred posts Numbered pagination, plus good internal links between related posts
Project gallery where browsing is the point "Load more" or infinite scroll, backed by real paginated URLs or individual project pages linked elsewhere
Small product range One page with everything, if it loads quickly
Large catalogue with filters Pagination for the main list; keep filter combinations out of the index

Whatever you pick for visitors, the test is the same: can every item be reached by following plain links?

A two-minute check

  1. Open your listing page and scroll to the bottom. Is there a "load more" button, infinite scroll or numbered links?
  2. View the page source (right-click, View page source) and search for page=2 or /page/2. If you find a normal link, crawlers have a route. If you find only a button, they may not.
  3. Pick an old item. Choose a post or project you'd only reach after several "load more" clicks. In Google Search Console, run URL Inspection on it to see whether it's indexed. Our guide on checking whether a page is indexed covers the steps.
  4. Check page 2's canonical, if you have numbered pages. In the source, find rel="canonical". It should point to page 2 itself, not page 1.

How to fix it, in order

  1. Add real page links. Many themes and page builders offer numbered pagination as a setting. If you keep "load more" for visitors, ask your developer to make each batch available at its own URL with a normal link as well.
  2. Fix canonicals that point every page to page 1.
  3. Link older items from somewhere else too: related-post links, category pages, your main navigation. See our guide to internal links for small websites.
  4. Make sure your sitemap lists the individual posts or projects, not just the listing page.

A hypothetical example

[Business name], an interior design studio, has 60 projects in a gallery that shows nine at a time with infinite scroll. Only those first nine are linked anywhere else. Search Console shows most older project pages as "Discovered, currently not indexed" or not known at all. They switch the gallery to numbered pages, keep each page's canonical pointing to itself and add "related projects" links on each project page. Discovery problems like this are usually fixable. What happens to rankings afterwards depends on the quality of the pages and the competition.

What's in your control, and what isn't

In your control: making every item reachable by plain links, correct canonicals, sitemaps and sensible internal linking.

Not in your control: how quickly Google crawls the newly linked pages, whether it chooses to index each one and where they rank. Making pages findable makes them eligible. It doesn't guarantee traffic.