Website redesign cost: a complete 2026 breakdown with numbers that matter.

1. What you're paying for in a redesign

A website redesign is not a cosmetic operation. It's a migration: taking everything that exists (content, structure, URLs, SEO history, functionality) and rebuilding it on a foundation that performs better than the original. The visual refresh is the most obvious output, but it's probably the least technically complex part of the work.

Cost depends on architecture changes, added functions, SEO migration, and platform replacement. Swapping WordPress CSS/images differs fundamentally from rebuilding PHP with redirects, Google business labels, and a submitted sitemap. Both may be called redesigns; compare actual work.

Scope matters more than price. A cheap redesign omitting SEO handover/redirects and retaining a slow platform changes looks without performance, while risking Google rankings. That's a false bargain.

The best time to clarify scope is before a project starts, not after you've paid a deposit and work is underway. Any developer worth hiring should be able to tell you, in plain language, exactly what the redesign includes and what you'll need to handle yourself or pay for separately. How my redesign process works →

2. Redesign vs. full rebuild: which one you need

Redesign changes appearance, layout, and information organization; rebuild replaces platform, code, or editor. Most good redesigns also rebuild because the original foundation often caused the problem.

WordPress requiring weekly plugin upkeep and remaining slow despite caching signals rebuilding. Theme/type changes leave the underlying defect, bringing you back to the same problem in two years.

When a rebuild on a clean, owned codebase is the right call:

• The current site runs on WordPress, a page builder subscription (Wix, Squarespace, Webflow), or GoDaddy Website Builder, and you want to stop paying platform fees and own your code outright.
• The site is slow regardless of how much you've optimized it, and the performance problem is structural: bloated theme code, unnecessary JavaScript, plugin overhead rather than something fixable with a caching configuration.
• You want to add functionality (booking, client portal, payment integration) that would require expensive plugins on the current platform or isn't possible without significant workarounds.
• The current hosting is controlled by the original developer and you've been paying monthly for access to something you should own outright.

When a visual refresh on the existing platform makes sense:

• The current platform is fast and technically sound, and the problem is purely cosmetic: dated design, outdated branding, or a layout that doesn't convert well.
• You own your codebase already and don't want to change the underlying technology.
• The site is hand-coded PHP or a similar lightweight setup, and the issue is purely that it looks dated, not that it performs poorly.

Both paths are valid. The question worth asking a developer before you get a price is: "Given what's wrong with my current site, are we redesigning, rebuilding, or both?" If the answer is vague, keep asking until it isn't. How to migrate off WordPress → WordPress to custom PHP: what the switch looks like →

3. What drives the price: the main cost variables

Redesign pricing is often quoted as a flat range. This is useful for setting expectations but not especially informative about what makes your specific project land at one end or the other. These are the variables that determine the number:

Page count and structural complexity. A 4-page site with a homepage, services, about, and contact is a different scope than a 12-page site with individual service detail pages, a blog or news archive, a gallery, a team directory, and multiple contact forms routing to different departments. Both are "a small business site." The cost reflects the actual scope.

Architecture changes. A 1:1 URL replacement is simpler than merging, splitting, renaming, or reorganizing pages. Larger changes demand careful forwarding/SEO handover; omissions harm rankings. Planning costs less than traffic recovery.

New functions, bookings, checkout, portals, payments, or quote calculators, are development projects within redesigns. Adding booking to a brochure/contact site substantially raises scope and price beyond visual refreshing.

Platform migration from WordPress, Squarespace, or GoDaddy Website Builder requires exporting/converting content, redirects, domain repointing, and staged testing. Source complexity/data volume determine this separate cost.

Content scope. Specify existing versus rewritten copy and supplied versus sourced/shot images. Writing/photography may be separate; assign responsibility to avoid mid-project waits.

Rush timing. Compressing six weeks to two can cost more by displacing other work. Normal schedules include reviews, content, device tests, and staged launch. Avoid artificial urgency.

