A catalog is divided into pages—that’s pagination. The first catalog page is linked from the homepage, but there are no links beyond the fifth page. The last products exist at direct URLs and in the site’s address map (sitemap), but the navigation chain breaks. Check the entire path to the end, including links back and changes to the number of pages after the catalog is updated.
Follow the links from the first page
Google recommends accessible URLs and regular links for paginated lists. Official documentation.
Start from the first public catalog page, not from a known URL for the last page. Write down the available links forward and follow them until you reach the end. Note where the chain stops or repeats. Compare the actual number of pages with the number indicated by the catalog’s current inventory. If page=7 opens manually but cannot be reached through links, the products exist, but the navigation is broken. A sitemap can provide additional URLs, but this check is about the actual link chain and whether visitors can find the last products.
First, middle, and last pages of the list
| Catalog page | How to reach it | What to check | How to confirm it is accessible |
|---|---|---|---|
| First page | Entry point to the list | Check next | The next URL is accessible |
| Fifth page | Where the chain breaks | Check the conditions | There is a page after it |
| Last page | The end of the catalog | Check the products | The number of pages is correct |
| Direct page=7 | Separate set of products | Check the canonical URL | Not the first page |
Open page numbers directly
Check the href attributes of next, prev, and page-number links in the source HTML and the DOM. A button without a URL is not a confirmed link for crawling. Open several pages directly in a new session: each should return the corresponding list without first clicking “Load more.” Record the status and final URL. If a client-side router displays the seventh page but a direct server request returns the first, the issue goes beyond how pagination is displayed. The developer must fix how page is handled on the server: direct loads and on-site navigation must show the same page of the list.
In the inspector, select the “Next” link and run $0.getAttribute("href") in the Chrome console. The expected result is the URL of the next page, for example /catalog/?page=6. If it’s a button without an address, there is no regular link. Open /catalog/?page=7 directly: the products on the seventh page should load, and the canonical should point to the selected URL for that page.
Find the next-link boundary error
Suppose the catalog has seven pages, and the “Next” link is rendered only when current < 5. Follow regular links from the first through the fifth page, then open the sixth and seventh pages directly. If they contain the required products, the connection is missing, not the resource itself. Fix the boundary and repeat the entire path. Add a one-page catalog to ensure that next does not appear there by mistake. This test set checks the rule on minimal, medium, and long lists. If the next-link boundary is wrong, simply adding more page numbers is not enough: the chain will break again when the number of products changes.
Fix the page-count calculation
Check how the total number of pages is calculated, how the page parameter is parsed, and the range of page numbers displayed. The last link must point to the actual end, not a fixed value. After making a change, preserve regular href attributes and filter state. If the “Load more” button loads additional products, each page must still have a URL that can be opened directly. Regular links between pages make it possible to find products without using this action. Don’t add hidden links to thousands of nonexistent pages just to satisfy a report. The generator must use the catalog’s actual contents and handle page numbers beyond the end of the list correctly.
Reach the last product and go back
The sixth and seventh pages are reachable from the first page through regular href links, and the last product opens. There is no link at the end to a nonexistent eighth page, and prev works. Repeat the check on a phone and with a filter: the selected value should not reset.
Also read: Site architecture: URL silo structure and click depth and Sitemap.xml: a complete guide to creating and optimizing it for SEO. Site checks are available on the reChecker technical audit page.