Should you rebrand before a website redesign?

Brand and website are connected, but they are not the same project

Positioning defines who the business serves, the problem it solves, and why it is a credible choice. Brand identity expresses that position through name, language, visual elements, and behaviour. The website turns those decisions into pages, journeys, proof, interactions, and a working system.

A full rebrand is not required simply because the current site looks dated. Equally, a new website cannot resolve an unresolved audience, offer, or company name through layout alone. Diagnose which layer is actually failing before combining scopes.

Rebrand first when foundational decisions are changing

Complete or substantially progress the rebrand before website design when the company is changing its name, target market, offer architecture, positioning, core message, or visual identity. Those choices affect domains, navigation, page copy, proof, art direction, components, and launch communication.

The brand work should produce enough usable direction for the website team: audience and positioning, message hierarchy, naming, voice, logo assets, colour and typography rules, photography or illustration direction, and examples of digital application. A logo file by itself is not a complete website brief.

Keep the brand when the website is the real constraint

A website redesign can proceed within the existing identity when the offer is understood, the brand remains credible, and the problem lies in structure, content, mobile experience, conversion, accessibility, performance, or technology. The site may still refine digital typography, layout, motion, and component rules without redefining the company.

A focused visual refresh may be included if the identity needs a better digital expression but not strategic replacement. Make the boundary explicit so stakeholders do not expect a complete brand system from a website scope. Review the broader components of a website redesign before estimating.

Run the projects together only with shared decisions and sequencing

Parallel work can shorten the calendar, but only if both teams use the same approved strategy and exchange outputs at defined points. The website team needs stable inputs before finalizing information architecture, copy, and visual design. The brand team benefits from testing the identity against real digital content and interface states.

Name one decision owner and create a combined dependency map. Decide when naming, positioning, message, logo, typography, palette, and imagery become stable enough for website production. Allow time to test the brand on navigation, forms, long-form content, product information, accessibility states, and small screens—not only presentation mockups.

Plan one launch even if there are two scopes

• Define the business change: what is different for customers after launch?
• Separate deliverables: state what belongs to brand strategy, identity, content, website design, and development.
• Map dependencies: identify which brand decisions block pages, copy, or build work.
• Inventory touchpoints: include domain, email, social profiles, documents, signage, campaigns, and product assets as relevant.
• Protect continuity: plan redirects and clear communication if the name or domain changes.