Nine times out of ten, the companies reaching out to us for a website redesign actually don’t have a design problem.

The site works, nothing’s on fire, but the backend is cluttered, and staff can’t find their way around it. Plus, templates are inconsistent, and every change goes through a developer. So the request is “we need a new website”.

What makes it even more interesting is that most companies have already had the redesign before. The site was clean at launch and then drifted back to this. One might blame the vendor and say that rtCamp can do a better job, but that’s not really a vendor’s fault. Teams rebuild WordPress again because the roles, templates, and workflows weren’t established at launch, so they drift again, as if on schedule.

In this WordPress site redesign guide, we’ll cover what a redesign costs, what can go wrong, whether you should replatform instead, and how to run the redesign so search traffic survives it. And, most importantly: how to fix processes and make the next WordPress redesign your last one.

TL;DR

• Most companies asking for a WordPress redesign have an operations problem, mistaking it for a design one.
• A redesign resets the site, but doesn’t change processes, which is why the same issues reappear in 3 years.
• Approximate WordPress website redesign cost: $5,000–$25,000 for a template refresh, $25,000–$100,000 for a full single-site redesign, $100,000–$250,000 for an enterprise rebuild with governance, $250,000–$600,000+ for multi-brand consolidation.
• Timelines: 8–12 weeks for a template refresh, 4–5 months for a full redesign, 9–12 months for a multi-site programme.
• Moving to AEM or Sitecore doesn’t fix governance. You’d pay six figures to inherit the same problem.
• Search rankings can survive a redesign if URL mapping and redirects are handled before the build.
• Whether AI is cheap or expensive is decided by the content model.
• You can avoid the need for a redesign every couple of years if your company treats the site as a product with an owner, an ongoing budget, and a backlog.

WordPress redesign can’t fix an operations problem

It may sound strange from a WordPress VIP Premier Partner that has accomplished 500+ WordPress projects, but this is us being honest with you. From our experience, companies too often think that they need a visual redesign, while in reality all their issues revolve around operations, which is an entirely different problem.

What the brief mentionsWhat it really meansNew visual designReusable page templatesEasier content managementReduced dependency on developersModern CMSSimple and clear workflowAccessibility complianceComponent rules editors can’t accidentally breakMulti-site or chapter refreshLocal flexibility inside central governanceFuture-proofingRoom to add AI features later

The companies requesting a redesign are, in most cases, looking for a better way to run their website. They call it a redesign because it has a clear price and a known process. An operating model is harder to put in an RFP.

Tip: There’s a quick way to tell whether you need a redesign or rather a rebuild. Take the 3 things that frustrate your team most about the current site, and for each one ask whether a new design would fix it. If most of them survive the redesign, the design was never the problem.

So, what do you really need if not redesign? Let’s briefly see the 3 main options. 

Redesign, replatform, or fix the operating layer?

3 different problems get called the same thing. We recommend matching the issue to the actual problem to save time and budget.

ProblemWhat it isSolutionDesign looks dated, everything else worksA visual problem✔️ A redesignEditors wait on developers for routine changesAn operating layer problem✔️ Component and permission work inside the current siteOne component exists in 5 versionsA design system problem✔️ Consolidate to a governed component librarySite is getting slowerUsually plugin and dependency debt✔️ Audit, remove, replace with governed codeMultiple brands or chapters drifting apartAn architecture problem✔️ Shared platform with per-brand flexibilityLicence costs no longer justify the platformA platform economics problem✔️ Replatform

Sometimes the answer really is a redesign. If the content model is sound, editors are working independently, but the site looks outdated, then go for a redesign and don’t let anyone talk you into an architecture project.

There’s also another, more radical fix: move to another platform. Here’s our take on whether it works. 

Would moving to AEM or Sitecore fix the problem?

It’s worth asking if moving from WordPress to AEM or Sitecore could solve the problem. Adobe Experience Manager has strong digital asset management and a mature workflow engine. Sitecore’s content operations tooling is great, too.

