Key takeaways
- Google ignores the meta keywords tag, so a WordPress tag is not a ranking keyword. Its only SEO effect comes from the /tag/name/ archive page it creates.
- For a small site with years of unmanaged tags, noindex tag archives by default and make deliberate exceptions. A publisher or store with curated tags should judge each archive on its own.
- Noindex only works on pages Google can crawl, so don’t block tag URLs in robots.txt. Use a 301 only when a close replacement exists, and never send every deleted tag to the homepage.
- In Yoast, the sitewide tag setting and each tag’s own Advanced setting are separate. AIOSEO handles paginated pages with separate settings, so check the source of /tag/name/ and /tag/name/page/2/, not just the toggle.
Adding more tags won’t make your WordPress posts rank better. Setting every tag archive to noindex won’t save a weak site either. Both shortcuts skip the one decision that matters: does this tag’s archive page deserve to be a search result?
Each tag you create gives WordPress a new public URL, usually /tag/tag-name/, plus /tag/tag-name/page/2/ and onward once enough posts share it. A site with 40 posts and 200 tags has made 200 listing pages, and most of them show one or two excerpts. That is where tags and SEO actually meet.
Do WordPress tags help SEO at all?
Not directly. A WordPress tag is a non-hierarchical taxonomy term for grouping posts. It is not a keyword field. Google’s list of supported meta tags says Google doesn’t use the meta keywords tag for ranking, and a post tag carries no more weight than that. Typing “best plumber London” into the tag box doesn’t tell Google anything about your post.
A lot of the confusion comes from the habit of treating tags like hashtags or the old meta keywords field. Tags are for readers. They link related posts across categories, and our guide to tags vs categories in WordPress covers that split in detail. Any SEO effect comes from the archive pages: they are either useful landing pages or thin lists that repeat content already on your site.
Thin archives are not a penalty. Google’s canonicalization documentation describes grouping similar pages and picking one to show. Thin archives still cost you something. Your blog’s search results fill up with near-empty listing pages, and you get one more set of URLs to keep tidy.
Which tag archives should stay in Google?
Keep a tag archive indexable when it collects a real group of posts that someone would search for as a group, and when no category already shows the same list. Everything else should be noindexed, merged into another tag or deleted.
| Tag situation | Example | Action |
|---|---|---|
| Several posts on a lasting topic, not covered by a category | “Sourdough” tagging recipes, equipment reviews and lessons | Keep indexable. Add a real description and check that your theme displays it. |
| Synonym of an existing tag | “boiler-repair” next to “boiler-repairs” | Move the posts to the stronger tag, delete the other one and 301 its URL to the survivor. |
| Same name as a category | A “Recipes” tag and a “Recipes” category | Delete the tag. The category archive covers it. |
| Used on one or two posts | “Boiler servicing” on a single article | Delete the tag, or noindex it if readers still use it to get around. |
| Useful for browsing, weak as a search result | A “Holiday hours” grouping | Keep the tag and noindex the archive. |
Sources disagree about where the default should sit. Yoast’s current help pages present indexable taxonomy pages as possible landing pages. Its 2023 beginner’s guide said most WordPress SEO experts hide tag archives, and many freelancers noindex all tags as standard. One r/Wordpress commenter said they disable tags on about 90% of client sites. Both camps use the same test, though: is the page useful? For a small business site with years of unplanned tags, both answers lead to the same place. Noindex the tag archives and make exceptions on purpose. Publishers and stores that maintain their tags should judge each one.
No one has an official minimum number of posts per tag. Rules like “five posts before indexing” are habits some teams use, not Google requirements.
How to audit your tags in one pass
- List every tag. Go to Posts > Tags and sort by the Count column. A crawler such as Screaming Frog also finds tag URLs that are still linked somewhere.
- Add Search Console data. In Performance, filter pages to URLs containing
/tag/and note impressions and clicks. An archive that gets impressions deserves a closer look before you remove it. - Group the problems. Mark synonyms, tags that share a category’s name, and tags used once or twice. Compare the posts each tag actually lists, not just the names.
- Look for overlap with your posts. If a tag archive and an article both get impressions for the same queries, the article is usually the better answer and the archive is in the way.
- Give each tag one action: keep, improve, noindex, merge or delete. For merges, write down the replacement URL.
- Back up first. WordPress keeps revisions for posts, but not for deleted tags. Export names, slugs and post assignments before you delete anything.
Which fix matches which tag
Keeping a page out of search, replacing it and removing it are three different jobs, and each one has its own tool.
- Noindex keeps an archive out of results while visitors can still use it. Google has to crawl the page to see the instruction. Its robots meta tag documentation warns that a URL blocked in robots.txt can still appear in results. Don’t block tag pages in robots.txt as well.
- A 301 redirect is for a merged synonym. Send the old archive straight to the tag that replaced it. Our explainer on how a 301 redirect affects SEO covers chains and testing.
- A 404 is fine for a deleted tag with no close replacement. Redirecting every old tag to the homepage helps nobody, and the 404s that then show up in Search Console are expected.
- A canonical is only for pages that really are duplicates. Google says canonical annotations are the preferred way to signal duplicates and that noindex is not the tool for it. Pointing every tag canonical at the homepage or the blog page is a misuse.
Leave tag slugs and the tag base under Settings > Permalinks alone. Keywords in a URL path barely help rankings, and every changed URL needs a redirect.
Where the noindex settings live
In Yoast SEO, open Yoast SEO > Settings > Categories & tags and turn off showing tags in search results. For one tag, edit it under Posts > Tags, open the Yoast SEO Advanced section and set “Allow search engines to show this content in search results” to No, as Yoast’s noindex guide describes. All in One SEO and Rank Math have similar taxonomy settings under their search appearance and titles screens, but the menu names are different.
A noindexed archive should also be taken out of your XML sitemap. Yoast does this automatically. If a noindexed URL stays in a sitemap, Search Console reports “Submitted URL marked noindex”. Yoast’s advice is to first confirm the noindex was intended.
Why tag pages still say “index” after you turned it off
The settings screen shows what you saved. The page source shows what Google actually receives, so check that.
In one Yoast support thread, a user turned off “Show tags in search results”, cleared every cache and switched plugins off one at a time. The tag pages still output index, follow, and URL Inspection still said the page was allowed for indexing. Support explained that individual tags can carry their own setting and that Search Console data isn’t real-time. A tag sitemap returning 404 did not prove the tags were noindexed.
Pagination can behave differently from page one. In an All in One SEO thread, page one of a tag archive output max-image-preview:large while page two output noindex, nofollow, max-image-preview:large. The fix was unchecking “No Index Paginated” and “No Follow Paginated” under Search Appearance > Advanced. Another AIOSEO report in late 2024 found paginated canonicals missing a slash, as in /tag/slugpage/2, and support supplied a code snippet. If you see that, update the plugin before writing workarounds.
To check a change:
- Open
/tag/name/logged out and view source. Find<meta name="robots"andrel="canonical". - Repeat on
/tag/name/page/2/. - Check the response headers for
X-Robots-Tag. Some hosts, Kinsta among them, add this header on staging, and it can survive a careless push to live. If your whole site has dropped out of search, also check Settings > Reading. - Run URL Inspection’s live test. Then give Google time to recrawl before you decide the change failed.
WooCommerce product tags are a separate decision
Product tags can be real shopping pages. WooCommerce’s documentation describes tags that group products across categories, and it ships templates for product-by-tag archives. A product keeps one URL however many categories and tags it belongs to, so tagging doesn’t duplicate product pages.
Use categories for product types and tags for groups shoppers would browse across categories, such as a material or a season. Use attributes when shoppers need to filter, because attributes don’t need archive pages of their own. Filter-combination URLs fall under Google’s faceted navigation guidance, which is a separate problem from tag archives. Adding 15 or 20 tags to every product is the same keyword-field mistake with more items to undo. After a WooCommerce update, check that your SEO plugin still outputs the right metadata. Yoast SEO 26.9 temporarily restored old behaviour after WooCommerce 10.5 changed its permalink logic.
How to stop tag sprawl from coming back
Sprawl is a habit problem more than a WordPress problem. Write a short rule into your editorial checklist: reuse an existing tag before creating a new one, and only create a tag when you can already name a few posts that belong in it. Give one person ownership of the tag list, and look at Posts > Tags once a quarter. For the wider set of checks around this, see our step-by-step WordPress SEO guide.
If you’d rather hand off the noindex settings, redirects and checks, SiteSelf handles SEO settings and redirects through chat on your existing site and reports what it checked on the live page.
Frequently asked questions
Can tag pages compete with my own posts in Google?
They can. Some site owners suspect it when tag URLs start getting impressions for queries their articles should win. No one has measured how often it happens. Search Console’s Performance report shows which URLs get impressions for a query. If a tag archive keeps showing up in place of the matching article, noindex the archive.
How many tags should a post have?
Google sets no limit. A handful that match how readers browse is plenty. More tags per post mostly means more thin archives.
I deleted tags and Search Console now shows 404s. Is that a problem?
No. A 404 is the correct response for a tag that no longer exists. Redirect only the ones that had links or traffic and have a close replacement.
Does noindexing a tag remove it from my site?
No. The tag stays on your posts and the archive still works for visitors. Noindex only asks search engines to leave the page out of results.
Should I remove the tag cloud from my footer?
It’s a common cleanup step, but it’s about navigation, not a ranking rule. If you keep tag links, make the link text say what’s on the other end. WCAG 2.2’s link purpose criterion asks for exactly that.
Leave a Reply