Pagination problems in WordPress can make archive pages, blog indexes, category listings, and custom post type archives difficult to browse. You may see page 2 returning a 404 error, repeated posts on every page, broken next and previous links, or pagination that simply does not appear. The good news is that most WordPress pagination issues come from a small set of causes and can be fixed with a methodical approach.
In this guide, you will learn how WordPress pagination works, what commonly breaks it, and the exact steps to troubleshoot archive and blog page pagination issues without guesswork.
How WordPress pagination works
WordPress uses query variables to determine which page of results should be displayed. On blog and archive views, the most important variable is usually paged. If the query is correct and your permalink structure is working, WordPress can generate URLs such as /page/2/ and load the next set of posts.
Pagination can break when a theme uses a custom query incorrectly, when permalink rules are outdated, when a plugin changes the main query unexpectedly, or when the wrong query variable is used. In some cases, server caching or SEO plugins can also interfere with paged archive URLs.
Before changing code, identify the exact symptom:
- Page 2 or higher returns a 404 error
- Pagination links appear, but every page shows the same posts
- Pagination links are missing entirely
- Category, tag, author, or date archives paginate incorrectly
- A custom blog page works on page 1 but breaks on deeper pages
Common causes of WordPress pagination issues
Permalink settings need to be refreshed
One of the most common reasons for broken pagination is stale rewrite rules. This often happens after changing themes, adding custom post types, or modifying archive settings.
To refresh permalinks, go to Settings and then Permalinks in your WordPress dashboard. Click Save Changes without changing anything. This flushes rewrite rules and often restores archive pagination immediately.
The wrong query variable is being used
On archive and blog pages, WordPress usually expects the paged variable. Developers sometimes use page instead, which is meant for paginated single posts or static pages in different contexts. If your template uses a custom WP_Query, make sure it passes the correct paged value.
A common logic pattern is to retrieve the current page from the query and pass it into the custom loop. If this is missed, every paginated URL may load page 1 content.
A custom query is replacing the main query
Many pagination issues start when a theme template creates a custom query for the blog or archive page instead of letting WordPress handle the main query. If pagination is tied to a secondary query but the links are generated from the main one, page counts and URLs can become inconsistent.
Whenever possible, modify the main query with appropriate hooks rather than replacing it in the template. This is especially important for category archives, tag archives, author pages, and the default posts page.
Incorrect use of pre_get_posts
The pre_get_posts hook is useful, but if it is applied too broadly it can affect admin screens, feeds, search results, or unrelated archive pages. If a function changes posts per page or query parameters without checking for the main query and the correct context, pagination can fail.
Make sure query modifications are limited to the intended front-end archive. For example, changes should usually target the main query and exclude the admin area.
Static front page and posts page configuration
If your site uses a static homepage and a separate posts page, pagination behavior depends on proper reading settings. A mismatch between the assigned posts page and a custom template can lead to broken paged URLs.
Check Settings and then Reading to confirm that your homepage and posts page are configured correctly. If your blog page is assigned in settings, avoid overriding it with a conflicting custom query unless absolutely necessary.
Plugin or theme conflicts
SEO plugins, cache plugins, redirection tools, and page builders can all interfere with archive pagination. Some plugins alter canonical URLs, rewrite requests, or cache page 1 and serve it for deeper paginated pages.
Switch temporarily to a default WordPress theme and deactivate plugins one by one to isolate the conflict. If pagination starts working, reactivate components gradually until the issue returns.
Step-by-step troubleshooting process
1. Test your permalink structure
Visit a broken paginated URL directly, such as /blog/page/2/ or /category/news/page/2/. If it returns a 404, save permalinks again first. If the problem remains, check whether your server supports rewrites correctly and whether your site is using the expected permalink format.
2. Confirm the correct page variable
If your theme uses a custom loop, verify that the current page number is being read correctly. Archive pagination usually depends on paged. If the query does not receive the current page value, WordPress will keep showing the first set of posts.
3. Check posts per page settings
Go to Settings and then Reading and review the number of posts shown at most. Then compare that with any custom code or plugin settings that alter posts per page. Conflicting values can create strange page counts or empty final pages.
4. Inspect theme archive templates
Review files such as home.php, archive.php, category.php, index.php, or custom templates used for the blog page. Look for custom WP_Query instances, hard-coded page numbers, or pagination functions tied to the wrong query object.
If a custom query is necessary, ensure the pagination function references that query and that the current paged value is passed into it.
5. Review pre_get_posts customizations
If your site uses custom functions to alter archives, inspect them carefully. Confirm they target only the main front-end query and only the intended archive type. Broad conditions often cause pagination bugs that affect multiple sections of a site.
6. Rule out plugin conflicts
Temporarily disable caching, SEO, redirection, and archive-related plugins. Then test pagination again. If the issue disappears, clear all caches and review plugin settings related to canonical URLs, redirects, and archive indexing.
7. Clear all caches
Even after fixing the root cause, stale caches may continue serving broken paginated pages. Clear your WordPress cache plugin, server cache, CDN cache, and browser cache before retesting.
Fixes for specific pagination symptoms
Pagination shows but page 2 returns 404
This usually points to rewrite rules, permalink conflicts, or a mismatch between the template and the requested archive structure. Start by saving permalinks. Then check for custom rewrite rules, redirection plugins, and server configuration issues.
Every paginated page shows the same posts
This often means the query is not receiving the current paged value. It can also happen when cached page 1 content is served on every archive URL. Review custom query logic and clear caches thoroughly.
Pagination links do not appear
If pagination is missing, first confirm there are enough posts to create multiple pages. Then verify that the template calls a pagination function and that the query has a total page count greater than one. A custom query with an incorrect posts per page value can hide pagination unexpectedly.
Pagination breaks only on category or custom post type archives
This may indicate archive-specific template logic, custom taxonomy rewrites, or plugin filters targeting only certain content types. Test the affected archive with a default theme and compare its behavior to the main blog index.
Best practices to prevent future pagination problems
- Use the main WordPress query for blog and archive pages whenever possible
- Limit pre_get_posts changes to the main front-end query
- Refresh permalinks after structural changes
- Test category, tag, author, date, and custom post type archives after theme updates
- Clear all caches after changing query behavior
- Avoid unnecessary redirects on paginated archive URLs
If you are building a custom theme, follow WordPress template hierarchy and query conventions closely. Small deviations in archive handling can create large pagination issues later.
For official reference, review the WordPress documentation on WP_Query and the pre_get_posts hook. These resources help clarify how pagination should be implemented in custom themes and plugins.
When troubleshooting WordPress pagination issues on archive and blog pages, start simple: refresh permalinks, inspect the query, test for conflicts, and clear caches. In most cases, that process will reveal the problem quickly and help you restore clean, crawlable pagination across your site.
Leave a Reply