Shopify Pagination Duplicate Content: Handling Paginated Collections
Search intent: fix · Updated February 2026
Shopify pagination duplicate content occurs when paginated collection pages (/collections/shoes?page=2, ?page=3) share nearly identical page structure - same title, meta description, navigation, and header - with only the product listing changing. Google dropped support for rel=next/prev in 2019, so the old solution no longer applies. The current best practice is: use unique meta titles and descriptions on each paginated page, add a canonical on page 2+ pointing to itself (not page 1), and focus on making each paginated page have enough unique content to justify indexing - or add noindex to pages beyond page 2 if they have very thin content.
Quick Diagnostic Checklist
- Does your collection have more than one page of products?
- View source on page 2 - is the title tag identical to page 1?
- What does the canonical tag say on page 2 - does it include ?page=2?
- Check Google Search Console Coverage for ?page= URLs - how many are indexed?
Not sure if your store has this issue?
Run a free scan to detect crawlability & indexing problems instantly.
What This Issue Means
Shopify collection pages paginate when collections have more products than fit on one page (default: 24-48 products). Each additional page - /collections/shoes?page=2, ?page=3, etc. - is a separate URL. If these pages share the same title tag, meta description, and minimal content differences, Google may treat them as near-duplicates and choose which to index or rank unpredictably. The historical solution (rel=next/prev link tags) was deprecated by Google in 2019 - so pagination SEO now requires different handling.
What Causes It (Shopify-Specific)
Same title and meta description on every paginated page
By default, Shopify themes output the same collection title and description on page 2, 3, 4 as on page 1: 'Shoes - Your Store'. Google sees these as duplicate page metadata, which reduces trust in pagination as intentional distinct pages.
No content differentiation between pages
Beyond the product grid changing, paginated pages often have identical headers, footers, navigation, and descriptive text. From Google's perspective, the ratio of unique to duplicate content is very low on page 2+.
Thin content on deeper pagination pages
Pages 5, 6, 7+ of large collections often contain only a few products from the 'long tail' of the collection - low-demand products that generate no search traffic themselves. These pages have thin content with no SEO value.
How to Detect It Manually
- 1Navigate to your largest collection and click to page 2 - look at the browser tab (title) and view-source (meta description)
- 2Is the title identical to page 1? ("Shoes - Your Store" on both page=1 and page=2?)
- 3Is the canonical on page 2 pointing to page 1 (wrong) or to ?page=2 itself (correct)?
- 4In Google Search Console → Coverage, search for "?page=" in the indexed URLs - how many paginated pages are indexed?
- 5Check if paginated pages beyond page 3 have significant organic traffic in Search Console
How to Fix It (Step-by-Step)
Add page number to title and meta on paginated pages
In your collection template or layout/theme.liquid, detect the page parameter and append it to the title and description to differentiate paginated pages.
{%- if current_page > 1 -%}
{%- assign page_suffix = ' - Page ' | append: current_page -%}
{%- else -%}
{%- assign page_suffix = '' -%}
{%- endif -%}
<title>{{ collection.title }}{{ page_suffix }} | {{ shop.name }}</title>
<meta name="description" content="{{ collection.description | strip_html | truncate: 155 }}{{ page_suffix }}">Ensure canonical on paginated pages points to self (not page 1)
Each paginated page's canonical should point to itself - /collections/shoes?page=2 should have canonical /collections/shoes?page=2. Do not canonicalize all paginated pages to page 1, as Google may then ignore page 2+ entirely.
{%- if current_page > 1 -%}
<link rel="canonical" href="{{ canonical_url }}?page={{ current_page }}">
{%- else -%}
<link rel="canonical" href="{{ canonical_url }}">
{%- endif -%}Add noindex to deep pagination pages with thin content
For stores with collections that extend to 5+ pages, consider adding noindex to pages beyond page 3. These pages typically contain low-demand products that aren't worth indexing.
{%- if current_page > 3 -%}
<meta name="robots" content="noindex, follow">
{%- endif -%}How SEOScan Detects This Issue
SEOScan detects paginated collection pages by identifying URLs with ?page= parameters. It checks whether: (1) the page title and meta description are identical to page 1, (2) the canonical is correct (self-referential, not pointing to page 1), and (3) deeper pagination pages have noindex if appropriate. Collections with more than 4 paginated pages are flagged for potential thin content on deeper pages.
Example Scan Result
Description
Collection /collections/clothing has 6 paginated pages. All 6 share identical title ("Clothing - Store Name") and meta description. Pages 4–6 have fewer than 12 products each. No noindex on deep pagination pages.
Impact
Google may de-prioritise paginated pages with duplicate metadata, potentially losing indexing on products only appearing on page 2+. Crawl budget spent on 5 near-duplicate pages.
Recommended Fix
Add current_page number to title and meta tags. Add noindex to pages beyond page 3 via meta robots tag. Ensure canonical is self-referential on each page.
Why It Matters for SEO
Crawl Budget Efficiency
Deep pagination pages consume crawl budget. For stores with large collections (100+ products), Google spending crawl budget on page 5 of a collection reduces crawling of important product and collection pages.
rel=next/prev is Deprecated - New Solution Required
Google deprecated rel=next/prev pagination signals in 2019. Stores still relying on this (or not having updated their approach) have no pagination SEO strategy at all - a common gap in Shopify documentation.
Products on Deep Pages May Not Get Indexed
If Google treats paginated pages as low-quality or thin, products only appearing on page 3+ of a collection may be crawled infrequently or not indexed - making them invisible in search.
Unique Metadata Signals Page Value
Adding page numbers to title tags ('Shoes - Page 2 - Store Name') signals to Google that each paginated page is intentionally distinct, improving how Google treats the pagination structure.
Real-World Validation Signals
- Google's John Mueller confirmed in 2019 that rel=next/prev is no longer used for pagination and that Google treats each paginated page individually - unique metadata and self-canonicals are the current best practice.
- Google Search Console data from large Shopify stores frequently shows paginated pages beyond page 3 being "Discovered - currently not indexed" or "Crawled - currently not indexed" - indicating Google is deprioritising them.
- Adding page numbers to collection title tags is one of the lowest-effort, highest-clarity signals you can add to help Google understand your pagination structure.
When this may not need fixing
If all your collections fit on a single page (fewer than 24-48 products depending on your pagination setting), this issue does not apply. Also, if Google Search Console shows your paginated pages have unique indexing and receive organic traffic, the current setup is working and changes may disrupt it.
Frequently Asked Questions
Q: Does Shopify handle pagination SEO automatically?
No - Shopify does not automatically differentiate title tags, meta descriptions, or handle pagination canonicals beyond outputting {{ canonical_url }} (which excludes the ?page= parameter on some themes). Pagination metadata differentiation requires theme customisation.
Q: Should I use rel=next/prev on my Shopify store?
No - Google deprecated rel=next/prev in 2019 and confirmed it no longer uses these signals. Adding them does no harm but provides no benefit. Focus on unique metadata per page and correct self-referential canonicals instead.
Q: Should paginated collection pages be noindexed?
It depends on depth. Page 2 and 3 of active collections often rank for specific product searches and should remain indexed with unique metadata. Pages 4+ often have thin product content and may benefit from noindex. Analyse Search Console traffic on your paginated pages before adding noindex.
Q: Can pagination cause a duplicate content penalty?
Google doesn't issue 'penalties' for duplicate content - but it may consolidate paginated pages into one representative URL, potentially excluding page 2+ from search results. Unique metadata and self-referential canonicals prevent this consolidation.
Check Your Store for This Issue
SEOScan automatically detects shopify pagination duplicate content: handling paginated collections and 3 related issues - with specific fixes for your store.
Run Free Scan