WordPress Pagination Not Working? 11 Fixes That Work

A laptop showing a plain blog page with numbered page links at the bottom — wordpress pagination not working guide
Pagination splits a long post list into numbered pages, so a fault on page two usually means a permalink, query, or template problem — not missing posts.

Page one of your blog loads perfectly. Page two returns a 404 error, shows the same posts again, or shows nothing at all. When wordpress pagination not working traps readers on the first page, most of your content becomes unreachable by browsing, and search engines may stop at page one too. The posts are safe. The links between pages, or the query behind them, are broken.

This guide works through the causes in order, from stale permalink rules to a custom query that ignores the page number. Test in a private browser window after each fix, so a cached copy never fools you, and take a backup before the deeper template fixes. Work through the fixes one at a time, clicking through to page two after each one.

Table of Contents

  • Why This Error Happens
  • Quick Checks
  • Diagnosing the Problem
  • Fix 1: Flush Permalinks and Test Page Two Directly
  • Fix 2: Check the Reading Setting for Posts Per Page
  • Fix 3: Clear Caches and Test Without a Caching Plugin
  • Fix 4: Test with a Default Theme to Rule Out the Template
  • Fix 5: Deactivate Plugins That Change Queries or Archives
  • Fix 6: Fix a Static Front Page with a Custom Posts Page
  • Fix 7: Check Custom Post Type and Custom Query Settings
  • Fix 8: Fix Pagination on a Page That Uses a Custom Query
  • Fix 9: Check the Category and Tag Base Settings
  • Fix 10: Fix Conflicts with Infinite Scroll and AJAX Loading
  • Fix 11: Rebuild the Archive Template and Reset the Query
  • What to Avoid
  • Frequently Asked Questions
  • Conclusion
  • Helpful Official Resources

Why This Error Happens

Pagination works in three steps: WordPress reads the page number from the address, asks the database for that slice of posts, and the theme prints the page links. If the address rules are stale, the query ignores the page number, or the theme prints the wrong links, page two fails while page one works. These are the breaks that happen most often.

1. Stale Permalink Rules Reject Page Two Addresses

Page two lives at an address like /page/2/, and WordPress needs a rewrite rule to recognise it. When the rules go stale — after a migration, a settings change, or a plugin that registers addresses — page one loads but page two returns a 404. The posts exist, the links are correct, and only the address lookup fails. This is the most common single cause.

2. The Posts-Per-Page Setting Disagrees with the Query

The Reading setting decides how many posts each page holds. If a theme option, a plugin, or a custom query sets a different number, WordPress can calculate the wrong number of pages — or decide there is no page two at all. The mismatch shows as missing page links, a 404 on the last page, or the same posts repeated on every page.

3. A Cache Serves Page One for Every Page Number

Caching plugins and server caches can mistake paged addresses for the same page, especially when the cache is set to ignore the page number. Visitors click to page two and receive a saved copy of page one, or a saved 404 from before the fix. The live query works, but nobody sees it. This cause survives every settings change until the cache is purged and its rules corrected.

4. A Plugin Rewrites the Archive Query

Plugins that filter archives, add custom sorting, or replace the main query can drop the page number from the request. The query then returns the first slice of posts for every page, or no posts at all for page two. The fault starts the day the plugin is installed or updated, and it affects every paged listing the plugin touches.

5. The Theme Template Ignores the Page Number

A theme template that runs its own query without reading the current page number will always show the first posts. A template that prints pagination links for the wrong query will link to pages that do not exist. Both faults survive cache clears and permalink flushes, because the data and the addresses are fine — only the template logic is wrong.

6. A Static Front Page Confuses the Page Number

When a static page is the homepage and another page shows the posts, WordPress uses two different page-number signals, and themes sometimes read the wrong one. The posts page then paginates incorrectly: page two 404s, repeats page one, or shows the static page again. This cause appears only on sites with a static front page, which is why it hides from the usual checks.

Quick Checks

Two minutes before the deep fixes.

  • Open page two directly — type /page/2/ after the blog address and press Enter.
  • Note what page two shows: a 404 error, the same posts as page one, or an empty page.
  • Check whether pagination fails on every listing or only one archive.
  • Open page two in a private browser window — does it behave differently?
  • Check whether the fault started after a migration, a plugin update, or a theme change.
  • Count your published posts and divide by the posts-per-page setting — should page two exist at all?

