How To Remove Archives And Categories In WordPress

WordPress builds archive pages you never asked for. Category, tag, date, author, one for every term and every page of pagination.

Most of them are thin listings that duplicate your posts and clutter the index.

Knowing how to remove archives and categories in WordPress means picking the right action: noindex, disable, delete, or unlink. Each solves a different problem, and the wrong one either leaves the URL indexed or wipes out rankings you already earned.

This guide covers all four, using Yoast SEO, Rank Math, and plugin-free code snippets.

You will also get the redirect rules, the archives worth keeping, and how to confirm removal in Google Search Console.

What Is a WordPress Archive Page?

A WordPress archive page is a dynamically generated listing of posts grouped by a taxonomy term, date, author, or post type. WordPress builds it on request from the template hierarchy. No archive exists as a stored row in the wpposts table, which is why the dashboard offers no delete button for one.

The taxonomy term does live in the database. Category and tag names sit in wpterms, with their type and post counts stored in wptermtaxonomy.

That split trips up almost everyone the first time. The term is data. The archive URL is a rendered view of that data.

Template files that produce archives: archive.php, category.php, tag.php, author.php, and date.php.

Delete the term and the URL dies with it. Delete the template file and WordPress falls back to index.php, so the archive URL keeps resolving anyway.

Which Archive Types WordPress Creates by Default

Six archive types generate automatically on a standard install, plus a paginated version of each.

Pagination multiplies all of it. A category with 400 posts and 10 posts per page produces 40 crawlable URLs, not one.

What Does Removing a WordPress Archive Actually Mean?

Removing a WordPress archive means one of 4 separate actions: noindex, disable, delete, or unlink. Each solves a different problem. Picking the wrong one either leaves the URL indexed or destroys internal links you needed. Decide which outcome you want before touching a single setting.

Noindex is the safe default for most sites. The archive stays live for humans, the meta directive <meta name="robots" content="noindex,follow"> pulls it from the index, and the follow value keeps link equity flowing to the posts underneath.

Here is where people wreck their own cleanup: they add noindex and then block the same URLs in robots.txt.

Google’s documentation is blunt about this. A page blocked by robots.txt is never crawled, so Googlebot never sees the noindex rule, and the URL can still surface in search results when other pages link to it.

Google also states directly that robots.txt is not a mechanism for keeping a page out of Search. Use noindex, or password protection, or remove the page.

Deleting is the only action that touches your actual content. Everything else is presentation.

Why Category, Tag, and Date Archives Get Removed

WordPress archives get removed because they duplicate post content, generate thin listing pages, and consume crawl attention that belongs to the posts themselves. Ahrefs studied roughly 14 billion pages and found 96.55% receive zero organic traffic from Google. Auto-generated archives make up a large share of that dead weight.

Duplicate content: a category archive repeats the same excerpts as the blog index and, on many themes, the full post body.

Thin tag pages: sites that attach 8 to 12 tags per post end up with hundreds of archives holding one or two posts each.

Date archives: Yoast recommends disabling them outright, because posts sharing a publication month have no topical relationship to each other.

Author archives: on a single-author blog, /author/admin/ is a byte-for-byte clone of the blog index.

Indexing Insight analysed 1.7 million pages across 18 websites and attributed 88% of not-indexed pages to quality issues. Archives sit right in that bucket.

Crawl budget is the reason people usually cite, and it is the weakest of the four. Google’s own threshold is 1 million+ unique pages updated weekly, or 10,000+ pages changing daily. Gary Illyes reconfirmed the million-page figure in 2025.

John Mueller has put it more plainly, saying over 90% of sites on the internet never need to think about crawl budget.

So if your blog has 300 posts, archives are not eating your crawl budget. They are diluting your site quality signals, which is a separate and more relevant problem.

The Search Console signals that point at archive bloat

• “Crawled, currently not indexed” climbing while your post count stays flat
• “Duplicate without user-selected canonical” on /tag/ or /category/ URLs
• Indexed page count far above the number of posts and pages you actually published

