
You click a category link and get an empty page, or a message saying nothing was found — yet the posts exist in your dashboard. When the wordpress category page not displaying posts problem appears, readers cannot browse your content by topic, and a whole section of the site looks abandoned. The posts are almost always safe. The page is failing to fetch them, or failing to show what it fetched.
This guide works through the causes in order, from a post that was never assigned to the category to a theme template that queries nothing at all. Take a backup before the deeper fixes, and test the category page in a private browser window after each change, so a cached copy never fools you. Work through the fixes one at a time, and stop when the posts appear.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Confirm the Posts Are Published and Assigned to the Category
- Fix 2: Check the Category Count and Slug in Posts Categories
- Fix 3: Flush Permalinks by Saving the Permalink Settings
- Fix 4: Clear Every Cache Layer and Test in a Private Window
- Fix 5: Check for a Plugin That Filters or Hides the Query
- Fix 6: Switch to a Default Theme to Test the Archive Template
- Fix 7: Check the Reading Settings and Posts Page Choice
- Fix 8: Look for a Page with the Same Slug as the Category
- Fix 9: Check Sticky Posts and Custom Query Settings
- Fix 10: Rebuild the Category Assignment with Bulk Edit
- Fix 11: Repair the Database Tables and Reassign the Default Category
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
A category page is an archive: WordPress looks up the category, asks the database for its published posts, and hands them to the theme template to display. If any step fails — the assignment, the lookup, the query, or the template — the page comes up empty. These are the failures that happen most often.
1. The Posts Were Never Assigned to the Category
A post belongs to a category only when its checkbox is ticked in the editor. Posts written quickly, imported from another site, or created by a plugin often land in the default category only. The category page is then correctly empty, because no post actually belongs to it. This is the cause when the category shows a count of zero in the dashboard.
2. The Posts Are Drafts, Scheduled, or Private
Only published, public posts appear on a category page. Drafts, scheduled posts waiting for their date, private posts, and password-protected posts are all hidden from visitors. A category full of drafts looks exactly like a broken category page from the front end, while the dashboard shows a healthy list of posts. The fix is a status change, not a repair.
3. A Stale Cache Serves an Old Empty Page
Caching plugins, server caches, and content delivery networks can all serve a saved copy of the category page from before the posts were assigned. The live query works, but visitors never see it — they see the frozen empty page. This is the cause when the page works in the dashboard preview or after a cache purge, but stays empty in a normal browser window.
4. A Plugin Changes the Query Before It Runs
Plugins can filter the main query: hiding categories, excluding post types, or rewriting the archive query entirely. A membership plugin, a content-restriction plugin, or a custom query plugin can empty a category page without touching a single post. The fault appears suddenly after a plugin install or update, and it affects every category the plugin touches.
5. The Theme Template Fails to Display the Results
The theme controls how archive results are shown. A theme with a broken or missing category template, a custom archive template that queries the wrong category, or a block theme with an empty archive template can fetch the posts and still show nothing. The fault appears after a theme change or a theme update, and it survives every cache clear.
6. A Permalink or Slug Collision Sends Visitors to the Wrong Page
If a page shares a slug with a category, or the permalink rules are stale, WordPress may serve the wrong content — a page instead of the archive, or a 404 instead of the post list. The category and its posts are healthy, but the address leads somewhere else. Slug collisions often follow creating a page named after a category, and stale permalinks follow a migration or a settings change.
Quick Checks
Two minutes before the deep fixes.
- Open Posts, then Categories — does the category show a post count above zero?
- Open one post that should appear — is it Published, and is the category checkbox ticked?
- Open the category page in a private browser window — do the posts appear there?
- Check whether the problem affects one category or every category on the site.
- Check whether it started after a plugin install, a theme change, or a migration.
- Check whether the category page shows an empty message, a 404 error, or a different page entirely.
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| Category count is zero in dashboard | Posts never assigned to the category | Fix 1 |
| Posts exist but are drafts or scheduled | Post status hides them from visitors | Fix 1 |
| Page works in a private window only | Stale cache serving an old empty page | Fix 4 |
| Empty after a plugin install or update | Plugin filtering the archive query | Fix 5 |
| Empty after a theme change or update | Theme archive template fault | Fix 6 |
| Category page shows a 404 error | Stale permalinks or slug collision | Fix 3 |
| Category page shows the wrong content | Page shares the category slug | Fix 8 |
| Count is wrong but posts are assigned | Database count or term data damaged | Fix 11 |
Fix 1: Confirm the Posts Are Published and Assigned to the Category
Start with the posts themselves. A category page can only show published posts that carry the category assignment, so confirm both facts in the dashboard before you touch settings, caches, or code. Most empty category pages end right here.