Diagnosing the Problem

SymptomCauseGo to Fix
Page two returns a 404 errorStale permalink rulesFix 1
No page links appear at allPosts-per-page setting too highFix 2
Page two shows page one postsCache serving the same pageFix 3
Same posts on every pageTheme query ignoring page numberFix 4
Fault started after a plugin updatePlugin rewriting the queryFix 5
Fault only on the posts pageStatic front page confusionFix 6
Fault only on a custom post typeCustom query or rewrite faultFix 7
Page links jump or load oddlyInfinite scroll or AJAX conflictFix 10

Fix 1: Flush Permalinks and Test Page Two Directly

Stale rewrite rules are the most common cause, and flushing them takes under a minute. Saving the permalink settings rebuilds the rules, including the rule that recognises /page/2/. Test the address directly afterwards, so you judge the live rules and not a cached link.

A laptop showing a plain settings screen with a save button — wordpress pagination not working guide
Saving the permalink settings rebuilds the address rules, including the rule that recognises page two.
  1. Go to Settings, then Permalinks, in the dashboard.
  2. Note which structure is selected, but do not change it.
  3. Click Save Changes at the bottom of the page.
  4. Wait for the confirmation message that the settings were saved.
  5. Open a private browser window and go to the blog page.
  6. Add /page/2/ to the blog address and press Enter.
  7. Check that page two loads with the next set of posts.
  • If page two still 404s, do the stronger flush: switch temporarily to Plain, save, then switch back to your structure and save again. The double rebuild clears rules that a single save leaves behind.
  • If 404 errors affect single posts as well as paged pages, our guide to WordPress 404 error fix covers the wider 404 checks.
  • A flush that restores page two proves the rules, not the content, were the fault — and it is the fix to repeat after every migration.

Fix 2: Check the Reading Setting for Posts Per Page

The Reading setting decides how many posts each page holds, and therefore how many pages exist. A value higher than your total post count means there is no page two to show, and a value changed by a theme option can disagree with the number the template expects. Check the setting before you chase a fault that does not exist.

  1. Go to Settings, then Reading, in the dashboard.
  2. Read the Blog pages show at most number.
  3. Count your published posts in Posts, then All Posts.
  4. Divide the post count by the per-page number — the result is the page count.
  5. If the result is one page or fewer, pagination correctly shows nothing.
  6. Lower the per-page number to 10 if you want more pages for testing.
  7. Click Save Changes and check the blog page for page links.
  • A per-page value of zero or a blank value can empty every listing, so treat any odd value with suspicion. Theme options can override this setting for archives — if the dashboard value looks right but the page shows a different count, check the theme’s archive or blog settings next.
  • Note the original value before you change it, so you can restore the site’s intended page size.
  • When the page count maths says page two should exist but the links do not appear, the theme or a plugin is suppressing them, and Fixes 4 and 5 chase that down.

Fix 3: Clear Caches and Test Without a Caching Plugin

A cache that ignores the page number serves the same saved page for every address. Clearing every cache layer, and briefly testing with the caching plugin off, separates a cache fault from a query fault. Test in a private window throughout, so the browser cache never interferes.

  1. Open page two in a private window and note what it shows.
  2. Purge the cache from your caching plugin’s menu or toolbar button.
  3. Purge the server or host cache from the hosting control panel, if one exists.
  4. Purge the content delivery network cache, if the site uses one.
  5. Hard-refresh the private window and open page two again.
  6. If page two still repeats page one, deactivate the caching plugin temporarily.
  7. Test page two again with the plugin off, then reactivate it.
  • If page two works with the caching plugin off, the plugin’s settings are the fault — look for an option that caches paged addresses separately, or excludes /page/ addresses from the cache. Some plugins cache the first page aggressively and need the paged addresses added to an exclusion list.
  • When cached pages keep returning after purges, our guide to WordPress cache not clearing covers the stubborn-cache checks.
  • A page two that works uncached proves the query is healthy and the cache rules need correcting.