But AEM’s annual licence runs $80K to $300K without implementation. The configured version with the DAM and the workflow engine takes months and a six-figure budget. Across the enterprises we’ve worked with, most use 30 to 40% of what they’re paying for, and five-year total cost of ownership lands somewhere between $900K and $1.8M. 

We call that the Platform Tax: it’s the gap between what you pay for and what you use. Licensing covers the whole platform, while your team uses only a part of that functionality. Most enterprises use only 30 to 40% of a product.

Finally, a licensed DXP doesn’t solve the governance problem. 

For example, Videojet ran 28 country websites with 12,000 pages of product documentation in 22 languages on Adobe CQ5. Desktop and mobile were on separate subdomains under different vendors. When CQ5 reached end of life, upgrading to AEM was priced beyond what was justifiable, so they moved to WordPress VIP, keeping URLs, tags, and markup intact while marketing kept publishing throughout. The governance problem they had on Adobe came from 28 sites built at different times with no shared rules.

You’ll find the same or similar problem on any platform. What decides whether you have it is the maturity of the operating layer.

To see better what solution might fit you, let’s see when the redesign is not the right one.

When not to redesign

Here are 3 situations where redesign isn’t the right solution:

• The design is fine, and the content model is the problem. If your pages look acceptable and the complaint is that publishing is slow, you don’t need a redesign. Structure the content, define the components, and the same design will feel like a different website.
• A component library exists, but it isn’t enforced. Some companies already commissioned a design system in the last redesign. It’s in Figma, it’s documented, and the site doesn’t follow it because nothing in the editor requires it to. That’s an implementation and permissions job measured in weeks.
• The constraint is how the team operates. Without an editorial calendar or an approval process, you’ll get an inconsistent site on any CMS. We recommend fixing the process first, so you’ll know afterwards whether you still need the redesign.

Now we are done with the cautionary part, so let’s finally see the cost of professional WordPress site redesign.

WordPress website redesign cost ranges

Below are the 4 most common requests with their typical market rates.

What you’re buyingTypical rangeWhat it includesTemplate refresh on your existing install$5,000–$25,0003–6 reusable templates, block-based editing, accessibility pass, basic training. No migration.Full single-site redesign$25,000–$100,000New design system, 10–20 templates, content migration, integrations, redirect strategy, accessibility remediationEnterprise rebuild with governance$100,000–$250,000Content modelling, component library with rules, permissions and workflow, complex integrations, phased launch, documentation, hypercareMulti-brand platform consolidation$250,000–$600,000+Shared architecture across brands or regions, per-brand flexibility, migration off one or more legacy platforms

These are approximate ranges, but if you want a specific estimate, the best is to get in contact with a team that has relevant experience in WordPress redesign and modernization services.

Now, let’s cover the main concern about redesign: search rankings. 

How to redesign a WordPress website without losing search rankings

This fear keeps redesigns sitting in draft, but the ranking issue is preventable with the right process.

After 500+ WordPress projects, here’s the process we at rtCamp use and recommend for saving rankings:

• Map every URL before the build starts. Done early, it shapes the information architecture, which means fewer redirects and less lost authority.
• Validate redirect chains. Chains need to resolve in one hop.
• Run a crawl simulation before the DNS switch. Crawl the staging site against the live URL inventory and compare, so you’ll see every missing destination.
• Move the metadata across. Port titles, descriptions, canonical tags, alt text, and structured data instead of regenerating them on the new site.
• Preserve the internal link graph. Rankings depend on internal linking. A new navigation without them will cost you positions even with perfect redirects.
• Treat Core Web Vitals as part of the SEO scope. Performance is a ranking input, and a redesign is the best opportunity to fix it.

This advice holds up in practice. VinSolutions moved off Kentico onto WordPress VIP multisite, redesigned in the process, and kept every SEO rank while improving Core Web Vitals by 48%. FleetNet America came off Drupal 9 on Acquia in weeks, with SEO preserved and Core Web Vitals twice what they were.