A WordPress news site documented by SEOMind carried over 15,000 indexed pages built from daily, weekly, tag, and author archives. After noindexing the archives and rebuilding the sitemap, the index shrank 4x and organic traffic rose 25% in a quarter.

One caution worth repeating. Harrison Jones tested taxonomy noindexing across several sites and found that noindexing archives in isolation dropped traffic 20%. Paired with pagination fixes, the same change produced gains of 30% and 20% on two other sites.

Archives also multiply identical title tags across dozens of URLs, which is often the first symptom people notice in an audit.

How to Remove Category and Tag Archives With Yoast SEO

Yoast SEO removes category and tag archives from search results through Settings > Content Types, using per-taxonomy toggles that write a noindex directive into the page head and pull the URL from the sitemap. Yoast runs on 13 million+ active installations, so this is the path most WordPress sites will take.

Open Yoast SEO > Settings > Categories (or Tags) and switch off “Show Categories in search results”.

The toggle changes two things. It outputs noindex in the head, and it drops the URL from sitemapindex.xml.

It changes nothing about the URL itself. /category/news/ still loads, still gets crawled, still passes internal link value through its post links. That is the point.

Date and author archives live somewhere else entirely, under Settings > Advanced.

• Date archives: Yoast recommends disabling these. Disabled date archives drop out of the index and the sitemap together.
• Author archives: disabling redirects /author/username/ to the homepage and removes the author sitemap.
• Format archives: almost nobody uses post formats. Turn them off.

Worth knowing: Yoast keeps date archives enabled on its own site, specifically because the team uses them to work through old posts during content cleanups. Handy trick, as long as you never link to them.

If you want the archives gone from search but still reachable in your menu, use the noindex toggle rather than the disable switch. Disabling triggers a redirect, and a redirected menu item is a bad experience.

How to Remove Archives With Rank Math

Rank Math handles archive removal through Titles & Meta, where each taxonomy gets its own Robots Meta panel with a Noindex checkbox. The plugin sits on 4 million+ active installations and gives finer control over paginated archives and attachment URLs than most competitors.

The paginated setting is the one people miss. Deep pagination is where most of the junk URLs actually live.

Rank Math also ships a Remove Snippet Data toggle per taxonomy, which stops schema output on archives you have already noindexed. No reason to keep feeding structured data to a page you removed from search.

Attachment pages deserve the same cleanup pass. Every uploaded image generates its own URL and its own near-empty page, and on an image-heavy site that quietly doubles your indexable URL count.

For archives that already earned links, the built-in Redirections module points the old URL at a live destination without a second plugin.

How to Disable WordPress Archives Without a Plugin

Disabling WordPress archives without a plugin takes 3 hooks: templateredirect for killing archive requests, registertaxonomyargs for making a taxonomy non-public, and wprobots for adding noindex to specific conditions. All 3 go in a site-specific plugin file or a child theme.

The simplest version intercepts the request before the template loads:

addaction( 'templateredirect', function() { if ( isdate() || isauthor() ) { wpsaferedirect( homeurl(), 301 ); exit; } });

Swap the 301 for statusheader( 410 ) when the archive has zero inbound links and you want it out of the index fast.

To kill tag archives at the source, filter the taxonomy registration itself with registertaxonomyargs and set 'public' => false plus 'rewrite' => false. WordPress then stops generating the rewrite rule entirely.

For noindex only, wprobots is the modern hook. WordPress 5.7 replaced the older wpnorobots function with this filter, and plenty of tutorials still show the deprecated version.

Placement matters more than the code. A child theme’s functions.php file works, but the snippets vanish the day you switch themes. A site-specific plugin survives theme changes, which is why I default to it. Same reason applies to leaving core files alone no matter how tempting a quick edit looks.

After changing taxonomy registration arguments, visit Settings > Permalinks and hit Save. Skipping the flush is the single most common cause of rewrite rules behaving unpredictably and live posts throwing intermittent 404 responses afterward.

Removing Author Archives on Single-Author Sites

A single-author blog has no reason to keep /author/admin/ alive. Redirect it to the homepage with an isauthor() conditional and be done.

