WordPress Tags SEO

Categories are the chapters of your site. Tags are the index at the back. If your site is about cooking, categories might be 'Baking', 'Grilling', 'Vegan'. Tags go narrower: 'sourdough', 'cast iron', 'tofu'. A post about sourdough bread belongs in 'Baking' and could be tagged 'sourdough' and 'wholemeal'. That is it – two tags. Do not treat tags as a keyword dump. Each tag should group multiple posts. If you create a tag that will only ever appear on one post, you are building a thin archive that offers no search value. I see sites with 50 tags per post. That is noise. Stick to 2–5. The SEO benefit of tags is internal linking between related posts. When a user clicks a tag, they see a curated list of articles, not a random assortment. That helps dwell time and topic authority. But only if the tag page has decent content – at least a few paragraphs of description, not just a list of titles. On one client site I reduced tags from 40 per post to 3. Crawl budget improved by roughly 30% and the thin archive pages stopped appearing in Search Console's 'Excluded by noindex' list. Some argue that tags are redundant if you already have good internal linking. I disagree because tags give users a browsing interface that categories cannot provide – categories are too broad for micro-topics. If you are not willing to write a short description for each tag archive, seriously consider setting it to noindex.

This matters most when you run a content-heavy site – say 200+ posts across several categories. Tags help you create topic clusters without adding more categories. For example, I run a tech blog with categories 'SEO', 'Content', 'Design'. Under 'SEO', I tag posts with 'technical seo', 'keyword research', 'link building'. Each tag archive becomes a hub of related articles. But only if each tag is used on at least three posts. A tag with one or two posts creates a weak page. My rule: if a tag has fewer than three posts, I set its archive to noindex using Yoast SEO settings. That saves crawl budget for pages that matter. Edge case: if you use a tag cloud widget, it often links to every tag archive, including thin ones. That wastes crawl allocation. Disable the cloud or filter it to show only indexable tags. If you have a large tag count, run a [technical SEO](/technical-seo/) audit to identify thin archives. Another scenario: you are building a site with [website structure](/website-structure/) that relies on tag-based navigation. Then each tag archive must be a compelling landing page with unique content. If you cannot write that, tags are not for you. In my own site, after auditing tags I trimmed from 150 tags to 30. The number of indexed pages dropped by 40% but organic traffic to tag archives increased by 15% because the remaining pages were stronger.

When I started this blog, I slapped 10+ tags on every post. I thought: more tags = more visibility. Wrong. I ended up with 400 tag archives, most with one or two posts. Google indexed them but never ranked them – they were thin, duplicated content. I also created synonyms: 'SEO tips', 'SEO advice', 'SEO best practices'. All the same. I changed my mind after I ran a [duplicate content](/duplicate-content/) check and saw 20 near-identical tag pages. My fix: I merged all synonyms into one tag per concept. I also set a policy: never create a tag on the fly. I maintain a controlled vocabulary of 20 tags in a spreadsheet. Every new post gets checked against that list. If a proposed tag does not exist, I either use an existing one or decide if the new one will be used on at least three future posts. Another mistake: I left all tag archives indexed. Now I noindex archives with fewer than three posts. I also added a [canonical tag](/canonical-tag/) pointing to the parent category for tag archives that add no value. The biggest lesson: tags are not for keywords. They are for grouping content. If you treat them like keyword stuffing, you hurt your site. I still fall into the trap sometimes – I recently created a tag 'AI writing' and had to merge it into 'AI content' after two posts. I should have thought ahead. For more on managing taxonomies, see my notes on [WordPress SEO](/wordpress-seo/) and [robots.txt](/robots-txt/) blocking.