Any site with a blog, a product range or a project gallery soon has more items than fit on one page. Something has to split that list up. The usual choices are numbered pages, a load more button or infinite scroll. Each one changes how people move through your content and how Google finds it.
Picking the wrong pattern rarely breaks a site outright. It quietly hides older posts and products from search instead. This guide covers how each option works and what Google’s own documentation says about them. It also covers the small build details that decide whether your deeper pages get indexed.
The three common patterns
Google’s Search Central documentation describes three common ways to present long lists. Each has strengths and weaknesses for visitors. None of them is wrong on its own. The trouble starts when the build hides content from crawlers.
- Pagination. People move between pages using next, previous and page number links. It shows how big the result set is and where you are in it. The tradeoff is extra links to manage and a fresh page load each time.
- Load more. A button adds more results to the same page. It can still show the total count of results.
- Infinite scroll. New items appear as the visitor scrolls. It feels natural but can cause scrolling fatigue.
For a small business blog with a few dozen posts, any of these can work for visitors. A shop with hundreds of products is a different story. Google notes that load more buttons and infinite scroll cannot handle very large result sets. Numbered pages are the safer choice once a list grows long.
Why Google can miss content behind a button
Google generally crawls links found in standard anchor elements with an href attribute. Its documentation is blunt that Google’s crawlers do not click buttons. They also generally do not trigger JavaScript that needs a user action to run. Its guidance on lazy loading content adds that Google Search does not interact with your page.
That matters because load more buttons and infinite scroll are usually built with JavaScript. If the only way to reach page three of your products is to press a button, Google may never see page three. The products on it can then sit outside search results. Older blog posts can drop from view in the same way.
The fix is not to abandon these patterns. It is to back them with real links that a crawler can follow. A visitor can still enjoy a smooth scroll. Underneath, each batch of content should also live at its own address that Google can reach.
Give every page its own URL
Google recommends giving each page in a sequence its own URL. A query parameter such as ?page=2 is a common way to do it. Each URL should show the same content every time it loads. That is why Google suggests absolute page numbers rather than relative values like ?date=yesterday, which change what a page shows.
Avoid putting page numbers after a hash in the URL. Google ignores fragment identifiers, so everything after the # is invisible to it. A site that loads page two at /blog#page2 looks to Google like the same page shown twice. Moving the number into a proper parameter or path solves this.
If you use infinite scroll, the address bar should change as new content becomes the main thing on screen. Google points to the History API for this. It lets people refresh, share or bookmark the spot they reached. Without it, someone who refreshes after a minute of scrolling lands back at the top.
Link the pages together
Each page in a sequence should link to the next one using a normal anchor tag. Google also suggests linking every page in the set back to the first page. That hints the first page may be the best landing page for the collection. Plain next and previous links in the HTML cover most of this.
Good pagination is one of the details worth raising early in the website development process. Adding crawlable links to a finished JavaScript gallery is usually harder than building them in from day one. Layout choices matter here too. The way a list behaves on small screens ties closely to the choice between adaptive and responsive design.
Canonical tags and the rel next and prev myth
A common mistake is pointing the canonical tag on every paginated page at page one. Google’s guidance says not to use the first page of a sequence as the canonical page. Instead, each page should have its own canonical URL. Pointing them all at page one sends the wrong message about pages that hold different items.
Older SEO advice often recommended rel next and rel prev link tags. Google no longer uses these tags. Other search engines may still use them, so there is little harm in leaving them in place. Just do not rely on them to get your deeper pages found by Google.
Titles, filters and sort orders
Paginated pages can share the same title and meta description. Google tries to recognise sequences and index them accordingly. You do not need to write fresh copy for page seven of your product list. Effort is better spent on the main category page itself.
Filters and sort options are a different matter. A link like ?order=price can create another version of a list that already exists. Google suggests keeping these variations out of the index with a noindex robots meta tag. Another option is discouraging crawling of those URL patterns with robots.txt.
For shops, Google also mentions a sitemap or a Merchant Center feed as a way to help it find every product. These are a backstop rather than a replacement for crawlable links. A sound link structure plus a sitemap gives Google two routes to the same items. It is the kind of groundwork covered by reputable SEO services.
Testing what Google can see
Once the build is done, check it. The URL Inspection tool in Search Console shows how Google renders a page. Look at the rendered HTML and confirm your listed items are there. For images, check that the URLs appear in the src attribute of the img elements.
Also check that content does not wait for a scroll or click before it loads. Google recommends loading content when it enters the viewport, using options such as native browser lazy loading or the IntersectionObserver API. Do not lazy load items people see straight away, since that slows them down. If your pages pass these checks, Google should be able to reach the whole set.
These checks fit neatly into an approach to website design and development that treats search as part of the build. Leaving them until after launch tends to mean rework. A short review at the staging stage catches most problems before visitors or Google see them.
Frequently asked questions
Is infinite scroll bad for SEO?
Not by itself. Problems arise when extra content only loads after a scroll or click with no crawlable links behind it. Give each batch its own URL and link the batches together so Google can reach them.
Should paginated pages point their canonical tag at page one?
No. Google’s guidance says each page in a sequence should have its own canonical URL. Using the first page as the canonical for the whole set is something it specifically advises against.
Do I still need rel next and prev tags?
Google no longer uses them. Other search engines may still read them. They do no harm, but they will not help Google find your deeper pages.
Can my paginated pages share a meta description?
Yes. Google says pages in a paginated sequence can share titles and descriptions. It tries to recognise the sequence and index it accordingly. Put your writing effort into the main category or blog page instead.