Defining governance rules for new pages and categories
New pages and categories require justification, responsible owners, classification, and a defined lifecycle before they can permanently expand the structure.
For website administrators and UX teams, "Proven Need" and "Clear Classification" are crucial in "Governance for Pages and Categories." The perspective "Structural Governance and Hubs" shows how these two points interact in practice.
Published: 3 min read · Author: Sebastian Geier
Which approval rules prevent unnecessary new pages and taxonomy levels?
New pages and categories are only created via a short, comprehensible request. The purpose, existing alternatives, classification, owner, and review date must be clarified before the technical implementation.
Clear Classification
A unified request captures user needs, alternatives, page type, parental reference, responsible role, and planned review date.
Architecture and subject matter experts jointly assess boundaries, reuse, and impact on navigation and taxonomy.
Approved elements are registered with their owner and lifecycle information; rejected requests are assigned an existing goal or merged.
Responsible lifecycle information
Newly created pages or categories without documented needs, owner, parental reference, or a defined review date.
Structural elements with only one piece of content, no usage, or overlap with existing goals.
Single-Case Structure
Single-Case Structure – A new category is created for a single campaign, but later lacks both sufficient content and a lasting purpose.
Hidden Duplicate – A new page describes the same need as an existing goal because the boundaries were not reviewed before approval.
Approval Without Consequences – The launch is approved, but ownership, review date, and rules for closure remain undefined.
Working Example: “Single-Case Structure”
A team requests a new category for three planned posts. The review shows that all content fits within an existing topic axis; instead of a parallel level, two controlled values are added, and a common review date is set.
Documented Need
Test criterion
Documented Need
The application describes a specific user task or content group and demonstrates why existing goals are insufficient to support it.
Test criterion
Clear Classification
Page type, canonical parent reference, and necessary links are compatible with the architecture model prior to creation.
Responsible lifecycle information A designated role assumes responsibility for content, review, and subsequent merging or removal after a defined deadline.
What needs to be reviewed before and after "Governance for Pages and Categories"
A suitable in-depth resource is available Information architecture for websites with many regionsHow does a website structure scale across many regions without interchangeable page copies?
In addition: Deriving Breadcrumb Markup from the Actual Page Hierarchy.
If you want to practically implement "Governance for Pages and Categories," you can refer to Robust Website Systems This document focuses on "Structural Governance and Hubs" and "Proven Needs."
Conclusion: Governance for Pages and Categories
Good governance prevents structural growth without hindering legitimate content. Clear criteria and accountability throughout the entire lifecycle are crucial.
Sources and Further Information
These primary sources make assumptions, system boundaries, and audit methods for "Governance for Pages and Categories" transparent.
Understanding Success Criterion 2.4.5: Multiple Ways – W3C WAIThe W3C guideline supports verifiable alternative paths and orientation in complex information repositories.
4. Make the service simple to use – GOV.UK Service ManualThe official standard requires simple, consistent service channels tested with actual users.
Key Thesis
An application specifies user needs, demarcation from existing content, page type, parental references, responsible parties, and review deadline. Categories are created only for permanently distinct groups with sufficient assignable content.
What This Is Not About
Governance is not a blanket ban on publication or an additional approval loop without expert decision criteria.
What it's about
It requires documented user needs, clear demarcation, and a responsible lifespan for new structural elements.
Information Architecture & Taxonomy
Create a content map as a binding architectural model.
"Governance for Pages and Categories" includes, as a separate review step, the question: Which fields make a content map more than just a one-off list of URLs?
Information Architecture & Taxonomy
Change URL structures without disrupting the content logic.
Supplements "Governance for Pages and Categories" with a separate decision: How do you change URL paths without losing relationships, rankings, or user entry points?
Insights Overview
All VELUNO Insights at a Glance
Further analyses on Website Systems, digital visibility, and robust working models.
Responsible Lifecycle: Practical Next Step
A streamlined application form can initially be made mandatory for new categories. The first decisions will show which criteria need more examples or clearer definitions.