4. Realistic cost ranges and what each tier delivers

These are 2026 ranges for a hand-coded, custom-built redesign from a boutique PHP developer. They're not bargain-basement marketplace prices and not full-service agency rates. Use them as a calibration point when evaluating other quotes you've received.

Ready copy, images, and brand guidelines reduce cost/time; developing them concurrently adds both. Mid-build pages, features, or URL changes alter pricing. Fixed fees require fixed scope.

For a rough estimate on your specific project, the cost estimator generates a directional number from a few inputs. For a written scope and a fixed price, a brief discovery conversation is the right next step. See full pricing detail →

5. Protecting your Google rankings through the migration

For sites earning search traffic, discuss ranking preservation before redesign. Outcomes depend on migration planning/execution; dramatic losses usually reflect specific preventable mistakes.

Forwarding map. Changed URLs with rankings, backlinks, or traffic must permanently forward to equivalents at launch. Google transfers earned authority through these forwards; omitted mappings create dead pages and discard that credit.

Inventory every existing URL and traffic-producing page using Google's free search reports. Build the forwarding map before coding and verify it prelaunch, rather than reconstructing it afterward.

Content preservation. Google ranks content. If you remove substantive content from a page during the redesign, the page's rankings can drop even with forwarding in place. Tightening copy is fine; cutting topics that the page ranked for is not. The goal is to improve how content is structured and presented, not to discard what made it rank.

Retain search listings. Carry titles/summaries over unless deliberately changing them. They win clicks; accidental generic replacements can erode rankings gradually even if initial positions hold.

Submit the new sitemap to Google/Bing within 48 hours. This 5-minute task speeds discovery instead of waiting weeks for search engines to find changed locations.

Proper transitions retain rankings and often improve within 60–90 days. Google uses speed/stability; reducing 4 seconds to under 1 earns benefits over time. Google speed checks → Speed-up guide →

6. Your existing content: what to keep, rewrite, or add

A clear assessment of your current content ranks among the most useful conversations to have before a redesign. Not every site goes into a redesign with content worth preserving word-for-word. And not every site needs a top-to-bottom rewrite. Understanding which situation you're in before the project starts helps scope it accurately and keeps the budget realistic.

Content worth keeping as-is: copy ranking for valuable terms, indexed pages driving Google traffic, refined service descriptions that convert, and material customers reference in calls or emails. Moving it verbatim preserves those gains.

Restructure useful copy buried in blocks, confusing navigation, or too many/few pages. Redesign offers a natural chance; reorganizing costs less than rewriting and often performs better.

Rewrite weak copy: feature-only services, resume-like About pages, or content outpersuaded by competitors. It's optional investment; retain successful copy and spend where words lose customers.

Add content gaps: competitor-ranking topics, pre-contact FAQs, and separate services currently combined. Building these while architecture is being defined costs less effort than adding after launch.

Replace 2015 stock photos, low-resolution images, or outdated team shots during redesign. Local professional shoots cost $500–$1,500 and often improve appearance more than design decisions; weak imagery undermines excellent layouts.

7. The math: what a redesign costs vs. what staying on your current site costs

Most business owners frame the redesign decision as a cost: "is $4,000 worth it?" The more useful framing is a comparison. What does the redesign cost, and what does not redesigning cost over the same period? The numbers usually surprise people.

The cost of staying on a WordPress site for 3 years. A typical small-business WordPress setup with a premium theme, a page builder (Elementor, Divi, or similar), and the standard plugin stack runs:

Over 3 years, platform overhead totals roughly $3,000–$7,500, excluding lost conversions/rankings. After 3 years, dependency, plugin renewals, and developer-bound code persist without ownership; spending maintains the platform rather than improving business.

Custom costs over 3 years. Managed Core hosting at $60/mo, billed monthly from launch, totals $2,160 over 3 years ($360–$720 if you self-manage a $10–$20/month VPS). No plugin/theme subscriptions or dependency chains; maintenance is minimal. Owned code moves freely between developers/servers or can be self-edited.

