Your Canonical Is Probably Right And Page Two Is Still Unreachable

If your catalogue runs past one page, SEO pagination comes down to two settings on page two. What its canonical points at, and whether Google can reach it by following a link.

So I went looking for how often the second one is wrong. Asking 28 Shopify storefronts for page two on 4th August 2026 got me 19 usable listings, and the split across them was lopsided: 12 had the canonical right, 8 had a link Googlebot could follow.

I'm John Butterworth. I founded Mint SEO in Manchester and I've spent 11+ years in SEO, most of it on collection pages, which is where pagination either helps a catalogue rank or caps how much of it Google ever sees.

Here is what to set, what to leave alone, and how to check your own catalogue in about five minutes.

The Pagination Setup That Decides The Outcome

Two settings in SEO pagination decide how a paginated sequence performs. Each page has to state which URL owns the content listed on it, and each page has to offer a route onward that a crawler can follow without running JavaScript.

Get both right and the rest is detail.

A Self Referencing Canonical On Every Page

Google's ecommerce pagination guidance is explicit about this: "Don't use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL." Page two owns the products listed on page two, so page two is what its canonical should point at.

That prevents one specific failure. When page two canonicalises back to page one, you are telling Google that the products listed on it belong to a URL that does not list them.

Two stores in my sample do exactly that. On Ruggable, page two canonicalises back to page one and exposes no crawlable link onward, so the 50 products listed there are attributed to a page that has never shown them. On Vuori, page two canonicalises to the homepage, which tells Google the products on it belong to a page that lists no products at all.

Those products are still sitting on the pages either way. Google is just being told to credit them somewhere else.

A Crawlable Link Between The Pages

The second setting is the one stores miss. Google's crawlable links guidance is direct about what qualifies:

Generally, Google can only crawl your link if it's an <a> HTML element with an href attribute.

Shopify tells merchants the same thing in its own pagination guidance:

Make sure each page is linked using a standard href attribute or anchor tag (<a href="…">) so Google can crawl the following page.

A button that loads more products doesn't qualify.

Neither does a click handler on a div.

On the Shopify audits I run, the pagination finding that changes rankings is almost never the canonical tag. It is that the theme renders the next-page control with JavaScript, so nothing past page one is reachable by link.

Google's pagination guidance says the same about the sequence specifically: "Include links from each page to the following page using <a href> tags. This can help Googlebot find subsequent pages." Themes still ship the button instead.

How Google Handles Pagination Now

Google treats paginated pages as ordinary pages.

There is no special handling to configure and no pagination-specific signal to send. The whole topic reduces to how the pages are tagged and how they are linked.

John Mueller of Google put the reassuring version of this to a thread asking what to do after the announcement: "The good part about all of this is that if pagination has worked for your site in the past, it'll continue to work in the same way." Nothing that was working needed changing.

Two tactics from the older documentation are still in circulation. Google no longer reads either one, so adding them changes nothing about how your paginated pages are crawled or indexed.

The Tags Google Stopped Using

These tags have done nothing for Google since 2019. On 21st March 2019 Google confirmed it had stopped using rel=next and rel=prev to consolidate indexing properties across a paginated set, and had not been using them for years. Kristina Azarenko, an ecommerce SEO consultant who covered the announcement as it landed, recorded Google's own explanation:

We noticed that we weren't using rel-next/prev in indexing for a number of years now, so we thought we might as well remove the docs.

You don't need to strip the markup out if it's already there. Her practical read was that "there's no need to remove these tags from your pages as other search engines like Bing still support them", and that still holds: the tags are inert for Google and harmless everywhere else.

Second on the list is the URL Parameters tool, which has been gone from Search Console since 2022. Guidance telling you to configure pagination parameters there is pointing at a screen that no longer exists, so any setup built around it stopped doing anything years ago.

Both of these matter for the same reason. Time spent maintaining either one is time not spent on the anchor link that decides whether page two gets crawled.

