Guide : Pagination

TL;DR — Pagination is splitting a long liste — products, blog posts, search results — à travers numbered pages comme page 1, 2, 3. Chaque page nécessite its propre URL, and vous vouloir moteur de recherches to be able to explorer tout of les so ils peut trouver the content lié from the deepar pages. The big mistakes are telling Google ceux deepar pages don’t matter (by canonicalizing les tout to page 1 or noindexing les).

Ce que pagination is

Quand vous have plus items que fit on un page — dire 500 products in a category, or années of blog posts in an archive — vous split les à travers a series of pages. Page 1 montre the premier batch, page 2 the suivant, and so on. Chaque page lives at its propre adresse (a URL), usually something comme ?page=2 or /page/2/.

That’s pagination. You’ve utilisé it a thousand times sans thinking à propos de it.

Pourquoi c’est important pour le SEO

Lune pages themselves almost jamais rank pour anything or obtenir direct trafic. Leur réel job is to be a chemin que moteur de recherches follow to reach the products or posts listed on les. Si a bot can’t obtenir to page 3, it can’t trouver the choses que are seulement lié from page 3.

So the whole game is simple: let moteur de recherches explorer every page in the sequence. La plupart pagination problems come from accidentally blocking que chemin.

The three façons to montrer paginated content

1. Numbered pages (traditional pagination). Page 1, 2, 3, chaque its propre URL. Ce is the safe, SEO-friendly par défaut.
2. A “Load more” button. Un page, and clicking the button loads the suivant batch. Fine si the button is construit on réel liens — a problem si it’s a JavaScript-only button que bots can’t click.
3. Infinite scroll. Content garde chargement as vous scroll. Great pour utilisateurs, but bots don’t scroll, so sans réel numbered-page liens somewhere, le contenu plus loin bas may jamais obtenir trouvé.

The mistakes to éviter

• Don’t point every page’s balise canonical at page 1. Que indique Google pages 2, 3, 4 are simplement duplicates of page 1 and shouldn’t be indexé — qui peut hide le contenu on les.
• Don’t ajouter noindex to page 2 and au-delà. It feels tidy, but it peut causer Google to eventually arrêter exploration ceux pages, and alors it loses the chemin to everything ils lien to.
• Don’t block pagination in robots.txt or ajouter nofollow to lune page liens. Les deux cut off the explorer chemin.

The un piece of history worth knowing

Là utilisé to be a special bit of code — rel="prev" and rel="next" — que told Google how paginated pages connected. Google stopped en utilisant it in 2019. Don’t panic and rip it out, though: Bing encore uses it and navigateurs utiliser it to charger the suivant page faster, so it’s worth keeping.

Vouloir the complet version — self-canonicals, the crawl-chain problem with noindex, and the strange story of how Google’s deprecation got découvert — switch to the Avancé tab.

TL;DR — Treat every paginated URL as a standalone page: self-referencing canonical, crawlable, indexable, réel <a href> liens. The classic mistakes — canonicalizing pages 2+ to page 1, noindexing les, nofollowing leur liens, blocking les in robots.txt — tout break the explorer chain to le contenu ceux pages lien to. Google silently stopped en utilisant rel=prev/next avant announcing it in March 2019; Bing encore uses it, so leave the markup in placer. Budget d’exploration seulement matters at very grand scale, and paginated pages drive almost aucun direct trafic (un cas study: ~0,3% of organic clicks) — leur valeur is as explorer paths.

Chaque paginated page stands on its propre

Ce is the unique mental shift que fixes la plupart pagination problems. Après Google dropped rel=prev/next, John Mueller put the nouveau reality plainly: “Pour the la plupart partie, we simplement index lune pages as we trouver les, so as we’ve recommended pour a long temps, it’s bon to assurez-vous que tout pages peut stand on leur propre.”

“Stand on their own” signifie chaque page in the sequence is a normal, indexable page with a self-referencing canonical — page 2’s canonical points at page 2, page 3’s at page 3. Google’s propre current guidance is explicit: give chaque page its propre URL canonique; do pas utiliser the premier page as the canonical pour the whole définir.

Un exception to normal meilleur pratique: Google dit identical <title> tags à travers a paginated sequence are fine. Pages in a paginated définir “don’t need to follow” the usual unique-title recommendation, so vous don’t have to contrive “Page 2 of 9” suffixes (though ils don’t hurt).