The redirect alone leaves a loose end. Most themes still print an author byline that links straight at the URL you just killed.

Strip the link from your post meta template, or remove the author display entirely, so no internal link points at a redirect.

Same principle applies to published dates shown in post templates once date archives are gone.

How to Delete a Category and Reassign Its Posts

Deleting a category removes the term from wpterms and unassigns it from every post. Posts survive. Posts left with no category get pushed into the default category set under Settings > Writing, which on a fresh install is Uncategorized.

Reassign first, delete second. Always.

The sequence:

1. Posts > All Posts, filter by the category you plan to remove
2. Select all, choose Bulk Edit, add the replacement category
3. Save, then confirm the new post count in Posts > Categories
4. Posts > Categories, Bulk Actions > Delete on the old term

Reverse that order and you get a pile of posts sitting in Uncategorized, which then needs sorting by hand.

Two things behave differently than people expect.

The default category cannot be deleted. WordPress blocks it. You can rename it and change its slug, which is what most people actually want.

Deleting a term never deletes posts. Deleting a custom post type registration does hide its content, since the posts stay in the database but lose their public URLs.

Tags follow identical rules. Removing a tag unassigns it from each post and nothing else, which makes tag cleanup far lower risk than category cleanup.

One consequence gets overlooked. Deleting a category strips every internal link that pointed at that archive, and posts that relied on it for navigation can turn into content nothing on the site links to. Check your menus and sidebar widgets before you hit delete, not after.

How to Remove the /category/ Base From WordPress URLs

Removing the category base turns /category/news/ into /news/. WordPress supports changing the category base under Settings > Permalinks but does not officially support removing it, so the job needs a plugin or a rewrite rule, plus 301 redirects for every URL you just changed.

This is a different request from noindexing an archive. Same keyword, completely different intent.

The four routes people actually use:

• Permalink settings: enter a single dot in the Category base field. An old workaround that breaks on some hosts. Test it before trusting it.
• Yoast SEO: the “Strip the category base” toggle under Advanced > Permalinks handles the rewrite at PHP level.
• Permalink Manager Lite: 100,000+ active installations, and its canonical redirect sends visitors from the old URL to the new one automatically.
• Remove Category URL: a single-purpose plugin that flushes permalinks for you on uninstall.

Slug collisions are the failure mode nobody warns you about until it happens.

WordPress checks rewrite rules in order and stops at the first match. Give a category and a page the same slug, and the category wins. Your page becomes unreachable with no admin notice and no warning.

Audit your category slugs against your page slugs before you touch anything. Ten minutes now beats a week of confused 404 reports later.

Then flush the rewrite rules. Settings > Permalinks, Save Changes, twice if the first pass does not stick.

Every old /category/slug/ URL now needs a 301 to /slug/. Skip that step and you drop every link and ranking those archives accumulated. The full walkthrough for stripping the category prefix covers the rewrite rules and the redirect map together.

Worth noting: shorter URLs do not rank better on their own. The gain is a cleaner structure and shareable links, nothing more. Same logic applies when you clean index.php out of your permalinks.

How to Redirect Removed Archives Without Losing Link Value

Redirect a removed archive to its closest live equivalent with a 301, or return 410 when the URL has no inbound links worth preserving. Gary Illyes confirmed in 2016 that 30x redirects no longer lose PageRank, and Google has repeated that position since.

Relevance decides whether the equity actually transfers.

Google treats a redirect pointing at an unrelated destination as a soft 404. The status code is accepted, the signals are not. Dumping 200 dead tag archives onto your homepage passes nothing.

Check before you choose. Ahrefs Site Explorer and the Links report in Search Console both show which archive URLs carry inbound links.

On the 410 question, John Mueller has said the difference is real but small: a 410 falls out of the index roughly a couple of days faster than a 404. He also confirmed in 2026 that 404s and 410s are not a negative quality signal.

Implementation splits two ways.