Use Your Pagination URLs Correctly

Every page in the sequence needs its own crawlable URL.

Every one of the 19 storefronts served a working ?page=2 URL, so not one of them had a URL problem at all. On Shopify the platform generates that parameter for you, which leaves the theme as the only place the sequence can break.

Google's wording on the URL itself is "Give each page a unique URL. For example, include a ?page=n query parameter, as URLs in a paginated sequence are treated as separate pages."

The URLs worth keeping out of the index are not those page numbers. They are the filtered and sorted variants. Google's instruction there is to "avoid indexing variations of the same list of results", blocking them with a noindex robots meta tag or discouraging the crawl in robots.txt.

A collection with four filters and three sort orders multiplies into combinations that list the same products in a different order. Those are what bloat an index. A plain numbered sequence does not behave that way.

Unique titles per page are worth the effort too. We append the page number on the catalogues we run, which stops page two competing with page one on an identical title string.

Duplicate Content And Indexing Across A Paginated Set

Leave the pages indexable. This is the question practitioners get stuck on, and in my experience it is the easiest of the three to get wrong in an expensive direction.

That is because noindexing page two feels tidy while costing you discovery. Deeper products are often listed nowhere else on the site, so suppressing the pages that list them is how a catalogue ends up with products Google has never seen.

Almost nobody does it any more. Across the 19 storefronts I crawled on 4th August 2026, one of the 19 storefronts applied a noindex tag to page two, and that was Allbirds. Its page two carries a self-referencing canonical and a crawlable page link, and is the only page in the sample serving a noindex tag.

Duplicate-content fear drives that instinct, and it does not survive scrutiny. Page two lists entirely different products from page one.

Once its canonical points at itself, nothing is left for Google to treat as a copy.

Pagination Or Infinite Scroll

Infinite scroll costs you rankings when it replaces the crawlable URL. It doesn't when it sits on top of one.

Shopify puts that mechanism in a single line:

Google can crawl, but it doesn't scroll, which means it can't access content unless it can click a link, so there's a good chance that most infinite scroll content won't get indexed.

ColourPop shows the version of it I meet most often. Its page two self-canonicalises but replaces its pagination links with a load-more control, so there is no anchor for Googlebot to follow.

So build both. Render the numbered URLs server-side so they exist in the HTML, then layer the scrolling behaviour over them for people. Your customers keep the experience they came for and Google keeps the route.

Seven of the 19 offered neither a crawlable pagination link nor a load-more control on page two. For those, there is no route onward at all.

Paginate Or Offer One Long Page

How deep any single sequence runs matters more than whether you paginate. A sequence running to hundreds of pages buries its own tail, which is a reason to lift the products-per-page value.

Page size is a theme setting almost nobody revisits after launch. Page two carried as few as 8 products on Allbirds and as many as 94 on Peet's Coffee.

That range is the difference between a sequence ending in a few clicks and one running for dozens of pages. What the depth does to shoppers is a conversion question we cover in our CRO framework guide.

One long page has a ceiling of its own, and it is a byte count. Gary Illyes, who works on crawling at Google, explained Googlebot's fetching architecture in March 2026:

If your HTML file is larger than 2MB, Googlebot doesn't reject the page. Instead, it stops the fetch exactly at the 2MB cutoff.

That downloaded portion is then passed to indexing "as if it were the complete file". Anything past the cutoff is never fetched or rendered.

This isn't theoretical for catalogue pages. Of the nine storefronts I could fetch without a browser, one served a page two of 4.67 MB of raw HTML, more than twice what Googlebot takes per URL. Pagination links sit at the bottom of a listing.

Common Pagination Mistakes, Measured On 19 Live Storefronts

Nine of the 28 storefronts I approached refused the request or served no listing, so every count below describes the 19 that answered. Those 19 were asked for /collections/all?page=2 through a headless browser on 4th August 2026, and for each one I read the canonical target, the meta robots tag, the product links and whether any route onward was a crawlable HTML anchor.