The rel=prev/suivant story — and pourquoi it’s the interesting partie

Back in 2011 Google introduced rel="prev" and rel="next" — <link> elements in the <head> que told Google qui URLs formed a paginated sequence so it pourrait consolidate signals à travers les. Pour la plupart of the 2010s, ajout les was standard technical-SEO hygiene.

Alors it quietly stopped mattering. The façon the SEO world trouvé out is the partie la plupart write-ups skip: Gary Illyes découvert, during internal research, que Google had déjà silently stopped en utilisant rel=prev/next — and had pas been en utilisant it pour some temps. He escalated it internally, and on March 21, 2019 the @googlewmc account made it public:

“Spring cleaning! As we evaluated our indexation signals, we decided to retire rel=prev/suivant. Studies montrer que utilisateurs love single-page content, aim pour que quand possible, but multi-part is aussi fine pour Recherche Google.”

The rationale: Google’s indexation had become bon suffisant at recognizing paginated sequences from headings, titles, and maillage interne que the explicit hint was redundant. Quand I spoke à propos de ce at SMX West in early 2020, the chose I kept coming back to was how complètement it caught the industry off guard — we’d tout been doing fonctionner que, it turned out, Google hadn’t been reading pour a pendant que.

Devrait vous supprimer rel=prev/next? Aucun — and ce is où a lot of personnes overcorrect. I covered exactly ce in my Ahrefs piece, SEOs Are Breaking Pagination Après Google Modifié Rel=Prev/Suivant. Garder it, parce que:

• Bing encore supports and recommends it. Bing’s guidance is unchanged — un rel="next" and/or un rel="prev" par page, in the <head>. Stripping it to “clean up after Google” peut seulement hurt votre Bing performances.
• Navigateurs prefetch with it — ils peut preload the suivant page pour a faster experience.
• It’s a W3C standard and helps with accessibility.

So: Google ignores it, everyone sinon encore benefits. Leaving it in placer is the correct appel.

Canonicals: self-reference, pas page 1

The old, now-harmful pattern was canonicalizing pages 2, 3, 4… back to page 1. The intent was to “avoid duplicate content,” but the effect is the opposite of ce que vous vouloir: you’re telling Google ceux deepar pages are duplicates que shouldn’t be indexé, qui orphans le contenu lié seulement from les and breaks the explorer chemin via the sequence.

Correct: chaque page is self-canonical. The un legitimate alternative is a view-all page — a unique URL showing the whole définir — with the paginated pages canonicalizing to que. Google’s older guidance leaned on view-all heavily; the current guidance softens it to “an option if the page loads fast enough.” Pour la plupart grand catalogs, self-referencing canonicals on chaque paginated page is the simpler, safer par défaut.

Devrait vous noindex page 2+? Almost jamais — and here’s the trap

The tidy-looking déplacer is to noindex everything past page 1 so seulement page 1 montre in search. The problem is ce que noindex fait to exploration over temps: Google eventually crawls noindexed pages moins, and peut effectively arrêter suivant the liens on les. Si page 3 is noindexed and Google arrête exploration it, Google loses its chemin to everything that’s seulement lié from page 3. That’s the crawl-chain problem, and it’s pourquoi noindex on pagination tends to quietly bury content.

Mueller’s heuristic pour si une page peut be safely noindexed is a utile gut vérifier: “If someone only saw this page from my site, would that be OK?” Pour a genuinely thin, valueless page the réponse pourrait be yes — but pour a paginated listing that’s the seulement route to dozens of products, the réponse is almost toujours aucun.

Où noindex is souvent appropriate: filter and sort variants, qui personnes confuse with pagination. A vrai paginated sequence (?page=2) devrait stay indexable. A filtered or sorted variant (/shoes/?color=red&sort=price) is usually a near-duplicate spider-trap candidate que vous may legitimately vouloir to noindex or block. Knowing qui is qui is the whole skill — ce overlaps heavily with how vous handle faceted navigation, qui is its propre topic.

The autre crawl-path killers

The même “don’t break the path” rule rules out a few plus patterns:

