Audit the website before redesigning it

A new visual treatment can address inconsistent imagery or typography. It cannot by itself explain a confusing offer or repair an unclear navigation structure. Start the redesign by identifying where each problem originates.

Walk through real visitor tasks

Ask someone unfamiliar with the site to find a product, check delivery information, locate relevant evidence and make contact. Test entry from a search landing page as well as the homepage. Record observable difficulties rather than treating internal preferences as user research.

• Check content accuracy and ownership.
• Review connections between products, industries and cases.
• Try menus, tables and forms on a phone.
• Record which updates require developer support.

Inventory the content

List URLs, titles, owners, review dates, source material and proposed actions. Include downloads and legacy campaign pages. Mark each item for retention, consolidation, revision or removal, with a reason. Low traffic alone does not make a credential or reference page unnecessary.

Plan migration before removal

Create a destination map for addresses that will change. Have the implementation team verify redirects, downloads, internal links, forms and analytics in a test environment. Keep backups, named launch owners and a workable recovery process.

Prioritize testable outcomes

Rank issues by business impact, supporting evidence and effort. Give each priority an acceptance task, such as finding a relevant case and inquiry route from a product page. Document uncertainty where analytics or research are unavailable.