Improve the current site
Good fit: The platform is stable and the main problem is content, navigation, mobile usability or conversion clarity. Watch for: Avoid piling new sections onto an architecture that no longer supports the customer journey.
A visual refresh is only one part of a redesign. Existing URLs, useful content, forms, analytics and customer journeys are business assets. Decide what to keep, change, redirect or retire before the work begins.
Good fit: The platform is stable and the main problem is content, navigation, mobile usability or conversion clarity. Watch for: Avoid piling new sections onto an architecture that no longer supports the customer journey.
Good fit: The underlying system works, but page patterns, visual hierarchy and interactions need a coherent update. Watch for: Existing templates, apps and technical limitations may constrain the result more than expected.
Good fit: The platform blocks essential functions, ownership, maintainability, performance or the required store and content structure. Watch for: URLs, redirects, data, integrations, forms, analytics and launch ownership need a documented migration plan.
Export what you can and record ownership before accounts, URLs or platform access change.
Give each old page a keep, improve, merge, redirect or remove decision. Avoid redirecting everything to the homepage.
New canonicals, titles, headings, internal links and sitemap entries must reflect the final route structure.
Forms, calls, bookings, checkout links, email delivery and analytics events need explicit post-launch tests.
Review crawl errors, redirect chains, index coverage, conversions and priority pages while search engines process the change.
No. A redesign can improve usability and technical foundations, but results depend on content quality, competition, authority, links, migration quality and many external signals.
Not necessarily. Useful, linked or intent-matching URLs should usually be preserved or redirected to the closest relevant replacement. Obsolete pages can be consolidated when the decision is documented.
Often, yes, but products, orders, customer data, URLs, redirects, apps, payment settings and platform export limits must be reviewed before scope and risk can be confirmed.
Priority URLs, redirects, canonicals, robots directives, sitemap output, forms, analytics events, mobile navigation, checkout paths and server errors should all be reviewed.
Share your brief today. We confirm the scope, timeline and total before any work starts.
Start your project