Field guide · technical workflow
Make page two of a WooCommerce category discoverable
A shop category may use Load More controls, infinite scroll or numbered pages. Whichever interface looks best, important products should remain reachable through stable addresses and accessible navigation. Page-one performance alone cannot prove product discovery.
Who this is for: Help a WooCommerce store owner diagnose product listing pagination when navigation and crawler-visible links disagree.
Editorial preview — facts, worked examples and publication approval are still being checked.
The practical problem
A practical make page two of a woocommerce category discoverable exercise: Load the category's second page directly and verify products and URL differ. The outcome is a documented decision backed by inspect canonical and internal-link consistency across representative pages. The final check is to test later product navigation on mobile with minimal JavaScript.
What you will be able to check
- Load the category's second page directly and verify products and URL differ.
- Inspect canonical and internal-link consistency across representative pages.
- Test later product navigation on mobile with minimal JavaScript.
Reproducible scenario
Worked example: Make page two of a WooCommerce category discoverable
A fictional WooCommerce apparel category lists 180 items and shows 24 at a time. Its theme replaces numbered links with a Load More button that works after JavaScript executes. On direct access to /product-category/shirts/page/2/, the server unexpectedly returns the first set of products. The site looks fine during a casual shopping session, but the testable concern is whether later products have stable discovery routes.
Starting assumptions
- The category legitimately contains multiple pages of distinct purchasable items.
- A tester can compare direct server responses and customer navigation both with and without enhancement scripts.
Decisions and checks
Inspect a later category address without a previous user session
Load page two directly, record response code and compare products against page one. A unique-looking URL that renders the same list does not establish independent pagination. Extract actual product links from raw HTML.
What to verify: A direct page-two request returns the intended distinct product set and accessible product detail links.
Separate primary pagination from sorting and filters
Assess whether page-two canonicals and sitemap decisions match the distinct product list. A price-sorted page-two state can be transient and should not automatically become another indexable category. Record each URL class separately.
What to verify: A written rule for meaningful pagination addresses and temporary presentation variants with no contradictory canonical signals.
Test the mobile Load More or page-navigation control against linked fallback routes
Use keyboard and narrow viewport testing to verify later items remain reachable. Revisit the same sample after a theme update because client-side rendering can alter HTML links without warning.
What to verify: Before/after mobile evidence and crawl records show real products remain discoverable beyond the first listing page.
Expected output: The deliverable is a category pagination acceptance test with direct URL evidence and a verified route to deeper products. The result may be to repair a template link, route handler or canonical strategy. It is not a promise that every page of product listings should be independently indexed.
This woocommerce category pagination audit scenario is illustrative; no real WooCommerce customer result or tested store is implied.
Open a later page directly
Select a category containing multiple pages and open the second page URL directly. Record the actual product set and response; a URL that renders the same products as page one is not a useful pagination path. Check that HTML links expose subsequent listing pages.
Reference: official · 2026-11-07
Review canonical signals against product sets
Google's ecommerce URL guidance recommends unique URLs for pagination and consistent canonical signals. Distinguish truly duplicated sorting/filter URLs from pages containing new products. Do not automatically canonicalise every later page to page one or make every navigation permutation indexable.
Reference: official · 2026-11-07
Include mobile and no-JavaScript checks
Test keyboard labels, mobile controls and product detail links on later listing pages. Re-crawl after a theme or pagination plugin update. The practical acceptance result is stable access to the inventory, not a dashboard claim of higher crawl budget.
Reference: official · 2026-11-07
Decision aid
Decision table: WooCommerce category pagination: SEO tests
| Observed page behaviour | Decision to consider | Verification evidence |
|---|---|---|
| Page two serves different products at a stable URL | Preserve crawlable pagination links even if the visual UI uses infinite scroll. | Compare HTML product identifiers and canonical responses. |
| Page two URL repeats the exact first-page assortment | Investigate routing or caching before approving indexing for that address. | Save raw request and product list diff with a developer owner. |
| Sort or stock parameter changes only order or availability state | Use a separate crawl/index decision rather than making every permutation canonical. | Inspect real URL variations and shopper behaviour. |
What a passing test looks like
These checks describe the evidence that should exist after a real implementation. They are not reports of tests already completed on a customer website.
Inspect a later category address without a previous user session
Expected result: A direct page-two request returns the intended distinct product set and accessible product detail links.
Keep as evidence: Save a dated, source-specific HTTP and rendered-product record with an assigned reviewer for inspect a later category address without a previous user session.
Separate primary pagination from sorting and filters
Expected result: A written rule for meaningful pagination addresses and temporary presentation variants with no contradictory canonical signals.
Keep as evidence: Save a dated, source-specific HTTP and rendered-product record with an assigned reviewer for separate primary pagination from sorting and filters.
Test the mobile Load More or page-navigation control against linked fallback routes
Expected result: Before/after mobile evidence and crawl records show real products remain discoverable beyond the first listing page.
Keep as evidence: Save a dated, source-specific HTTP and rendered-product record with an assigned reviewer for test the mobile load more or page-navigation control against linked fallback routes.
Scope and limitations
The stock and page-size values are illustrative. WooCommerce theme, block setup, third-party filters, caches and custom pagination can differ. Google can process some JavaScript, but this exercise tests directly accessible paths to reduce ambiguity. Always verify the real application and customer journey.
Sources and verification
These references explain documented technical behaviour. The worked decisions are illustrative until checked on your own installation.
- official reference — Google recommends a distinct URL for each pagination page and consistent use of canonical paths across links and sitemaps. Recorded: 2026-11-07