Pagination and SEO: Splitting Pages Correctly
Pagination splits large amounts of content – but implemented wrongly, it costs visibility. This is how you make page numbering SEO- and user-friendly.
What you will learn
- What pagination is and where it is used
- How Google treats rel=next and rel=prev today
- Which SEO problems wrongly implemented pagination causes
- Which best practices apply for crawlable, indexable pagination
- Which outdated approaches you should avoid
What is pagination?
Pagination (page numbering) divides related but extensive content across several consecutive pages. Page numbers or “Next”/“Previous” buttons connect them so that users can navigate sequentially. You find it everywhere many elements belong to one page:
- E-commerce: category pages with many products
- Blogs and news: article archives and long post lists
- Forums: long discussion threads
- Galleries: many images at once
The main purpose is a better user experience: shorter load times and a digestible amount of information per page.
rel="next" and rel="prev": then and now
For a long time, Google recommended the link attributes rel="next" and rel="prev" in the <head> to indicate the relationship of paginated pages. In 2019, however, Google announced that it had no longer been using these attributes as an indexing signal for years. Paginated pages have since been treated like normal, independent pages.
Nevertheless, it can make sense to keep the attributes: other search engines like Bing still use them, and they help accessibility. For Google SEO, however, they are no longer decisive.
SEO challenges from pagination
Problems almost always arise from faulty implementation, not from pagination itself.
- Duplicate content: When paginated pages have the same title, descriptions, and H1 as the first page, or a
?page=1exists in addition to the root page. As long as the main content differs per page, they are not true duplicates. - Thin content: When an article is artificially split into many pages with little content each – often to maximize page views.
- Dilution of ranking signals: Backlinks and internal link equity spread across many URLs instead of bundling.
- Crawl budget: Crawling many paginated URLs consumes crawl budget that may then be missing for more important pages.
Pagination carries four risks: duplicate content, diluted signals, crawl budget waste, and weak individual pages.
Best practices
Every page of a pagination series should canonicalize to itself – not all to page 1.
1. Use crawlable anchor links
The foundation is that search engines can reach the paginated pages at all. Use standard HTML links (<a href="your-url">) and do not load links exclusively via JavaScript. The basics are covered under internal linking and JavaScript SEO.
2. Self-referencing canonical tags
Every paginated page should have a self-referencing rel="canonical" – so page 2 points to itself:
This is correct because every page, with its own unique content, represents the “master copy.” Additional parameters (e.g. for sorting) belong in rel="next"/rel="prev", but not in the canonical.
3. Slightly adjust on-page elements
Since every paginated page can rank and compete with the root page, signal to Google that the first page is the primary one: on subsequent pages, add the page number to the title (e.g. “Buy the best widgets – page 2”) and to the meta description. Introductory text and an optimized category image belong only on the root page. These deliberately sub-optimal titles keep Google from showing subsequent pages instead of the root.
4. Do not put paginated pages in the sitemap
Paginated URLs are indexable but rarely an SEO priority. They therefore do not belong in the XML sitemap – that is where the most important canonical URLs go.
5. URL parameters instead of fragments
Implement pagination via real URL parameters where possible (example.com/category?page=2) or clean paths – but never via fragment identifiers (#page2), since content after the # is generally not crawled. Also make sure that non-existent pages (e.g. ?page=99 with only 4 pages) return a 404 so that no crawling trap arises. The former “URL parameters” report in the Search Console no longer exists – Google discontinued it in 2022 and recognizes pagination patterns itself today.
6. Optimize click depth
Pagination increases the click depth to deeper-lying content. Reduce it with a flatter architecture (more specific subcategories instead of huge main categories) or a clever pagination design with links to the first/last page and jumps across several pages.
Special case: infinite scroll and “Load more”
Endless scrolling and “Load more” buttons are user-friendly but a hurdle for bots: Googlebot does not scroll or click. So that all content stays crawlable, an equivalent paginated series with crawlable anchor links is needed in the background, one that also works without JavaScript. While scrolling, JavaScript adjusts the URL via the History API (pushState). At its core, the same best practices apply, plus a more comfortable user layer.
Outdated and wrong approaches
- “Do nothing”: Relying on Googlebot alone leaves the ranking to chance – often a subsequent page then ranks instead of the root.
- Canonicalizing to a “View All” page: If a show-all page offers good UX, no pagination is needed; if it offers poor UX, it is not a solution. The combination confuses search engines.
- Canonicalizing all pages to page 1: a classic mistake. It falsely signals identical content – Google may then ignore the deeper-lying pages and their linked content.
- `noindex` on paginated pages: risky, because Google can, in the long term, treat the links as
nofollow. Content that is linked only via these pages then drops out of the index. - Blocking crawling entirely (robots.txt/`nofollow`): saves crawl budget but prevents the discovery of deeper-lying content. A trade-off depending on priority.
Conclusion
Pagination is a useful tool for structuring extensive content. Because Google treats paginated pages like independent pages, clean implementation matters: crawlable links, self-referencing canonicals, slightly adjusted on-page elements, no sitemap entry, and a fallback for infinite scroll. Anyone who avoids the outdated practices ensures that users and search engines work with the content optimally.
FAQ
Frequently asked questions
No. In 2019, Google confirmed that it had not used these attributes as an indexing signal for a while. Paginated pages are treated like normal pages. For Bing and accessibility, you can still keep them.
No, that is a common mistake. Every paginated page has unique content and should get a self-referencing canonical tag. Canonicalizing to page 1 can lead to Google ignoring deeper-lying content.
No. They are indexable but not an SEO priority. The sitemap should contain the most important canonical URLs, not the pagination pages.
In the background, create a paginated series with crawlable anchor links that also works without JavaScript. While scrolling, JavaScript adjusts the URL via the History API so that bots reach all content.
Quiz
Test your knowledge
Five questions on SEO-friendly pagination.
Question 1 of 5
How does Google treat paginated pages today?