{"id":430,"date":"2026-11-10T10:00:00","date_gmt":"2026-11-10T09:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=430"},"modified":"2026-11-10T10:00:00","modified_gmt":"2026-11-10T09:00:00","slug":"website-url-structuur-beheren","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/choosing-a-url-structure-that-survives-reorganisations\/","title":{"rendered":"Choosing a URL structure that survives reorganisations"},"content":{"rendered":"

Web addresses are often chosen as a page is created. Department names, years and temporary campaign terms then quietly enter the URL structure. The next reorganisation makes those addresses illogical. Choose a few simple rules based on lasting content and visitor tasks. A good structure need not reflect every internal division.<\/p>\n

Name the subject that will remain recognisable<\/h2>\n

An address should help explain the information behind it. Prefer a recognisable subject or service term. An internal project code may help staff but tells new visitors little. A department name may also be too temporary if responsibilities shift regularly.<\/p>\n

In a fictional example, a maintenance service moves from the \u201cTechniek Noord\u201d department to a national team. An address based on the service remains meaningful. One containing the old department requires a change or explanation unrelated to the visitor's task. This does not mean place names are never useful; they belong in the content when location genuinely distinguishes it.<\/p>\n

Separate navigation from the web address<\/h2>\n

A page can be reached from several menus or overviews without needing different addresses. Moving a link to another section need not automatically change its URL. Discuss with the builder how the chosen website setup supports this and which dependencies exist.<\/p>\n

Agree the depth too. A long sequence of subfolders may precisely reflect today's organisational structure but complicate changes. A completely flat structure may instead create naming conflicts. Choose a level that distinguishes content without embedding every editorial category in the address.<\/p>\n

For developing websites<\/a> this is a content decision with technical consequences. Do not record the rules only in a development note. Editors must be able to determine the right address for a new page.<\/p>\n

Record exceptions and changes<\/h2>\n

A practical agreement covers naming, spelling, use of years and an owner for changes. Years make sense for genuinely time-specific publications, less so for service pages that stay current annually. Campaigns can receive short, recognisable addresses with an advance decision about their destination afterwards.<\/p>\n