How to Organize Website Content Before Design Starts

List the pages, documents, service descriptions, FAQs, articles and other material that already exist. Mark what is current, outdated, duplicated, incomplete or worth preserving. This prevents useful information from disappearing simply because the new design looks different.

Organize topics around the questions visitors are trying to answer: What does the business do? Which service fits my problem? How does the process work? What makes the work credible? How do I start?

Internal department names may be useful to the business, but they are not always useful navigation labels for customers.

A topic usually deserves a dedicated page when it has a distinct audience, search intent, service, process, or amount of useful supporting detail. Thin pages that repeat the same message should often be combined into something stronger.

Decide the main navigation, parent pages, child pages and supporting article relationships before polishing individual sections. Once the hierarchy is clear, page design becomes a question of presentation rather than discovery.

Service hubs should point to detailed capabilities. Articles should link to the service they support. Deep pages should provide routes back to broader sections. Planning these relationships early prevents orphaned content later.

A useful architecture should accept new pages without forcing the entire menu to be rebuilt. Create broad hubs where appropriate and let deeper pages live underneath them. The goal is a system that becomes more useful as content is added.