Plugin level: Redirection by John Godley runs on 2 million+ active installations, logs 404s, and works on servers with no .htaccess access. Managed hosts like WP Engine deprecated .htaccess entirely, which makes the plugin route the only practical one there.

Server level: .htaccess on Apache or a rewrite block in the Nginx config fires before WordPress loads. Faster, though the real-world gap is small until you are managing hundreds of rules.

Illyes also advised keeping 301s live for at least a year so Google has time to consolidate the signals.

Then there is the part everyone forgets. Redirects handle external traffic, but your own site keeps pointing at the removed URLs.

Category widgets, sidebar term lists, related post modules, and nav menu items all survive the archive they linked to. Run a crawl in Screaming Frog SEO Spider, then repair the internal links that now hit a redirect or a dead end.

Breadcrumb trails that include a category level need the same treatment, since they render on every single post.

Redirecting is not a substitute for pointing your internal links at live destinations in the first place.

Which Archives to Keep on a WordPress Site

Keep an archive when it has unique content above the post list, receives organic clicks, and holds more than 5 posts. Everything failing all 3 tests is a candidate for removal. Site type decides most of it before you ever open Search Console.

Ecommerce is the clearest case, and the one people get wrong most often.

Research across roughly 30 leading ecommerce sites, run with seoClarity and published by Practical Ecommerce, found parent and child category pages rank for 19% more keywords than product detail pages and drive 413% more traffic.

Noindexing WooCommerce product categories on a store running faceted navigation is one of the fastest ways to delete your own revenue. WooCommerce powers over 8 million active installs, so this mistake scales.

Publishers sit in the opposite position on date archives. A monthly archive groups posts that share nothing but a timestamp.

Category archives on a publisher site earn their place when someone actually writes an intro, links out to the pillar content, and treats the page as a destination rather than a list. A query loop block pulling in curated posts does that job without custom templates.

Single-author blogs have no reason to keep author archives, ever. It is a duplicate of the blog index with a different URL.

If you are stripping most of the archive layer, give people another way through the content. A visible search field replaces a lot of taxonomy browsing.

Quick reality check on the whole exercise. Ahrefs found 96.55% of pages get zero traffic from Google, so the odds are strongly against your tag archives being the exception.

How to Confirm Archives Are Removed From Google

Confirming archive removal takes 3 checks: URL Inspection for the noindex directive, the Pages report for the excluded count, and a site: operator search for a rough sense of what is left. Noindex only takes effect after Googlebot recrawls, so none of this is instant.

Start with URL Inspection in Google Search Console.

Paste a category or tag URL. You want to see Indexing allowed? No: ‘noindex’ detected in ‘robots’ meta tag. That confirms the directive is reaching Googlebot rather than being blocked upstream.

Treat that third row as a sanity check, not a metric. John Mueller has said plainly that a site: query is not a comprehensive list of your pages and that Search Console is the place to get real counts.

The Removals tool has one legitimate use here: buying time. It suppresses a URL from results for about six months while the permanent noindex propagates. Google’s own documentation calls it a first step toward permanent removal, never the removal itself.

Timelines vary more than people expect.

Onely tracks indexing across popular sites and reports that Google indexes 56% of indexable URLs within 1 day and 87% within 2 weeks. Deindexing follows the same crawl-rate logic in reverse, so a high-authority domain clears in days while a low-traffic blog can take months.

IndexCheckr’s study of 16 million pages found 93.2% of pages that do get indexed are indexed within six months. If your archives are still showing after that window, something is blocking the directive rather than delaying it.

Recheck at 7 days, 30 days, and 90 days. Anything more frequent is just refreshing a dashboard.

Which Mistakes Break a Site When Archives Are Removed

Six mistakes account for nearly every archive cleanup that goes wrong: blocking noindexed URLs in robots.txt, deleting a top-performing category, leaving menu links pointing at dead URLs, changing the category base without redirects, skipping the permalink flush, and noindexing WooCommerce product categories.

Robots.txt plus noindex: Google never crawls the URL, never reads the directive, and the archive stays indexed indefinitely. This is the single most common self-inflicted wound in the whole process.

