Pagination is one of those SEO topics where you get five different answers from five different experts. Should you noindex paginated pages? Canonicalize them to page 1? Leave them alone? The truth is that the right answer depends on your site structure, your content type, and how Google discovers your deeper pages.
In this practical walkthrough, we break down when to noindex, when to use rel canonical, and how to preserve link equity across paginated series. We use a decision tree approach with real examples from blog archives and e-commerce category pages.
Why Pagination Matters for SEO
Pagination refers to the numbered pages you see at the bottom of blog archives, category listings, or search results (page 2, page 3, and so on). These URLs typically look like /blog/page/2/ or /category/shoes?page=3.
Google has been clear on this: pagination is often the only way crawlers can discover older articles, deeper product listings, or archived content. If you block those paths, you risk orphaning entire sections of your site.
According to Google’s own guidance, pagination in most cases should not contain noindex, because that is often how Google finds older content. But there are exceptions, and this is where a nuanced approach beats a blanket rule.
The Common Mistakes People Make
- Applying noindex to every paginated URL without considering internal linking.
- Setting a rel=canonical from page 2, 3, 4 pointing to page 1 (this tells Google those pages are duplicates, which they are not).
- Using noindex, nofollow together on paginated pages, which cuts off crawl paths entirely.
- Forgetting that once Google treats a page as noindex long-term, it may start treating it as nofollow too.
The Decision Tree: Should You Noindex Your Paginated Pages?
Instead of applying a one-size-fits-all rule, work through this decision tree for each paginated section on your site. We break it down further here.
Step 1: Are your deeper pages reachable via other internal links?
Ask yourself: if I remove pagination from Google’s index, can Googlebot still reach page 47 of my blog archive through another route (sitemap, related posts, tag pages, hub pages)?
- Yes: You may safely consider noindex on paginated pages.
- No: Leave paginated pages indexable. Blocking them will orphan old content.
Step 2: Do paginated pages generate search traffic?
Check Google Search Console. Filter URLs that contain /page/ or ?page=. If those pages receive impressions or clicks, keep them indexed. This is the sort of thing a solid design studio ships without fuss.
Step 3: Are paginated pages providing value to users?
Blog archive page 12 with no unique text is rarely valuable. But an e-commerce category page 3 with 48 different products is genuinely useful.
Step 4: Choose your treatment
| Scenario | Recommended Treatment |
|---|---|
| E-commerce category with unique products per page | Index, self-referencing canonical, follow |
| Blog archive, no unique text on paginated views | Index but low priority, self-canonical |
| Thin tag or author archives | Noindex, follow (only if content is reachable elsewhere) |
| Filtered category views (color, size, price) | Noindex, follow or robots.txt disallow |
| Paginated comments on a single article | Canonical to the main article URL |
Real Example 1: A WordPress Blog Archive
Imagine a blog with 400 articles. The homepage links to the 10 most recent posts, and pagination handles the rest (/page/2/, /page/3/, up to /page/40/).
If you add noindex, follow to every paginated page, Google will initially crawl those pages and follow the links to older posts. But over time, Google tends to treat long-term noindexed pages as nofollow. Your older articles slowly lose their crawl path.
Better solution: Keep pagination indexable with self-referencing canonicals, and also build:
- An HTML sitemap linking to every article
- A robust internal linking strategy (related posts, contextual links)
- An XML sitemap submitted through Search Console
This way, even if Google eventually deprioritizes paginated URLs in search results, your older content stays discoverable.
Real Example 2: An E-commerce Category Page
Take a shoe store with a category page /mens-running-shoes/ containing 240 products spread across 10 paginated pages. See blackhatworld.com for their take.
Each paginated page shows 24 unique products. Even though the H1 and intro text are shared, the product listings differ. These pages are not duplicates.
- Set a self-referencing canonical on each paginated page (page 2 canonicalizes to page 2).
- Do NOT canonical page 2 back to page 1. Google will likely ignore that anyway, and it is not the intent.
- Keep pages indexable so product pages are discoverable and can rank for long-tail queries.
- If you have layered navigation (filters), noindex the filtered combinations that create infinite URL variations.
Preserving Link Equity Across Paginated Series
Link equity flows through links. If you cut those links, you cut the equity. Here is how to preserve it:
- Never use nofollow on internal pagination links. Let PageRank flow to deeper pages.
- Use clear numbered navigation (1, 2, 3, … 40) instead of infinite scroll only. Give crawlers actual anchor tags.
- Interlink from hub pages to important deep content so it does not rely solely on pagination.
- Include all URLs in your XML sitemap, including target pages that pagination leads to.
- Avoid infinite scroll without pagination fallback. If you use JavaScript infinite scroll, provide crawlable paginated URLs underneath.
What About rel=”next” and rel=”prev”?
Google stopped using rel="next" and rel="prev" as indexing signals back in 2019. You can still include them for accessibility and for other search engines like Bing, but they will not help you with Google directly. There’s a good explainer over at hackmd.io.
Quick Implementation Guide by Platform
WordPress with Rank Math or Yoast
- Both plugins offer an option to noindex paginated archives.
- Only enable it if you have strong alternative internal linking to deeper content.
- Yoast defaults to self-referencing canonicals on paginated pages, which is the safer choice.
Shopify
- By default, Shopify sets canonicals on paginated collection pages pointing to themselves. Good default.
- Do not manually canonical page 2 to page 1 through theme edits.
BigCommerce and Custom Platforms
- Ensure paginated URLs are crawlable and have self-referencing canonicals.
- Add
<meta name="robots" content="noindex, follow">only when deeper content is reachable via other paths.
Summary: The Safe Default in 2026
If you are unsure and want the safest default:
- Keep paginated pages indexable.
- Use self-referencing canonicals.
- Ensure every important deep URL is reachable through multiple internal paths, not just pagination.
- Submit a clean XML sitemap for target content.
Only apply noindex to paginated pages when you have confirmed that your deep content is reachable elsewhere and that those paginated URLs bring no meaningful search value.
Frequently Asked Questions
Should paginated pages be indexed?
In most cases, yes. Google has confirmed that pagination is often how it discovers older content. Only noindex paginated pages if you have alternative crawl paths to that deep content.
Should I canonical page 2 to page 1?
No. Page 2 is not a duplicate of page 1. Google will likely ignore the canonical, and you risk sending confusing signals. Use a self-referencing canonical instead.
Is pagination bad for SEO?
Pagination itself is not bad. Poorly implemented pagination, such as JavaScript-only infinite scroll without crawlable URLs, or cutting off deep content, can hurt SEO.
What happens if I noindex all my paginated pages?
Short-term, Google will drop them from the index but still follow links. Long-term, Google may treat them as nofollow, effectively orphaning your older content.
Do rel=next and rel=prev still work?
Google stopped using them as indexing signals in 2019. They are still valid HTML and can help other search engines and accessibility tools, but they will not directly impact Google rankings.
Should I use noindex, follow or noindex, nofollow on paginated pages?
If you do decide to noindex, always use noindex, follow so link equity can still flow. Never use noindex, nofollow on internal pagination.