Pagination SEO best practices shifted fundamentally in 2019 when Google retired the rel="next" and rel="prev" markup signals it had supported for years — and as part of a complete SEO strategy for South African businesses, getting pagination right is increasingly critical as catalogues grow and Google's crawl resources stay finite.
Whether you manage a WooCommerce catalogue, a news archive, or a listing-heavy directory, the way you structure paginated content determines what Googlebot can crawl, which pages get indexed, and which products disappear from search results. Many SA websites in 2026 are still following advice built for that older era: this post covers what Google actually wants, the two mistakes that orphan your content, and a practical decision framework for any SA site.
The good news is that Google's official ecommerce pagination guidance is more flexible than most site owners expect — three different approaches all receive Google's blessing.
The bad news is that the wrong variation of any one of them will silently block Googlebot from reaching products and articles buried on pages 2, 3, or 10 of a paginated series. Given that crawlability issues on South African sites often go undetected for months, getting pagination right from the start is materially easier than diagnosing the damage later.
Quick Answer
Pagination SEO best practices in 2026 centre on three Google-approved approaches: self-referencing canonical tags on each paginated page, a consolidated "View All" page, or standard standalone indexing of each page. Rel="next" and rel="prev" were retired in 2019 and offer no ranking benefit. Never noindex paginated pages — Googlebot will stop following their links, orphaning products only accessible on those pages. Use noindex on filter and sort URL variants, not on the core page sequence itself.
Jump To
Are deep pages in your catalogue invisible to Google?
Send us your site and we'll identify which paginated pages Googlebot is skipping — and exactly what needs to change to bring them back into the index.
Get a Pagination AuditWhy Pagination SEO Still Trips Up SA Sites in 2026
Pagination is the practice of splitting a long list — products in a category, blog archive posts, search results — across multiple sequential pages, each accessible via a unique URL. Done correctly, it keeps individual pages fast and usable. Done incorrectly, it creates a chain of technical problems that compounds the larger your catalogue grows.
The confusion in South Africa stems from two overlapping misconceptions. First, many developers and site owners still add rel="next" and rel="prev" link tags, believing these help Google understand the series. Google confirmed in 2019 that it no longer uses these as indexing signals. Adding them causes no harm, but provides no benefit either.
Second — and far more damaging — many site owners have been told to noindex paginated pages to save crawl budget. This gets the logic backwards: noindexing paginated pages causes Googlebot to stop following links on those pages. Any product on page 4 or page 7 becomes effectively invisible — without a crawl it cannot appear in search results.
Common mistake: Adding noindex to every paginated page beyond page 1 to "protect crawl budget." Result: Googlebot abandons the link chain at page 1, and all products only discoverable from deeper pages drop out of the index.
Correct approach: Self-referencing canonical tags on each paginated page, standard <a href> sequential links throughout, and noindex reserved only for filter and sort URL variants — not the core page sequence.
The Three Pagination Approaches Google Accepts
Applying pagination SEO best practices starts with choosing the right implementation pattern. Google's official ecommerce guidance recognises three valid approaches, and all three are defensible depending on your site's size and structure.
| Approach | How It Works | Best For | Key Risk |
|---|---|---|---|
| Self-Referencing Canonicals | Each paginated URL has a canonical tag pointing to itself; sequential <a href> links connect the series | Most SA ecommerce catalogues; blog archives | None if implemented correctly — this is the recommended default |
| View-All Page | A single page loads all items; all paginated URLs canonical back to it | Small-to-medium catalogues where a full list loads within performance budgets | Page becomes too heavy for SA mobile users on slow connections |
| Standalone Indexing | Each page carries a self-referencing canonical and is treated as a destination page in its own right — not merely a continuation of a series | Paginated pages that can rank independently on their own keywords (e.g., an archive page 2 that naturally attracts searches distinct from page 1) | Requires genuinely unique content and distinct meta tags on every page — not just a page number difference; otherwise the pages compete with each other |
The approach to avoid without exception: pointing all paginated pages' canonical tags back to page 1. This instructs Google that pages 2, 3, and beyond contain no unique content worth indexing — and it cuts off the internal link equity that should be flowing down through those pages to the products and articles they list.
Key Takeaway: Canonical Tags on Paginated Pages
Each page in a paginated series should carry a self-referencing canonical tag — meaning the canonical for example.co.za/category/?page=3 should point to example.co.za/category/?page=3, not to the root category page. Never use page 1's URL as the canonical for all pages in the series.
Implementation: Canonical Tag + Pagination Nav
Self-referencing canonical in <head> — URL matches the page's own URL:
<link rel="canonical" href="https://www.example.co.za/category/?page=3">Minimal crawlable nav — every link a plain <a href>, no JavaScript:
<nav aria-label="Pagination">
<a href="/category/?page=2">Previous</a>
<a href="/category/?page=1">1</a>
<a href="/category/?page=2">2</a>
<a href="/category/?page=3">3</a>
<a href="/category/?page=4">Next</a>
</nav>One additional technical requirement across all three approaches: Google specifically recommends using standard <a href> tags for all pagination links, including "Next", "Previous", and numbered page links. Google's crawlers do not click JavaScript-rendered buttons or trigger on-click events — your pagination navigation must exist as crawlable HTML links, not JavaScript calls, or Googlebot cannot discover subsequent pages.
How Pagination Affects Your Crawl Budget for Large SA Catalogues
Google defines crawl budget as the set of URLs it can and wants to crawl — a finite resource determined by your server's response consistency and how much of your site appears worth crawling. For most small South African sites, crawl budget is not a meaningful constraint. For larger catalogues — clothing retailers, electronics stores, directories with thousands of listings — it becomes a real concern.
The core problem is that poorly implemented pagination multiplies low-value URLs. A category with 500 products split across 50 paginated pages creates 50 URLs Googlebot must decide how to handle. If many of those pages carry identical meta descriptions, duplicate title tags, and no meaningful unique content of their own, Google's crawl demand for them drops — and the products listed on those pages suffer in turn.
The straightforward fix: give every paginated page a genuinely unique meta title and description, even something as simple as appending "— Page 3" to the category title. That single change signals to Googlebot that each URL warrants a fresh crawl, rather than treating the series as a wall of identical content.
Crawl Budget Quick Wins for Paginated Sites
- Unique meta title and description on every paginated page (even a simple page number suffix)
- Standard HTML
<a href>links throughout pagination navigation — no JavaScript rendering - Avoid URL fragments (
#) for pagination: Google ignores the fragment portion of any URL entirely, soexample.co.za/category#page3delivers no pagination signal to Googlebot at all - Keep your server response times fast: slow responses reduce Google's crawl rate limit
- Block filter and sort URL variants via robots.txt or noindex — not the pagination sequence itself
- Include a link back to page 1 in every paginated page's navigation to reinforce its primacy
- Submit an XML sitemap listing your canonical category and product URLs — when deep pages are hard to reach via crawl, the sitemap gives Googlebot a direct discovery path
For more on managing crawl efficiency site-wide, see our guide to improving crawlability for SA websites, and if you suspect pages have dropped out of Google's index already, our website indexation guide covers the diagnostic steps.
Not sure how many of your category pages Google is actually crawling?
Share your Search Console data with us and we'll show you which paginated pages are being skipped, how deep Googlebot is reaching, and where the indexation drop-off begins.
Request a Crawl ReviewInfinite Scroll and Load More: What Google Cannot See
Infinite scroll — where the page automatically loads more content as the user scrolls — has become a popular choice for product feeds and news streams because it removes navigation friction for human users.
The problem is that Google's crawlers do not scroll. They read the HTML content of a URL and follow the links within it; they cannot trigger the scroll event that loads additional products, and they generally cannot click the "Load More" button that replaces conventional pagination on many SA retail sites.
The practical result is that a product listing implemented as infinite scroll may show Google only the first batch of items. If a product appears only in the items loaded after scrolling — items that are never in the initial HTML response — that product is invisible to Googlebot and will not rank for anything.
Problematic: An SA clothing store replaces paginated category pages with infinite scroll. Google crawls the initial page load — 24 products. The remaining 180 products are loaded via JavaScript on scroll and never appear in Google's index. Those 180 product pages see no organic traffic.
Correct: The same store implements infinite scroll for the user experience, but maintains a parallel paginated version of the same category accessible via crawlable URLs. Google crawls the paginated version and indexes all 204 products. Human users see the smooth scroll experience; Googlebot sees clean HTML pages.
Google's official guidance for infinite scroll and load-more implementations is explicit: implement JavaScript SEO best practices and use sitemaps or product feeds to ensure complete content discovery. For South African ecommerce stores using Google Merchant Center, a clean and comprehensive product feed is a practical safety net — even if Googlebot cannot reach a product page via crawl, a correctly formatted feed entry can still appear in Google Shopping results.
Filtering and Sorting: Where Duplicate Content Traps Hide
Pagination, filtering, and sorting are distinct problems that SA ecommerce sites frequently mishandle together. A category with 20 paginated pages can generate thousands of URL variants once filters (colour, size, brand, price range) and sort orders are layered in — each combination a separate URL. Without intervention, Googlebot crawls walls of near-identical pages while missing the ones that actually matter. The guidance here differs from core pagination:
| URL Type | Recommended Treatment | Reason |
|---|---|---|
Core paginated pages (?page=2, ?page=3) | Crawlable + indexable with self-referencing canonical | These pages contain unique product listings and carry internal link equity |
Sort variants (?sort=price-asc) | Block via robots.txt or noindex | Duplicate content — same products, different order, no SEO value |
Filter combinations (?colour=red&size=M) | Block via robots.txt or noindex (unless the filter has genuine search demand) | Usually duplicate content; occasionally valuable (e.g., "red sneakers" as a real search query) |
Paginated filter combinations (?colour=red&page=2) | Block via robots.txt | Extremely low-value; never worth crawl allocation |
Implementation: Blocking Filter Variants in robots.txt
User-agent: *
Disallow: /*?sort=
Disallow: /*?colour=
Disallow: /*?size=
Disallow: /*?colour=*&page=Core paginated pages (?page=2, ?page=3) need no disallow rule — they remain crawlable by default. Verify patterns in Search Console's URL Inspection before deploying.
The exception worth noting: some filter combinations correspond to real search queries. "Red sneakers South Africa" or "laptops for home office South Africa" may have enough organic search volume to justify a purpose-built, indexable landing page. These are not auto-generated filter URLs — they are deliberate, curated pages with unique content. Our guide to ecommerce filtering best practices covers when faceted navigation pages are worth indexing and how to structure them for organic search.
Key Takeaway: Paginated Pages vs. Filter Pages
Noindex belongs on filter and sort URL variants, not on your core pagination sequence. Getting this distinction wrong — applying noindex to all paginated pages — is the single most common pagination mistake on SA ecommerce sites, and it silently removes products from Google's index over time.
Pagination and SA's Mobile-First Reality
South Africa's internet landscape is overwhelmingly mobile. According to Netcash's analysis of SA online shopping data (as of December 2024), 72.7% of SA web traffic comes from mobile devices, and 51.7% of online purchases occur via smartphone. Google has indexed the web on a mobile-first basis since 2019, meaning it primarily uses the mobile version of your pages to determine rankings.
For paginated pages, this creates a performance consideration beyond pure search mechanics. A page that loads quickly on mobile — fast HTML, properly sized images, no render-blocking resources — is crawled more thoroughly than a slow JavaScript-heavy equivalent. Many SA users access the web via mobile data rather than fixed broadband, so page weight affects both real users and Googlebot's crawl efficiency at the same time.
Load More implementations that trigger heavy JavaScript bundles on each tap are particularly problematic here — they increase technical complexity for Googlebot and slow the experience for real users simultaneously. Standard paginated HTML pages with clean <a href> navigation remain the most robust choice for SA sites where mobile performance and search discoverability must coexist.
If paginated pages are failing Core Web Vitals thresholds, fixing that pays dividends in both user experience and crawl rate — Google explicitly links faster server response times to higher crawl frequency.
Why South African Businesses Choose Growth Pulse Media for Technical SEO
Pagination problems rarely announce themselves. A site owner sees normal traffic on category page 1 and never notices that Googlebot stopped reaching pages 4 through 12 six months ago — taking a large portion of the catalogue with it. Finding these gaps requires a crawl audit cross-referenced against Google Search Console's Coverage report and indexed page counts per section.
At Growth Pulse Media, we run that process as part of technical SEO engagements for South African businesses. We check which paginated URLs are being crawled and at what depth, identify canonical tag errors, flag filter and sort variants wasting crawl budget, and confirm whether infinite scroll or load-more setups have left product pages outside the index. We keep a limited client load — every engagement receives senior-level attention, not a checklist handed to a junior.
Who This Is NOT For
Small single-category sites. If your entire product range fits on one page, pagination is not a factor. Spend the time on content and links instead.
Sites in the early crawl phase. If Google has not yet crawled your primary pages, pagination optimisation is premature. Get core category and product pages indexed before worrying about pagination depth.
Developers wanting a single universal rule. There is no one correct approach — the right method depends on catalogue size, server capacity, and content uniqueness per page. If you need a prescriptive single answer, the nuance here will frustrate you.
Businesses whose primary traffic is paid search. If paid campaigns through Google Merchant Center account for nearly all your catalogue visibility, organic pagination improvements will take months to show returns. The investment has long-term value, but it should not displace active campaign work in the short term.
Ready to find out which of your category pages Google is actually indexing?
We will audit your pagination structure, identify indexation gaps, and give you a prioritised fix list — no obligation, and we will get back to you within 24 hours.
Book a Pagination SEO ReviewFrequently Asked Questions About Pagination SEO Best Practices
Does Google still support rel="next" and rel="prev" pagination tags?
No. Google officially confirmed in 2019 that it no longer uses rel="next" and rel="prev" as indexing signals. Adding these tags causes no harm, but they provide no ranking or crawl benefit for Google. Focus instead on self-referencing canonical tags and crawlable anchor href pagination links, which are the signals Google actually acts on.
Should I noindex paginated pages beyond page 1?
No — this is one of the most damaging pagination SEO mistakes. When Google encounters a noindex tag on a paginated page, it stops following the links on that page. Any products or articles that are only accessible from those deeper paginated pages will not be crawled and will eventually drop out of the index. Reserve noindex for filter and sort URL variants, never for the core pagination sequence.
Is infinite scroll bad for pagination SEO best practices?
Infinite scroll is problematic for search performance if the content loaded on scroll is not accessible via static, crawlable URLs. Google's crawlers cannot scroll, so products that only appear after the scroll trigger will not be indexed. The recommended solution is to implement infinite scroll for the user experience while maintaining a parallel paginated version using standard HTML links that Googlebot can discover and follow.
How many products per paginated page is best for SEO?
Google does not specify a product count per paginated page. The practical balance is between page load speed — which affects both Googlebot's crawl rate and your users' experience — and the total number of pages in the series. Very few products per page creates unnecessary pagination depth; too many creates a slow-loading page that performs poorly for SA mobile users. Test page speed with your actual product images loaded and adjust accordingly.
What is the correct canonical tag for paginated pages?
Each paginated page should have a self-referencing canonical tag — the canonical URL for page 3 of a series should point to page 3, not to the root category page. Pointing all pages' canonical tags back to page 1 tells Google that the deeper pages contain no unique content worth indexing, which effectively cuts off internal link equity flowing to the products listed on those pages.
Fix Your Pagination SEO Before It Costs You More Rankings
Growth Pulse Media audits paginated SA websites for exactly the errors described here: canonical misconfigurations, noindex on core pages, filter URLs consuming crawl budget, and infinite scroll implementations leaving products stranded outside Google's index. We work with WooCommerce, Shopify, and custom-built SA catalogues. Senior attention, limited client load — no obligation, and we'll get back to you within 24 hours.
Get Your Pagination Audit