Nobody redesigns a website for fun. It's usually a slow build-up of small annoyances that eventually cross a line: a sales rep who apologises for the site before sending a prospect the link, a marketing hire who asks why publishing a page needs a developer, a board member who pulls it up on their phone and says nothing. This guide covers both halves of the decision: how to tell whether you actually need a redesign, and what the process looks like week by week once you commit.
Part 1: The Signs You Need a Redesign
1. Traffic is flat or growing, but leads aren't
The clearest signal there is. If traffic sources look right and volume is holding, but form fills and demo requests are flat, the site itself is the leak. Usually the value proposition doesn't land fast enough, the calls to action are vague or buried, or there's too much friction between "interested" and "submitted a form". Our WordPress lead generation work covers what a site built to convert looks like.
2. Publishing anything new requires a developer
Marketing should be able to add a page, update a case study or launch a landing page without filing a ticket. If every change routes through a developer, that's an architecture problem, and it compounds: the harder publishing is, the less gets published.
3. Load time has quietly got worse
Slow pages are often the visible symptom of years of plugins, unoptimised images and database bloat. They lose visitors before they see your value proposition and work against your Core Web Vitals and rankings.
4. The site looks like it was built for a different company
Not "outdated" in a vague aesthetic sense, but misaligned: generic service lists that could describe any competitor, messaging that predates a positioning shift, a homepage leading with something you no longer prioritise.
5. Mobile is an afterthought
A meaningful share of B2B research happens on a phone, even when the decision is made at a desk. Cramped forms, buried navigation and case studies that are hard to read on mobile lose those moments.
6. Nobody can say when it was last properly audited
A technical SEO pass, a security review, an accessibility check. If the honest answer to "when did someone last check this properly" is "we're not sure", treat that as a signal on its own.
A useful gut check: on your phone, try to complete the journey a prospect would: find a case study relevant to their industry, then find the contact form. If you hesitate or get frustrated on your own site, a prospect with less patience and no loyalty to your brand will bounce well before you would.
Refresh or Rebuild?
Not every sign means "start a full rebuild tomorrow". Load time and an overdue audit are often maintenance and optimisation problems you can fix without touching the design. A content structure that can't support self-service publishing, or a value proposition mismatch baked into the page templates, usually needs a rebuild. Get an honest technical and content audit before committing budget to either, and check what a rebuild realistically costs with our B2B WordPress cost breakdown.
Part 2: The Redesign Process, Week by Week
Vague answers ("it depends on scope") are technically true and completely unhelpful. This is what a standard B2B WordPress redesign realistically looks like.
Weeks 1 to 2: Discovery
Stakeholder interviews, a technical audit of the current site, and a content and SEO review to establish what must be preserved. This phase ends with a scoped project brief both sides agree on. Rushing discovery is the most common cause of scope disputes three months later.
Weeks 3 to 4: UX and wireframes
Information architecture and low-fidelity wireframes for key templates: homepage, service pages, resources. Navigation and content hierarchy get decided here, before anyone looks at colours or fonts, which keeps feedback focused on structure rather than taste.
Weeks 5 to 7: Visual design
High-fidelity design for the approved wireframes, typically two rounds of feedback. Reopening approved wireframe decisions here is the main source of scope creep.
Weeks 8 to 13: Development
The custom theme is built against the approved designs: templates, custom plugin or block work, integrations and content migration. It's the longest phase and the one clients see least of, which is why regular progress updates matter.
Weeks 14 to 15: QA, SEO and launch
Cross-browser and device testing, a full redirect audit if URLs change, performance testing against Core Web Vitals targets, and a staged launch with the new site tested in parallel before cutover.
What actually extends timelines isn't development speed. It's content delivery and sign-off discipline. Late copy and images, or approved decisions reopened two phases later, add weeks that have nothing to do with how fast anyone can build.
Protecting Your Rankings
A redesign that changes URLs without 301 redirects, drops existing meta data, or launches with unresolved technical issues can cost real ranking ground. Crawl the current site first, map every URL, carry over titles and descriptions for your top pages, and monitor rankings and crawl errors daily for the first two weeks after launch.
What to Ask an Agency
Ask what happens if content isn't ready on time, and whether their timeline assumes you'll hit every delivery date. A realistic proposal builds in buffer and is upfront about what causes slippage. Our B2B website RFP template lists the other questions worth asking. If you're weighing a redesign, book a scoping call and we'll tell you honestly whether you need a rebuild or a refresh.
FAQ
How do I know if my B2B website needs a redesign?
The clearest signs are traffic holding steady while leads stay flat, marketing needing a developer for every content change, worsening load times, messaging that no longer matches your positioning, a poor mobile experience, and no recent technical, SEO or accessibility audit.
How long does a B2B WordPress redesign take?
A standard B2B WordPress redesign typically takes 12 to 15 weeks from discovery to launch: two weeks of discovery, two of UX, three of visual design, six of development and two of QA and launch. A refresh of a sound existing build can be faster; portals, membership functionality and deep integrations can take 20 weeks or more.
Do we need a full rebuild or just a refresh?
If the site looks dated but the content architecture, page speed and technical foundation are sound, a design refresh can solve it. If publishing requires developer time, the site is structurally slow, or the content model can't support what the business needs now, only a rebuild will fix it.
What causes redesign timelines to slip?
Mainly content that isn't ready when design and development need it, and scope changes after wireframes are approved. Both are avoidable with a content plan agreed before kick-off and a change process that treats new requests as scoped additions.
Will a redesign hurt our search rankings?
Only if it's done carelessly. Map every changed URL with 301 redirects, preserve or improve titles and meta data, run a technical audit before launch and monitor rankings afterwards. Planned this way, rankings typically hold or improve within a few months.
Does the site stay live during the redesign?
Yes. The new site is built and tested in a staging environment while the current site runs normally. Cutover at launch typically takes minutes, not hours.
Written by
Meera Iyer · Creative & UX Strategist
Meera leads UX strategy and creative direction. She translates brand identity into digital experiences that convert and retain customers.
Meet the team →