Fix 4: Test with a Default Theme to Rule Out the Template

The theme prints the page links and runs the archive query. A template that ignores the page number, or prints links for the wrong query, breaks pagination while everything else works. A brief switch to a default theme proves whether the theme or the data is at fault.

  1. Go to Appearance, then Themes, in the dashboard.
  2. Activate a default theme, such as Twenty Twenty-Four or Twenty Twenty-Five.
  3. Open the blog page in a private window and click to page two.
  4. If page two works, the old theme’s template is the fault.
  5. Switch back to your theme and check its blog and archive settings.
  6. Look for a custom archive template, a builder template, or a pagination option.
  7. Fix or remove the faulty template setting, then test page two again.
  • Switching themes does not delete content, and your theme’s settings return when you switch back — but note customiser choices first, just in case. In a block theme, check the Archive and Blog Home templates in the Site Editor for a query block with pagination enabled; a query block without its pagination block shows no page links.
  • In a classic theme, a custom archive file that builds its own query without the page number is the usual culprit.
  • A default theme that paginates correctly proves the data and addresses are healthy.

Fix 5: Deactivate Plugins That Change Queries or Archives

Plugins that filter, sort, or replace archive queries can drop the page number from the request. The fault starts with an install or an update, and it affects every listing the plugin touches. Deactivating suspects one at a time finds the culprit without losing settings.

  1. Note which plugins were installed or updated just before the fault started.
  2. Go to Plugins, then Installed Plugins, in the dashboard.
  3. Deactivate the most recent suspect plugin first.
  4. Open page two in a private window and check whether it loads correctly.
  5. If nothing changes, reactivate the plugin and try the next suspect.
  6. When page two works, you have found the culprit — check its settings for a query or archive option.
  7. Leave the culprit deactivated, or reconfigure it, before you move on.
  • Test archive-filtering, custom-sorting, and content-restriction plugins first, because they rewrite queries by design. SEO and redirection plugins come next, because they can intercept paged addresses before WordPress sees them.
  • Deactivate one plugin at a time — bulk deactivation tells you a plugin is at fault but not which one. If conflicts keep recurring across the site, our guide to WordPress plugin conflict fix covers the systematic isolation method.
  • A wordpress pagination not working fault that vanishes with one plugin deactivated has named its own culprit.

Fix 6: Fix a Static Front Page with a Custom Posts Page

A static front page with a separate posts page uses two different page-number signals, and themes sometimes read the wrong one. The posts page then fails to paginate: page two 404s, repeats page one, or shows the homepage content. Checking the Reading assignment and the theme’s handling of it resolves the confusion.

A laptop showing a plain homepage layout beside a blog listing layout — wordpress pagination not working guide
A static homepage and a separate posts page use different page signals, and a theme that reads the wrong one breaks page two.
  1. Go to Settings, then Reading, in the dashboard.
  2. Confirm A static page is selected, with distinct Homepage and Posts page choices.
  3. Confirm the two dropdowns do not name the same page.
  4. Click Save Changes, then flush permalinks as in Fix 1.
  5. Open the posts page in a private window and click to page two.
  6. If page two fails, check the theme’s posts-page template for a custom query.
  7. Remove or correct the custom query so the main query handles the listing.
  • The posts page must be an empty page — any content typed into it is ignored, because the theme’s blog template takes over. A page builder template assigned to the posts page is a common trap: the builder’s own query ignores the page number, while the theme’s template would have handled it correctly.
  • If the site has no static front page, this fix does not apply — skip to Fix 7.
  • A posts page that paginates after the template correction proves the assignment was fine and the display logic was wrong.

Fix 7: Check Custom Post Type and Custom Query Settings