• Don’t nofollow pagination liens. Chaque paginated page is partie of votre lien interne graph; nofollowing the nav liens blocks PageRank flow and explorer signal to the deepar pages.
• Don’t block pagination in robots.txt. Que arrête Google reaching lune pages at tout — and therefore everything lié from les.
• Utiliser réel <a href> liens pour pagination contrôle. Google crawls URLs trouvé in href attributes; a JavaScript-only “Load more” button que fires an onclick sans a réel lien is invisible to Googlebot. Google is explicit que its robots d’exploration “don’t ‘click’ buttons and généralement don’t trigger JavaScript functions que exiger utilisateur actions.”

Infinite scroll and “Load more” — faire les crawlable

Infinite scroll is fine pour utilisateurs and hostile to robots d’exploration unless vous give bots a fallback. The fix is a paginated, crawlable counterpart: réel ?page=n URLs with <a href> liens (souvent surfaced in a footer or a <noscript> fallback) que expose the même content the scroll loads dynamically. Même advice pour “Load more” — the button peut drive the UX, but là devrait be a réel anchor-link chemin to every page of results behind it. Pour very grand catalogs, lean on XML sitemaps (or a Merchant Center feed) to supplement discovery, since vous pouvez’t count on lien discovery alone reaching everything.

Données structurées on paginated content

There’s aucun special schema type pour “a paginated series.” Mark up what’s en réalité on chaque page: Product markup belongs on individual product pages (pas the pagination container), and Article markup on chaque page of a multi-part article series. Don’t essayer to express the prev/suivant relationship via données structurées — that’s pas ce que it’s pour.

Budget d’exploration and the reality vérifier

Pagination creates a lot of URLs, qui is pourquoi it obtient blamed pour crawl-budget problems. The honest réponse: pour la plupart sites it doesn’t matter. Budget d’exploration is a réel constraint seulement at grand scale — think 1M+ pages, or very grand rapidly modification catalogs. Google has, in Mueller’s framing, “a lot of experience dealing with pagination” and learns votre URL patterns over temps, so it généralement handles paginated sequences bien sans special configuration.

And worth keeping in perspective: paginated pages drive almost aucun direct organic trafic. Un well-known cas study trouvé pagination URLs accounted pour seulement ~0,3% of total organic clicks, with aucun negative SEO impact from having lots of les indexé. Que reinforces the framing throughout ce page — paginated pages earn leur garder as explorer paths to le contenu ils expose, pas as ranking pages in leur propre correct. So the practical advice I garder giving: don’t over-engineer it. Faire lune pages crawlable and self-canonical, alors leave les alone and let Google figure it out.

Un honest caveat: getting the technical setup correct — crawlable liens, self-canonicals, aucun accidental noindex — seulement garde the door ouvrir. It doesn’t guarantee Google crawls, indexes, or ranks quelconque donné paginated page, and it doesn’t guarantee trafic or an AI citation soit. Ce que it removes is the architectural raisons content on deepar pages obtient missed in the premier placer.

Ce topic sits alongside the rest of the structure du site cluster — internal linking, faceted navigation, Structure d’URL, and breadcrumbs tout shape the même crawl-path question from différent angles.

AI summary

A condensed prendre on the Avancé version:

• Pagination splits grand content sets (category pages, archives, search results, article series) à travers sequentially numbered URLs. Chaque page’s SEO valeur is as a explorer chemin to le contenu it liens to — pas as a ranking page.
• Chaque paginated page devrait stand on its propre: indexable, crawlable, with a self-referencing canonical. Google: give chaque page its propre URL canonique — don’t canonicalize pages 2+ to page 1.
• rel=prev/next: Google silently stopped en utilisant it avant announcing the retirement on March 21, 2019 (Gary Illyes trouvé it internally). Bing encore uses it, navigateurs prefetch with it, it’s a W3C standard — so don’t supprimer it.
• Don’t noindex page 2+ in normal cas: noindexed pages obtenir crawled moins and Google peut arrêter suivant leur liens, breaking the explorer chain to content lié seulement from ceux pages. Mueller’s tester: “Si someone seulement saw ce page… voudrait que be OK?”
• Filter/sort variants ≠ pagination. Vrai ?page=n stays indexable; filtered (?color=red&sort=price) variants are souvent legitimately noindexed/blocked.
• Aussi éviter: nofollowing pagination liens, blocking les in robots.txt, and JavaScript-only “Load more” buttons. Utiliser réel <a href> liens; give infinite scroll a crawlable paginated fallback.
• Données structurées: mark up what’s on chaque page (Product, Article); aucun schema type expresses a paginated series.
• Budget d’exploration matters seulement at grand scale (~1M+ pages). Paginated pages drive ~0,3% of organic clicks in un cas study. Don’t over-engineer it.
• Aucun guarantees: correct setup removes the architectural raisons deepar pages obtenir missed — it doesn’t guarantee exploration, indexation, rankings, trafic, or AI citations.

