ShipworkSite inspection
Pagination

Crawlability

PaginationAre paginated pages set up right?Internal searchIs site search eating crawl budget?URL parametersAre parameters creating duplicates?Log analyserWhat does Googlebot actually crawl?Robots builderNeed a robots.txt file?Soft 404sAre pages “not found” but returning 200?JavaScriptCan crawlers see it without running JS?FreshnessIs my site quietly going stale?Robots.txtDoes robots.txt say what I think?

Indexing

Sitemap lastmodAre my sitemap dates valid?SitemapIs my sitemap actually fetchable?IndexingIs Google allowed to index my pages?CanonicalsIs Google indexing the wrong URL?Index signalsDo sitemap and index signals agree?Sitemap generatorNeed a sitemap.xml for my site?Bulk URL statusWhere does each of these URLs really land?Redirect builderNeed the redirect rules?RedirectsAre my URLs answering directly, over HTTPS?

On-page

Keyword ideasWhat are people searching for?SERP previewHow does my page look in Google?Content qualityAre your pages too thin or too alike?Image weightAre images slowing the page?CannibalizationAre pages competing with each other?On-page checkDoes the page use its target phrase?ImagesAre my images accessible and loading?Meta tag builderWhat should my title and share tags say?DuplicatesDo my pages compete for one query?

Links

Orphan pagesWhich pages can no link reach?Link graphHow deep do your pages sit?Anchor textDo links say what they point at?Outbound linksAre external links still alive?Broken linksAre internal links sending visitors nowhere?

Structured data

Rich resultsIs my markup eligible for a rich result?Structured dataIs my product schema valid?Schema coverageDo my key pages carry structured data?Social previewHow does my page look when shared?Schema vs pageDoes markup match the page price?Schema builderNeed valid JSON-LD?

International

Hreflang sitemapDo page and sitemap hreflang agree?HreflangDo my language versions link back?Hreflang builderNeed the hreflang tags?Page DoctorWhy is this page not doing well?Redirect planMy site has dead links — what redirects do I write?Sitemap diffIs anything missing from my sitemap?Robots simulatorWhat does my robots.txt actually block?Can Googlebot?Can Googlebot fetch this URL?
Every error, explainedGuides
Pricing Learn Error guides Run free audit

+1 free check

Welcome to Shipwork

Sign in free and your next check this month is on us.

Continue with GoogleContinue with email

We email you a 6-digit code. No password.

No card needed. Reports and watches follow you to any device.

Are your paginated pages set up correctly?

Paginated pages are easy to get wrong. Canonicalising page 2 to page 1 tells Google that page 2 does not exist, so the products or posts on it are never discovered through the sequence.

Reads the canonical and rel next/prev signals on a set of your pages. Saved to your account if you are signed in to a paid plan.

How this check works

Shipwork reads a set of your pages, identifies the paginated ones, and checks two signals: whether each paginated page canonicalises to itself (correct) or to a non-paginated URL (wrong), and whether it carries rel next/prev so crawlers can walk the sequence.

What the pagination SEO checker looks for

The pagination SEO checker looks for paginated URLs of the form ?page=2 or /page/2 among the pages it reads, the links on them, and any rel next or rel prev hints. It then inspects the canonical of each paginated page it actually fetched. If that canonical points to a version without a page number, it reports that the paginated page canonicalises to a non-paginated URL.

It also notes paginated pages that carry no rel next or rel prev. The free run reads a sample of up to 20 pages, and pagination is often absent from a sitemap, so the check also counts paginated links found on the home page as evidence that pagination is in use. Where no sampled page is itself paginated, it says the deeper checks could not run.

How to read a pagination finding

A pass means each paginated page the check read declared itself as its own canonical, which is the usual correct setup. A finding that page 2 canonicalises to page 1 is the classic mistake: it tells a search engine that page 2 is a duplicate of page 1, so the items listed only on page 2 may never be discovered through it.

A missing rel next or rel prev is reported as information, not an error. It is a hint that helps crawlers walk a sequence in order, and it is not a requirement. The check reads markup only, so it cannot confirm what a search engine ultimately indexed. Use it to catch the canonical error, not to certify a whole pagination system.

Common causes and why they matter

The wrong canonical usually comes from a theme or SEO add-on that applies one template rule to every listing page, including pages two and beyond. A store that canonicalises all collection pages to the first dumps the contents of later pages out of the index. Filtered and sorted views, which also look paginated, get caught by the same rule.

When page 2 and onward are treated as duplicates of page 1, products or articles that appear only deeper in the series lose their route into the index. The listing pages themselves also compete for one query instead of presenting a sequence. That is a discovery problem, and it can quietly cap how much of a large catalogue is found.

How to fix pagination signals

Each paginated page should point its canonical at itself, including the page number. Correct the template or the add-on that injects the canonical rather than editing a single page, then re-run the check. Keep rel next and rel prev if your platform already emits them; they make the sequence explicit for crawlers that read them.

Leave later pages out of the sitemap and list the first page instead, letting internal links lead a crawler through the series. If you use a store platform, check whether its listing template or an installed app is overriding the canonical, since that is the usual source of the error. Confirm the change on a live page two before assuming it is fixed.

When to use related checks

Use canonical check for canonical problems on other page types, and index signals when a URL in your sitemap is noindexed or canonicalised away. Both catch conflicts this pagination check does not.

The canonical tags guide explains how to choose the preferred URL for a set of versions. Pagination is one case of that decision; faceted navigation and tracking parameters are others, and each has a check that reads the signal it depends on.

Questions

Should page 2 canonicalise to page 1?
No. Each paginated page should canonicalise to itself. Pointing page 2 at page 1 tells Google page 2 does not exist, so its items are not discovered through it.
Do I need rel next/prev?
It is a hint Google no longer uses for indexing, but other crawlers still read it and it makes the sequence explicit. It does no harm.
Should paginated pages be in the sitemap?
Generally no: list the first page and let links lead the crawler through the rest. Listing every page of a long series wastes crawl budget.
Does Google use rel next and rel prev?
It is a hint that helps crawlers understand a sequence. It is not a requirement, and this check reports its absence as information rather than an error. Emitting it does no harm and can help crawlers that do read it.
How do I check pagination SEO on my site?
Run the check on your domain. It finds paginated URLs in the pages and links it reads, then inspects each paginated page's canonical and its rel next or rel prev. It reads a sample, so confirm the fix on a live page two afterwards.
Why does my paginated page show as canonicalising to the first page?
A theme or SEO add-on is likely applying one canonical rule to every listing page, including pages two and beyond. Correct that rule at its source, then re-run the check to confirm each paginated page now declares itself as canonical.

Keep reading

What this reads

  • Reads public pages from outside your network, the way a crawler does.
  • No signup, and nothing is stored on the free checks.
  • One of 83 checks across discovery, content, markup, trust and catalogue data.
83checks
0signups needed
0stored on free checks
Cool, just ran an audit and got some insights! Let’s see if I can fix them :)
Tenta Dev, @DevTenta
Whoah! this site is crazy, nothing to roast at all
Ainreek, @AinreekAI
cool as heck, tried it on my blog and the insights it gave are helpful and not bluff.
Refaat 🍉 (Mouse), @1Mouse__