Short answer: For most WooCommerce shops, numbered pagination on real URLs (/shop/page/2/, /shop/page/3/) is better than a Load More button. Every product page in the catalogue gets a crawlable address, shoppers can go back to where they were, the footer stays reachable, and each page can be cached. On a stationery store I replaced Load More with numbered pages and kept AJAX only for filters, where it actually helps.
What was wrong with Load More
The shop page showed the first batch of products with a Load More button underneath. It looked modern, but it caused problems you only notice after a while:
- Products deep in the catalogue had no page of their own. Load More fetched more products with JavaScript, without a new URL. A search engine that doesn't click buttons only sees the first batch. Google can render JavaScript, but it doesn't click "Load More," so products that only appear after a click are only found through other links.
- The back button lost the shopper's place. Someone clicks "Load More" four times, opens a product, presses Back, and lands at the top with the first batch again. On a phone, that's when people give up.
- The footer was hard to reach. Each click pushed it further down.
- Nothing to share. "Look at page 3 of the pencils" isn't possible when page 3 doesn't exist.
- Caching gets harder. Every Load More request is an AJAX call that runs PHP. Numbered pages are normal pages that a page cache can store.
What I built instead
Real URLs for every page
Each page of products has its own WordPress URL: /shop/page/2/, /product-category/pens/page/3/ and so on. Those are the URLs WooCommerce already supports. I didn't invent a new system; I stopped hiding the existing one.
The pagination shows the first page, the last page and the pages around the current one, with Prev and Next:
← Prev 1 … 4 5 6 … 31 Next →
Every number is a normal <a href> link to the real URL. Clicking it loads a normal page, so the browser history, the back button and caching all work the way people expect.
AJAX only when filters are active
The shop has filters for category, brand, colour, price and sort order. Reloading the whole page every time someone ticks a checkbox would feel slow, so filters use AJAX:
- No filter active: pagination links behave like normal links.
- A filter active: the same links are intercepted by JavaScript, and the next page of filtered results loads without a full reload.
That gives search engines and shoppers clean, crawlable pages for the main catalogue, and gives shoppers who are filtering a fast experience.
One product card, everywhere
The normal page and the AJAX response use the same PHP function to print a product card. That avoids a classic bug where filtered results look slightly different from the main grid, or miss the "Out of stock" label.
Site structure, on-page, and content strategy that compounds organic traffic.
Same number of products per page in both modes
The store shows 18 products per page. That number is set once and used by both the normal shop query (loop_shop_per_page) and the AJAX filter query. If they differ, page 2 in one mode doesn't match page 2 in the other, and products get skipped or repeated.
SEO details to get right
- Self-referencing canonicals.
/shop/page/2/should have a canonical tag pointing to itself, not to page 1. Pointing every page to page 1 tells Google to ignore the products on later pages. Yoast SEO and Rank Math do this correctly by default; check it if you use something custom. - Don't noindex paginated pages. People used to do this to "avoid duplicate content." For an online shop, it mainly hides products from discovery.
- Unique titles help. Many SEO plugins add "Page 2 of 31" to the title automatically. That makes each page distinct in search results.
- Print the links in the HTML if you can. In this build the pagination links use the real URLs, so Google, which renders JavaScript, can follow them. If you're building from scratch, rendering the links on the server is the safer choice for crawlers that don't run JavaScript.
When infinite scroll or Load More is fine
Load More makes sense when you also keep paginated URLs underneath. Some themes update the URL to /page/2/ as the next batch loads, so every state can still be bookmarked and crawled. It's also fine for content that doesn't need to rank, like a feed of reviews.
If you're choosing between a plain Load More button with no URLs and numbered pagination, choose pagination.
FAQ
Is Load More bad for SEO?
A Load More button that fetches products with JavaScript and no new URL can stop search engines from finding products beyond the first batch. If each batch also has its own crawlable URL, the SEO impact is much smaller.
Should WooCommerce paginated pages be noindexed?
Usually not. Paginated shop and category pages help search engines discover products. Give each page a self-referencing canonical and let it be indexed.
How many products per page should a WooCommerce shop show?
Most shops use 12 to 24. Use a number that fills complete rows on desktop and loads quickly on mobile. This store uses 18, which divides evenly into rows of 2, 3 and 6.
Can I use AJAX filters and normal pagination together?
Yes. Use normal links for unfiltered browsing and switch to AJAX only when a filter is active. Keep the same products-per-page number in both modes so the pages line up.
From a live rebuild of a Bangladeshi stationery store's shop page. For more on keeping that shop fast, see how to cache WooCommerce without breaking the cart. Want a technical SEO review of your own catalogue? See my SEO service.
Full-funnel campaign management, from setup to scaling spend profitably.

