
What a tag page actually is
A tag page is an auto-generated archive that your CMS creates the moment an author types a tag into a post. In WordPress it lives at /tag/whatever/ and lists, usually in reverse chronological order, every post that carries that tag. Categories are the site's fixed skeleton; tags are the loose, freeform layer on top. One post typically sits in one category but can carry five, ten, or (in badly run newsrooms) thirty tags.
That freeform quality is exactly why tag pages are both useful and dangerous. Nobody plans them. They accumulate. I have audited publisher sites where the article count was 40,000 and the tag archive count was 90,000. Nobody decided to build 90,000 pages. They just happened, one careless keystroke at a time.
Why tag pages matter for SEO
Three real reasons, in order of importance:
1. Topical authority. Google has publicly confirmed that topic authority is a ranking system for news content. A well-built tag page proves depth of coverage on a subject: dozens of dated articles, by named authors, going back years. The SEO for Journalism piece this entry links below makes the point well: tag pages rarely earn many clicks themselves, but they demonstrate to search engines that you are the outlet that has covered this entity continuously. The New York Times curates top stories on its topic pages, The Athletic builds player pages with reciprocal links from articles, and The Globe and Mail surfaces trending topic pages from its homepage. None of those are traffic plays first; they are authority plays.
2. Internal linking and crawl paths. A tag page is a hub. It gives old articles a persistent link from a page that keeps getting fresh links itself. On big sites, tag hubs are often the only realistic way deep archive content keeps receiving any internal PageRank at all.
3. Long-tail rankings, occasionally. Some tag pages do rank, usually for entity queries where no single article is the obvious answer. That is a bonus, not the goal. If you justify tag pages purely on their own traffic, most of them fail the test.
The failure mode: archive bloat
Here is what I actually see in crawls. Tags used once, ever, producing an archive with a single teaser and 90% boilerplate. Near-duplicate tags (/tag/core-web-vitals/, /tag/cwv/, /tag/web-vitals/) splitting the same cluster three ways. Paginated tag series stretching to page 40 with nothing but titles. Multiply that across years and your index becomes mostly archives, which means Google spends its crawl on pages you do not care about, and its quality systems evaluate a site that is majority thin content. When the "Crawled, currently not indexed" bucket in Search Console is full of tag URLs, that is Google telling you it looked and decided the pages were not worth keeping.
Tags, categories, and curated topic hubs
| Aspect | Category page | Tag page | Curated topic hub |
|---|---|---|---|
| Created by | Site architecture decision | Authors, ad hoc | Editors, deliberately |
| Typical count | 5 to 30 | Hundreds to tens of thousands | Dozens, hand-picked |
| Unique content | Sometimes an intro | Usually none | Intro, curated top stories, FAQs |
| Should it be indexable? | Usually yes | Only if it earns it | Yes, that is the point |
| SEO role | Site structure, navigation | Entity coverage, internal links | Topical authority flagship |
How to audit your tag pages
Step by step, the way I run it:
- Crawl the site with Screaming Frog and filter URLs matching your tag path (
/tag/,/topics/,/etiqueta/, whatever the CMS uses). Export the list with word count, inlinks, and indexability status. - Pull the tag-to-post counts from the CMS. In WordPress, the Tags screen shows post counts per tag; sort ascending and marvel at how many sit at 1.
- Cross-reference Search Console. In the Page indexing report, check how many tag URLs are indexed versus "Crawled, currently not indexed". Then check the Performance report filtered to the tag path: if 10,000 indexed tag pages produced 40 clicks last year, you have your answer about their standalone value.
- Check server logs or the Crawl Stats report to see what share of Googlebot hits goes to archives. On bloated sites it is embarrassing.
Fixing it
Run every tag through the decision path in the diagram above. Tags with real post volume and planned future coverage get kept and upgraded: write a short intro, pin the cornerstone pieces at the top, and link to the tag page from relevant articles and, for your money topics, from the homepage. Duplicate tags get merged, with posts retagged and the losers 301-redirected to the survivor. Everything else gets noindexed or deleted outright, and deleted tags should return 410 or redirect somewhere genuinely relevant, not to the homepage.
Just as important: fix the input. Give authors a controlled vocabulary or at least a tagging guideline (existing tags first, three to five per post, no single-use tags without editor sign-off). Otherwise you will run this same cleanup again in eighteen months.
- Create tags only for topics with consistent, ongoing coverage
- Curate your important tag pages: intro copy, pinned top stories
- Link tag hubs from articles and the homepage where they matter
- Merge duplicate and near-duplicate tags with 301s
- Give authors a tagging guideline and enforce it
- Let every author invent tags with zero oversight
- Index one-post tag archives and hope for the best
- Blanket-noindex all tags on a news site; you lose real authority signals
- Judge tag pages purely on their own clicks
- Redirect deleted tags to the homepage in bulk
FAQ
Should I just noindex all tag pages?
Do tag pages rank on their own?
How many tags should a post have?
Are tag pages duplicate content?
Should paginated tag pages be indexable?
I run full technical audits that quantify exactly this: how many tag and archive URLs you have, which ones earn their place, and a prioritized cleanup plan.
Source: https://www.seoforjournalism.com/p/tag-topic-pages-news-seo
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.







