A category called “Experimental” can hold nearly every post on an experimental music blog and still tell a visitor very little. Its size makes it look established, but someone looking for tape-label interviews, field recordings, or close listening notes must sift through the whole archive. A useful category does more than collect posts: it gives readers a recognizable way into them.
Category names appear in navigation, on article pages, and above archive listings. Each appearance promises that a click will lead somewhere more specific than the site as a whole. Before adding a category, keeping one, or retiring one, test that promise from the reader’s side. Is it clear what belongs there? Will the posts meet that expectation?
Start with the job a category needs to do
A category groups articles around a subject or editorial approach that can sustain an archive. On a music site, “Field Recordings” might gather reviews, interviews, and listening essays in which recording an environment is central. “Interviews” groups by format instead, regardless of musical subject. Either approach can work if the distinction is deliberate and applied consistently.
A tag is often better for a narrower connection: a format, technique, or theme that cuts across categories without needing a place in the main navigation. A series groups pieces conceived as a sequence, often under a shared title or premise. And a worthwhile subject can be covered in a standalone article without becoming a category, tag, or series. Turn every interesting word into a category and readers face a menu of near-empty destinations.
Try completing one plain sentence: “This category helps readers find ______.” Avoid using the category name or a phrase as broad as “related content.” For “Cassette Culture,” the answer might be “reporting and criticism about tapes, the labels that release them, and the practices of making and circulating them.” That gives an editor grounds to include one post and exclude another. If the answer describes everything the publication covers, the category is probably too broad.
Test the label against the posts already published
Read the proposed archive as a visitor would; don’t stop at the post count. Open the first several entries and compare their subjects with the label. “Drone” is misleading if most posts mention sustained sound only in passing. Several substantial pieces on drone practice, on the other hand, may justify a category even while the archive is modest.
A quick audit can expose a weak label without turning the exercise into a traffic report:
- Make a candidate list. Record the titles you would put in the category today. Leave out posts that need strained explanations to fit.
- Write an inclusion rule. Say what must be central to a post, rather than merely present somewhere in it.
- Check the archive view. Read the titles and opening lines in sequence. Would someone who clicked that label recognize a common purpose?
- Mark the exceptions. Note posts that belong elsewhere and relevant posts the current system makes hard to find.
- Try the name aloud. If editors need a private definition to apply it, readers may struggle too.
Count is a constraint, not a verdict. Two closely related, substantial pieces can make a promising archive if the publication has a credible reason to develop it; twenty loosely connected posts can make a poor one. A single article is usually better served by an article link, a tag, or a category kept out of prominent navigation until it has more to offer. What matters is whether the destination is useful now, not whether the number looks impressive.
Look for a reader’s route, not an editor’s filing habit
“Reviews” may feel like an obvious category to an editor because reviews follow a familiar production workflow. A listener might want to explore electroacoustic work across reviews, essays, and interviews. Neither route is inherently better. The publication has to decide which ones deserve space in its navigation.
Good routes answer questions readers might actually have: Where is the writing about tape circulation? Which pieces treat field recording as a practice? Where are the long-form interviews? “Miscellaneous,” “Updates,” or a catch-all for posts that fit nowhere else may describe how an editor files work, but they give a reader little reason to click.
Consider an essay about an artist using environmental recordings, released on cassette, and discussed in an interview. All three connections may matter, but that doesn’t mean the piece needs three categories. Choose its primary category by what it chiefly examines. Add a secondary category only if the site genuinely supports another main route; tags and contextual links can carry the remaining connections.
This matters especially in a small publication. If nearly every post sits under “Noise,” “Ambient,” “DIY,” and “Experimental,” those archive pages start to look alike. After clicking two labels and finding nearly identical lists, a reader has little reason to trust either one.
Check whether neighboring categories are distinguishable
Write a one-sentence scope for each category that might overlap with the proposed one. “Cassette Culture” could cover production, distribution, collecting, and releases in the cassette medium. “DIY Practice” might cover independent methods beyond tapes, such as self-organized performances, handmade instruments, or small-scale publishing. They overlap, but they need not mean the same thing.
If the scopes cannot be separated without arbitrary rules, merge the categories or narrow one. “Ambient” and “Drone,” for instance, can point to different listening concerns, but the genre names alone won’t draw the editorial boundary. One site might separate writing centered on sustained-tone composition from broader writing on ambient music. Another, with only a handful of relevant posts, might keep one category and use tags for the finer distinction. Test either rule against actual articles before putting both labels in the menu.
Inspect the destination, not only the name
Even a clear label can lead to a poor archive. Vague article titles may hide what the pieces cover; loosely related updates may bury older work. Browse the category page on a phone as well as a larger screen. Check the first few entries, then scroll down. Are the articles substantially related? Can a visitor tell a review from an interview or an explanatory piece?
A short description can clarify the scope, particularly when a familiar musical term has several meanings. Describe what the archive contains rather than making a sweeping claim about a genre or scene. “Reviews and essays on environmental sound used as recording material” tells a reader more about a field-recording category than a grand statement about the form’s significance. A description cannot fix an incoherent archive, but it can make a coherent one easier to enter.
Check what happens when a post leaves the top of the list, too. If the category works only while its newest article is visible, its titles may need work or its inclusion rule may be too loose. On a site that publishes infrequently, older entries are often the substance of the archive, not a flaw to hide. Their relevance should be apparent to someone who doesn’t know when or why they were published.
Use evidence carefully
Reader behavior can reveal friction, but no single number settles a category’s value. Visitors who click through to articles may be finding what they need. Visitors who leave immediately may have been misled by the label—or may have found their answer at a glance. Small independent sites may not get enough visits for fine distinctions to mean much.
Repeated requests and conversations can be more revealing. If readers keep asking where the cassette-label coverage lives, try making that route easier to find. If contributors regularly disagree about where to file posts, the boundary may be unclear. And if a category sits in the menu but editors rarely use it, inspect the archive before giving it more prominence.
Search terms, when available, offer clues rather than instructions. Repeated searches for “interviews” might mean visitors cannot spot an existing interview archive; they do not prove that every interview needs a top-level category. Weigh those signals against the posts you have and the publication’s editorial direction. A small, carefully defined field-recording archive may be worth keeping even if a broad reviews archive gets more visits. Distinctiveness and ease of finding work matter alongside volume.
Decide what to do with an existing category
An audit should end with a specific editorial action. Four outcomes are common:
- Keep it. The label is clear, the posts fit, and the archive offers a recognizable reading path. Document its scope for future editors.
- Rename it. The collection is coherent, but the name obscures it. Check how the label appears on article pages and in navigation before changing it.
- Merge it. Two archives promise essentially the same route. Choose the clearer scope, then review the combined posts for outliers.
- Retire or demote it. The category has too little distinct purpose to justify its position. Move suitable posts elsewhere and consider a tag if the narrower connection is still worth preserving.
Take care with changes to existing URLs. Depending on the publishing system, renaming or removing a category may change the archive address, post addresses, or both. Check the site’s settings first. If addresses change, preserve useful old destinations with appropriate redirects, then review navigation and existing links. Don’t leave readers at an empty page.
Retiring a category does not mean its subject was unimportant. “Cassettes” might hold two valuable pieces that would be easier to find under a wider “Independent Releases” archive, with a cassette tag preserving the narrower connection. Equally, “Independent Releases” might be so vague that a carefully bounded cassette category makes more sense. Judge the destinations readers get, not the apparent weight of a larger menu.
Set a boundary future posts can follow
Category usefulness can erode quietly. An editor adds a marginal post to make an archive look active; later, that post becomes a reason to interpret the category more broadly. Keep a short scope note with the editorial documentation: its purpose, two or three kinds of posts that belong, and one likely false match.
For “Field Recordings,” the note could include a close analysis of location sound used as primary material and an interview substantially about recording environments. It could exclude a review that briefly mentions rain audible between tracks. That exclusion keeps the archive from turning into a list of passing references.
Revisit the note when a genuinely awkward post appears, not whenever a piece has more than one subject. If several strong articles repeatedly fall between two categories, revise the boundary. If only one does, file it by its primary emphasis and make the secondary connection visible within the article. A single exception rarely needs a new category.