Should WordPress Categories, Tags, and Author Archives Be Indexed?

Index an archive when it works as a landing page: a reader arriving from search would find a coherent list, an explanation of what it covers, and a reason to stay. Keep an archive out of search when it duplicates another page, lists a single post, or exists only because WordPress creates one for every term and author. There is no rule that applies to every site. Google does not document that noindexing archives improves the rankings of the rest of a site, so make the decision on what each archive gives a reader and whether someone will maintain it.

The decision has three parts: list the archive types your site actually produces, compare each one with the page it competes with, and apply the rule through a control that search engines can read.

Inventory the archive types and their purpose

WordPress can create an archive for every category, tag, author, date, post format, and custom taxonomy term, plus internal search results and numbered pages of each; the template hierarchy, checked September 27, 2026, lists templates for each of these archive types and for search results. Start by counting what exists. From the site’s directory:

wp term list category --fields=name,slug,count --orderby=count
wp term list post_tag --fields=name,slug,count --orderby=count
wp user list --has_published_posts --fields=ID,user_login,display_name
wp taxonomy list --public=1 --fields=name,label

For each type, note three things in a table:

Then open a few archives of each type in a private window. Look at what a visitor actually sees: a heading, a description, a list of posts, and navigation to further pages. An archive that shows only a heading and excerpts is a list. An archive with a written introduction that explains the topic, groups the posts sensibly, and links to the most useful ones is a page.

Compare archives with competing pages

The problem to look for is not that an archive exists but that it answers the same question as another page on the site.

• A category and a service page. If garden.example/category/garden-design/ lists blog posts and garden.example/garden-design/ describes the service, they target the same searcher. Decide which one should appear for that topic. Usually the service page should, and the category can either be noindexed or given a distinct job, such as “articles about garden design.”
• Tags that repeat categories. A tag with the same name as a category often produces two lists of nearly the same posts.
• Single-post tags. A tag used once produces an archive with one excerpt, which is a weaker version of the post it lists.
• Author archives on a one-author site. When one person writes everything, the author archive lists the same posts as the blog page, in the same order.
• Date archives. Month and year lists rarely match a question anyone searches for, unless the site is a dated publication where readers browse by issue.

Google’s duplicate URL guidance, checked September 27, 2026, says it does not recommend using noindex to steer canonical selection within one site, because noindex removes the page from Search entirely. That fits archives: noindex an archive because you do not want that archive in search at all, not as a way of pointing its value at a similar page.

Two short, illustrative examples show how the same questions lead to different answers. Neither describes a real site.

Choose the control for each archive

Once you know which archives should stay out, pick a control that does what you intend.

Avoid blocking archive paths in robots.txt to keep them out of search. A blocked URL cannot be crawled, so any noindex on it is never seen. Avoid pointing every archive’s canonical at the home page too; Google’s duplicate URL guidance, checked September 27, 2026, describes canonicals for duplicate or very similar pages, and an archive is not a duplicate of the home page.

In WP Visibility 2.10.3, the Indexing section of the settings screen has a switch for author archives (indexable by default), date archives (noindexed by default), internal search results (noindexed by default), and paginated archive pages from page 2 onward (indexable by default). Noindex these taxonomy archives covers a whole taxonomy, with post formats ticked by default, and each category or tag has its own Search engine indexing setting on its edit screen. The setting applies to the archive page, not to the posts in it. Details are in Keep a Page Out of Search.

Check robots, canonical, and sitemap output

After changing the rules, check what the archives actually send. Use one archive of each type you changed and one you left indexable:

for u in \
  "https://garden.example/category/garden-design/" \
  "https://garden.example/tag/pruning/" \
  "https://garden.example/author/sam/" \
  "https://garden.example/2026/05/"; do
  echo "== $u"
  curl -sI "$u" | grep -iE '^HTTP|x-robots-tag'
  curl -s "$u" | grep -ioE "<meta[^>]*name=.robots.[^>]*>|<link[^>]*rel=.canonical.[^>]*>"
done

The addresses are illustrative. For each one, confirm:

• a noindexed archive returns 200, carries noindex in its robots meta tag or header, and is not blocked in robots.txt;
• an indexable archive has a self-referencing canonical and no noindex (WP Visibility 2.10.3 prints no canonical on date archives, so expect none there);
• a merged term’s old URL redirects to the surviving page.

Then check the sitemap. An archive you have noindexed should not be listed, because Google’s sitemap guide, checked September 27, 2026, says to include the URLs you want to see in search results. WordPress core’s own sitemap includes author archives, according to the WordPress 5.5 sitemaps announcement, checked September 27, 2026. WP Visibility’s sitemap replaces core’s while its Sitemaps module is on, lists no author or date archives, lists term archives that contain at least one post, and leaves out noindexed terms and taxonomies; the file list is in Submit Your Sitemap. If a noindexed archive is still listed, the sitemap may be cached. In 2.10.3, editing a term clears WP Visibility’s sitemap cache, but changing the Indexing settings does not, so run wp visibility flush after changing them. Why a page is missing from your XML sitemap covers the other cache checks, which work in both directions.

Page 2 and later of an archive follow their own rules. WordPress pagination SEO covers those.

Review the decision on a schedule

Archive rules drift. Someone adds forty tags in a month, a second author joins, or a category becomes the main entry point for a topic. Put a short review on the calendar, for example each quarter, and repeat the inventory:

1. Rerun the term and author counts. Look for new single-post tags and new categories.
2. Open the three most-visited archives in your analytics and read them as a visitor would.
3. Check that every indexable archive still has a description and a clear purpose.
4. Recheck robots and canonical output on one archive of each type.
5. In Search Console’s Page indexing report, compare indexed archive URLs with the rules you set. Noindexed archives should be listed under the reason URL marked ‘noindex’ once Google has recrawled them, according to the Page indexing report help, checked September 27, 2026. Google’s noindex documentation says a revisit can take months for less important pages.

Record the rule for each archive type and the reason in one place. When the next person asks why tags are noindexed, the answer is written down rather than inferred from a setting.