Guide SEO titles and snippets · 9 of 9
Category and Tag Page Title Tags: A Pattern That Scales
Title category and tag pages with patterns that scale, write archive descriptions, handle pagination, and decide which archives to index.
Key takeaways
- Build category and tag titles from a template pattern.
- Use a short archive intro as the meta description.
- Noindex thin tags and sorted or filtered lists.
Category and tag pages are the archive pages your CMS builds for each topic: a blog category, a product category, or a tag. They are easy to forget because nobody writes them by hand. So their title tags often come out as “Archives | Brand” or just the tag name. This guide gives you title and description patterns for category and tag pages that scale across hundreds of archives, plus a rule for which ones to index.
It ends with a template table you can give to your developer. For the general rules on writing titles and descriptions, see the guide to SEO titles and meta descriptions.
Why category and tag pages need a pattern
A site may have 20 categories and 400 tags. You cannot write each title by hand, and you should not need to. A good pattern builds a clear title from the archive’s name and type.
Without a pattern, the template often fills in a generic line. Google’s guide to influencing title links warns against vague titles and repeated boilerplate text. “Archives | Brand” on 400 pages is both. The guide to duplicate title tags explains how to find these groups and fix them by template.
Name what the archive contains
The title should tell people what they will find on the page. That means the topic plus the kind of content:
- A blog category: “[Topic] Guides and Articles | Brand.”
- A product category: “[Product Type] | Brand,” or “[Product Type] for [Use] | Brand” when the category is specific.
- A tag: “[Tag Name] Articles | Brand.”
Avoid labels like “Category:” or “Tag:” at the start. They are CMS words, not search words. Nobody searches for “Category: Coffee.”
On software and SaaS sites, blog archives sit next to product pages. Keep the patterns distinct so an archive never looks like a product page. The guide to SaaS title tags has the product-side patterns.
Write descriptions from a short archive intro
The best category description comes from a short intro at the top of the archive. Two or three sentences that say what the category covers and who it is for. Your template can then use that intro as the meta description.
If you have no intro, a pattern still works: “Read [number] guides about [topic], from [subtopic] to [subtopic].” Only use a number if the template can count posts and keep it current.
An archive with no intro and no description may get a snippet built from post titles or other page text. That can look messy. Adding a real intro is usually the better fix than a snippet control. The guide to nosnippet and snippet controls explains when those controls make sense.
Handle paginated archives
Large archives split into pages: page 1, page 2, and so on. Google’s pagination best practices say pages in a paginated sequence can use the same titles and descriptions. Google tries to recognize the sequence. So you do not need a unique title for page 7.
The same guidance asks for a few other things:
- Give each page its own URL, such as
?page=2or/page/2/. - Do not set page 1 as the canonical for every page. Each page gets its own canonical URL.
- Link pages in order with normal
<a href>links. - Do not use
#fragments for page numbers.
Some teams still add “Page 2” to the title so people can tell pages apart in a browser tab. That is fine, and it is optional.
Decide which archives to index
Not every archive deserves to be in search results. A category with 40 posts and a clear intro can be a useful landing page. A tag with one post is a thin page that repeats that post.
Use a simple rule:
- Index categories and tags with enough posts to be useful and a clear, distinct topic.
- Noindex tags with very few posts, near-duplicate tags, and archives that only sort or filter another list.
To keep an archive out of results, use the noindex rule from Google’s robots meta tag specification. Do not block it in robots.txt if you want the noindex rule to be read. Google’s pagination guide also suggests keeping filter and sort variations out of the index.
Set the threshold that fits your site, write it down, and apply it in the template. Then you do not need to decide page by page.
Match the breadcrumb and the title
Archive pages often show a breadcrumb trail, such as Home › Blog › Coffee. The category name in the breadcrumb should match the one in the title. If you mark up breadcrumbs, the same name appears in the structured data too. The guide to breadcrumb schema explains that markup.
Worked example: a blog with 12 categories and 300 tags
Fictional example. An imaginary coffee blog crawls its archives. All 312 archive pages have the title “Archives | Bean Notes.” The team changes the template:
- Categories now use “[Category] Guides and Articles | Bean Notes,” such as “Cold Brew Guides and Articles | Bean Notes.”
- Each category gets a two-sentence intro, used as the meta description.
- Tags with fewer than five posts are set to noindex. That covers 260 tags.
- The remaining 40 tags use “[Tag] Articles | Bean Notes.”
Two template changes and one rule fixed all 312 archive titles. The threshold of five posts is the team’s own choice, not a Google rule.
Where DEX fits
DEX connects search research, content planning, article writing, and publishing on the connected site. Planning your categories as real topics makes their archive pages easier to title and describe.
Template table for category and tag pages
| Archive type | Title pattern | Description pattern | Index decision | Fictional example |
|---|---|---|---|---|
| Blog category | [Category] Guides and Articles | Brand | From the archive intro: what it covers and who it is for | Index if it has a clear topic and enough posts | Cold Brew Guides and Articles | Bean Notes |
| Product category | [Product Type] | Brand | Main product types, key choices, and shipping or care details stated on the page | Index | Travel Mugs | North Cup |
| Tag with many posts | [Tag] Articles | Brand | “Articles about [tag], including [two subtopics].” | Index | Grinder Articles | Bean Notes |
| Tag with few posts | [Tag] Articles | Brand | Same pattern | Noindex below your threshold | Moka Pot Gaskets Articles | Bean Notes |
| Paginated archive page | Same as page 1, optional “Page N” | Same as page 1 | Index, with its own canonical URL | Cold Brew Guides and Articles, Page 2 | Bean Notes |
| Sorted or filtered list | Same as the base archive | Same as the base archive | Noindex | Travel Mugs (sorted by price) | North Cup |
FAQ
Do paginated category pages need unique titles?
+
No. Google says pages in a paginated sequence can share titles.
Should tag pages be indexed?
+
Index tags with enough posts and a clear topic; noindex thin ones.
What should a category page description say?
+
What the archive covers and who it is for, ideally from a short intro.
Sources
Dex SEO is an AI SEO agent for small businesses. Every article here is planned from search data, drafted by Dex, fact-checked against the sources it cites, and reviewed by the team before it is published.
How this article was made: planned and drafted by Dex from search data, fact-checked by Dex (4 claims checked), then approved by the Dex SEO team.