Compare the two: the redesign costs $3,000–$7,500 once, and the 3-year operational cost drops to $2,160 on managed hosting. The WordPress path costs $3,000–$7,500² over the same period and you still own nothing at the end. Against a plugin-heavy WordPress stack, the rebuild pays for itself on running costs in roughly two to four years; against a lean one it may never pay back on fees alone, so speed, rankings, and ownership have to carry the case.

Conversion economics. Four-second sites lose readers. Google reports bounce increases of 32% from 1 to 3 seconds, 90% from 1 to 5. Improving 10 monthly qualified leads by 20% can repay rebuilding within months without more ads. Results vary, but slow-site costs show in closing, not invoices.

Site speed optimization: what moves the needle →

8. How to evaluate a redesign quote before you sign

Getting quotes from multiple developers is reasonable. Comparing them correctly requires structure, because redesign quotes are notoriously easy to make look comparable when they're describing entirely different scopes. Here's how to evaluate what's in each proposal.

Normalize scope before comparing price. Write out a brief: current site URL, page list, what you're keeping versus adding, current platform, functionality needed at launch, who provides content, and what post-launch support you expect. Send the same brief to every developer. Quotes written against an identical brief are comparable. Quotes written against vague email threads are not.

Ask about ranking protection. Competent developers clearly explain old-to-new forwarding. Vague or unprompted omission signals insufficient migration care.

Clarify hosting control. Expect your own account and mobility. Resolve unclear bundled-hosting ownership before signing to avoid later transition costs/friction.

Ask what the post-launch support window is. A defined window (30–60 days) during which post-launch bugs are fixed at no charge is standard on a professional project. If there's no mention of post-launch support in the quote, ask. The answer reveals something about the developer's confidence in their work.

Price omissions. Post-launch SEO setup costs $500–$1,500; specialist redirects cost $300–$800 plus unfamiliar-site investigation; unplanned content migration consumes billable hours. Quotes excluding these can cost more overall. Add missing work before comparing.

9. Key takeaways

• A hand-coded website redesign runs $3,000–$7,500 as a one-time fixed cost. The range reflects how much the information architecture changes, what new functionality is added, and whether the underlying platform is being replaced alongside the visual update.
• Most redesigns are rebuilds in disguise. If the site runs on WordPress with plugin debt, a page builder subscription, or developer-controlled hosting, a visual refresh on the same foundation leaves the underlying problem in place. The goal is a fast, owned codebase, not a better-looking version of the same constraints.
• Protecting your search rankings during a redesign is not optional if the site has search traffic. Forwarding every old web address, keeping your existing search listings intact, and handing Google a fresh map of the new site are non-negotiable parts of a professional move. Skipping them costs more to fix later than they would have cost to do correctly at the start.
• Most existing content is worth migrating, not rewriting. What deserves a rewrite: copy that doesn't convert, pages that don't rank. What deserves restructuring: content in a poor organization. What deserves a word-for-word carry-over: anything that's already ranking or converting well.
• The true cost comparison often tips toward rebuilding: staying on a WordPress stack with plugin and hosting overhead costs $3,000–$7,500 over 3 years² with nothing owned at the end. A clean hand-coded rebuild runs $2,160 on managed hosting over the same period. Against a plugin-heavy stack it pays for itself in roughly two to four years on running costs alone; against a lean one, recovered conversion rate and rankings have to make the case.
• Normalize scope before comparing quotes. A cheap quote that doesn't include forwarding your old web addresses, protecting your search rankings, or post-launch support isn't a better deal. It's a different (smaller) scope. Add the missing pieces before declaring any quote the winner.
• Ask ownership questions before signing anything. Who controls the domain? Who controls the hosting? Do you receive the codebase? The correct answers are unambiguous: everything is in your name, you can move or hand off the site without the developer's cooperation.

10. Common questions

See all web design FAQs →