Blog / Technical SEO /
Pagination on WordPress and Shopify: what Google needs
Open almost any audit tool on a blog or an online store and you’ll see a cluster of warnings about pages ending in /page/2/ or ?page=3. Duplicate titles. Duplicate meta descriptions. “Thin content.” It looks like a mess, and the instinct is to tidy it away with a noindex or a canonical pointing at page one.
That instinct is usually wrong, and I’d resist it. Paginated pages aren’t a problem to hide. They’re the route Google takes to reach your older posts and your products further down a collection. Cut that route and those pages get crawled less, linked less and found less.
The short answer to what Google needs: real, crawlable links to each page in the series, each page canonicalised to itself, and nothing blocking them. The rest is detail.
What changed with rel=”next” and rel=”prev”
For years, the advice was to add rel="next" and rel="prev" tags so Google understood the pages were a series. In 2019 Google said it hadn’t used those tags for indexing for some time. It now works out the relationship from the links on the page.
You don’t need to remove the tags if your theme or SEO plugin still outputs them. Other search engines and browsers may still read them, and they do no harm. But they won’t save a pagination setup that’s broken in other ways, and adding them isn’t a fix for anything.
The three things that matter
1. Every page has a link Google can follow
Pagination only helps if Google can move from page one to page two to page ten using ordinary <a href> links. Things that get in the way:
- “Load more” buttons and infinite scroll with no fallback. If new items only appear after a click or a scroll triggered by JavaScript, Google may never see them. The fix is to make sure each batch also exists at its own URL (
/page/2/,?page=2) with a normal link to it. - Links that only work with JavaScript, such as a button with an
onclickinstead of anhref. - Pagination shown only on mobile or hidden behind a toggle that doesn’t render in the HTML.
My quick test: view the page source (not the inspector, the raw source) and search for page/2 or page=2. If it isn’t there as a link, Google probably isn’t following it either.
2. Each page canonicalises to itself
Page 2 is not a copy of page 1. It lists different posts or products. So the canonical tag on page 2 should point to page 2.
The common mistake is a canonical on every paginated page pointing back to page one. That tells Google “ignore this page, the real one is page one”. It may then pay less attention to the links on it, and those are exactly the links to your deeper content. I covered canonicals more generally in canonical tags explained with real examples.
There’s one exception worth knowing: a “view all” page. If you have a single page that shows everything and loads quickly, you can point the paginated pages at it. Most stores and blogs don’t have one that loads quickly, so this rarely applies.
3. Don’t noindex or block the series
Noindexing pages 2 onwards feels tidy. The risk is that Google gradually crawls a noindexed page less and may stop following its links. On a blog with hundreds of posts, or a collection with hundreds of products, that’s a lot of content relying on a weaker path. I wouldn’t take that bet to clear a few audit warnings.
Blocking paginated URLs in robots.txt is worse: Google can’t crawl them at all. If you’re unsure which tool does what, robots.txt and noindex: when to use which goes through it.
Will page 7 of your blog archive rank for anything? Almost certainly not, and it doesn’t need to. Its job is to be crawled so the posts it links to get found.
Pagination on WordPress
WordPress handles most of this out of the box. Blog, category, tag and author archives paginate at /page/2/, /page/3/ and so on, with ordinary links.
What to check:
- Your SEO plugin’s canonical output. Yoast and Rank Math both set self-referencing canonicals on paginated archives by default. If someone has customised this, check page 2’s source.
- “Noindex subpages of archives” settings. Some plugins have had an option like this over the years. Unless you have a specific reason, leave paginated archives indexable.
- Theme pagination. Some themes swap numbered links for a “load more” button. Check that the button is backed by a real URL, or switch to numbered pagination.
- Posts per page. Under Settings, Reading, the “Blog pages show at most” number decides how deep your archive goes. Ten posts per page on a site with 400 posts means 40 pages to click through. Raising it a little shortens the path, as long as pages stay fast.
Category and tag archives are where pagination adds up quickly. If you have dozens of tags with one or two posts each, that’s a separate problem, covered in WordPress categories and tags: an SEO-friendly setup.
Pagination on Shopify
Shopify collections paginate with a ?page=2 parameter, and the theme decides how many products appear per page and how the links look.
What to check:
- The canonical on
?page=2. Shopify themes normally output a canonical that includes the page parameter, which is what you want. Older or heavily customised themes sometimes strip it and point every page back to the main collection URL. View source on page 2 and look. - Infinite scroll and “load more” in the theme. Popular with stores because it feels smooth on a phone. Make sure the theme still renders normal pagination links in the HTML underneath.
- Products per page. Set in the theme’s collection settings. A collection of 300 products at 12 per page is 25 pages deep. More per page reduces depth, but every extra product card adds images, so balance it against speed.
- Filters and sorting on top of pagination.
?page=2&sort_by=price-ascendingmultiplies URLs fast. Shopify’s default robots.txt already blocks sort parameters on collections; that’s covered in faceted navigation and SEO for e-commerce.
On a store, pagination is also a hint about structure. If a collection runs to 20 pages, it might be doing too many jobs. Splitting it into sub-collections gives shoppers and Google shorter, more relevant lists.
What about duplicate titles?
Audit tools flag “Blog – Page 2” and “Blog – Page 3” as duplicate titles when the page number isn’t in the title. Minor, but easy to fix. Most SEO plugins add “Page 2 of 10” automatically, and on Shopify you can add the page number in theme.liquid with the current_page variable.
You don’t need unique descriptions or intro text on every paginated page. Many sites show the collection or category description on page one only, which is sensible.
A five-minute check
- Open your blog archive or largest collection and go to page 2.
- View source. Find the canonical tag. Does it point to page 2?
- Search the source for a link to page 3. Is it a normal
href? - Look for a
noindexin the robots meta tag. Is there one? - Paste the page 2 URL into the URL Inspection tool in Search Console and check it’s allowed to be crawled and indexed.
If all five look right, your pagination is doing its job. If one doesn’t, that’s your fix for this week.
Related reading
- Canonical tags explained with real examples
- Faceted navigation and SEO for e-commerce
- Crawl budget: does a small site need to care?
- WordPress categories and tags: an SEO-friendly setup
Go to page 2 of your biggest collection or archive now and view the source. What does the canonical say?