# SEO pagination: connecting a paged catalog

> Build a sequence of distinct URLs and crawlable links without canonicalizing every catalog page to the first one.


**Pagination splits a collection into pages with their own addresses.** For SEO, search engines need to discover those links and access each part’s content. A button that changes the screen does not, by itself, establish a crawlable route to the next products.

Google recommends [distinct URLs and sequential links](https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading). Pages in a sequence contain different parts of the collection; they should not all be declared duplicates of page one.

## Page two contains different mugs

In this fictional example, a shop shows some mugs first and provides the rest at `/shop/mugs/?page=2`. The team had copied the canonical URL for `/shop/mugs/` onto that second page.

The decision is to give page two its own canonical and link to it from page one. Product-page links need to work as well. This fragment represents part of page one’s HTML:

```html
<nav aria-label="Catalog pages">
<a href="/shop/mugs/?page=2">Mugs, page 2</a>
</nav>
```

Page two declares its own address:

```html
<link rel="canonical"
  href="https://example.com/shop/mugs/?page=2" />
```

The domain is illustrative. In an actual implementation, check that the address delivers the second page’s products and that previous and following links represent the sequence correctly.

## “Load more” can coexist with accessible pages

An interface can append products without reloading the entire screen. Beneath that experience, there should be a way to reach each part through URLs and links the crawler can follow. Google explains that it does not interact with buttons to trigger loading as a person would.

A simple check is to open page two’s address directly in a new session. If it always returns the first products and changes only after a click, the parameter does not yet represent the promised state. Examine the HTML response and rendering; the [JavaScript SEO article](/en/guides/javascript-seo/) helps distinguish those results.

Do not rely exclusively on `#page=2` to represent another indexable page: Google generally does not use fragments to discover different content that way. A collection state needs an address the server and search engine can interpret.

## Pagination and filters answer different questions

`?page=2` moves to other products in the same collection. `?sort=price` may reorganize the same products. Separating those effects helps prevent a sorting rule from removing access to later pages. [Faceted navigation](/en/guides/faceted-navigation-seo/) covers that classification.

Google no longer uses `rel="next"` and `rel="prev"` tags to identify these relationships. Adding them does not replace visible, crawlable links or establish the correct canonical.

## Test the entire route

Start at the category, open page two and reach a product that did not appear on page one. Return to the catalog and check that the navigation retains an understandable state. Then verify that canonical URLs return their corresponding content. That route can expose a defect that a review of the shop’s first screen would miss.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