- Go to Posts, then All Posts, in the dashboard.
- Find a post that should appear on the category page.
- Check its status reads Published, not Draft, Scheduled, or Private.
- Open the post and look at the Categories panel in the sidebar.
- Confirm the correct category checkbox is ticked.
- Click Update if you changed anything, then repeat for the other posts.
- Open the category page in a private window and check for the posts.
- Imported posts are the usual surprise: an import can bring the posts but drop the category assignments, leaving every post in the default category.
- Scheduled posts deserve a second look too — a post scheduled for the future will not appear until its date arrives, no matter how many times you refresh.
- If the posts are published and assigned but the page stays empty, the fault is in the lookup or the display, and the next fixes chase it down.
Fix 2: Check the Category Count and Slug in Posts Categories
The Categories screen shows the truth about each category: its name, its slug, its parent, and how many posts WordPress counts in it. A count that disagrees with what you assigned, or a slug that does not match the link you clicked, explains an empty page without any deeper fault.
- Go to Posts, then Categories, in the dashboard.
- Find the category and read the number in the Count column.
- Click the count number to see the posts WordPress believes belong to the category.
- If the list is empty, the assignment in Fix 1 did not save — repeat it.
- Click Edit on the category and read its Slug carefully.
- Compare the slug with the address in the browser — they must match.
- Click View under the category name to open its true archive address.
- Slugs are easy to get wrong: a renamed category keeps its old slug unless you edit it, and two similar categories can differ by one letter. The View link is the reliable test, because it uses the stored slug rather than the address you guessed.
- If View shows the posts but your menu link does not, the menu link is stale — update it from the View address.
- A count that stays wrong after correct assignment points at damaged term data, which Fix 11 repairs.
Fix 3: Flush Permalinks by Saving the Permalink Settings
Permalink rules tell WordPress how to turn a category address into a database query. When the rules go stale — after a migration, a settings change, or a plugin that registers its own addresses — the category address can return a 404 or the wrong content. Saving the permalink settings rebuilds the rules without changing anything else.
- Go to Settings, then Permalinks, in the dashboard.
- Read the current structure and note which option is selected.
- Do not change the structure — click Save Changes at the bottom.
- Wait for the confirmation message that the settings were saved.
- Open the category page in a private window and check for the posts.
- If the page still 404s, switch temporarily to Plain, save, then switch back and save again.
- Clear any cache after the flush, so visitors get the rebuilt rules.
- Flushing is safe: it rewrites the rule set, not your content, and saving without changes is the standard WordPress way to do it. The temporary switch to Plain is a stronger flush for stubborn cases, because it forces a full rebuild of the rules in both directions.
- If category pages 404 while single posts load fine, our guide to WordPress permalink structure causing 404 covers the deeper permalink checks.
- A flush that restores the page proves the rules, not the posts, were the fault.
Fix 4: Clear Every Cache Layer and Test in a Private Window
Caches freeze pages. A caching plugin, a server cache, a content delivery network, and the browser itself can each serve an old empty copy of the category page long after the live page works. Clear every layer, then test in a private window where no browser cache interferes.
- Open the category page in a private or incognito window first, as a baseline.
- In the dashboard, purge the cache from your caching plugin’s menu or toolbar button.
- Purge the server or host cache from the hosting control panel, if one exists.
- Purge the content delivery network cache, if the site uses one.
- Hard-refresh the private window with Ctrl and F5 on Windows, or Cmd, Shift, and R on a Mac.
- Check the category page for the posts.
- Repeat the test in a normal window after clearing the browser cache.
- Test the private window before you purge anything: if the posts appear there, a cache was the whole fault, and the purge is just cleanup. If the posts appear after the purge but vanish again later, a cache setting is re-freezing the empty page — check for cache rules that exclude archive pages from clearing.
- When the site keeps showing old content after purges, our guide to WordPress website showing old content covers the stubborn-cache checks.
- A page that works privately but not normally is a cache fault, never a content fault.
Fix 5: Check for a Plugin That Filters or Hides the Query
Plugins can rewrite the archive query before WordPress runs it. Membership, restriction, search, and custom-query plugins are the usual suspects, and the fault typically starts the day one is installed or updated. Deactivating plugins one at a time finds the culprit without losing any settings.
- Note which plugins were installed or updated just before the fault started.
- Go to Plugins, then Installed Plugins, in the dashboard.
- Deactivate the most recent suspect plugin first.
- Open the category page in a private window and check for the posts.
- If nothing changes, reactivate the plugin and try the next suspect.
- When the posts return, you have found the culprit — check its settings for a category or archive option.
- Leave the culprit deactivated, or reconfigure it, before you move on.
- Test membership and restriction plugins first: they hide content by design, and a misconfigured rule can hide a whole category from everyone, including logged-out visitors. Search and filtering plugins come next, because they rewrite queries for their own results pages and can leak the rewrite into archives.
- Deactivating one plugin at a time keeps the diagnosis honest — bulk deactivation tells you a plugin is at fault but not which one.
- If plugin conflicts keep recurring, our guide to WordPress plugin conflict fix covers the systematic isolation method.
Fix 6: Switch to a Default Theme to Test the Archive Template
The theme renders the archive. A broken category template, a custom query in the archive file, or a block theme with an empty archive template can all produce an empty page from a healthy query. Switching briefly to a default theme proves whether the theme or the data is at fault.

