Website Redesign Cost: What Actually Drives the Price
There’s no single number for what a redesign “should” cost, because a redesign isn’t one thing: it’s a bundle of separate decisions, each with its own price tag. Here’s how those decisions actually add up.
“Redesign” gets used for two very different projects. One is a visual refresh: same pages, same content, same underlying structure, just updated typography, color, layout, and imagery. The other is closer to a rebuild: new information architecture, new CMS or framework, new content, sometimes new functionality entirely. The first can often be scoped as a set of template updates. The second is effectively a new build that happens to reuse your domain and brand. Most quotes vary wildly because people are asking for one and pricing the other in their head.
Content migration is the line item people underestimate most. If your site has thirty pages of long-form content, product listings, or years of blog posts, someone has to decide what moves as-is, what gets rewritten, and what gets cut. That’s editorial work, not design work, and it scales with volume, not with how nice the new templates look. A ten-page marketing site and a three-hundred-page resource library are not the same redesign even if the new design itself is identical.
Changing platforms changes the math entirely. Restyling a site on the CMS it already runs on is contained work: you’re touching templates and stylesheets, not rebuilding the plumbing. Moving off WordPress into something like a headless setup or a framework such as Next.js means rebuilding routing, forms, integrations, and hosting from scratch, on top of the design work. That’s a legitimate reason to switch platforms: better performance, better editing workflow, fewer plugin dependencies, but it should be a deliberate decision, not something that happens by default because “redesign” quietly became “rebuild” somewhere in scoping.
Before scoping anything, audit what you already have. Old sites usually have more salvageable parts than owners assume: a component library that mostly works, copy that just needs editing rather than replacing, an information architecture that’s fine and just looks dated. Redesigning only what’s actually broken: instead of rebuilding everything because it’s easier to say yes to than to audit, is usually both cheaper and faster. If you want a rough sense of where your own project lands before talking to anyone, our free software development cost calculator is a reasonable starting point for putting numbers to scope.
What actually moves the number
- Number of unique page templates. A blog and a homepage and a pricing page and a product page are four templates, not one: each unique layout has to be designed and built separately, even if the visual style is shared.
- Content volume and migration complexity. Every page, image, and piece of copy that has to be reviewed, rewritten, or moved is manual effort that scales linearly with how much content exists.
- CMS or framework change. Staying on your current platform keeps the work contained to design and templates; switching platforms adds a full technical migration on top of it.
- Custom functionality. Forms, calculators, e-commerce, gated content, or third-party integrations each need their own scoping: they don’t come free with a new visual design.
- Design system complexity. A handful of reusable components is cheap to build once and reuse everywhere; heavy custom illustration, animation, or one-off page layouts multiply the design hours.
- SEO and redirect preservation. If URLs, page structure, or the CMS itself changes, someone has to map old URLs to new ones and verify nothing that currently ranks gets orphaned.
Frequently asked questions
Do I need a full rebuild or just a redesign?
Usually a redesign. A rebuild makes sense if the current platform is genuinely limiting you: you can’t add the features you need, performance is a real problem, or the CMS is being discontinued. If the complaint is really “it looks dated” or “it doesn’t convert well,” that’s a design and content problem, solvable without touching the underlying platform.
How long does a website redesign take?
It depends entirely on which of the two projects above you’re actually doing. A template-level visual refresh on an existing platform is a much shorter timeline than a full platform migration with content rewrite, because the second one includes a build project inside the redesign project.
Will a redesign hurt my SEO rankings?
It can, but not because of the redesign itself: it’s almost always caused by changed or missing URLs without redirects, removed content that was ranking, or a site structure change that breaks internal linking. None of that is unavoidable; it just needs to be planned for explicitly rather than treated as a design-only project.
Should I switch CMS platforms during a redesign?
Only if the current one is actually the bottleneck. Bundling a platform migration into a redesign because “we’re already touching it” is how a contained project turns into an open-ended one. If the current CMS does the job, keep it and spend the budget on design and content instead.
What’s cheaper: a redesign or starting over?
A redesign that reuses working components, existing content, and the current platform is almost always cheaper than starting from a blank slate, because a genuine rebuild has to redo everything the old site already had, including the parts that were fine.
If you’re trying to scope your own redesign and want a second opinion on where it actually falls, take a look at our services or get in touch.