A WordPress tag archive is a page listing posts assigned that tag. Sometimes it’s a useful collection, such as all the articles about ventilation cleaning. Sometimes it’s several nearly identical pages with one article each. Don’t hide them all just because of the CMS, or make them all searchable just to increase the number of URLs.
Noindex is a rule for search engine crawlers that prevents a page from being included in the index. It does not block visitors from accessing the page.
Make the decision based on the archive’s content and role on the site. Configure the SEO plugin only after making that decision. Keep in mind that a hidden tag archive and a hidden article are different things: noindex on an archive should not accidentally affect the posts themselves.
Which URLs to collect
In the WordPress dashboard, go to Posts → Tags. For the tags you’ve selected, open the public archive and save its URL. The menu name may differ for a custom post type, but start with actual pages containing content for visitors, not just rows in the admin list.
For each tag, record the number of published posts, its topic, and how it differs from an existing category. Open the archive while logged out and check the list, title, description, and links to the posts. The number of posts alone is not a quality threshold. Two detailed guides to a specific task may be more useful than ten unrelated news items.
Add information about existing visits and external links, if you have it. If you don’t have analytics, mark the field as unknown. Don’t replace it with zero: unknown traffic and confirmed absence of visits are different grounds for changing a page.
Example: a tag differs from a category
Imagine a workshop blog with a category called “Ventilation maintenance.” It covers cleaning, diagnostics, parts replacement, and seasonal recommendations. The tag “Air duct flushing” groups posts about flushing methods, preparing a room, and questions about cost. This is a fictional example of a site structure, not the result of promoting a client.
This tag addresses a narrower need. Its archive can be developed into a clear collection: explain who the posts are for, put them in order, and link to them using specific titles. Visitors can see why they opened the page even if they don’t know how WordPress works.
Another tag, “Interesting,” contains the same single news item as the “News” category. The archive doesn’t explain the topic or help visitors choose what to read next. It has no purpose of its own. For this tag, consider noindex or revising the tag system without affecting the news item itself.
When to keep an archive open to search
Keep an archive open if it serves as a standalone navigation page: it has a clear topic, genuinely groups relevant content, and has a different purpose from nearby categories. This is an editorial decision, not a guarantee of indexing or rankings.
Yoast’s documentation on categories and tags includes separate settings for taxonomy visibility in search and metadata templates. The existence of this setting doesn’t mean every tag must appear in search. Prepare the content first, then check the title and description shown on the public archive.
Check that the description doesn’t repeat the site-wide text and that visitors can see the posts without searching the blog. If the collection keeps becoming empty, find out why: posts may have been deleted, set to draft, or assigned the wrong tag. Don’t make an empty page searchable just because you once planned to fill it.
How to set noindex for tags in Yoast
If you decide to hide all tag archives, go to Yoast SEO → Settings → Categories & Tags and open the Tags settings. Turning off the option to show tags in search results disables their search visibility through the plugin’s rule. Save the changes, then check the public HTML of one tag archive.
For an individual tag, use its editing screen and the available SEO settings. Under Advanced, find “Allow search engines to show this content in search results” and select No. This method is described in Yoast’s noindex guide. The translation and location of the section depend on the interface language and version.
Don’t disable SEO controls and assessments to apply noindex: that setting controls whether the editor tools are displayed. And don’t use WordPress’s “Discourage search engines from indexing this site” checkbox for a single archive: it applies to the entire site. After changing a tag, open a related article separately and make sure its indexing rule remains unchanged.
What to check after saving
Open the archive’s source HTML. Find robots and record its actual value. Check the response headers for the main request: an additional X-Robots-Tag may also affect indexing. If the HTML and headers don’t match what you expected, first find out where each rule comes from.
If the rule isn’t output at all, check SEO tags after changing a theme.
After clearing the relevant cache, check the archive as an ordinary visitor. An administrator may see the updated page while everyone else sees the old one. Compare the same URL and the time of the response. If the value is still unchanged, don’t conclude that noindex “doesn’t work”: the public document may not have been updated yet.
A change to the HTML doesn’t confirm that the search engine’s index has changed immediately. Check the URL in Search Console for Google and in Yandex Webmaster for Yandex, and record the date of the check. Until a new crawl takes place, distinguish the verified site setting from the unknown state of the search index.
A hidden tag can still be useful to visitors on the site. You don’t have to remove its navigation link just because of noindex. That’s a separate decision: does the link help people find content, or does it just clutter the page with dozens of random words?
When to rename or merge tags
If two tags refer to the same topic using different words, first choose the preferred name and reassign the relevant posts to it. Record both old URLs and what you’ve decided to do with each. Renaming a visible tag doesn’t necessarily change its slug, so check the URL separately. After merging, review the published posts: the collection should include all the agreed-upon content, and the menu should link to its actual address.
How to write a task and review the work
Give the developer a specific list of tags and one decision for each: keep it open and improve the collection, hide the archive, or merge duplicate tags. For a merge, specify in advance where to move the posts and what to do with the old URL. Simply deleting a tag isn’t a substitute for this plan.
Acceptance criteria for the example: “Air duct flushing” remains a standalone archive with the relevant content; “Interesting” gets noindex; the published news item remains open to search; and menu links point to the expected collections. Ask the developer to include the URLs checked, robots values, and date of the check.
For the sitemap, use the WordPress sitemap guide; to check a large set of archives, use the technical audit. General resources on working with pages are collected in the blog. A good result here is a clear system of collections, with each rule applied to the right page type and confirmed by a public response.