- Go to Appearance, then Themes, in the dashboard.
- Activate a default theme, such as Twenty Twenty-Four or Twenty Twenty-Five.
- Open the category page in a private window and check for the posts.
- If the posts appear, the old theme’s archive template is the fault.
- Switch back to your theme and check its archive or category template settings.
- Look for a custom archive template, a query setting, or a builder template assigned to archives.
- Fix or remove the faulty template, then test the category page again.
- Switching themes does not delete content, menus, or widgets permanently — they return when you switch back — but note your customiser settings first, just in case. In a block theme, open the Site Editor, then Templates, and check the Archive template for a query block that actually lists posts; an empty template shows an empty page.
- In a classic theme, a child-theme archive file that queries the wrong category is a common culprit.
- A default theme that shows the posts proves the data is healthy and the display is broken.
Fix 7: Check the Reading Settings and Posts Page Choice
The Reading settings decide which page shows the post list, and a wrong choice can starve archives of posts. A static front page with no posts page, or a posts page that conflicts with an archive, changes how WordPress builds every listing. The settings are few, but each one matters.
- Go to Settings, then Reading, in the dashboard.
- Read whether Your latest posts or A static page is selected.
- If a static page is selected, confirm the Posts page dropdown names the right page.
- Confirm the Homepage and Posts page are not the same page.
- Read the Blog pages show at most number — it must be above zero.
- Click Save Changes if you changed anything.
- Open the category page in a private window and check for the posts.
- A Blog pages show at most value of zero, or a blank value, can empty every listing on the site, not just one category. The static-page trap is subtler: a page assigned as the posts page takes over the blog listing, and a theme that mishandles the assignment can break category archives alongside it.
- If the settings look correct but the page stays empty, the fault is narrower — a slug collision or a query change — and the next fixes narrow it further.
- Note the settings before you change them, so you can restore the original choice.
Fix 8: Look for a Page with the Same Slug as the Category
WordPress gives pages priority in some address lookups. If a page shares a slug with a category — for example, a page called “News” and a category called “News” — visitors clicking the category link may land on the page instead of the archive. The category page is not empty; it is never reached.