Custom post types and custom queries carry their own rewrite rules and pagination logic. A post type registered without archive support, or a custom query that sets its own post count, can break pagination for that listing while ordinary posts paginate fine. Check the registration and the query together.

  1. Confirm the fault affects a custom post type, not ordinary posts.
  2. Check the post type’s settings for an archive slug and rewrite rules.
  3. Flush permalinks after any change to the post type settings.
  4. Open the post type archive in a private window and test page two.
  5. Check any code snippet or plugin that modifies the query for that post type.
  6. Look for a hardcoded post count that disagrees with the Reading setting.
  7. Correct the count or remove the override, then test page two again.
  • A post type with archives disabled shows no listing at all, which looks like a pagination fault when only page one was ever linked. A custom query with a fixed post count is subtler: WordPress calculates the page count from one number and fetches posts with another, so the last page 404s or repeats.
  • Keep the query’s post count in step with the Reading setting, or leave the count unset so the main query decides.
  • If the fault affects ordinary posts too, the cause is site-wide — return to Fixes 1, 3, and 5 rather than chasing the post type.

Fix 8: Fix Pagination on a Page That Uses a Custom Query

A page that lists posts with a custom query — from a builder, a shortcode, or a code snippet — must read the current page number and pass it to the query. A custom query that forgets the page number always returns the first slice of posts. The fix is to make the query page-aware, or to let the main query do the listing instead.

A laptop showing a plain page editor with a list of posts — wordpress pagination not working guide
A custom query that never reads the page number always returns the first posts — the query must be page-aware.
  1. Identify the page whose listing fails to paginate.
  2. Open the page in the editor and find the query block, shortcode, or builder module.
  3. Check whether the query has a pagination setting, and turn it on if present.
  4. For a code snippet, check that it reads the current page number from the address.
  5. Confirm the snippet passes that page number into the query arguments.
  6. Save the page, clear the cache, and test page two in a private window.
  7. If the snippet cannot be made page-aware, replace it with the theme’s archive template.
  • Builder query modules usually carry a pagination toggle that is easy to miss — it sits in the module settings, not on the page. Shortcodes sometimes need a pagination attribute added by hand; check the shortcode’s documentation for the exact attribute.
  • Code snippets are the riskiest: a snippet copied from a tutorial may work on the homepage and fail on a page, because the two contexts expose the page number differently.
  • When in doubt, prefer the theme’s own archive template over a hand-built query — it handles pagination correctly by default.

Fix 9: Check the Category and Tag Base Settings

The category base and tag base are the prefixes in archive addresses, such as /category/ and /tag/. Changing or removing them alters the rewrite rules for every archive, and a bad base can break paged archive addresses while single posts keep working. Check the bases on the Permalinks screen before you rebuild anything.

  1. Go to Settings, then Permalinks, in the dashboard.
  2. Scroll to the Optional section at the bottom.
  3. Read the Category base and Tag base fields.
  4. If a base was changed recently, note the old value before touching it.
  5. Restore the default bases — category and tag — for testing.
  6. Click Save Changes to flush the rules with the restored bases.
  7. Open a category archive in a private window and test page two.
  • Removing the category base entirely requires a plugin or code, and a half-removed base is a classic source of paged-archive 404s. If the site relies on custom bases, restore them one at a time after the test, flushing permalinks after each change, so a bad base is caught individually.
  • A category archive that paginates with default bases but not with custom ones has named the faulty base.
  • If permalink structures cause 404s more widely, our guide to WordPress permalink structure causing 404 covers the deeper structure checks.

Fix 10: Fix Conflicts with Infinite Scroll and AJAX Loading

Infinite scroll and AJAX “load more” features replace numbered pagination with automatic loading. When they conflict with the theme’s pagination — or when they are half-configured — the page links can vanish, jump, or load the wrong posts. The fix is to choose one navigation method and disable the other cleanly.

  1. Check the theme options for an infinite scroll or AJAX loading setting.
  2. Check for a plugin that adds infinite scroll or “load more” buttons.
  3. Turn the infinite scroll feature off temporarily.
  4. Clear the cache and open the blog page in a private window.
  5. Check that numbered page links appear and that page two loads correctly.
  6. If you want infinite scroll, re-enable it and check its pagination fallback setting.
  7. Keep only one method active — numbered links or infinite scroll, never both fighting.
  • The conflict shows in several ways: page links that disappear when scrolling starts, “load more” buttons that fetch the same posts repeatedly, or page-two addresses that 404 because the feature rewrote the links. A feature that loads more posts must still respect the page count — one that ignores it will loop forever or stop early.
  • Test with the browser’s JavaScript console open if you are comfortable: script errors on scroll point at the conflicting code.
  • A clean choice between the two methods ends the fight permanently.