Now, let’s get to the WordPress website redesign process to briefly see what each step requires.

The redesign process, phase by phase

Most redesign projects have the following 5 phases, but we offer the 6th one as part of our engagement. This is how we at rtCamp sequence it:

1. Audit. First, we do content inventory, technical review, plugin and dependency audit, accessibility baseline, and URL inventory. We also take a look at how your team publishes today to see where exactly the issues are. The output is a roadmap.
2. Pilot. We build one page type end-to-end, including content model, components, editor experience, and permissions. It allows us to settle most of the arguments that would otherwise surface later.
3. Phased build. Our team prepares templates, components, migration, and integrations in an order determined by dependency.
4. Enablement. rtCamp provides role-specific training, written documentation, and a reference site inside the platform that catalogues every block, pattern, and typography rule. When we unified 3 publications for Private Media, we built this as a Documentation Kit inside their multisite network, so the rules stayed available as the team changed.
5. Hypercare. We offer 30 days of post-launch stabilisation with the build team still on it, so everything goes smoothly after launch.
6. Evolution. This is the phase most redesign proposals don’t include, unfortunately. At rtCamp, we provide a dedicated person who owns the component library, approves additions, and keeps the platform current.

Our tip: don’t start with a homepage

Every redesign kickoff wants to see the homepage first. It’s the page executives look at, so it becomes the page that gets designed, reviewed, and re-reviewed while the rest of the site waits.

But the homepage is the least reusable page on the site. It has a layout that appears only once, and its components exist nowhere else. Starting there produces a beautiful page and no system, and the templates then get built quickly at the end of the budget.

We recommend starting with the page type you publish most. As a result, the homepage will be designed faster, because by the time you design it you’ll know what the components are.

What you should have as a result of a redesign

If you’ve already gone through a WordPress website redesign in the past, you know how easily things can derail after launch. 

The secret to not making it happen is knowing exactly what you should have at the end and making sure your partner knows this from the first call.

Here are the main aspects to highlight during the first consultation as core expectations:

• Staff should be able to build a landing page from approved components. No need for a developer. The components are on-brand and accessible because they were built that way, so nothing has to be reviewed for compliance afterwards. This is totally doable: Dealertrack, part of Cox Automotive, cut landing page time to market by half when this replaced their previous process.
• Editors should have freedom inside a locked pattern. They can change the text, the image, and the link, but they can’t change the heading level, break the colour contrast, or drag a block somewhere that collapses on mobile.
• Permissions should be tiered by role. Contributor, editor, manager, administrator, with regional or brand scoping where the company needs it.
• Publishing should follow a defined path. Draft, review, approval, publish, with scheduling and expiry dates where content has a shelf life.
• Everything should be documented inside the platform. There should be a reference site within the network that catalogues every block, component, typography rule, and style guideline.

This level of governance is what you should expect from a redesign to avoid the same problems in the future. 

What if you’re redesigning more than one site?

Everything so far assumes one site, but if you run several, the redesign question changes.

Here’s how it tends to go. A company has sites for a few brands, regions, or chapters, each built by a different team, so each ends up with its own templates, plugin stack, and way of shipping changes. Then a redesign gets approved, and because the sites are separate, they get quoted and built separately. 

The maths makes this painful. On one site, a governance gap is not so crucial, but across 10 sites the same gap is disastrous. Each site builds its own version of the component, installs a plugin nobody vetted, and within 2 years, the 10th site costs as much to build as the first did.

Running WordPress Multisite doesn’t prevent any of that on its own. Multisite shares a codebase and a database, but it doesn’t decide who can publish what, which components exist, or what happens when someone needs a layout that isn’t in the library. 

What works instead is OnePress. It’s an open-source framework with 6 modules covering design, plugins, media, search, users and logs, and it puts 70–80% of the estate on common foundations while each site keeps its own identity, content and team. It’s GPLv2, so the code is yours, and you can hand it to another vendor whenever you want.

