“5 to 10 tags per post” is the answer that shows up in nearly every article on this topic, repeated so often it’s treated as settled fact. It’s not wrong, exactly, but it’s incomplete in a way that causes real problems: it treats a blog covering one narrow topic the same as a blog covering five, and it treats tags as an SEO lever when their actual job is closer to a library card catalog than a ranking signal.
Here’s a more useful way to think about it, along with the tag mistakes that quietly hurt a site’s usability and search visibility more than the raw count ever does.
What a tag is actually for
WordPress ships with two built-in taxonomies for organizing content: categories and tags. Categories are meant to be broad, hierarchical, and few, the handful of major sections a site is divided into (Recipes, Travel, Reviews). Tags are meant to be specific, non-hierarchical, and applied more loosely, the granular topics a single post touches on, cutting across categories (a post in the “Recipes” category might carry tags like “gluten-free,” “30-minute meals,” and “instant pot”).
The functional purpose of a tag is to let a reader who’s interested in one specific thread pull together every post that touches it, regardless of which broader category each post lives in. A recipe blog’s “gluten-free” tag might surface posts filed under Breakfast, Dinner, and Dessert categories alike, that cross-cutting connection is something categories alone can’t do. This matters because it reframes the sizing question entirely: the right number of tags isn’t a fixed count, it’s however many genuinely distinct, reusable topic threads a given post actually touches.
Why the flat “5-10” rule breaks down
A tightly focused single-topic blog, a site that only publishes recipes, say, often has real content for only two or three meaningfully distinct tags per post before running out of legitimate topic threads to attach. Forcing five to ten tags onto a post like that means padding with tags that either overlap heavily with each other or barely apply to the post’s actual content, which is precisely the kind of low-signal tagging that dilutes a tag archive’s usefulness.
Conversely, a broad, multi-topic site, a general lifestyle or news blog covering cooking, travel, product reviews, and personal essays, genuinely does touch more distinct threads per post, and artificially capping tags at three or four on that kind of site under-serves readers who’d benefit from those cross-cutting connections.
The number that actually matters is: how many genuinely separate, specific topics does this individual post cover? For most single-topic posts, that lands somewhere in the 3-7 range in practice, the “5-10” guideline isn’t wrong so much as it’s a rough average masquerading as a rule.
The real cost of over-tagging
Piling on tags “just in case they help SEO” causes two distinct problems, one for readers and one for search engines.
For readers, a tag archive page is only useful if it groups a meaningfully related, sizeable set of content. A tag applied to exactly one post is a dead end, a reader clicks it expecting more related content and finds nothing else there, which reads as a broken or neglected part of the site. Over-tagging inflates the number of these single-post, orphaned tag archives on a site, and a site with hundreds of one-post tags has effectively built a maze with no exits.
For search engines, thin archive pages (a tag page with one or two short posts and little unique content of its own) are a textbook example of what Google’s own documentation on thin content describes as low-value, and at scale, a site with hundreds of near-empty tag archives can dilute how a search engine allocates its crawl budget, the finite number of pages a crawler will bother indexing on a given site in a given window. This isn’t a minor technical footnote for a small blog, but it becomes a real, measurable problem once a site passes a few hundred posts and its tag count has grown unchecked alongside it.
The real cost of under-tagging
The opposite failure is quieter but still costs something. A site that tags posts inconsistently, or barely tags them at all, loses the cross-referencing value tags exist to provide. A reader who finishes a post about “sourdough starters” and wants more content specifically about fermentation, rather than baking broadly, has no path to that unless a tag connects those posts directly. Without it, that reader either gives up or falls back on the site’s search box, which is a meaningfully higher-friction path than a single click on a relevant tag.
Under-tagging also means related-posts widgets and “you might also like” sections, many of which pull from shared tags rather than categories, have less signal to work with, producing weaker, less relevant recommendations across the whole site.
A practical process for tagging a new post
Rather than aiming for a specific count, work through these questions when publishing:
- What are the two or three most specific topics this post is actually about? Not the category it lives in, the sub-topics within that category. A post titled “10 Gluten-Free Breakfast Ideas” touches gluten-free, breakfast, and quick recipes as genuinely distinct threads.
- Do any of these tags already exist on the site, or would this create a new one? Before creating “gluten free” as a new tag, check whether “gluten-free” (with a hyphen) already exists. Tag fragmentation, the same concept split across two or three slightly different tag names, is one of the most common and easily avoidable tagging mistakes, and it splits a topic’s content across multiple weak archives instead of one strong one.
- Would this tag ever have more than three or four posts under it, eventually? If a tag is genuinely going to remain a one-off, it’s probably too specific to be a tag, it might belong in the post’s search-optimized meta description instead, or simply not need a dedicated tag at all.
- Does this tag help a reader find genuinely related content, or is it here because a keyword tool suggested it? Tags added purely because they contain a target keyword phrase, without genuinely organizing content, tend to be the ones that turn into the thin, orphaned archives described above.
Auditing an existing site’s tags
For a site with an established backlog of posts, an occasional tag audit catches the accumulated mess that ad hoc tagging tends to produce over time. A workable process:
- Pull a list of every tag on the site along with its post count, available through WordPress’s own Tags screen under Posts » Tags, sortable by count.
- Identify tags with only one or two posts attached, these are candidates for either merging into a related, larger tag, or removing entirely if they don’t represent a genuinely recurring topic.
- Look for near-duplicate tags (singular/plural variants, hyphenated vs. non-hyphenated versions, close synonyms) and consolidate them using WordPress’s tag merge functionality, or a plugin like Term Management Tools for bulk operations across a large tag list.
- Check whether any tag has grown so large it’s functionally become a category, if a tag has accumulated hundreds of posts and covers nearly the same ground as an existing category, it may be worth restructuring as a category or sub-category instead.
This kind of cleanup is tedious on a large site, but it’s a one-time cost against a compounding benefit, every new post tagged well afterward keeps the site’s information architecture from decaying again at the same rate. For a site with several thousand posts and years of inconsistent tagging behind it, doing this in one sitting isn’t realistic, a more sustainable approach is tackling the audit in batches, starting with the highest-traffic tag archives first, since fixing those delivers the most visible benefit for the effort spent, then working down through progressively lower-traffic tags as time allows.
Tags versus categories: a boundary that gets blurred constantly
A recurring source of tag sprawl is using tags to do a category’s job. If “Travel,” “Recipes,” and “Reviews” exist as both categories and, separately, as tags applied inconsistently across posts, that’s redundant structure doing the same job twice, confusingly. A clean rule of thumb: categories answer “what section of the site does this belong to” (and a post should generally live in one, or at most a small handful, of categories); tags answer “what specific, cross-cutting topics does this post touch” (and can be more numerous and more loosely applied). If a term could plausibly serve as a category, broad, applies to a large chunk of the site’s overall content, rarely changes, it belongs there, not duplicated as a tag.
Tags and SEO: what’s actually true versus what’s outdated advice
A lot of the “use more tags for SEO” advice still circulating online dates back to an earlier era of search engine behavior, and treating it as current is part of why over-tagging persists. What’s actually true today: a well-organized tag structure helps internal linking, which genuinely does support SEO by helping search engines understand how content on a site relates to itself and by keeping visitors on the site longer through relevant cross-links. What’s not true, or at least badly overstated: that tags themselves function as a significant direct ranking signal, or that more tags straightforwardly means more search visibility. Search engines have gotten considerably better at recognizing thin, auto-generated archive pages for what they are, and Google’s guidance on doorway pages and low-value content has, if anything, made it riskier rather than safer to generate large numbers of near-empty tag archives purely to create more indexable URLs.
The practical takeaway: tag for genuine organizational value first. Any SEO benefit that follows is a byproduct of doing that well, not something to chase directly by maximizing tag count.
A worked example: tagging one post from scratch
Take a hypothetical post titled “How to Meal Prep Chicken for the Week (5 Easy Methods)” on a general food blog that also covers baking, restaurant reviews, and kitchen gear.
Working through the process above: the post’s genuinely distinct topics are meal prep, chicken (as a specific protein-focused sub-topic, since the blog covers multiple proteins across other posts), and batch cooking. A fourth candidate, “weeknight dinners,” is tempting to add but on reflection overlaps heavily with meal prep for this particular blog’s existing tag set, checking the site’s tag list first reveals “meal prep” already covers that ground for most of the blog’s existing posts, so adding a near-duplicate would just fragment the archive. A fifth candidate, “high protein,” genuinely applies and isn’t redundant with anything else already in use, so it stays.
That leaves four tags: meal prep, chicken, batch cooking, high protein. Not the “5-10” the generic rule suggests, and not padded to hit a number, four tags that each represent a real, reusable topic thread with enough existing and future content to make the corresponding archive page worth visiting.
Common tagging mistakes worth checking for specifically
- Capitalization and punctuation inconsistency. “Meal Prep,” “meal prep,” and “Meal-Prep” can register as three separate tags in WordPress if entered inconsistently across different posts and different authors, splitting what should be one unified archive into three weak ones.
- Tagging with the post title’s exact keywords instead of underlying topics. A post titled “10 Best Budget Laptops for Students in 2026” doesn’t need a tag matching that exact phrase, the actual reusable topics are “budget laptops” and “student tech,” which will apply cleanly to future posts in a way the exact original title phrase won’t.
- Letting different authors on a multi-author site tag independently with no shared reference. Without a documented, shared tag list (even a simple spreadsheet), each writer tends to invent slightly different tags for the same underlying topics, and the fragmentation compounds post by post.
- Never revisiting tags after initial publication. A site’s topic focus shifts over years of publishing, and tags created early on for a narrower blog often stop making sense as the site’s scope broadens, periodic review catches this drift before it becomes unmanageable.
Making tag archive pages actually worth visiting
Beyond getting the tag count and consistency right on individual posts, the archive page a tag links to matters in its own right. A default WordPress tag archive is just a chronological list of post excerpts with the tag name as a heading, functional, but thin. A few themes and plugins allow adding a short descriptive blurb at the top of a tag archive page, which both helps human visitors understand the collection at a glance and gives search engines actual unique content on that page beyond the aggregated excerpts, which meaningfully improves how that page is likely to be treated compared to a bare, undifferentiated list.
What this looks like for different blog types
A single-topic niche blog (a site exclusively about houseplants, say) will naturally converge on a smaller, tighter tag vocabulary, maybe 30-50 tags total across the whole site, each used across a healthy number of posts, because the topic space itself is narrower. A broad multi-topic blog covering several distinct subject areas will naturally need more tags to do the same organizing job, simply because it’s covering more conceptual ground, but the same discipline about avoiding one-off, orphaned tags applies regardless of the blog’s breadth. The absolute tag count matters far less than whether every tag on the site is pulling its weight by connecting a meaningful cluster of related content.
Tags in RSS feeds and syndication
One overlooked practical effect of tags: many RSS readers, content aggregators, and some newsletter tools let subscribers filter or route content by tag rather than by full-post subscription. A reader who only wants “meal prep” content from a broad food blog, rather than everything the blog publishes, may rely on a tag-specific RSS feed to get exactly that subset, WordPress generates these automatically at a predictable URL pattern for every tag without any extra setup. This is a small, easy-to-miss benefit of consistent, well-organized tagging that has nothing to do with search rankings at all, and it’s one more reason sloppy or fragmented tags quietly cost a site more than the on-page tag count suggests.
The bottom line
Tag count isn’t the metric that matters, tag usefulness is. A post should carry however many tags represent genuinely distinct, specific topics it covers, checked against tags that already exist on the site rather than creating near-duplicates, and skipped where a topic is too narrow to ever gather more than one post under it. Treating “5-10 tags” as a rule to hit on every post, regardless of what the post actually covers, is how sites end up with bloated tag clouds full of dead-end archive pages that help nobody, readers or search engines. The next time a post is ready to publish, skip the mental checklist of “did I hit ten tags yet” and ask instead whether each tag being added would genuinely help a reader find more of what they just enjoyed. That single question does more for a site’s long-term organization than any fixed number ever will.