01

Define the website’s business role

A website can attract organic demand, qualify enquiries, support sales, serve customers and partners or strengthen employer branding. Prioritise these roles and specify measurable actions: enquiries, calls, downloads, registrations, purchases or support requests.

02

Map audiences and journeys

For each segment, describe the task, decision criteria, objections, expertise and devices. Map the entry query or channel, information needed and intended action. Navigation should follow these journeys, not the reverse.

03

Prepare structure and content

List services, solutions, industries, case studies, articles, documents, vacancies and support sections. Identify available copy, photography, video and information owners. For a large site, define page types and mandatory fields early so content is managed systematically.

04

Specify SEO and migration requirements

Before redesign, export existing URLs, traffic-driving pages, metadata, files, structured data and inbound links. Require URL preservation or an exact 301 redirect map. Specify regions, languages, search priorities and expert-content topics.

05

Describe functionality and integrations

Assess catalogues, filters, search, forms, accounts, payments, chat, maps and calculators alongside CRM, ERP, telephony, email and APIs. Name each system’s owner, available integration methods and data to exchange.

06

Agree platform and operational requirements

Specify the CMS, such as MODX, editor roles, training, hosting, domain, backups, SSL, updates and support. Separately define personal-data handling, accessibility, performance and post-launch development.

07

Prepare acceptance criteria

Before publication, test responsive layouts and overlaps, forms, integrations, speed, metadata, canonical URLs, sitemap, robots rules, redirects, analytics, social previews and editorial workflows. This makes launch a controlled process.