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.
The substantive cost drivers in a redesign are: how much the information architecture changes (moving pages around, merging services, restructuring the URL pattern), how much new functionality is added on top of what existed, how the SEO migration is handled, and whether the underlying platform is being replaced at the same time. A designer swapping CSS and images on an existing WordPress site is not doing the same job as a developer rebuilding that same site from scratch on a clean, fast PHP codebase with old web addresses forwarded to the new ones, behind-the-scenes labels that tell Google exactly what your business is, and a fresh map of the new site handed straight to Google. Both are called "a redesign." They're not comparable tasks.
Understanding what's included in the quote before you sign is more important than the number itself. A cheap redesign that skips the search-ranking handover, doesn't forward your old web addresses to the new ones, and leaves you on the same slow platform you started on is a false bargain. You get a website that looks new and performs identically, with the added risk that Google may drop your rankings because the move wasn't handled.
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 our redesign process works →
2. Redesign vs. full rebuild: which one you need
These terms get used interchangeably in most web design conversations, and the conflation causes expensive confusion. A redesign changes the appearance, layout, and information organization of a site. A rebuild replaces what the site is built on: the underlying platform, the code itself, or the system you log into to edit pages. In practice, most good redesigns are rebuilds in disguise. Often, the reason the site needs a redesign is that it's built on something that's the core problem.
The clearest signal that you need a rebuild, not just a redesign: your current site is on WordPress, has accumulated a plugin stack that needs weekly maintenance, and loads slowly regardless of what caching you throw at it. Refreshing the theme and typography on that site is like repainting a car with a cracked engine block. The surface looks better. The fundamental issue is still there. You'll be back in the same position 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 real 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.
How much the information architecture changes. A redesign where every URL maps 1:1 to a new version of the same page is less complex than one where pages are being merged, split, reorganized into a new hierarchy, or renamed entirely. The more the structure changes, the more careful the plan for forwarding old web addresses to new ones needs to be, and the more work the search-ranking handover requires. A redesign that changes a lot of web addresses without a proper forwarding plan will hurt rankings. Planning that work costs money but costs a lot less than recovering from a traffic drop.
New functionality added on top of the existing feature set. Every piece of new functionality (a booking calendar, an e-commerce checkout, a client portal, a payment form, a live quote calculator) is a development project inside the redesign. If the current site is a brochure site with a contact form and the redesign adds online booking, the booking system is not a line item in a visual refresh. It's a significant development addition that raises the project cost accordingly.
Platform migration work. Moving from WordPress to hand-coded PHP, from Squarespace to a self-hosted codebase, or from GoDaddy Website Builder to anything else requires exporting your existing content, converting it, forwarding old web addresses to new ones, pointing your domain name at the new site, and testing at each stage. The migration work is a defined cost that varies with how complex the source platform is and how much data needs to be transferred.
Content scope. Does your current copy migrate as-is, or does it need rewriting? Are you providing images, or do they need to be sourced or shot? Copywriting and photography aren't always included in a development quote; they're separate scopes. Make sure the quote you get specifies who's responsible for content so there's no mid-project standstill waiting for inputs nobody thought to define.
Timeline compression. Standard redesign timelines allow for design review rounds, content integration, cross-device testing, and a staged launch. Rush projects that need to be complete in two weeks instead of six weeks are possible, but they cost more because they require concentrated effort that displaces other work. If you're not in a rush, don't create artificial urgency or you'll end up paying for it.
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.
| Scope tier | Typical cost range | What it covers |
|---|---|---|
| Visual refresh on existing hand-coded site | $3,000–$5,000 | Updated design, CSS, and layout on a codebase that's already sound. Minimal structural changes, existing URL pattern preserved, content migrates 1:1. Appropriate when the foundation is technically solid but looks dated. |
| Standard redesign + rebuild (4–8 pages) | $3,000–$7,500 | Full rebuild on a clean PHP codebase. New design, migrated content, old web addresses forwarded to the new ones, your existing search listings preserved, a fresh site map handed to Google, and speed tuned to pass Google's page-speed health checks. The complete package for most small business sites. |
| Redesign with new functionality added | Quoted per project | Everything in the standard rebuild, plus new features: booking systems, e-commerce, client portals, custom forms, payment integration. Cost scales with the complexity of new features on top of the base rebuild. |
| Platform migration from WordPress / page builder | $3,000–$7,500 | Full content export, conversion, and reimplementation on a hand-coded codebase you own outright. Plugin overhead eliminated, no ongoing platform subscription. Includes forwarding every old web address and the full search-ranking handover. |
| New website build (comparison) | $2,800–$5,000 | No existing site to migrate. Clean build from scratch. Generally less complex than a redesign because there are no old web addresses to forward, no content to convert, and no existing rankings to protect—just forward-looking design and development. |
A few things that affect where in any given range a project lands: having your content ready (copy, images, brand guidelines) at kickoff keeps things on the tighter end; needing content developed during the project stretches both timeline and cost. Scope changes after a project starts (adding pages, adding features, changing the URL structure mid-build) also affect the final number. Fixed-price quotes require fixed scope. That's not developer rigidity, it's just how project math works.
For a rough estimate on your specific project, the website 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 any site with meaningful search traffic, the ranking question is the most important conversation to have before a redesign starts. The answer to "will I lose my rankings" depends entirely on whether the migration is planned and executed correctly. Most horror stories of traffic falling off a cliff after a redesign are not accidents: they're predictable failures from specific, avoidable mistakes.
The forwarding map. Every web address on your current site that has rankings, backlinks, or traffic needs to automatically forward to its new location. If the address of one of your pages changes during the redesign, the old address needs to send visitors and Google straight to the new one, permanently and immediately on launch day. Done right, Google passes the credit and authority the old page earned over to the new destination. Skip it, and every page that used to exist turns into a dead "page not found" error, and any ranking or authority it carried just gets thrown away.
A responsible redesign starts with a complete inventory of your current pages: checking every web address on the existing site, listing every one that gets traffic (using the free Google tools that report what people search to find you), and building the forwarding list before any new code is written. That list becomes something you can verify before launch, not something pieced together from memory 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.
Keep your search listings intact. The clickable headline and short summary that Google shows for each of your pages in search results should carry over to the new site and only be changed on purpose, not wiped out by accident. Those headlines are what convince people to click your link instead of a competitor's. If they vanish and get replaced with generic filler, you may hold your rankings at first before they slowly slide.
Tell Google about the new site right away. Within 48 hours of launching the redesigned site, an updated map of all your pages should be handed directly to Google and Bing. This tells the search engines where everything lives now, instead of waiting weeks for them to stumble across it on their own. It's a 5-minute step that can noticeably speed up how fast your new pages show back up in search.
Executed properly, most sites see rankings hold during the transition and improve within 60–90 days as Google re-checks the faster, cleaner version. The speed improvement alone is a significant ranking signal. Google has said plainly that it uses its page-speed and stability health checks to decide rankings, and a rebuilt site that cuts load time from 4 seconds to under 1 second sees a ranking benefit over time. Google's page-speed health checks explained: what they are and why they matter → How to speed up your website →
6. Your existing content: what to keep, rewrite, or add
One of the most useful conversations to have before a redesign is a clear assessment of your current content. 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 that's already ranking for terms you care about, pages where Google has indexed specific content and drives traffic to them, service descriptions that have been refined over time and convert well, and any content that customers reference when they call or email. Moving this material verbatim preserves what it's already earned.
Content worth restructuring, not rewriting: existing copy that covers the right topics but is buried in long blocks of text, organized in a way that doesn't match how visitors navigate, or spread across too many pages (or too few). The redesign gives you a natural opportunity to reorganize without starting from scratch. Moving material into a better structure costs less than rewriting and often improves performance.
Content worth rewriting: service pages that describe what you do but not why it matters to the customer; an about page that reads like a resume; any page where a competitor's site is significantly more persuasive on the same topic. Rewriting is an investment, not a requirement. If the existing copy is performing, leave it. If it's costing you customers, that's where you spend money.
Content worth adding during the redesign: pages your current site is missing that competitors rank for; FAQ sections that answer the questions customers ask before they contact you; service pages that are currently combined on one page and would each rank better as their own page. Adding content during a redesign is more efficient than adding it after launch, because the site structure is being defined anyway. If you have a list of content gaps, the redesign is the right time to address them.
One practical note on images: if your current site has outdated photography (stock photos from 2015, low-resolution images, or team photos that no longer represent the business), the redesign is the right moment to fix that. Professional photography costs $500–$1,500 for a local business shoot and makes a larger visual impact than almost any design decision. The best design in the world looks weaker with weak images.
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:
- Premium theme annual renewal: $50–$100/year
- Page builder annual renewal: $50–$200/year (Elementor Pro, Divi, etc.)
- WooCommerce or booking plugin: $100–$300/year if you're using one
- Security plugin (Wordfence, Sucuri): $100/year
- Backup plugin (UpdraftPlus Pro, etc.): $70/year
- Premium hosting adequate for WordPress: $20–$50/month ($240–$600/year)
- Developer maintenance time for updates, plugin conflicts, and security patches: $500–$1,500/year at a modest $75/hour, if you're paying someone to handle it
Total recurring cost over 3 years: roughly $3,000–$7,500 in platform overhead, before accounting for any performance problems that hurt your conversion rate or search rankings. That's money spent maintaining a platform, not improving the business. At the end of 3 years, you own nothing. The site is still on a platform you depend on, with plugins requiring renewal, and a codebase you cannot move without the original developer.
The cost of a clean rebuild over the same 3 years. A hand-coded PHP site runs on commodity hosting ($10–$20/month on a VPS) with no plugin renewals, no theme subscriptions, and no platform dependencies. Hosting over 3 years costs $360–$720 total. Maintenance is minimal because there are no plugins to update and no dependency chains to manage. The codebase is yours. You can hand it to any developer, move it to any server, or modify it yourself if you have the skills.
Compare the two: the redesign costs $3,500–$7,000 once, and the 3-year operational cost drops to under $800. The WordPress path costs $3,000–$7,500 over the same period and you still own nothing at the end. The rebuild breaks even in under 18 months once you factor in the eliminated recurring costs.
The conversion rate angle. A site that loads in 4 seconds loses a meaningful percentage of visitors before they see your content. Google's own data shows bounce rates increase by roughly 32% when load time goes from 1 second to 3 seconds, and 90% when it goes from 1 second to 5 seconds. If your current site generates 10 qualified leads per month and a faster version improves that by 20%, the rebuild pays for itself through recovered leads within months, with zero additional ad spend. That math varies for every business, but the direction is consistent: a slow site has a measurable cost that doesn't show up on an invoice but shows up in your close rate.
The one-time cost that isn't. A cheap redesign that doesn't fix the underlying platform or skips SEO migration often requires a second redesign within 2–3 years. If you spend $1,500 on a theme swap that leaves you on the same WordPress stack and costs you traffic because the old web addresses weren't forwarded properly, you haven't avoided the $5,000 rebuild. You've delayed it and paid $1,500 for that delay. The redesign decision is worth doing once, correctly, rather than across two rounds. 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 directly how they protect your search rankings. "How do you make sure my old web addresses forward to the new ones so I don't lose my Google traffic?" is a question every competent redesign developer should answer crisply. If the response is vague or that forwarding isn't mentioned until you ask, that signals how carefully the move will be handled.
Ask who controls hosting at project end. The answer should be you, in an account you own and control. If the developer bundles hosting in a way that makes it unclear whether you can move the site later, clarify before signing. Moving a site to self-controlled hosting afterward adds avoidable cost and friction if the ownership terms aren't clear from the start.
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 out what's missing. A quote that leaves out the search-ranking handover, forwarding your old web addresses, and moving your content isn't cheaper than one that includes them. It looks cheaper on the invoice but costs more overall once you add those back. Getting your search setup right after launch costs $500–$1,500 separately. Forwarding the addresses on a site with meaningful search history costs $300–$800 from a specialist who didn't build the site and has to study it first. Moving content that nobody planned for costs developer hours at whatever rate applies. Tally the missing items before calling any quote the best deal.
Specific questions to ask every developer before signing a redesign contract: What exactly is included in protecting my search rankings? How do you forward my old web addresses, and can I see an example from a previous project? Who controls hosting at project end, and can I move the site without your involvement? What is your post-launch support policy and how long does it last? What do I own at project end—do I get the codebase, and in what form? If any of those gets a vague answer, keep asking. The details matter.
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 under $800 in operational costs over the same period. The rebuild breaks even in under 18 months once you factor in eliminated recurring costs and recovered conversion rate.
- 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
A hand-coded redesign runs $3,000–$7,500 as a one-time, fixed-scope cost. The lower end covers a focused rebuild where the content and URL structure are mostly preserved and the work is primarily replacing a slow or outdated codebase with a fast, clean one. The higher end reflects more complex work: structural re-architecture, added functionality like booking systems or client portals, significant content restructuring, and more involved SEO migration work across a larger page set. A range before discovery is directional, not a quote. What makes it land at one end versus the other is the actual scope of what's changing and what's being added. A fixed price comes after you define scope.
A redesign changes how the site looks and how information is organized. A rebuild replaces what the site is built on: the platform, the code itself, or the system you log into to edit pages. In most real projects these happen simultaneously because the reason a site needs a redesign is often that the foundation itself is the problem. A WordPress site with plugin debt and slow load times doesn't improve from a theme swap. The bloat is structural. Moving to a hand-coded PHP codebase eliminates the overhead at the source. When getting a quote, ask explicitly: "Is this a visual refresh on the existing platform, or a full rebuild on a new codebase?" The answer changes the scope significantly and the price should reflect that difference clearly.
Not if the move is planned and executed correctly. A proper redesign forwards every old web address that has traffic or rankings straight to its new location, keeps the clickable headline and summary Google shows for each page intact through the transition, keeps the substantive content on each page in place, and hands Google a fresh map of the new site within 48 hours of launch. Handled this way, rankings hold through the move and often improve within 60–90 days because the new site loads faster and Google has made clear it factors page speed and stability into rankings. Horror stories of sites losing half their traffic after a redesign come from failing to forward the old addresses, accidentally deleting content, or quietly removing pages with nothing forwarding to a new spot. Those are planning failures, not inherent consequences of redesigning. Any developer you hire should walk you through exactly how they protect your search rankings before you sign anything.
A focused redesign of a 4–8 page small-business site generally runs 3–5 weeks from kickoff to launch. Larger sites, complex structural changes, or new functionality added on top push that to 6–10 weeks. The main variable extending timelines beyond code and design is content: if copy needs to be written, reviewed, and approved during the project, or if photography needs to be scheduled, those review cycles add time unrelated to development. Having content decisions made before the project starts (even a rough draft and clear direction on images) is the most reliable way to keep a redesign on track. The build itself requires no downtime. The new site is fully built and tested before launch, so the current site stays up throughout.
Yes, all of it. Your copy, images, contact form submissions, downloadable files, and any other content on the current site is fully portable. Most redesigns carry the existing content forward and restructure how it's organized rather than starting fresh. Rewriting copy is an option, not a requirement. Some clients use the redesign to refresh service descriptions, add missing pages, or sharpen messaging. Others migrate word-for-word and focus spending on speed, structure, and SEO improvements. Both approaches work. The decision doesn't need to happen before getting a quote. Content scope can be defined separately once the structural and technical work is priced. What matters is that the content decision gets made explicitly, not left undefined until it creates a mid-project standstill.
The development and design work on a hand-coded redesign runs $3,000–$7,500. If you need copywriting for some or all pages, budget an additional $800–$2,500 depending on page count and depth. Professional photography for a local business shoot (headshots, workspace, team, product) costs $500–$1,500. A complete redesign with new development, updated copy, and professional photos for a 5–8 page business site comes in around $5,000–$12,000 total depending on scope. Content additions are optional. If your existing copy is ranking and converting, it carries over at no additional cost. Scoping content explicitly ensures nothing gets accidentally assumed to be included when it isn't.
If the current site has meaningful organic traffic, a domain that's more than a couple of years old with backlinks, or content that took time to produce and rank, migrating that through a redesign is the right call. You're preserving what the site already earned rather than starting over. If the current site has minimal traffic, was built on a free template with no SEO work, has a domain registered in the last year, and content is thin, the migration overhead may not be worth it. A clean build with proper structure from day one can be faster and more efficient than carefully migrating a weak foundation. Before deciding, ask a developer to pull a quick snapshot from Google's free reporting tools: how much traffic you get, how many of your pages Google has on file, and which searches you already rank for. That data makes the decision concrete rather than theoretical.
The most common reasons redesigns run over quote: scope additions after kickoff (adding pages or features that weren't in the original brief), content ownership undefined (neither developer nor client knew who was writing copy, so it became an expensive mid-project conversation), URL structure decisions changing after development started and requiring rework, and stakeholder review cycles happening too late and requiring revisions to completed work. All are avoidable with a clear written brief before any work starts. A fixed-price quote requires fixed scope. If the scope expands, the cost expands proportionally. That's not a surprise once stated clearly, but becomes unpleasant if neither party had that conversation before the deposit cleared.