Most website redesigns are sold before they are diagnosed. Someone decides the site “looks dated,” a proposal appears, and six months later the organization has a prettier website that generates the same number of leads it did before, sometimes fewer. That is the failure mode this playbook exists to prevent.
If you are weighing website redesign services right now, the useful question is not “which agency has the nicest portfolio.” It is “what problem am I actually solving, and is a full rebuild the cheapest way to solve it?” Sometimes the answer is yes. Often it is no.
A website redesign is a full rebuild of your site’s structure, design, content, and platform, not a fresh coat of paint. It is warranted when the site’s structure, technology, or content is actively blocking growth, and it typically runs 8 to 20 weeks and $15,000 to $100,000+ depending on page count, custom functionality, and how much content has to be rewritten. If your only complaint is aesthetic, you probably need targeted improvements, not a redesign.
This guide covers when to rebuild, what the work actually includes, what drives cost, how to protect your search visibility through the transition, where redesigns go wrong, and how to judge whether yours worked.
When a redesign is actually warranted
A redesign earns its budget when the problem is structural. Real triggers include:
- Your information architecture no longer matches your business. A professional services firm that added three practice areas since the last rebuild is usually cramming them into navigation designed for one. Visitors cannot find what they came for because the site was organized around a version of you that no longer exists.
- The platform is a liability. Unsupported CMS versions, abandoned page builders, a theme nobody can safely update. If routine edits require a developer, or security patches keep breaking layouts, you are paying rent on a house that is falling down.
- Mobile and performance are structurally bad. Not “could be faster”, structurally bad, because the site was built desktop-first and no amount of optimization fixes the foundation.
- The site cannot support how you sell now. No gated resources, no functional forms, no way to route inquiries. A manufacturer whose buyers now research spec sheets online cannot serve them from a five-page brochure site.
- You have merged, rebranded, or repositioned. New name, new audience, new offer, the old site is describing a company that does not exist.
- Accessibility gaps are baked into the markup. If the DOM order, color system, and component library all fight WCAG conformance, remediation costs more than rebuilding.
When a redesign is NOT warranted
Be equally honest about the cases where a rebuild is the wrong tool:
- “It looks dated.” Design fatigue is real, but you see your site a thousand times more often than your prospects do. If the site converts, a visual refresh; typography, imagery, hero sections, costs a fraction of a rebuild.
- “Traffic is down.” That is usually a content, technical SEO, or algorithm problem. Rebuilding the site does not fix it and can make it worse. Diagnose first. Our breakdown of what foundational SEO really includes is a better starting point than a redesign proposal.
- “Leads are flat.” Often a messaging, offer, or follow-up problem. A new site with the same weak value proposition produces the same weak results.
- A new marketing director wants to make a mark. Legitimate motivation, bad justification. Tie the rebuild to a business constraint or wait.
- You redesigned 18 months ago. Unless something material changed, you have a maintenance and content problem, not a design problem.
The honest test: write down the three specific outcomes you expect. If you cannot connect each one to something only a rebuild can change, do not rebuild. For a fuller diagnostic, read the signs it’s time to redesign your website.
What a redesign actually includes
Buyers are often surprised that design is the smallest part. A credible scope covers:
- Strategy and discovery — goals, audiences, competitive landscape, analytics review, stakeholder interviews.
- Information architecture — sitemap, navigation, URL structure, content model.
- Content — the audit, the rewrite, the migration. This is where most projects stall.
- Design — design system, key templates, responsive behavior, accessibility standards.
- Build — CMS setup, templates, components, integrations, forms, CRM connections.
- SEO and migration — redirect mapping, metadata, structured data, technical carryover.
- QA and launch — cross-browser, cross-device, accessibility, performance, analytics validation.
- Post-launch — monitoring, fixes, training, iteration.
If a proposal covers design and build but hand-waves content, SEO migration, and QA, it is not a redesign. It is a template installation with an invoice attached.
The five phases
1. Discovery. Two to four weeks. Where you decide what the site must do. Skip this and you will litigate it later at three times the cost.
2. Information architecture. One to three weeks. Sitemap, URL structure, content model. This is the highest-leverage phase and the one clients most want to rush.
3. Design. Three to six weeks. A design system and key templates, not forty bespoke page comps. Bespoke pages are how projects die.
4. Build. Four to eight weeks. Templates, components, integrations, content loading. Runs in parallel with content production if you have planned well.
5. Launch. One to two weeks of QA, redirects, and monitoring. Launch is a checklist, not a celebration. The celebration is 90 days later when the numbers hold.
For a concrete sense of what good execution produces, see our walkthrough of great website functionality.
What it costs, and what drives cost
Broad ranges for the organizations we work with — professional services firms, nonprofits, manufacturers and retailers:
- $15,000–$35,000 — small marketing site, 10–25 pages, largely standard functionality, most content supplied by you.
- $35,000–$75,000 — mid-size site, 25–75 pages, custom templates, integrations, meaningful content work.
- $75,000–$150,000+ — large or complex sites: heavy content volume, custom applications, multi-audience architecture, e-commerce, portals.
The variables that actually move the number:
- Page count and content volume. The single biggest driver. Fifty pages that need rewriting is a content project wearing a redesign costume.
- Who writes the content. Agency-written content can be a third of the budget. It is also the line item most likely to save the project.
- Custom functionality. Calculators, member portals, product configurators, ERP integrations.
- Design scope. Every page that needs a unique layout adds design, build, and QA time.
- Stakeholder count. A nonprofit board with nine opinions costs more than a founder with one. This is real, and it is rarely priced honestly.
- Migration complexity. A thousand legacy URLs with no redirect logic is a project of its own.
Cheap redesigns are not cheap because someone found efficiency. They are cheap because strategy, content, SEO migration, or QA got cut. Ask which.
How to protect SEO through the rebuild
This is where redesigns quietly destroy value. Search rankings live on URLs, and a rebuild changes URLs. Handle it deliberately:
- Inventory everything before you touch anything. Crawl the current site. Export every URL with its traffic, rankings, backlinks, and conversions. You cannot preserve what you never measured.
- Keep URLs that work. The instinct to “clean up” URL structure costs more than it gains. Change URLs only when the structure is genuinely broken.
- Map every redirect one-to-one. Old URL to the closest equivalent new URL — not a blanket redirect to the homepage, which Google treats as a soft 404. Follow Google’s guidance on 301 redirects and site moves.
- Carry over the content that ranks. If a page earns traffic, its substance survives the rebuild. Trim it and the rankings go with it.
- Preserve titles, metadata, and structured data. These get regenerated by templates and silently wiped constantly.
- Do not launch with noindex on. Staging environments are blocked from indexing for good reason. Someone forgets to remove it on roughly every third project. Check it twice.
- Monitor for 90 days. Crawl errors, index coverage, rankings, conversions, weekly at first. A small dip in weeks one to three is normal. A sustained one is a problem to fix now, not next quarter.
Build accessibility in at the same time. Conforming to WCAG 2.2 during design costs a fraction of retrofitting after launch, and it overlaps heavily with good SEO fundamentals.
Common failure modes
The traffic drop. Almost always redirects, lost content, or a stray noindex. Preventable in every case, and preventable only before launch.
Scope creep. It rarely arrives as one big request. It arrives as fourteen small ones. Fix it with a written scope, a change-order process, and a single decision-maker.
Content paralysis. The most common reason redesigns run late. The design is done, the build is done, and everyone is waiting on the About page. Assign content owners and deadlines in week one, or buy the content.
The DIY rebuild. Sometimes right for a five-page site. Usually it means an internal team learns page builders on your budget, ships in fourteen months, and skips redirects entirely. Count the internal hours honestly before calling it free.
Launch-and-abandon. The site goes live, the team exhales, and nobody touches it for two years. Then you are back here.
How to measure success
Aesthetics are not a metric. Set your baseline before launch and track against it:
- Organic traffic and rankings — recovered to baseline within 60–90 days, growing after.
- Conversion rate — form fills, calls, downloads, applications, as a percentage of sessions.
- Qualified leads — volume and quality. More junk inquiries is not a win.
- Engagement — pages per session, time on key pages, scroll depth on money pages.
- Operational metrics — how long it takes your team to publish a page without a developer.
- Core Web Vitals and accessibility — pass or fail, tracked.
Agree on these numbers before the project starts. Every one of them requires a pre-launch baseline, which is why analytics review belongs in discovery.
How to choose a partner
Short version: hire the firm that asks about your business before showing you designs. Look for a documented discovery process, a named SEO migration plan, honest content scoping, references from organizations your size, and a clear post-launch plan. Be wary of anyone who quotes a firm price on the first call, treats SEO as an add-on, or shows you comps before asking what the site must accomplish. We go deep on this in our guide to choosing a website redesign agency.
Fit matters as much as skill. A firm that works with professional services firms understands long sales cycles and partner review. One that works with nonprofits understands boards, donors, and program complexity. Ask who they build for.
Start with the diagnosis
The best redesigns start with a clear, specific problem and a number attached to it. If you can name what is broken and what success looks like, a rebuild is a good investment. If you cannot, spend a few weeks finding out before you spend six figures guessing.
Ready to find out whether you need a redesign or something smaller? Book a website redesign consult and we will review your current site, your goals, and your options honestly, including the option of not rebuilding. See how we approach website design and development, or explore how a rebuild fits into a broader digital marketing strategy.
Frequently Asked Questions
How much do website redesign services cost? Most small business and nonprofit redesigns run $15,000–$35,000; mid-size sites with custom templates and integrations run $35,000–$75,000; large or complex builds run $75,000–$150,000 or more. Page count, who writes the content, and custom functionality drive the number more than design does.
How long does a website redesign take? Typically 8 to 20 weeks. Discovery takes 2–4 weeks, IA 1–3, design 3–6, build 4–8, and launch 1–2. Content production is the most common cause of delay, so assign content owners and deadlines at kickoff.
Will a redesign hurt my SEO? It can, but it does not have to. Crawl and inventory the current site first, keep URLs that work, map every changed URL to a one-to-one 301 redirect, carry over the content that ranks, and verify noindex is off at launch. Then monitor rankings and index coverage weekly for 90 days.
Do I need a full redesign or just a refresh? If your complaint is visual, you need a refresh. If your site’s structure, platform, or content is blocking growth — you cannot organize new services, cannot publish without a developer, cannot support how you sell, you need a redesign. Write down three expected outcomes and see whether a rebuild is the only way to get them.
Should we rebuild the site ourselves? For a small brochure site with someone genuinely capable in-house, maybe. For anything larger, count the real internal hours, the delivery timeline, and the risk of a botched migration. DIY rebuilds most often fail on redirects, accessibility, and finishing at all.