If you’re scoping a redesign for one site now and expect to touch the others within a couple of years, this is worth considering. Redesigning them one at a time is almost always more expensive.

To give you a better idea of how this works, here’s how our client has moved to OnePress and what results it gave them.

How Cox Automotive moved 8 brands to one platform

Cox Automotive came to us with 8 brands on 8 separate builds, split across Adobe Experience Manager and Kentico. We consolidated them onto one governed WordPress platform in 12 months, reusing about 70% of the design across brands, and brand commonality went from 2% to 50%. Engagement rose 103%, leads doubled, and performance improved 21%.

Source: Coxautoinc.com

Now, let’s move on to the topic that companies always include in RFPs: AI.

Should AI be part of a redesign?

A couple of years ago, this question didn’t come up, but now it’s in most redesign conversations. Municipal websites, professional bodies, membership organisations and mid-sized nonprofits are all raising it.

The specific asks repeat, like site search, a built-in chatbot, content summaries, and translation. Most want to know they can add these later without rebuilding.

But the thing is, every one of those capabilities depends on how your content is structured. A chatbot that answers questions about your services needs those services stored as content with fields and relationships. Search needs a taxonomy. Translation needs content separated from layout.

Which means the thing that decides whether AI is cheap or expensive is the content model you’re choosing now. If you get it right, you’ll be able to add a chatbot in weeks. But if you get it wrong, each one of these features will become a bespoke build with a low return. That’s a large part of why 42% of enterprise AI pilots died before reaching production in 2025, up from 17% the year before. 

When we work on AI, we use the 5 AI Dimensions Framework: 

Content discovery on LLMs

AI-led editorial

AI-led personalisation

WordPress as an AI-integrated platform

AI-accelerated development

A redesign decides the first, second, and fourth directly, because all three come down to how your content is modelled and how your editorial system works.

WordPress 7.0 ships with a native AI layer, including 3 AI connectors rtCamp contributed for OpenRouter, LM Studio, and OpenAI. So much of what used to be custom work now comes with the platform.

To sum up everything we’ve covered, here are the questions you might want to add to your next RFP. 

12 questions to put in your redesign RFP

These 12 questions might help you choose a true partner instead of another vendor:

1. Who owns the component library after launch, and how does a new component get approved and added?
2. What exactly can each editor role publish without approval, and what does the platform prevent them from doing?
3. What is your plugin vetting process, and how are installs gated?
4. Who owns the platform in month 13, and what does that cost?
5. What documentation is delivered, where does it live, and how is it kept current?
6. How is accessibility validated, by what method, and is remediation at the component level or the page level?
7. Can you show us your URL mapping and redirect validation process, and when in the schedule it happens?
8. What training is delivered, broken down by role, and is it recorded?
9. What does post-launch support cover, for how long, and what happens later?
10. Do we receive source code, design files, and full administrative access, with no dependency on you to make changes?
11. If we add a second site or brand next year, what carries over and what gets built from scratch?
12. Which of your engagements has run longest, and how does that platform differ now from what you launched in year one?

But the main concern companies have before the redesign is the question of when they’ll have to do it again. Indeed, redesigns done for a tick don’t bring meaningful changes, so here’s our advice on how to avoid that.

How to avoid the need to redesign every couple of years

It usually happens like this. Marketing needs a form, so someone installs a plugin. Later it’s a slider, then a popup, then an events calendar. Each one brings its own CSS and JavaScript, and most of it loads on every page whether that page uses it or not. 

A redesign will fix that for a while. The new site is faster on launch day because there’s less on it, and then the same thing starts again. 

To avoid this cycle, you have to introduce a change in how you think about the website.

Almost every company treats its site as a project. A project has a budget, a launch date, and an end. When it ends, the team disperses, and the agency moves on. That’s why the site is at its best on launch day and gets a little worse every week after, until the gap between what it is and what you need is wide enough to justify another redesign. So you do it again.

