People ask how much a website redesign costs as if it were one product. It is not. Updating five service pages is a different job from replacing an unsupported WordPress theme, restructuring the content and migrating an online store. If two proposals look comparable, check whether they describe the same work.
The WordPress options I cover here start from $1,000 with Elementor Pro for a focused brochure website, or $2,000 for a custom Gutenberg build with Skylit.DEV (opens in a new tab). Ecommerce redesigns start from $2,000 with Elementor and WooCommerce, or $3,000 for a custom Gutenberg and Skylit.DEV store. Those are starting points for a defined scope, not a flat fee. Migration, integrations and custom development determine the final quote.
Before choosing a route, establish what is failing. Slow pages, falling enquiries, broken integrations and a growing backlog of updates give the project specific problems to solve. Your existing content, search visibility and customer data may still be valuable, even when the software behind them needs replacing.
- Slow pages that lose visitors before the offer is visible.
- Falling enquiries or orders while the site still looks “fine”.
- Broken forms, payments or integrations that nobody owns.
- A growing backlog of updates because every change needs a workaround.
Keep what still works. Rebuild the parts that make the website difficult to use, maintain or grow, and price the project around those problems.
Should you update, redesign or rebuild?
“Redesign” gets used for several different jobs. That is how two quotes can look similar while describing completely different amounts of work.
| Approach | When it makes sense | What you gain and what you keep |
|---|---|---|
| Update the existing website | The structure and editing setup work, but content, images, forms or individual performance issues need attention. | Smaller scope, less disruption and continued use of the investment you already made. Existing structural limitations remain. |
| Redesign on the existing foundation | The technology is supported and maintainable, but navigation, layouts, messaging or the mobile experience need substantial changes. | A better customer experience while reusing suitable content, functionality and infrastructure. |
| Rebuild on a fresh foundation | The theme or builder is a dead end, updates cause problems, or the next stage of the business needs a different structure. | More control over performance, editing and functionality, with extra work for migration and testing. |
If the main problem is oversized images and poor hosting, address those before committing to a complete rebuild. If every change requires another workaround around an abandoned theme, continuing to patch it can become a poor use of money.
The technical decision comes down to dependencies: the theme, page builder, plugins, custom code and hosting. Check whether they can be updated together, whether important functionality depends on unsupported components, and whether the editing setup can accommodate the next stage of the business.
A rebuild also does not mean throwing away your domain, useful articles, customer data or every existing URL. Those may be some of the most valuable things you own. You can build a fresh technical foundation and carefully bring the useful parts across.
For a completely new business, there may be nothing to migrate. An established company has a different responsibility: improve the website while protecting what customers and search engines already use.
Signs your website needs a redesign
A website built several years ago deserves a review if it has largely been left alone. The strongest reason to act is a growing collection of actual problems, especially when the website is supposed to support sales every day.
Organic traffic or conversions are declining
Start by checking what dropped. Search Console shows impressions, clicks and search positions. Analytics and your enquiry or order records show what happened after the visit. Fewer search impressions, lower click-through rates and fewer completed forms need different investigations.
Google’s own guidance identifies several possible causes of declining search traffic, including technical issues, ranking changes, security problems and changing demand. Compare affected pages and queries, and check the same period in the previous year where the data allows it. See Google’s guide to diagnosing traffic drops.
Test the enquiry form, confirm that notification emails arrive and check that conversion events are recorded correctly. If visitors cannot submit a request, changing the homepage headline will not fix that. If demand has fallen across your industry, a redesign alone cannot create it again.
Once the cause is clearer, you can decide whether you need technical repairs, better content, a different customer journey or a broader rebuild. That gives the project something measurable to improve.
Slow loading and poor Core Web Vitals
Open the website on a phone using a mobile connection. Try to read a service page, open the menu and complete the contact form. Watch for delayed buttons, jumping content and images that take too long to appear.
Core Web Vitals give the performance review specific measurements:
| Metric | What it measures | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | When the largest visible image or text block renders. | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page visually responds to user interactions. | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Unexpected movement of visible content. | 0.1 or less |
Assess these at the 75th percentile, separately for mobile and desktop, so the result reflects most visits. Lab tests help diagnose problems, but a single Lighthouse score does not replace real visitor measurements. See Google’s Web Vitals documentation.
The underlying work may involve reducing server response time, configuring caching, resizing images, reviewing font loading or removing unnecessary JavaScript. A large hero image and a slow third-party booking widget require different fixes. Buying a different builder without understanding the bottleneck is an expensive experiment.
The website no longer represents the business
Perhaps your services changed, the team grew or you now serve a different type of client. Meanwhile, the website still leads with an offer you barely sell and photographs you would no longer put in a proposal.
That is where a redesign can improve more than appearance. You can explain current services properly, show relevant work and make the next step easier to find.
Editing matters here too. Reusable page templates, consistent service layouts and clearly defined content fields let your team publish without rebuilding every page manually. If adding a landing page requires a developer each time, the content management setup deserves attention alongside the visual design.
Accessibility has been overlooked
Small text, weak contrast, missing form labels and menus that cannot be used with a keyboard can make ordinary tasks difficult or impossible for some visitors. A modern visual style can still contain all of these problems.
The 2026 WebAIM Million report found automatically detectable WCAG failures on 95.9% of the one million homepages it tested. This was automated testing of homepages, rather than a complete accessibility audit of every website, but it shows how common basic problems remain. See WebAIM’s 2026 accessibility report.
Use WCAG 2.2 AA as a practical target when scoping accessibility work. Review semantic headings, colour contrast, visible keyboard focus, form labels, error messages and navigation with a keyboard. Automated scans need to be supported by manual testing. WCAG is an accessibility standard, not a Google ranking certificate. See W3C’s WCAG 2.2 standard.
WordPress core, theme and plugin updates are overdue
If updates have been avoided because somebody is worried the site will break, there is already a maintenance problem. Expired licences, abandoned extensions and undocumented custom changes make it harder to understand what can safely be updated.
WordPress recommends keeping software current, using trusted sources and maintaining backups as part of its security guidance. A website continuing to load does not establish that it is being maintained safely. See WordPress security guidance.
Review WordPress core, the active theme, plugins, custom code and the hosting environment together. Test updates on a staging copy before changing the live site, then check forms, page layouts and any connected services. A backup is more useful when the restoration process has also been tested.
Sometimes a controlled update and cleanup are enough. Sometimes replacing unsupported components means rebuilding much of the site anyway. Urgent security work should happen promptly, even if the larger redesign comes later.
Technical SEO and GEO during a redesign
If your website has barely changed in several years, it is sensible to review how clearly it explains the business and how easily search systems can access that information. Buyers should be able to find specific services, evidence of your work, useful answers and current company details.
The technical SEO review should cover whether important pages can be crawled and indexed, whether internal links expose the main services, and whether duplicate URLs have a sensible canonical URL, the preferred version for indexing. Accidental noindex directives, broken links and valuable content buried in inaccessible interfaces deserve attention before adding new features.
Work around AI search visibility is often called GEO, or generative engine optimization. A useful proposal should explain which content and access problems it will address. “LLM ready” on its own describes very little.
For Google’s AI search features, its current guidance continues to emphasize SEO fundamentals. Google says it does not use llms.txt for Search and does not require special AI structured data. Adding a file or installing a plugin does not establish that the underlying visibility problems have been fixed. See Google’s guidance on generative AI search.
Clear service pages, readable text, accurate business information and credible case studies give visitors and search systems useful material to work with. Relevant structured data should agree with the visible content. Other AI services have their own access rules, which should be checked individually where they matter to the business.
Some of this work can be done on your current website. A rebuild becomes useful when the existing structure makes it unnecessarily difficult. For the wider visibility question, see how to get your business mentioned in ChatGPT.
How much does a WordPress website redesign cost in 2026?
The following WordPress redesign packages start at the prices shown, in US dollars. They describe the service options covered in this guide, rather than market-wide minimums. None of them is a flat price for every project. Each proposal needs a defined scope for content, functionality, migration and recurring costs.
Elementor Pro website redesign: from $1,000
(opens in a new tab)For a focused 3 to 6 page business website, Elementor Pro (opens in a new tab) provides a practical visual editing route. The scope can cover responsive page layouts, standard enquiry forms, basic security configuration and technical SEO setup, with the exact deliverables identified in the proposal.
Global typography and colour settings, reusable layouts and consistent spacing make it easier to maintain the design. You should be able to update content, create landing pages from the agreed templates and publish posts without writing code. Training should cover those specific tasks.
At the starting price, the scope needs to stay focused. A brochure site does not quietly include a booking platform, custom calculator, full copywriting project and several integrations because they happen to fit on six pages.
Custom Gutenberg website rebuild: from $2,000
(opens in a new tab)For a site with many services, case studies, team profiles or other repeatable content, a custom Gutenberg (opens in a new tab) build with Skylit.DEV allows the content structure and editing interface to be designed around the business. Custom post types organize different kinds of content. Custom fields hold details such as service attributes or project results. Templates control how those records appear.
Business content should also survive a theme change. WordPress recommends registering custom post types in a plugin rather than tying them to the theme. That separation is useful when planning long-term maintenance and future redesigns. See WordPress guidance on custom post types.
Reusable Gutenberg blocks and patterns provide consistent layouts, while custom development allows more deliberate control over markup, styles and scripts. The route starts from $2,000 for a defined scope. Integrations and deeper performance work increase the quote. It is not a flat rebuild fee.
Both Elementor and Gutenberg can support structured content and integrations. The choice depends on editing requirements, development scope and the level of control needed over the implementation. A custom build still needs appropriate hosting, efficient queries and sensible asset loading to deliver its performance benefits. For broader planning bands across different providers, see the small business website cost guide.
WooCommerce redesign costs: from $2,000 or $3,000
(opens in a new tab)An online store includes the steps after somebody clicks “buy.” Payment methods, shipping, taxes, product variations, order emails, stock updates and refunds all need attention.
Elementor and WooCommerce (opens in a new tab) projects start from $2,000. Custom Gutenberg and Skylit.DEV ecommerce builds start from $3,000. Product imports, subscriptions, accounting connections, complex delivery rules and automations can move the price substantially higher.
The scope should include checks for successful and failed payments, stock changes, order notifications and the behaviour of any external connection. If an inventory system is temporarily unavailable, the integration needs a defined way to report the failure and recover. These details affect both development time and ongoing support.
Store performance also needs to account for dynamic pages. Cart, checkout and customer account pages should be excluded from full-page caching to avoid serving stale or incorrect session content. A fast cached homepage does not establish that checkout works properly. See WooCommerce’s performance guidance.
An existing store also needs a plan for customer and order data, including orders placed while the replacement is being built. The size of that job is not obvious from the number of pages.
There is no fixed ceiling
A company might need several languages, thousands of records, customer accounts, approval workflows or connections to internal systems. It may also need substantial content work and input from several teams.
There is no useful universal maximum for that. Each project still needs an agreed scope and budget, with additional work priced deliberately. “No ceiling” should never mean an open invoice.
What 2026 website pricing research shows
Clutch’s 2026 web design pricing guide says most web design projects reviewed on its platform cost less than $10,000, while reporting an average project value of $38,105.39. The same guide lists around $100 to $149 per hour as a common rate range for web design companies shortlisted on the platform. See Clutch’s web design pricing guide.
Those figures need context. They describe service categories and project scopes in Clutch’s review data. They are not a representative survey specifically of small business redesigns commissioned during 2026. Large projects can pull an average far above what most individual buyers spend.
Use the research to understand the spread of professional project budgets, then compare proposals for the actual work you need. It does not mean your five-page website should cost $38,000. The starting prices above apply to the defined WordPress service options, not to every possible redesign.
Website migration costs: protecting URLs, content and data
Starting with existing content can save time. Starting with undocumented functionality, outdated layouts and years of accumulated problems can add it back.
Someone needs to identify which pages bring relevant traffic, which content should stay, what can be merged and what customers still use. If URLs change, old addresses need to lead to appropriate replacements. Google’s migration guidance specifically calls for URL mapping and permanent redirects where URLs move. See Google’s site migration guidance.
That work belongs in the quote. The SEO migration plan for a website redesign should include:
- A URL inventory:record existing pages and identify useful traffic, backlinks and content before removing anything.
- A redirect map:use permanent 301 or 308 redirects where addresses change, sending visitors to relevant replacements.
- Metadata and link checks:preserve or deliberately revise page titles, descriptions, canonical URLs and internal links.
- Indexing checks:verify the live site’s crawl settings and remove staging-only indexing restrictions at launch.
- Sitemap and monitoring checks:update the XML sitemap and monitor indexing, errors and search performance after launch.
Redirecting every removed page to the homepage is not a thoughtful migration plan. Keeping existing URLs where they still make sense can reduce the amount of change that needs managing.
There should also be a tested backup, a launch plan and a way to recover if something goes wrong. For a store, that includes protecting live orders and customer records during the switch.
Some search fluctuations can happen after substantial changes. The sensible goal is to reduce avoidable disruption and monitor the result, rather than promise that nothing can move. A prettier replacement that loses your useful content or breaks enquiries has failed at a basic part of the job.
Are cheap website redesign offers realistic?
An advertisement promising a complete website for $99 or a webshop for $199 deserves a closer look at the scope. Some offers are real. Others leave out work that buyers reasonably assume is included.
A beginner might accept a small fee to build a portfolio. A provider might assemble a tightly defined template very quickly. A platform might charge little upfront because its business depends on monthly subscriptions. Those can all be legitimate arrangements when the limits are clear.
A template can be enough
If you need a simple online presence and the template fits, there is no reason to make the project more complicated. Reusing layouts is a normal way to reduce work. The questions become useful when you need something outside the package.
The advertised price may only open the conversation
Sometimes the number covers a very small base package. After discovery, the proposal becomes $1,000, $2,000 or more as a starting point for the real scope. That can be reasonable if the advertisement explained what the advertised price included.
Unlimited functionality
Promises such as unlimited functionality, guaranteed rankings or permanent support deserve a clear written explanation. They rarely survive a real brief.
The working hours still need to add up
Take an illustrative project requiring 40 to 80 working hours across planning, communication, building, revisions, testing and launch. That is a workload example, not a measured industry average.
| Total project fee | Revenue per hour at 40 hours | Revenue per hour at 80 hours |
|---|---|---|
| $99 | $2.48 | $1.24 |
| $199 | $4.98 | $2.49 |
Those amounts are business revenue before software, equipment, electricity, internet, advertising, taxes and support. They are not take-home pay.
A $99 package can make sense if it takes very little labour, is subsidized to win future work or earns money through subscriptions. Expecting 40 to 80 hours of experienced, attentive work for the same fee is where the proposal becomes difficult to believe.
Before buying, check the total first-year cost, renewal prices, ownership, revision limits and what happens when something breaks.
What about outsourcing to India, Pakistan or elsewhere?
Lower operating costs can make a competitive quote possible. That is a reason to consider a provider, but the country does not tell you whether the person can build your website or understand your requirements.
Check communication directly. Have a call in the language you will use for the project, ask the provider to explain the requirements back to you, and review relevant live work. Agree on who does the work, how changes are priced and when support is available.
Rates vary too much to set one worldwide minimum for capable work. Look for a credible implementation and handover plan, with evidence that the provider has handled similar requirements. The guide to hiring a web developer covers that evaluation in more detail.
Does AI reduce website development costs?
AI can reduce the time needed to write layouts, produce repetitive code and work through implementation problems. The benefit depends on whether the developer can specify the task accurately, understand the output and recognize when it is wrong.
The tools also have operating costs. Premium subscriptions and usage-based API charges sit alongside hosting, design software, testing tools and licences. For context, my own heavy-use AI bills have exceeded $1,000 in a month. That is one example of the cost of the workflow, rather than a minimum every developer needs to spend.
There is also work around the implementation. Somebody must understand the business, choose the right approach, check the output, handle exceptions, test forms and payments, protect existing content and take responsibility for the launch. Generating a page quickly does not prove those things have been handled.
The “type a prompt and your business website is done” demonstrations become misleading when they present a good-looking first result as a finished client project. Generated work still needs checks for accessibility, compatibility with the existing site and behaviour when an integration fails. Those requirements apply regardless of who or what wrote the first version.
That does not mean AI can never lower a project’s price. A tightly scoped job may become cheaper, or the same budget may buy more work. The saving depends on the whole project, including review and corrections, rather than the time it takes to generate the first version.
Finding clients is part of running a development business too. Advertising, proposals and discovery take time and money. In a competitive market, providers may raise or lower prices, accept smaller margins or change what they offer. Your quote should make clear what work the budget actually buys.
You would not price a house by adding up the bricks and cement and deciding that everything above that is unnecessary margin. WordPress may be available without a software purchase, and AI may produce code quickly, but neither tells you what it will take to build and maintain the website your company needs.
What a website redesign proposal should include
A useful proposal should make these points clear:
What stays and what changes
Pages, URLs, content, data and existing functionality. Rebuilds should say what is being migrated, not only what is being designed.
What is included
Design, content work, forms, integrations, migration, testing and launch support. Two quotes cannot be compared if one of those is missing.
How you will edit it
Updating pages, creating landing pages and publishing posts. The handover should cover the tasks you actually need.
How quality will be checked
Representative mobile layouts, keyboard navigation, agreed performance targets and complete form or checkout journeys.
What you own
The domain, website accounts, content, files and access needed to move providers. Ownership should not be an afterthought.
What costs recur
Hosting, domain renewals, Elementor Pro or other licences, external services and maintenance. The build fee and the running costs should be visible separately.
Define how extra work is handled: revision limits, scope changes, pricing and approval before additional work begins. Ongoing updates, backups, uptime monitoring and occasional fixes still need an owner after launch. Otherwise, the new website can accumulate the same maintenance problems as the old one.
Final takeaway
If the existing foundation is healthy, targeted updates may be enough. If it keeps getting in the way of routine changes, reliable updates and the functionality your business needs, a rebuild becomes easier to justify.
The right time is when those problems are costing you useful opportunities, making ordinary work difficult or leaving known maintenance issues unresolved. You do not need to wait until the website stops working completely.
A worthwhile redesign gives you a website that represents the business properly, works reliably and is easier to manage after launch. The budget should make that outcome possible.
If you are planning a WordPress website redesign, send me your current URL, the main problems and the functionality you need next. I can review the existing setup, recommend an Elementor Pro or custom Gutenberg approach with Skylit.DEV where appropriate, and define the migration, development and support scope before quoting the project.
Frequently asked questions
How much does a small website redesign cost in 2026?
The service options in this guide start from $1,000 for an Elementor Pro brochure website of around 3 to 6 pages, or $2,000 for a custom Gutenberg build with Skylit.DEV. Those are starting points for a defined scope, not a flat fee. Content work, migration, functionality and performance requirements determine the final quote.
Is updating an existing website cheaper than building a new one?
It can be, when the current technology is supported and the problems are limited. If repairs require replacing much of the foundation, a rebuild may be a better use of the budget. An inspection should establish that before committing to either route.
Can a rebuild keep my domain, content and Google visibility?
You can normally keep your domain and migrate useful content. Keeping suitable URLs and planning redirects where they change reduces avoidable disruption, but rankings and traffic cannot be guaranteed. Migration and checks after launch should be part of the project.
Will I be able to edit the redesigned website myself?
That should be agreed as part of the build. Elementor Pro can support visual editing, while a custom Gutenberg setup can provide reusable blocks and layouts. The handover should cover the tasks you actually need, including page updates, landing pages and posts.
How much does an ecommerce redesign cost?
The ecommerce service options here start from $2,000 with Elementor and WooCommerce, or $3,000 for a custom Gutenberg and Skylit.DEV build. Those are starting points, not a complete store price. Product data, existing orders, payment and shipping requirements, integrations and automations can increase the scope substantially.
