WordPress Tag Pages and SEO: What They Do, and What to Noindex

WordPress tags are a navigation feature that people keep treating as an SEO feature.

They do not improve rankings. Used carelessly they generate hundreds of thin archive pages, and used sensibly they help readers find related posts. That is the whole of it.

This covers what tags actually do, whether their archive pages should be indexed, and how to clean up a site that already has too many. The numbers below come from auditing this site, which turned out to be a good example of the problem.

The short version

• Tags are for readers. They are not a ranking factor.
• Set tag archives to noindex unless a tag archive is genuinely a page worth landing on.
• A tag used on one post is not a tag. It is a duplicate of that post.
• Empty tags are untidy rather than dangerous, and worth deleting anyway.

What Tags Actually Do

A tag creates an archive page listing every post carrying it, at /tag/something/.

That page has no content of its own. It is a list of titles and excerpts pulled from posts that already exist elsewhere on the site.

Which is why tags do not help rankings. You are not adding information; you are creating another route to information you already published. The route can be useful to a reader. It is rarely useful to a search engine.

Tags versus categories

A useful test: if you were designing the site’s menu, would this be in it? If yes it is probably a category. If it is a word that describes the post but would never be a menu item, it is a tag.

Should Tag Archives Be Indexed?

For almost every site, no.

An indexed tag archive competes with the posts it lists, for the same terms, with less content. When Google has to choose between your post about a topic and your tag page listing posts about that topic, you want it to pick the post.

The exceptions are real but narrow. A tag archive worth indexing is one that functions as a genuine landing page: it has its own introductory content, it covers a topic a person would search for, and it is maintained. A news site’s archive for an ongoing story qualifies. A blog tag called “tips” does not.

How to set it

In Yoast this is under Search Appearance, Taxonomies, Tags, “Show Tags in search results”. Setting it to off writes noindex into the tag archive and removes tags from the sitemap. AIOSEO has an equivalent setting.

Worth knowing: the same toggle controls both. Once tags are noindexed, there is no tag sitemap, which is correct behaviour and surprises people who go looking for one.

Use noindex, follow rather than blocking tags in robots.txt. Blocking stops Google reading the page, which means it never sees the noindex and the URL can still appear in results.

What Tag Sprawl Looks Like in Practice

This site is a reasonable illustration, and not a flattering one.

Six hundred and twenty-five tags across 140 posts, and 613 of them point at nothing.

That is what happens over years of publishing when tags are typed into the box rather than chosen from a list. Each new phrase creates a new tag, posts get deleted or retagged, and the tags stay behind.

How much damage is it doing?

Less than the usual warnings suggest, and the reason is worth understanding.

The tag archives here are set to noindex, follow, so none of them competes with a post. And an empty tag has no posts, which means no post links to it, which means Google has almost no route to find it. The URLs exist and are mostly invisible.

What they do cost is crawl budget, if anything does reach them. On this site Google makes around 53 crawl requests a day with only 10% of those going to discovery, so wasted fetches are not free. The indexing audit found 51 URLs in the crawled but not indexed bucket, and the junk in that list was pagination, feeds and author archives rather than tags.

So the honest verdict on this site: the tags are untidy, they are not the problem, and they should still be deleted because an audit should not have to explain 613 phantom URLs every time.

When Tags Do Cause Real Damage

Three situations, and only the first is common.

• Tag archives left indexable. This is the one that actually costs rankings. Dozens of thin archive pages competing with the posts they list, for the same terms.
• One post per tag. A tag used once produces an archive page that is a near-duplicate of that single post. If those archives are indexed, you have doubled your page count with copies.
• Tags in the main navigation. Putting tag archives in the menu sends internal link equity to pages that exist to list other pages.

If your tags are noindexed and not in the menu, none of these applies and you can treat the cleanup as housekeeping rather than an emergency.

URL Structure

WordPress puts tag archives at /tag/name/ and category archives at /category/name/ by default. Both bases can be changed or removed under Settings, Permalinks.

People change these more often than they should. Two things worth knowing before you do:

• Removing the base creates collisions. Strip /category/ and a category called “seo” lives at /seo/, which is exactly where you might later want a post or page. WordPress will not warn you.
• Changing it breaks existing URLs. Every archive URL changes at once. If any were indexed or linked, that is a redirect job you did not plan.

If the archives are noindexed anyway, the base is invisible to search and changing it gains nothing. Leave it.

Should the category appear in post URLs?