Deleting your best landing page: pull the Pages report in Search Console and sort by clicks before you delete a single term. Some category archives outrank the posts inside them on broad queries.

Orphaned menu items: disabling an archive triggers a redirect or a 404, but the nav menu keeps linking to it. Every visitor who clicks lands somewhere unexpected.

No redirect map: stripping the category base without 301s drops every archive URL at once, and the links they earned go with them.

Skipping the rewrite flush: setting a taxonomy to 'public' => false without saving permalinks produces intermittent not found responses on live post URLs, which is a nightmare to diagnose because it looks random.

Killing WooCommerce categories: product category archives drive faceted navigation and commercial rankings. Noindexing them is not cleanup, it is amputation.

One more that rarely makes lists. People clean up archives, then never touch the destination page.

Whatever you redirect a removed archive to has to answer the same query the archive did. Otherwise Google logs a soft 404 and the transfer quietly fails.

Build a useful 404 template with search and category links before you start removing things. Some percentage of visitors will hit one no matter how careful your redirect map is, and a blank error page turns a small mistake into a lost session.

Last thing, and it is the one I wish someone had told me earlier: do this on staging first. Archive removal touches rewrite rules, and rewrite rules fail silently.

FAQ on How To Remove Archives And Categories In WordPress

Does deleting a category delete its posts?

No. Deleting a category unassigns the term from every post and removes it from wpterms. Posts stay published. Any post left with no category falls into the default category set under Settings > Writing.

Should I noindex or delete WordPress tag archives?

Noindex first. It takes 5 minutes in Yoast SEO or Rank Math and reverses instantly. Delete only the single-use tags you never plan to build into topic clusters, and redirect any that earned links.

Can I delete the Uncategorized category?

No. WordPress blocks deletion of the default category outright. Rename it and change its slug instead, or assign a different default under Settings > Writing and delete the old term afterwards.

Why are my archives still showing in Google after noindex?

Googlebot has not recrawled yet. Confirm the directive with URL Inspection in Google Search Console, then check that robots.txt is not blocking the URL, which would stop the crawler ever seeing the noindex rule.

Does removing archives improve rankings?

Not directly. Removing thin archives reduces index bloat and duplicate content, which improves site quality signals. Traffic gains usually come from the posts underneath, not from the archive removal itself.

Should I block archives in robots.txt?

No. A blocked URL never gets crawled, so Googlebot never reads the noindex tag and the archive can stay indexed. Google states plainly that robots.txt is not a mechanism for keeping pages out of Search.

How do I remove archives without a plugin?

Use 3 hooks: templateredirect to intercept archive requests, registertaxonomyargs to set public false, and wprobots to add noindex. Put them in a site-specific plugin, then flush rewrite rules.

Do I need to redirect removed archive URLs?

Only when the archive has inbound links or organic clicks. Check Ahrefs Site Explorer or the Links report first. Zero-signal archives can return 410, which clears them from the index faster than 404.

Should I remove WooCommerce product category archives?

No. Product category archives rank for broad commercial queries and power faceted navigation. seoClarity research found category pages drive 413% more traffic than product pages. Remove product tag archives instead.

Why did my post URLs start 404ing after disabling a taxonomy?

You changed taxonomy registration without flushing rewrite rules. Visit Settings > Permalinks and click Save Changes. WordPress rebuilds the rules, and the intermittent 404 responses on live posts stop.

Conclusion

Working out how to remove archives and categories in WordPress comes down to a decision, not a plugin setting. Match the action to the problem, then execute it once, cleanly.

Audit before you delete. Pull the Pages report, check which taxonomy URLs earn clicks, and leave those alone.

Map every removed URL to a live destination. A 301 that lands somewhere unrelated passes nothing.

Flush the rewrite rules, refresh your sitemap, then crawl the site afterwards to catch internal links still pointing at dead terms.

Then leave it alone for 30 days. Deindexing runs on Google’s crawl schedule, not yours.

Archive cleanup is maintenance, not a growth tactic. The payoff shows up quietly, in your posts.