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.

Why are Core Web Vitals critical for technical SEO?

PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.

Core Web Vitals: what really affects rankings

Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.

LCP: why 8 seconds is not an image problem

LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.

Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.

Solution:

1. Move to <img> with fetchpriority="high" and loading="eager"
2. Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
3. <link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
4. Remove render-blocking scripts above hero with defer

Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.

If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.

CLS: what causes layout shifts and how to stop them

CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.

Sources:

• Images without dimensions. <img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
• Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via min-height or load before main content.
• Web fonts. font-display: swap with size-adjust minimizes CLS.
• Dynamic content — add skeleton placeholder with dimensions.

INP: why interface freezes for 500ms

INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.

Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.

Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:

• Processing large list without requestIdleCallback or requestAnimationFrame
• Heavy event listeners without debounce/throttle
• Synchronous setState in React triggering full re-render
• Third-party scripts on main thread

Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.

How do structured data and Schema.org improve search visibility?

Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.

Markup types by scenario:

• E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
• Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
• Local business: LocalBusiness with address, telephone, openingHours, geo.
• FAQ: FAQPage with mainEntity — questions appear as expandable block.

Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.

How to conduct a technical SEO audit

Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.

Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.

JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.

Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.

Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.

What does the optimization process look like?

What deliverables do you receive?

• Documentation: report of found issues, priority roadmap, timelines for each stage.
• Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
• Training: one or two calls reviewing typical mistakes for your team.
• Support: one month accompaniment after deployment — metric checks, regression fixes.

How many positions can you regain through technical SEO?

We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.

Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.