The alternative is to treat the site as a product. A product doesn’t launch and end. It has an owner, a small ongoing budget, a backlog, and a rhythm. Change is normal rather than exceptional. 

That shift is harder to sell internally than a redesign, because it has no launch date and nothing to unveil. But it’s the only way you end up with a better site in year five than the one you launched.

Before you scope, find out what needs rebuilding

Sometimes the design really is the problem. Still, often it’s the content model, the component rules, or the fact that nobody has owned the platform since the last launch.

That’s what our free 20-hour discovery audit is for. We map your current architecture, audit the content model, plugins, and accessibility baseline, and help you build the internal business case. It happens before any contract is signed, and if the answer is that you need a straightforward redesign, we’ll tell you that.

Get a free 20-hour audit of your WordPress setup

We’ll audit your content model, plugins, and accessibility, and help build the business case.

contact us to book a call

Frequently Asked Questions

How long does a WordPress redesign take?

A focused template refresh on an existing install typically runs 8–12 weeks. A full redesign with content migration, integrations and accessibility work usually runs 4–7 months. Multi-site programmes with a governance model run longer, 9–12 months from contract to launch.

Can we redesign without migrating all our content?

Yes, and it’s often the right call. Content audits routinely find that a large share of pages get no meaningful traffic. Migrating less is cheaper, faster, and better for the reader.

Who owns the code and the design files?

You. At rtCamp, we provide full administrative access, source code, and design files, with no dependency on us to make changes. 

Can we add AI features later?

Yes. We treat AI readiness as part of the redesign rather than a phase after it.

Do we have to move to WordPress VIP?

No. VIP suits organisations with high traffic, strict compliance requirements, or large editorial teams. Plenty of clients run governed WordPress on other managed hosts or their own cloud infrastructure. We’ll recommend based on your traffic, security review, and internal capacity. For a free consultation, contact us here.

Can you work with our existing design team or agency?

Yes. Some clients bring finished designs and ask us to build and govern the platform. Others have an in-house brand team we build the component library with. 

Do we need to stop publishing during the redesign?

No. From our experience, when we moved Videojet‘s 28 sites and 12,000+ pages off Adobe CQ5, marketing kept publishing throughout. It takes planning and delta migration, but it’s worth it.

TL;DR

WordPress redesign can’t fix an operations problem

Redesign, replatform, or fix the operating layer?

Would moving to AEM or Sitecore fix the problem?

When not to redesign

WordPress website redesign cost ranges 

How to redesign a WordPress website without losing search rankings

The redesign process, phase by phase

Our tip: don’t start with a homepage

What you should have as a result of a redesign

What if you're redesigning more than one site?

How Cox Automotive moved 8 brands to one platform

Should AI be part of a redesign?

12 questions to put in your redesign RFP

How to avoid the need to redesign every couple of years

Before you scope, find out what needs rebuilding

Get a free 20-hour audit of your WordPress setup

Frequently Asked Questions

How long does a WordPress redesign take? 

Can we redesign without migrating all our content? 

Who owns the code and the design files? 

Can we add AI features later? 

Do we have to move to WordPress VIP?

Can you work with our existing design team or agency?

Do we need to stop publishing during the redesign?

On this page

WordPress redesign, WordPress website modernization

Credits

Aviral Mittal

Author

Aviral Mittal

Author

Aviral Mittal is the Chief Marketing Officer at rtCamp, where he established and leads the marketing function, building and growing a team of 20+ specialists across content, SEO, design, and growth…

VIEW PROFILE

Contributions and Updates: Usama Usama Quraishi Marketing Executive

Related articles

• Migration process, timeline & team

  Articles

• Kentico to WordPress migration guide: How enterprises do it safely

  Articles

Comments

Leave a Reply Cancel reply

Name*

Email*

Comment*

Submit

Δ