Fix 11: Rebuild the Archive Template and Reset the Query

If every other fix fails, the archive template itself may carry a damaged query or a stale builder layout that no setting can reach. Rebuilding the template from the theme default, and resetting any query modifications, gives pagination a clean foundation. Take a backup before this fix, and note the current template settings.

  1. Take a full backup of the site before you start.
  2. In a block theme, open the Site Editor, then Templates, then Archive.
  3. Check the template for a query block with pagination enabled.
  4. If the template looks damaged, reset it to the theme default or rebuild the query block.
  5. In a classic theme, check the archive file in a child theme for a custom query.
  6. Remove the custom query so the main query handles the archive.
  7. Clear the cache, flush permalinks, and test page two in a private window.
  • Rebuilding is a last resort because it discards customisations, but a template that cannot paginate is already broken — the rebuild restores the working default. In a block theme, the Archive template needs a query block, a post template inside it, and a pagination block after it; any missing piece breaks the listing.
  • In a classic theme, the main query already knows the page number, so a custom query is usually unnecessary — removing it is the fix, not a loss.
  • A rebuilt template that paginates proves the old layout, not the data, was the fault.
A laptop showing a clean blog listing with numbered page links — wordpress pagination not working guide
A rebuilt archive template with a working query block restores page links that no setting could reach.

What to Avoid

  • Do not change the permalink structure to “fix” pagination — flush the rules first, and only change the structure deliberately.
  • Do not set the posts-per-page value to zero or leave it blank — it can empty every listing on the site.
  • Do not run infinite scroll and numbered pagination together — choose one method and disable the other.
  • Do not copy a custom query snippet without checking it reads the page number — a query that ignores paging always shows page one.
  • Do not bulk-deactivate every plugin at once — deactivate one at a time so you learn which one caused the fault.
  • Do not use pirated themes, plugins, activators, or cracks — they can inject code that breaks archives and invites malware.
  • Do not judge the fix in a normal browser window — test page two in a private window so a cached copy never fools you.

Frequently Asked Questions

Why does page one work but page two return a 404?

Because page two needs a rewrite rule that page one does not. Stale permalink rules recognise the blog address but not the /page/2/ address, so page two falls through to a 404. Flushing the permalinks, as Fix 1 describes, rebuilds the rule and restores page two.

Why does page two show the same posts as page one?

Because something ignores the page number: a cache serving the same saved page, a theme query that never reads the page number, or a plugin that rewrites the query without it. Test with the cache off first, then with a default theme, to separate the three causes.

Why are there no page links at all?

Either there is only one page of posts at the current posts-per-page setting, or the template has no pagination block. Check the maths in Fix 2 first — divide the post count by the per-page number. If more than one page should exist, check the template for its pagination block or links.

What is the wordpress pagination not working fix for a static front page?

Confirm the Homepage and Posts page are distinct pages in Settings, then Reading, flush the permalinks, and check the posts-page template for a custom query that reads the wrong page signal. The posts page must be an empty page handled by the theme’s blog template, not a builder page with its own query.

Can a caching plugin break pagination?

Yes, when it caches paged addresses as if they were the same page. The fix is to purge the cache, confirm page two works with the plugin off, and then correct the plugin’s settings so paged addresses are cached separately or excluded. Never leave the plugin off permanently just to fix pagination — correct its rules instead.

Will switching themes delete my content?

No. Switching themes does not delete posts, pages, categories, or media. Menus and widget placements may need reassigning, and customiser settings are theme-specific, so note them before you switch. The default-theme test in Fix 4 is safe, and switching back restores your theme exactly as it was.

Conclusion

When wordpress pagination not working strands readers on page one, the fault is usually stale permalink rules, a posts-per-page mismatch, a cache that ignores page numbers, or a query that never reads the page number. Flush the permalinks, check the reading setting, clear every cache, and test the theme and plugins one at a time. Finish by clicking through to page two, page three, and back in a private window, because working page links on the live site are the only proof that counts. Keep one navigation method, one post count, and fresh rewrite rules, and readers will reach every page you publish.

Helpful Official Resources

Leave a Reply

Your email address will not be published. Required fields are marked *