- Go to Pages, then All Pages, in the dashboard.
- Search for a page whose title or slug matches the category name.
- Open the page and click Edit to read its slug in the permalink.
- Compare the page slug with the category slug from Fix 2.
- If they collide, rename the page slug to something distinct.
- Save the page, then flush permalinks as in Fix 3.
- Open the category address in a private window and check for the posts.
- The collision often follows a well-meant idea: creating a page to introduce a category, with the same name. WordPress allows the shared slug in different content types, but the front-end lookup must choose one, and the page usually wins.
- Keep category slugs and page slugs distinct as a standing rule — prefix the page slug, or give the page a different name entirely. After renaming, update any menu links that pointed at the old page address.
- A category page that appears once the collision clears proves the address, not the archive, was the fault.
Fix 9: Check Sticky Posts and Custom Query Settings
Sticky posts and custom queries change archive listings in ways that surprise. A category whose posts are all sticky can behave oddly in some themes, and a custom query — from a code snippet, a builder, or a theme option — can override the category filter entirely. Check both before you blame the database.
- Go to Posts, then All Posts, and look for posts marked Sticky.
- Open a sticky post in the category and check the Stick to the top of the blog option.
- Unstick the post temporarily and test the category page.
- Check the theme options and any code-snippet plugin for a custom archive query.
- Look for a query that sets a category, a post count, or a post type explicitly.
- Disable the custom query temporarily and test the category page.
- Restore the query only after correcting the category or post-type value it sets.
- Custom queries are the deeper trap: a snippet written for the homepage can leak into archives if it does not check which page it runs on, and a builder template can carry a query block filtered to the wrong category. Read any custom query as a sentence — which posts does it ask for, and does the category page match that request?
- If the query asks for a post type the category does not hold, the page comes up empty no matter how many posts the category owns.
- When caches also interfere with query testing, our guide to WordPress cache not clearing helps you get a clean test.
Fix 10: Rebuild the Category Assignment with Bulk Edit
When assignments look correct but the archive stays empty, rebuilding them forces WordPress to rewrite the stored relationships. Bulk Edit reassigns the category to many posts at once, which clears stale or half-saved assignments that the single-post editor does not show.
- Go to Posts, then All Posts, in the dashboard.
- Tick the checkboxes beside the posts that belong to the category.
- Open the Bulk actions dropdown and choose Edit, then click Apply.
- In the bulk editor, find the Categories checkboxes.
- Tick the correct category — and untick any wrong category.
- Click Update to save the bulk change.
- Open the category page in a private window and check for the posts.
- Bulk editing also reveals assignments the single editor hides: a post ticked for the category in the bulk view but missing from the archive points at a count or term fault, not an assignment fault. Work in small batches if the category holds many posts, so a save error does not undo the whole batch.
- After the rebuild, check the category count in Posts, then Categories — it should now match the number of posts you assigned.
- A count that still disagrees means the stored term data itself needs repair, which is the last fix.
Fix 11: Repair the Database Tables and Reassign the Default Category
If every other fix fails, the stored term relationships or counts in the database may be damaged. A repair rebuilds the term counts, and reassigning the default category gives orphaned posts a home. Take a full backup before this fix, and use a reputable database tool rather than hand-editing tables.
- Take a full backup of the site, including the database, before you start.
- Install or open a trusted database optimisation plugin, or use the host’s database tool.
- Run a repair and optimisation on the term and term-relationship tables.
- Go to Settings, then Writing, and confirm the Default Post Category is set.
- If the default category was deleted, choose a live category and save.
- Return to Posts, then Categories, and confirm the counts look correct.
- Open the category page in a private window and check for the posts.
- Database repair is a last resort because it touches stored data directly, but the term tables are small and the repair is routine. Never delete term rows by hand — a deleted term can orphan posts across the site.
- If the repair changes the counts, the damage was real, and the archive should now list the posts. If the page still stays empty after a repair, the fault is almost certainly in a theme template or a must-use plugin that the earlier tests did not reach — revisit Fixes 5 and 6 with every plugin deactivated and a default theme active at the same time.
- A wordpress category page not displaying posts fault that survives all eleven fixes is rare, and a clean simultaneous test usually names the culprit at last.

What to Avoid
- Do not delete a category to “fix” an empty page — its posts move to the default category and the archive address breaks.
- Do not create a page with the same slug as a category — the page can swallow the archive address.
- Do not bulk-deactivate every plugin at once — deactivate one at a time so you learn which one caused the fault.
- Do not edit database tables by hand — use a repair tool and a backup, or ask your host for help.
- Do not install a “category fix” plugin from an unknown source — use the dashboard checks in this guide first.
- 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 in a private window so a cached empty page never fools you.
Frequently Asked Questions
Why is my category page empty when the posts exist?
Because the posts are not assigned to the category, are not published, or are hidden by a cache, a plugin, or a theme template. The dashboard list and the front-end archive answer different questions: the dashboard shows what exists, and the archive shows what is published, assigned, and allowed through the query. Work through Fixes 1 to 6 to find which layer is blocking the posts.
Why does the category count say zero when posts are assigned?
The stored count can fall out of step with the real assignments after an import, a bulk change, or damaged term data. Rebuild the assignments with Bulk Edit as Fix 10 describes, then check the count again. If the count still disagrees, the term tables need the repair in Fix 11.
Can a caching plugin empty a category page?
A cache cannot empty the live query, but it can serve a saved empty copy of the page from before the posts were assigned. The result looks identical to a broken archive. Purge every cache layer and test in a private window, as Fix 4 describes, to separate a cache fault from a real one.
Why does one category work and another stay empty?
Because the fault is specific to that category: its slug, its assignments, a page sharing its slug, or a plugin rule that targets it. Compare the working category with the broken one in Posts, then Categories — slug, count, and parent — and check for a page with the same slug. A fault that affects every category points at the theme or a site-wide plugin instead.
What is the wordpress category page not displaying posts fix after a migration?
Flush the permalinks first, then clear every cache layer, then check that category slugs survived the move unchanged. Migrations commonly leave stale permalink rules and cached empty pages, and both are fixed in minutes. If the page still stays empty, check for a page that now shares the category slug, and confirm the posts kept their category assignments in the move.
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 6 is safe, and switching back restores your theme exactly as it was.
Conclusion
When the wordpress category page not displaying posts problem empties a section of your site, the posts are usually safe — the page is failing to fetch or show them. Confirm the assignments and the published status, check the count and the slug, flush the permalinks, clear every cache, and test plugins and the theme one at a time. Finish by opening the category page in a private window and counting the posts yourself, because a live listing is the only proof that counts. Keep category slugs distinct from page slugs, and your archives will keep listing the posts readers came to browse.
