Pagination SEO: How to Set It Up for Category Pages

What is pagination and why does it matter for SEO?

Pagination is the practice of splitting a long list of products, posts or results across several pages. For SEO, every page in the series needs its own crawlable URL and correct signals. Get it wrong, and Google never reaches your deeper products, so your rankings suffer.

Picture a category with 400 products. Also, showing them all on one page makes the page slow. So you split them into groups of 24 or 48. However, that split also draws a map for search engines.

In technical audits, our team sees pagination mistakes all the time. For example, Google never indexes the products after page two. Moreover, nobody notices for years, because the home page and the first category page look fine.

In this guide we walk through each pagination decision: Google's current position, canonicals, infinite scroll, filters and audit steps. We also recommend reading our post on category structure for large websites alongside it.

Does Google still use rel=next and rel=prev?

No. Google's official documentation states that it no longer uses these tags. They once described the relationship between pages in a series. Today Google works out those links with its own systems, so it does not need the markup.

You can read the source in Google Search Central's guide to pagination and incremental page loading. In addition, the deprecation is stated there in plain words.

Should you delete the tags? Not necessarily. They do no harm, but they bring no benefit either. So skip the cleanup project and spend your time on the work below.

• Give every page a unique, clean URL.
• Link pages to each other with real anchor elements that carry an href.
• Give every page its own canonical URL.
• Keep filter combinations under control.

One note: other search engines may read signals differently. Moreover, that means you should check your target markets before you remove the tags. On a Google-focused site, though, the list above is your priority order.

How does each paginated page get its own URL?

Every page needs a separate URL that returns the same content when you type it into a browser. Also, the most common pattern is a query parameter such as ?page=2. Alternatively, you can use path-based URLs like /category/page/2/. Google accepts both.

The key rule is this: do not use a fragment (#) for page numbers. According to Google's documentation, Google ignores fragment identifiers. In addition, if the next page link differs only after the hash, Googlebot may not follow it.

Our team treats these URL rules as a standard:

• The first page lives at one address only, such as /category/. You never serve it a second time at ?page=1.
• Numbers are sequential and predictable: 2, 3, 4.
• A page number that does not exist returns a 404, not an empty list with a 200.
• Uppercase letters, session IDs and stray parameters stay out of the URL.

The list looks simple. Yet if ?page=1 and the main address both return a 200, you create duplicate content. Moreover, you can test your redirects with our redirect checker.

How do you set up canonical tags for pagination?

Each paginated URL should point to itself as the canonical. In other words, page two carries a canonical pointing to page two. Google's guidance also tells you not to use the first page as the canonical for the whole series. Each page holds its own items, so each needs its own identity.

For example, the head of page two contains this line:

<link rel="canonical" href="https://example.com/shoes/?page=2">

The key reference is Google's guide to consolidating duplicate URLs. It also explains that a canonical is a hint, not a command. So it must not conflict with other signals, such as internal links and sitemaps.

Our team checks three things. First, the canonical must be an absolute URL. Second, the protocol and host must be correct on parameter URLs. Third, the canonical must point to a page that really returns a 200.

Why is canonicalizing every paginated URL to page one a mistake?

Google treats the canonical page as the main version and folds the others into it. Also, if most products sit on pages two and three, those products are absent from page one's content. As a result, Google may struggle to discover them.

This mistake is common on plugin-driven sites. An SEO plugin writes page one as the canonical for every paginated URL by default. Worse, nobody reviews that setting after installation.

You can test your own site in a few minutes:

1. Open page two of your category in a browser.
2. Search the page source for the word canonical.
3. If the address points to page one instead of page two, fix the setting.
4. Use the URL Inspection tool in Google Search Console to see which canonical Google picked.

This takes about ten minutes. In our experience, the usual result is that deep products get discovered again. For help with a full technical review, see our SEO consulting page.

How should you write pagination links for Googlebot?

Pagination links must be real anchor elements with an href. Google's link guidance says it can reliably crawl only a elements that carry an href attribute. Buttons, spans and links that work only through a JavaScript click handler can cause problems.

You can use the crawlable links documentation as your source. The guidance also says Google cannot reliably parse javascript: URLs.

Modern frameworks make this mistake easy. A developer wires the next button to an onclick handler. Everything works for users, but Googlebot never reaches page two.

• Write next and previous links as plain HTML links.
• Keep the page numbers (1, 2, 3 and the last page) visible on screen.
• Use meaningful link text. If you only show an arrow icon, add an accessible label.
• If JavaScript adds the links after load, verify that they exist in the rendered HTML.

So the issue is the markup, not the look. Once the markup is right, you can style the design however you like.

How does infinite scroll affect SEO?

Infinite scroll loads new content automatically as the user scrolls down. In addition, it can feel pleasant for users. However, search engines do not scroll. They see only the content from the first load and the links in the HTML. Left alone, deep content stays undiscovered.

Google's documentation accepts infinite scroll as a valid user experience. It also notes that an unclear result size can cause "scrolling fatigue."

The way to make infinite scroll SEO-friendly is to build a paginated structure underneath. For example, the address bar updates to ?page=2 as the user scrolls. When someone opens that address directly, they get the content of page two.

Three rules matter in this approach:

• Each content segment has its own URL that opens directly.
• Each page returns real content from the server, or through pre-rendering.
• Page links exist at the bottom and work even with JavaScript off.

Reaching the footer is another problem with infinite scroll. Moreover, users may never find your contact details. Therefore, a sticky footer or a load more button should be a real part of the design.

Should you use a load more button or numbered pagination?

Both have a place. According to Google's documentation, a load more pattern keeps content on one page and can show the total result count. However, it cannot handle very large result sets. Also, numbered pagination scales, and each page becomes its own target.

For users, the difference is clear. Load more feels smooth on mobile. Numbered pagination, on the other hand, gives people a sense of position. Returning to the same spot with the back button is also much easier.

In practice, our team suggests a hybrid model. In addition, the user loads more products with a button, but behind the button sits a real href and a separate URL. This way, users get a smooth flow and Googlebot finds the pages through links.

With JavaScript off, the button works like a normal link. In addition, you update the address bar as new products arrive. In short, experience and crawlability do not have to be alternatives.

Which pagination method should you choose, and when?

The choice depends on content volume, device usage and your team's technical capacity. Moreover, the table below compares four common methods from an SEO point of view. Keep in mind that the ratings are a general framework based on field experience, not a guarantee.

Read the table like this: as risk grows, link and URL discipline matters more. For example, with bare infinite scroll, skipping the three rules above leaves deep content invisible.

How should pagination work on ecommerce category pages?

In ecommerce, pagination means product discovery and the spread of internal link value. Also, every product needs at least one crawlable path. On pages two, three and beyond, the product links must exist as real HTML.

A category page is also a search result target. When a user types "women's running shoes," they usually land on page one. So page one carries the competitive signals. Later pages, in contrast, work for product discovery.

We recommend these practices:

• Show the category description only on page one. Do not repeat it on other pages.
• Keep your best sellers and in-stock products on page one.
• Keep the number of products per page fixed, so it does not change on every visit.
• Move out-of-stock links to the end of the series, or remove them.
• For full product page detail, see our ecommerce product page guide.

You can also find this topic in our wider ecommerce SEO for product and category pages post. As a store grows, plan category architecture and pagination together.

How do filters and sort parameters interact with pagination?

Filters (color, size, price) and sort parameters multiply your URL count once they combine with pagination. For example, 10 filter values across 5 pages can create hundreds of new URLs. In addition, most of them do not deserve a place in search results, and they drain crawl resources.

To keep unwanted variations out of the index, Google recommends the noindex robots meta tag. Moreover, that advice fits filter pages and alternative sort orders in particular. However, if a filter has real search demand, such as "black running shoes," you can choose to leave that page indexable on purpose.

Ask these questions to decide:

• Do people actually search for this filter combination?
• Does the page have its own title and a unique product list?
• Is the number of combinations manageable?

If all three answers are yes, treat the page like a landing page. Also, if not, limit it with noindex or robots.txt. To edit robots.txt, our robots.txt generator makes the job easier.

How do you write titles, descriptions and content on paginated pages?

Each paginated URL needs a unique title and description. Adding the page number to the end of the title is a fair start, for example "Running Shoes, Page 2." This way you avoid the same title repeating in search results.

The bigger topic is content, though. In addition, if the category description repeats on page two, Google sees the same text on dozens of pages. Therefore, we suggest keeping the long description on page one only.

• Title: the main category name plus the page number.
• Meta description: write it differently from page one, or leave it blank and let Google choose.
• H1: the category name can stay the same. Do not add the page number to the H1.
• Images: use meaningful alt text for each product.

You can check title length and appearance with our Google SERP preview tool. To generate all tags in one place, the meta tag generator helps.

How do pagination and internal linking affect each other?

Pagination is part of your internal link structure. Through page numbers, products sit at a certain click depth from the main category. Moreover, the longer the path to deep products, the later and less often Google reaches them.

That is why a single next link is not enough on a ten-page category. Also, users and bots need ten clicks to get from page one to page ten. Showing some of the page numbers on the first page cuts that depth.

These solutions reduce depth:

• Show the first page, the last page and the numbers around the current page in the pagination bar.
• Spread product links across subcategories and brand pages.
• Link popular products straight from the home page or a category showcase.
• Link to the relevant category from blog posts.

Our internal linking strategy guide covers the wider logic. In addition, pagination is not a rule. It is depth management.

How many products should you show per page?

There is no single right number. Page speed, mobile usage and product variety decide it. Moreover, showing too few products raises the page count and click depth. Showing too many makes the page heavy, and your Core Web Vitals may suffer.

Example calculation: if a category has 480 products and you show 24 per page, you get 20 pages. Also, if you show 48 per page, you get 10 pages. This is only an example calculation. Test results should make the real call.

Our approach is simple. First we measure the current page speed. Then we look at the weight of product images. After that, we compare two product counts with an A/B test. So the decision rests on data, not assumptions.

Note: Google does not recommend a fixed number of products. Be careful with "ideal number" claims that circulate online.

Should paginated pages go into the sitemap?

That depends on your site architecture. Google has no official requirement here. As a team, we always include the first page in the sitemap. For deeper pages, we prefer to list the products themselves rather than the paginated lists.

The reasoning is this: a sitemap tells Google which URLs matter. In addition, if product pages already sit in the sitemap, your reliance on deep pagination links drops. This way, Google finds products by two routes.

Keep these points in mind when you build a sitemap:

• Include only URLs that return a 200 and canonicalize to themselves.
• Leave out redirected and noindex URLs.
• Update the date only when the content really changes.

For sitemap work, see our XML sitemap generator and our post on the sitemap lastmod tag.

How does pagination affect crawl budget?

If you set up pagination carelessly, Googlebot spends limited crawl resources on low-value pages. Parameter combinations, empty pages and repeated lists eat those resources. On large sites, this can delay the discovery of new products.

Crawl budget is rarely a problem for small sites. For a store with tens of thousands of products, though, the picture changes. Moreover, that is why you should keep the pagination and filter structure clean from the start.

Look at these signals to spot crawl problems:

• The share of parameter URLs in Search Console crawl stats.
• The number of pages in the "Crawled, currently not indexed" status.
• The URLs Googlebot visits most in your server logs.

We explained why crawl behavior changes in our post on why Googlebot crawls less. For products that never get indexed, read it together with our technical SEO tips.

How does pagination affect speed and Core Web Vitals?

Pagination directly sets page weight. Also, the more products and images on a page, the longer it takes to load. With infinite scroll and load more patterns, the risk of layout shift (CLS) and interaction delay (INP) also grows.

If the page jumps while new products load, users tap the wrong thing. So reserve the height of product cards in advance. Also set width and height values for images.

• Load images in the first screen right away, and lazy load the ones below.
• Serve images in a modern format and at the right size.
• Do not block the main thread for long while new products load.

For details, see our posts on what Core Web Vitals are and what lazy loading is. Above all, do not lazy load the first product image.

How does pagination work for mobile users?

On mobile, pagination has to work for fingers. Tiny page numbers cause mis-taps. So make link areas large enough and leave space between the numbers. Google uses mobile-first indexing, so the link structure in your mobile version directly affects your rankings.

Hiding the desktop page links on mobile is a common mistake. For example, a design team removes page numbers from the mobile layout and keeps only a load more button. In addition, if no real link sits behind that button, Googlebot cannot reach page two on mobile.

• Keep the same pagination links in the mobile and desktop versions.
• Make tap targets large enough.
• Keep the user's position while new products load.
• Return users to the same product spot when they press the back button.

Most sites skip the last item. Moreover, if users jump back to the top of the list after viewing a product, your pagination fails on experience. In short, technical correctness and ease of use both affect conversions.

How do you read pagination data in Search Console?

Search Console shows pagination problems only indirectly. There is no dedicated pagination report. Instead, you read the page indexing report, URL Inspection and crawl stats together. Also, this tells you whether deep pages are discovered and indexed.

First, paste the second and third URLs of a category into URL Inspection. Look at the canonical Google selected. In addition, if it differs from the one you wrote, your canonical signals conflict.

1. Open the "Not indexed" section of the page indexing report.
2. Filter for parameter URLs and check their status.
3. Test a deep product URL with URL Inspection.
4. Check the share of parameter requests in crawl stats.

If you see many deep products that are discovered but not indexed, review your pagination links and internal link depth. However, not every unindexed page is an error. Moreover, you leave some URLs out on purpose.

How should pagination work on blog and archive pages?

On blogs, pagination decides how easily people find older posts. New posts appear on page one and drift to pages two and three over time. Without pagination links, older posts are found only through the sitemap or internal links.

Here, our team suggests linking every post from its related category and tag pages as well. In addition, you can keep important older posts near the first pages by linking to them from new posts. Also, this way you do not depend on pagination alone.

• Use a self-referencing canonical on category archives.
• Limit date archives and thin tag pages.
• Link important posts to their related category.

When you think about blog architecture in general, look at our SEO category posts as an example. In addition, each post links to a category and a few related posts.

What are the most common pagination mistakes?

The mistakes we meet most often come from small settings and stay hidden for a long time. Moreover, the table below shows each mistake with its symptom and fix. This list reflects our audit experience, not statistics.

Most of these mistakes show up together. For example, a plugin breaks the canonical, and the theme ties the next button to JavaScript. So audit the whole setup, not single items.

How do you audit pagination step by step?

You do not need an expensive tool for the audit. A browser, Search Console and a crawler are usually enough. Also, the sequence below is the short routine our team uses.

1. Open pages two and three of a category and confirm that the URLs are unique.
2. Read the canonical in the page source and make sure it points to the page itself.
3. Turn JavaScript off and test whether the next page links remain visible.
4. Crawl the site and check how many clicks it takes to reach the last pages.
5. Use URL Inspection in Search Console to see whether a deep product is indexed.
6. Type a page number that does not exist and confirm that the server returns a 404.

These six steps catch most problems. Moreover, if you repeat them regularly, you spot regressions from new releases early.

What should your pre-launch pagination checklist include?

A pre-launch checklist keeps mistakes from reaching production. In addition, you can share the items below with your development team. All of them rest on Google's official guidance, and you can adapt them to your site.

• Every page has a unique URL without a #.
• The first page lives at one address, and ?page=1 redirects to it.
• Every page shows its own canonical.
• Next and previous links are real a elements with an href.
• Page titles differ by page number.
• Filter and sort variations are under control.
• If infinite scroll exists, page links sit at the bottom.
• Page speed and layout shift have been measured.

Once you build this list, you reuse it for every new category. So pagination becomes a lasting standard rather than a one-time project.

One last warning: do not expect results right after you change pagination settings. Google needs time to reprocess new canonical and link signals. Therefore, watch the page indexing report and crawl stats for a few weeks, and avoid changing too many things at once.

How does our team work on pagination projects?

At Talha Aslan and team, we treat pagination as part of site architecture, not as a stand-alone topic. First we scan the current state. Then we produce a prioritized fix list. Moreover, your developers can apply that list directly.

Our workflow is short. In step one, we review crawl and index data. Next, we audit canonical, link and filter rules. Finally, we prioritize the fixes and track the results.

If you work in ecommerce, see our ecommerce consulting page. For the technical foundation, see our SEO consulting page. Also, if you want a deeper review, get in touch.