Separate question, and the answer is usually no. Putting the category in a post’s permalink means the URL changes if you ever recategorise the post, and the keyword in the path is worth very little.

A flat /post-name/ structure is more durable, which matters more than any ranking consideration. This site uses it.

While You Are There: Categories

The same decision applies and the answer differs more often.

Category archives are better candidates for indexing than tags, because they map to the site’s actual structure and a reader might plausibly search for one. But only if the archive is more than a list.

• Keep the count low. Five to ten for most sites. If every post has its own category, they are tags with a different name.
• One category per post, so the structure means something.
• Index them only if they earn it. An archive with a few hundred words of real introduction can rank for a broad term. A bare list cannot.

On this site both categories and tags are noindexed. The categories are the better candidate of the two, but the honest reason not to open them up yet is crawl capacity rather than principle: there is no point adding indexable pages while good posts are still waiting to be crawled for the first time.

Cleaning Up

In order, and the first step decides how urgent the rest is.

• Check whether tag archives are indexed. View source on any tag page and look for the robots meta, or search your tag URL in Search Console’s URL Inspection. If it says noindex, the pressure is off.
• Set them to noindex if they are not. One setting, sitewide, done.
• Delete empty tags. Posts, Tags, sort by count, select everything showing 0 and delete. Nothing links to them, so nothing breaks.
• Merge single-use tags. Either apply them to more posts or remove them. A tag that will only ever describe one post is not serving a reader.
• Decide a tag list and stop improvising. Pick the ten to twenty cross-cutting topics the site genuinely covers, and choose from that list rather than typing.

If some tag archives were indexed and ranking

Check before deleting. If a tag archive has impressions in Search Console, noindexing it loses whatever it was getting.

In that case the better move is usually to keep the tag, add real introductory content to the archive, and treat it as a page rather than a list. That is work, so only do it where the data says it is earning something.

Deleting a tag does not delete the posts, and the tag URL will 404 afterwards. That is correct for a page that was never meant to rank, and the technical checklist covers when a 404 is the right answer rather than a redirect.

How long it takes, and what to expect

The cleanup itself is quick. Deleting several hundred empty tags is a sort, a select-all and one click, and merging the single-use ones is an afternoon at most.

What to expect afterwards is less dramatic than the effort suggests:

• If the archives were noindexed already: no ranking change at all. You have tidied up, not optimised.
• If they were indexed and thin: the index count falls over a few weeks as Google re-crawls, and any competition between archives and posts stops. Improvement, if it comes, is slow and modest.
• Either way: a cleaner audit, which is worth something on its own when you are trying to find a real problem among the noise.

Nobody has ever fixed a traffic problem by deleting tags. It is maintenance, and it is worth doing as maintenance rather than as a fix.

How to Use Tags Well

• Few. Fewer tags than categories plus a bit, not hundreds.
• Reusable. A tag should apply to several posts, now or soon.
• Cross-cutting. The point of a tag is to link posts that sit in different categories.
• Two or three per post, chosen from your list.
• Not a keyword exercise. Tagging a post with your target keyword does nothing. Keyword placement happens in the content, not the taxonomy.

And the simplest rule: if you cannot name three posts that would carry a tag, do not create it.

Frequently Asked Questions

Do WordPress tags help SEO?

Not directly. Tags create archive pages that list posts rather than adding content, so they give a search engine nothing new. They help readers move between related posts, which is a real benefit and a different one.

Should tag pages be noindexed?

For almost all blogs, yes. An indexed tag archive competes with the posts it lists for the same terms, with less content. The exception is a tag archive maintained as a genuine landing page with its own content.

How many tags should a post have?

Two or three, chosen from a list you decided in advance. The number matters less than whether each tag applies to several posts.

Do too many tags hurt my site?

Mainly if the archives are indexable. This site has 625 tags, 613 of them empty, and they cause little harm because the archives are noindexed and nothing links to them. They are still worth deleting for tidiness.

Should I delete unused tags?

Yes. Nothing links to an empty tag so nothing breaks, and it stops every future audit having to account for them. Check Search Console first if any tag archive was indexed and getting impressions.

What is the difference between tags and categories?

Categories are the site’s structure, few in number, and often worth keeping in the menu. Tags are cross-cutting topics that link posts across categories. If it would belong in your navigation it is probably a category.

Should I block tag pages in robots.txt?

No. Blocking stops Google reading the page, so it never sees the noindex tag, and the URL can still appear in results. Use noindex, follow and leave the page crawlable.