Register custom taxonomy

Register a Services taxonomy for the Projects post type so each case study can be categorized by service offering. Create human-friendly labels like Design, Development, and Strategy, make it hierarchical so agencies can add sub-services, and ensure the taxonomy appears on the project editor and in the REST API. Also add a widget or block that lists service terms with counts for the sidebar.

Before I expose the taxonomy to the client, make it approval-friendly. Show a proposed list of top-level terms and where they will appear on the site, flag overlapping terms that will confuse reviewers, and recommend URL patterns and term descriptions so procurement or product teams can approve quickly. Call out where changing term slugs later would break links.

The client briefing just used ‘UX’, ‘Design’, and ‘User Experience’ interchangeably and the content team is now unsure which taxonomy terms to use. I manage categorization and the head of product will sign off. I’m afraid choosing the wrong canonical names will force a migration later. What’s the best short process to settle on canonical terms with stakeholders and a safe interim mapping to avoid broken URLs?

Across our sites, small variations of service taxonomies multiply and make cross-site searching, reporting, and reuse a nightmare. I oversee three agency sites and want to simplify so terms are consistent and discoverable. Which two governance rules should I impose and how do I onboard content teams to follow them? Provide an implementation checklist and a one-paragraph rationale to share with leadership.