SaaS SEO · Technical SEO
SEO pagination: Google's rules and errors on a SaaS site
SEO pagination is splitting a long list into successive pages, each with its own URL, so Google can crawl and index every listed item. Google asks for only three things: link pages together with real a href links, give each page a unique URL with its own canonical, and avoid indexing sort and filter variants. On a SaaS site, the stakes are the blog, the integrations library, templates and the help centre.
Franck Gordi
· 8 min read
Href links
Unique URLs
Canonical per page
Key takeaways
- Googlebot follows URLs found in the href attribute of a elements: it does not click a "Load more" button or trigger infinite scroll.
- Google no longer uses rel="next" and rel="prev" tags, although other search engines may still use them.
- Each paginated page needs its own URL and its own canonical: Google advises against canonicalising the whole sequence to page 1.
- Pages in the same paginated sequence can share the same title and meta description, according to Google's documentation.
- Google ignores URL fragments: a page number placed after a # can stop Googlebot from following the link.
Why does pagination matter for SaaS SEO?
Because a page reachable only from page 4 of a list exists for Google only if page 4 is crawlable. Google's documentation on pagination and incremental page loading starts from this point: showing a subset of results improves performance, but you must make sure the crawler finds all the content.
On a SaaS site, long lists are everywhere: blog archives, integrations directory, template gallery, case studies, help centre articles, customer reviews. These are often the pages carrying the long tail. Poorly implemented pagination does not trigger a penalty: it simply makes those pages invisible or hard to discover.
Pagination, "Load more" or infinite scroll: which to choose?
Google leaves the user experience choice to you, provided the crawler can find every item. It compares the three patterns itself.
Display patterns
Three patterns, one crawling constraint
- Numbered pagination
- Tells users the result size and their position. Each page is a distinct URL, the simplest format to make crawlable.
- "Load more" button
- A single page for all content, but Google doesn't click buttons. A crawlable link is needed alongside it.
- Infinite scroll
- Intuitive, but can cause scrolling fatigue and can't handle very large volumes. Same crawlable-link requirement.
- Shared constraint
- Items loaded after the first view must stay reachable through URLs linked with a href, or through a sitemap.
Google's three rules for crawlable pagination
Link pages sequentially
Each page must contain an a href link to the next page. Google also suggests linking every page in the collection back to the first one, hinting that page 1 is probably the best landing page. Links generated only by a JavaScript click handler don't count: Google's JavaScript SEO basics state that links must be crawlable.
Use URLs correctly
One unique URL per page, for example with a ?page=2 parameter, because Google treats each page of a sequence as a separate page. Each page declares its own canonical. No page number in a # fragment, which Google ignores.
Avoid indexing sorts and filters
The same list sorted by date, popularity or filtered by category produces near-identical URLs. Google recommends blocking their indexing with the noindex robots meta tag, or discouraging their crawling through robots.txt.
The most common pagination errors
Diagnosis
Four errors, four fixes
- Canonical to page 1
- Pages 2 onward ask Google to ignore them. Fix: a self-referencing canonical on each page.
- Following pages set to noindex
- A widespread practice that is absent from Google's pagination guidance, which reserves noindex for sorts and filters.
- JavaScript-only links
- Buttons or onClick without href. Fix: real a href links to each page, even if the interface stays dynamic.
- # fragment as page number
- Googlebot may treat the page as already retrieved. Fix: a ?page=n parameter or a /page/n path.
A canonical pointing to page 1 is the costliest error, as it directly contradicts Google's guidance. The mechanism is detailed in our article on the canonical tag. On a site producing many list URLs, pagination also interacts with crawl budget, and its depth should be planned with internal linking: an important page should not depend only on page 7.
What to do with rel="next" and rel="prev"?
Nothing urgent. Google says it no longer uses them, but notes other search engines may still do so. Keeping them does no harm; adding them never replaces visible a href links in the page, which remain the only signal Google follows to discover next pages.
How to check pagination before release?
- Rendered code: each page contains an a href link to the next one, visible without interaction.
- URLs: one parameter or path per page, no # fragment.
- Canonical: each page declares itself, never page 1.
- Variants: sorts and filters set to noindex or excluded from crawling.
- Search Console: URL Inspection on an item listed on the last page confirms it is discovered and indexed.
If whole sections of your library stay undiscoverable, the cause usually sits in the template, not a single page. A technical SEO project on crawling and indexing fixes the template, and an SEO audit that prioritises bottlenecks tells you whether the issue deserves attention before the others.
Frequently asked questions about SEO pagination
Does Google still use rel="next" and rel="prev"?
No. Google says it used these link elements in the past to identify next and previous pages, but no longer uses them. Other search engines may still use them, so keeping them causes no harm.
Should page 1 be the canonical for every paginated page?
No. Google explicitly says not to use the first page of a paginated sequence as the canonical page, and to give each page its own canonical URL. Otherwise items listed on page 2 and beyond may no longer be discovered.
Do paginated pages need different titles?
Not necessarily. Google usually recommends distinct titles, but states that pages in a paginated sequence can share the same title and description, because it tries to recognise pages in a sequence.
Is a "Load more" button SEO-friendly?
Only if a crawlable link exists as well. Google's crawlers don't click buttons and generally don't trigger JavaScript functions that require user actions. Content loaded on click must remain reachable through a URL linked with a href.
Can I use #page=2 in the URL?
No. Google ignores fragment identifiers, the text after the #. If the next-page URL only differs by its fragment, Googlebot may not follow it, thinking it already retrieved the page. A parameter such as ?page=2 works.
What about sorting and filters on a paginated list?
Google advises avoiding the indexing of sort and filter variants, such as ?order=price, either with the noindex robots meta tag or by discouraging crawling of those URL patterns in robots.txt.
Sources and scope
Documentation accessed October 1, 2026. This article relies on Google's public guidance; it presents no client case and no measured gain.
About the author

Franck Gordi
Independent SEO and GEO consultant for B2B SaaS. He helps software companies become visible on Google and cited by AI engines.
LinkedIn →