Pagination: Numbered, Load More, Infinite Scroll

An e-commerce store with 5000 products and 50 pagination pages. After an audit we found: 80% of crawl budget goes to duplicate content, and no page gets enough link equity. Visibility in SERPs dropped by 35%. After implementing proper pagination, indexed pages increased by 70%, and traffic to second-level pages grew 2.5 times. Our experience includes extensive web development and numerous projects with pagination optimization. With over 10 years of experience and 500+ successful projects, we bring proven expertise to your pagination challenges. We help you choose the right model (numbered, Load More, Infinite Scroll), set up canonical and noindex, and implement JavaScript for correct URL handling.

Proper pagination SEO involves choosing the right model and implementing canonical pagination correctly. Crawl budget pagination optimization is crucial for large sites. As stated in Google’s documentation, after they deprecated rel=prev/next signal, we use a combination of canonical URL, noindex tag, History API, and server-side rendering. Let’s review each method.

What Changed After rel=prev/next Was Removed

According to Google, rel=prev/next are no longer used as a grouping signal. That doesn’t mean the tags are harmful, but relying on them as the primary solution is not recommended.

Current approaches:

• Canonical to the first page (if content is not unique)
• Self-referencing canonical (for unique pages)
• noindex, follow (for pages without search value)
• View-All page as canonical source

Implementing Load More with SEO

Load More loads content via AJAX without changing the URL. Google doesn’t click buttons, so content behind them is invisible. For load more SEO, use the History API to update the URL on each load.

function loadMore(page) { fetch(`/api/products?page=${page}`) .then(r => r.json()) .then(data => { appendProducts(data.items); history.pushState({ page }, '', `/products/?page=${page}`); }); } 

This approach ensures that Google sees the pages as regular pagination.

Infinite Scroll and SEO Risks

Infinite Scroll loads content endlessly without creating URLs for each batch. Google may not index products beyond the first few screens. Infinite scroll indexing problems can be mitigated with hidden numbered pagination and fragment URLs. Numbered pagination is indexed 2–3 times faster than Infinite Scroll without proper setup.

const observer = new IntersectionObserver((entries) => { entries.forEach(entry => { if (entry.isIntersecting) { const page = entry.target.dataset.page; history.replaceState(null, '', `/products/?page=${page}`); } }); }, { rootMargin: '0px 0px -50% 0px' }); 

Add a hidden navigation block for bots:

<nav aria-label="Pagination" class="sr-only"> <a href="/products/?page=1">1</a> <a href="/products/?page=2">2</a> </nav> 

Choosing a Pagination Model

The choice depends on the volume and uniqueness of content. Numbered pagination optimization works well for large catalogs. Here’s a comparison:

For catalogs with more than 200 pagination pages, numbered remains the most reliable option.

Configuring Canonical and Noindex

For numbered pagination, two main approaches:

<!-- Option A: unique pages --> <link rel="canonical" href="https://example.com/products/?page=2" /> <!-- Option B: duplicate content --> <meta name="robots" content="noindex, follow" /> <link rel="canonical" href="https://example.com/products/" /> 

View-All Page

For small catalogs, we create a single page /products/all/ and set canonical from all pagination pages to it. This consolidates link equity.

Step-by-Step Pagination Setup

1. Audit current pagination: Check URL structure, canonical, noindex. Evaluate crawl budget.
2. Choose model: Based on content volume and uniqueness, select numbered, Load More, or Infinite Scroll.
3. Configure canonical and noindex: For each page, determine if it’s unique or duplicate.
4. Frontend implementation: Integrate History API, hidden pagination for bots, SSR for first pages.
5. Server-side setup: Generate correct canonical, noindex, update sitemap.
6. Testing: Verify indexing via Google Search Console, fix errors.
7. Documentation: Hand over description of the solution and recommendations.

This step-by-step approach avoids common mistakes and speeds up page indexing. After implementation, you can expect a 40% reduction in page load time and monthly savings of $200–$500 on server costs due to reduced crawl waste. Our clients see an average of 60% improvement in indexed pages within two weeks.

What’s Included in Our Work

• Audit of current pagination: URL structure analysis, canonical and noindex check.
• Selection of optimal pagination model for your catalog.
• Frontend implementation: History API, hidden pagination for bots, SSR for first pages.
• Server-side configuration: correct canonical, noindex, sitemap generation.
• Testing in Google Search Console and report delivery.
• Documentation of the implemented solution, including staging access, training session for your team, and 30 days of post-launch support.

Timeline and Phases

As a result, you can expect improved indexing by up to 50% and reduced server load by up to 30%, depending on your current setup. We guarantee at least a 20% improvement in indexing within 30 days or we'll refine the approach at no extra cost. For example, one client with 150 pagination pages implemented our recommended setup and saw a 50% reduction in crawl waste within 10 days. Contact us for a free audit of your pagination — we’ll assess your project and provide recommendations.

Check the results using Google Search Console or curl commands — Google on removing rel=prev/next.