Of the 19 storefronts I checked on 4th August 2026, 12 served a self-referencing canonical on page two of their full catalogue. The canonical is the setting every guide leads with, so finding it correct on nearly two thirds of the sample was the expected result.

Only 8 of those 19 storefronts exposed a crawlable HTML link from page two to another page in the sequence. Fewer than half give Googlebot a route past the first screen of products.

Those two groups overlap less than you would expect. Five of the 12 storefronts that got the canonical right still exposed no crawlable link to another page in the sequence.

That is the whole finding in one number, because the tag and the link are not the same job. Fixing a canonical is a one-line theme edit, while the link depends on how the collection template was built. Every store named here is linked. Peet's Coffee is the sharpest case, where page two self-canonicalises across 94 product links and exposes no crawlable link to any other page.

Kylie Cosmetics, at the other end of the sample, shows what the fix looks like in place. Its page two self-canonicalises and exposes 21 crawlable page links, so Googlebot can walk the sequence from any point in it, while Hiut Denim inverts the common failure with a crawlable page link and no canonical tag at all.

Check The Canonical, The Link And The Robots Tag On Page Two

Three checks settle whether your catalogue has an SEO pagination problem, and all three are visible in the page source without a crawler.

Load page two of your largest collection and view source. The canonical should contain page=2, and the meta robots tag should not say noindex.

Then search the source for page=3 and confirm it appears inside an <a href> rather than inside a script or a button. If it only appears inside JavaScript, Googlebot has no route to page three and the rest of your sequence is reachable only by sitemap.

If that third check fails, it is your issue whatever the first two say. It is also the first thing on my ecommerce SEO checklist for a catalogue.

When Pagination Costs You Crawl Budget

Google's crawl budget documentation was last updated on 22nd July 2026, and two lines in it changed how I explain this to clients.

Every site starts with the same default, conservative crawl capacity limit.

Capacity isn't something a large site is granted and a small one is denied. The second line matters more for pagination:

While each crawler has a different crawl demand, the crawl capacity limit is shared across all crawlers. This means that high demand from one crawler can reduce the capacity available for others.

Read that against a deep paginated sequence and every page-number URL is drawing on the same allowance as your product pages, now shared with crawlers that are not Googlebot.

Volume is rarely what decides it, though. Google aims that guide at "Large sites (1 million+ unique pages) with content that changes moderately often (once a week)". For most catalogues the cost shows up as allocation instead, and allocation follows internal linking. A crawl-log audit posted to r/TechSEO on 1st May 2026 by u/jetsash showed it on a 400-page ecommerce site:

Googlebot was crawling paginated archive pages, tag pages with near-duplicate content, and old blog posts with zero backlinks, multiple times per week. The 12 main category pages that drive 80% of revenue? Crawled roughly once every 3 weeks.

Nothing in that log is really about pagination. The archives were simply better linked than the categories, and rebalancing that is ecommerce SEO strategy work.

Get Your Paginated Pages Checked Properly

Five stores in my sample had the canonical right and no way onward, and all five look perfectly healthy to anyone clicking through them in a browser.

Nothing on the front end shows it, so it survives every round of manual checking. An internal linking map we built for BedShelfie across products, collections and blog content was the same class of work, and that 12-week campaign ended with a 256% increase in Google Search sales.

Our SEO audit treats the crawl path through your collections as one part of a system, which is what we mean by eight disciplines and one job.

You see what Googlebot reaches, what it spends its allowance on, and which templates hold products back.

Page-two reachability is one of the first things we check on a catalogue. Get your SEO audit.

Pagination Questions Worth Short Answers

Say the canonical, the link and the robots tag all check out and the collection pages still underperform. That leaves SEO pagination in the clear.

The collection page design and structure is where I would look next.

The other two candidates are how well those category templates convert and whether the pages match what people search for at all. Both are covered in our guide to ecommerce conversion rate work.