Documentation officielle

Primary-source guidance from the moteur de recherches.

Google

• Pagination meilleur practices pour Google — current canonical guidance: give chaque page its propre URL canonique, the three UX patterns (pagination, charger plus, infinite scroll), and crawlable-link requirements.
• Pagination with rel=“next” and rel=“prev” (2011) — the original (now-deprecated) guidance, kept pour historical context.
• Video à propos de pagination with rel=“next” and rel=“prev” (2012) — the 2012 follow-up.
• Consolidate duplicate URLs — canonicalization méthodes (the adjacent topic que pagination handling dépend on).

Bing / Microsoft

• Implementing markup pour paginated and sequenced content — Bing’s still-current rel=prev/next guidance: un rel="next"/rel="prev" par page, in the <head>, pairable with canonical.
• Bing Webmaster Guidelines.

Quotes from the source

On-the-record statements from Google. Chaque lien is a deep lien que jumps to the quoted passage on the source page.

Google — the rel=prev/suivant retirement (March 21, 2019)

• “Spring cleaning! As we evaluated our indexing signals, we decided to retire rel=prev/next. Studies show that users love single-page content, aim for that when possible, but multi-part is also fine for Google Search.” — @googlewmc, March 21, 2019. Voir the tweet
• “Google no longer uses these tags, although these links may still be used by other search engines.” — Recherche Google Central, pagination docs. Jump to quote

Google — give chaque page its propre canonical

• “Give each page its own canonical URL” — and don’t utiliser the premier page as the canonical pour tout paginated pages. Jump to quote
• On exploration JavaScript pagination: Google’s robots d’exploration “don’t ‘click’ buttons and generally don’t trigger JavaScript functions that require user actions to update the current page contents.” Jump to quote

John Mueller, Google — pages doit stand on leur propre

• “For the most part, we just index the pages as we find them, so as we’ve recommended for a long time, it’s good to make sure that all pages can stand on their own.” Coverage
• On the heuristic pour noindexing a paginated page: “If someone only saw this page from my site, would that be OK?” Si yes, vous pouvez noindex it — but that’s a élevé bar pour la plupart paginated content. Coverage

Pagination SEO checklist

A réussir to confirmer moteur de recherches peut explorer votre paginated sequences and le contenu behind les:

• Chaque paginated page has its propre unique URL (e.g. ?page=2) — aucun fragment identifiers (#) marking page numbers (Google ignores fragments).
• Chaque page carries a self-referencing canonical — pas a canonical pointing back to page 1 (unless you’re deliberately en utilisant a view-all page).
• Pages 2+ are indexable (aucun blanket noindex).
• Pagination contrôle are réel <a href> liens, pas JavaScript-only buttons.
• Pagination liens are pas nofollowed.
• Pagination URLs are pas blocked in robots.txt.
• rel="prev" / rel="next" left in placer (pour Bing, navigateur prefetch, accessibility) — même though Google ignores les.
• Infinite scroll / “Load more” has a crawlable paginated fallback with réel anchor liens.
• XML sitemaps supplement discovery pour grand catalogs (surtout JS-rendered listings).
• Filter/sort variants (e.g. ?color=red&sort=price) handled separately from vrai pagination — noindex/block ces si ils ajouter aucun unique valeur.
• Données structurées marks up what’s on chaque page (Product, Article), pas the pagination container.

The mental models

1. Paginated pages are explorer paths, pas destinations. Leur job is to expose the products/posts lié from les so bots (and PageRank) peut reach ceux. Une fois vous internalize que, almost every rule follows: don’t do anything que breaks the chemin. Un cas study clocked pagination at ~0,3% of organic clicks — ils don’t rank, ils route.

2. “Can this page stand on its own?” Mueller’s reframing après the rel=prev/suivant retirement. Treat chaque paginated URL as a normal, self-canonical, indexable page plutôt que a dependent fragment of a définir.

3. The four crawl-chain breakers. Garder ces straight and la plupart pagination mistakes disappear:

• Canonicalizing pages 2+ → page 1 (dit “duplicate, don’t index”)
• noindex on pages 2+ (obtient crawled moins → liens arrêter being followed)
• nofollow on pagination liens (blocks PageRank + explorer signal)
• robots.txt disallow (blocks accès entirely)

4. “Google uses it” ≠ “it’s still useful.” rel=prev/next is the canonical exemple: Google dropped it, but Bing uses it, navigateurs prefetch with it, and it’s valid HTML. Decide ce que to garder on tout consumers, pas simplement Google.

5. Pagination vs. faceted variants. A vrai sequence (?page=2) stays indexable. Filter/sort variants (?color=red&sort=price) are usually near-duplicate clutter vous pouvez noindex or block. Same-looking URLs, opposite handling — classify avant vous configurer.

How devrait a long listing expose plus items?

Pagination mistakes que cut the explorer chemin

Canonicalizing every page to page un

Page two and plus tard contain différent items, so page un n’est pas leur equivalent. Let component pages self-canonicalize; utiliser redirections or canonical consolidation seulement quand URLs are genuinely duplicates.

Ajout noindex to page two and au-delà

The directive removes ceux URLs from the index and peut weaken the chemin to items lié seulement from deepar pages. Garder the sequence crawlable and améliorer the listing au lieu de hiding its continuation.

Building infinite scroll sans persistent URLs

A scroll event or button n’est pas a explorer chemin. Pair the experience with unique, loadable page URLs and réel anchors so every item remains reachable sans utilisateur interaction.

Courant pagination échecs

Products on plus tard pages ne sont pas découvert

Symptom: Items visible après clicking or scrolling jamais apparaître in a explorer. Probable causer: The suivant batch loads seulement via JavaScript and has aucun anchor URL. Fix: Expose persistent paginated URLs, lien les with normal anchors, and vérifier a explorer beginning at page un reaches the item URLs.

Google selects page un as canonical pour the whole series

Symptom: Inspection d’URL reports page un as Google’s canonical pour deepar pages. Probable causer: Tout pages declare page un as canonical or render nearly identical content. Fix: Utiliser self-canonicals, distinct item sets, stable titles où utile, and consistent lien internes to chaque component page.

Robots d’exploration loop via endless page numbers

Symptom: A explorer discovers vide or repeated URLs far au-delà the dernier réel page. Probable causer: The suivant lien is generated sans checking si un autre batch exists. Fix: Arrêter emitting the suivant anchor on the final page and retourner a proper not-found réponse pour impossible page numbers.

Pagination signal référence

Testez vos connaissances: Pagination

Five rapide questions on handling pagination pour le SEO. Pick an réponse pour chaque, alors vérifier.

Ressources utiles

My pagination writing

• SEOs Are Breaking Pagination Après Google Modifié Rel=Prev/Suivant: Here’s How to Obtenir It Correct — my principal piece on ce topic: pourquoi to garder the markup, and the four mistakes que break pagination.
• Balise canonicals: A Simple Guide pour Beginners — the canonical mechanics que pagination handling dépend on.
• The Beginner’s Guide to SEO technique — où pagination sits in the bigger explorer/index picture.

My speaking

• Video: Patrick Stox on pagination, SEO technique & community (Moteur de recherche Land, SMX West 2020) — my prendre on how Google’s quiet rel=prev/suivant deprecation caught the industry off guard, and pourquoi SEOs over-engineer pagination.

From autour the industry

• Pagination meilleur practices pour Google (Recherche Google Central) — the current official guidance.
• Implementing markup pour paginated and sequenced content (Bing Webmaster Blog) — Bing’s still-current rel=prev/suivant requirements.
• Gary Illyes — The Googler Who Découvert rel=prev/suivant Ne … plus Pris en charge (Moteur de recherche Roundtable) — the story of how the deprecation surfaced.
• Google’s Advice On Pagination & Page Series Post rel=suivant and rel=prev (Moteur de recherche Roundtable) — Mueller’s “stand on their own” guidance.
• Ce que se produit quand 67% of a site’s indexé URLs are pagination? (GSQI / Glenn Gabe) — the cas study où pagination drove seulement ~0,3% of organic clicks with aucun negative impact.
• Explaining the ‘rel=prev/suivant’ saga of 2019 (Embryo) — a clair walkthrough of the deprecation and its aftermath.

Journal des modifications