SKR Tips logo SKR TipsWebsite tips that actually work
WordPress

WordPress Custom Taxonomy for Game Patch Versions

The most common message our wiki got was never about strategy. It was some version of: is this still right after the update?

WordPress admin post list with a patch version column beside game guide titles

The most common message our wiki got was never about strategy. It was some version of: is this still right after the update? We had the patch number written in the first line of every guide, which helped exactly nobody, because readers arrive from search on one page and have no way to ask the site which other guides were revised for the same patch. Our only answer was a search box that matched the literal string 4.2 across 300 pages, including the ones where 4.2 was a damage number.

So we did what most fan sites do and made patch tags. Within a season the tag cloud had 47 entries, 31 of them patch numbers, and the content tags that readers actually used were buried among them. That is the point where a custom taxonomy stops being an architecture hobby and starts being the cheapest fix available. It took me an afternoon, most of which was spent cleaning up the tags I should not have created.

Why patch numbers do not belong in your tags

Tags and patch versions answer different questions. A tag says what a guide is about. A patch version says when a guide was last true. Mixing them means your tag archives become a pile of two unrelated axes, and the reader browsing for boss fights has to skip past 4.0.1 and 4.1 to find them.

There is a crawl cost too. Each patch tag generates an archive page, and most of ours held one or two posts. Search Console listed 24 of those archives as crawled and not indexed within six weeks, which is the expected outcome for a page with two links and no text on it. None of that hurt us badly, but it was noise in a report I was using to find real problems.

The deeper reason is that a separate taxonomy gives you a separate URL space and a separate admin column. Once patch versions live under their own prefix, you can list every guide written for the current patch on one page, and you can sort the admin post list by patch to see what still needs reviewing. Neither is possible when the information is a tag or a sentence in the body text. For the general rule on the two built-in options, our piece on choosing between categories and tags covers where each one earns its place.

Registering the taxonomy without touching your theme

Put the code in a must-use plugin, not in your child theme functions file. Create wp-content/mu-plugins/patch-taxonomy.php and WordPress loads it automatically with no activation step and no way for a theme switch to take your taxonomy with it. I learned this the slow way when a theme change made 300 posts look like their patch data had evaporated. The terms were still in the database the whole time, just orphaned from any registered taxonomy, so nothing would render them.

Call register_taxonomy on the init hook with a name under 32 characters. The arguments that actually change your day are these.

ArgumentSet it toWhat it buys you
hierarchicalfalseA tag-style box with autocomplete, which is right for flat version numbers
show_admin_columntrueA patch column in the posts list, sortable, so audits take minutes
show_in_resttrueThe block editor panel appears at all, and the field is scriptable later
rewrite slugpatchArchives land at /patch/4-2 instead of a query string
publictrueTerm archives exist for readers, not only for your admin screens

Flush permalinks once after you add it, by opening the permalinks settings screen and saving. Skip that and every term archive returns a 404 while the taxonomy itself works fine in the editor, which is a confusing twenty minutes if you do not know to expect it.

Name your terms with a sortable format from the start. We used 4.2 and 4.10, and 4.10 sorted before 4.2 alphabetically. Zero padding to 04.02 looks ugly in a URL, so we kept the display names and added a numeric term meta field for ordering. Deciding this before you have 40 terms saves a migration.

You probably do not need a custom post type

The usual advice when someone asks about this is to build a guide post type first, then attach taxonomies to it. I would push back on that for most fan sites. A custom post type means new templates, new archive logic, a migration of existing posts, and a permalink change for every guide you already published, with the redirect work that follows. A taxonomy on your normal posts asks for none of that and delivers the thing you wanted, which was grouping and filtering.

The case for a post type is real but narrow: you need it when guides have a different set of fields from your news posts and you want a different editor experience for each, or when you want guides excluded from the main blog feed entirely. Our wiki never needed either. If you are already running a post type, register the taxonomy against both it and post in the same call, so cross-posted content stays filterable.

If you do move URLs later, handle the redirects deliberately rather than relying on a plugin to guess. We wrote up the method in renaming a wiki page without losing its search traffic.

Making the archives worth a reader's time

An empty term archive that lists three post titles is not useful and will not hold a ranking. Two changes made ours earn their keep. First, add a description to each term, two or three sentences on what changed in that patch, and print it at the top of the archive template. Second, set a floor: terms with fewer than three posts get excluded from the archive listing and from the sitemap until they fill up.

Retiring old terms matters more than creating new ones. After three seasons we had 61 patch terms, and anything older than the previous major version was dead weight. We merged minor versions into their parent, 4.2.1 and 4.2.2 into 4.2, kept redirects from the old archive paths, and the term count dropped to 19. Guides still carried their precise patch in the body text for anyone who cared about the exact build.

One habit to adopt on day one: when you revise a guide for a new patch, remove the old term rather than adding to it. A guide tagged with five consecutive patches tells the reader nothing. A guide tagged with the one patch it was verified against tells them whether to trust it.

FAQ

Will this slow down my site?

Not measurably. Taxonomy queries hit indexed tables, and a term archive is roughly as expensive as a category archive. The cost shows up only if you start querying across several taxonomies at once on a busy page, which is a template problem rather than a taxonomy problem.

Can I convert my existing patch tags into terms?

Yes, and the built-in importer under Tools handles tag to taxonomy conversion for most cases. Back up first, run it on a copy, and expect to fix a handful of terms by hand where the names were inconsistent. Ours had 4.2, v4.2 and Patch 4.2 as three separate tags.

Should patch archives be indexable?

Only the ones with real content on them. We allow indexing for terms with a written description and at least three posts, and block the rest. That split came from watching which archives attracted impressions at all, and the thin ones never did.

What happens to my terms if I remove the plugin?

The term relationships stay in the database and simply stop rendering anywhere. Drop the file back in and everything reappears. That is the main argument for mu-plugins over theme code, since a theme switch has the same effect without warning you.

MO
Matthias Okeke

Matthias ran a clan website and a fan wiki for years before writing about them. He covers the sites gaming communities build, from guides to patch note pages.

More posts by Matthias

More in WordPress

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto