A redesign that does not throw away what already works
Most redesigns lose something on launch day — a page that ranked, a form that converted, a URL someone linked to years ago. This one starts by finding those and keeping them.
What you get
- Review of the current site: structure, content, speed and conversion points
- Redesigned pages in Figma, then built as a responsive front end
- A URL and redirect map applied before launch, not after
Start from what is working
Before anything is drawn, the current site gets read the way a visitor and a crawler read it: which pages get traffic, which ones convert, where people leave, and which URLs other sites link to.
That list is the constraint the redesign is built inside. A site that looks better and performs worse is a very expensive way to lose ground, and it is the normal outcome when the new design is briefed only on how the old one looks.
Redirects are part of the design
The single most common way a redesign costs money is URLs. Pages move, slugs get tidied, a section is merged into another, and everything that pointed at the old address lands on a 404 — including the search results that were sending you customers.
Every existing URL is mapped to its destination on the new site before launch, and the ones with nothing equivalent get a deliberate decision rather than a default. This is unglamorous and it is the part that protects the investment.
Ship in stages where it helps
A full-site relaunch on one date is the riskiest version of this work. Where the site allows it, the redesign goes out in stages — the templates that carry the most traffic first — so problems surface on one section rather than on all of them at once.
It also means value arrives earlier. The pages that matter get better in month one instead of everything getting better in month five.
What it costs
- Design and buildFrom$1,999 per project
The design work above, continued into a working responsive front end in React, Next.js and Tailwind CSS, so nothing is lost between the file and the live site.
Common questions
Will a redesign hurt our search rankings?
It can, and it usually does when URLs change without a redirect map, when page content is cut back, or when the new build is slower than the old one. Those are the three causes, and all three are avoidable — which is why the URL map and a performance check are part of the work rather than an add-on. Nobody can promise rankings will hold, but they can be protected deliberately instead of hoped for.
Can you redesign without rebuilding?
Yes. Plenty of these are design-only: the redesigned pages are delivered as Figma files and your developers build them. The redirect and structure work is still worth doing in that case, and I will hand it over as part of the design.
Our site is on WordPress or Webflow. Does that change anything?
It changes what the rebuild looks like, not whether it is possible. A WordPress site is usually rebuilt as theme templates, a Webflow site inside Webflow, and either can move to a Next.js front end if there is a reason to. Where the current stack has custom back-end functionality, that part stays with your developers.
Other services in this area
- Custom web development
- Figma to React build
- Landing page design & build
- Webflow development
- Framer development
- WordPress development
- Website maintenance
- Performance & accessibility audit
Need the design before the build? UI/UX design
Have a project in mind? Let’s talk.
Get in touch
