The short answer
Start with the problem customers or staff are having. If a focused fix will solve it and the rest of the site is reliable, improve what you have. If the same layout is getting in the way across several pages, consider a phased redesign. Compare a rebuild when the underlying setup keeps blocking important work. An old-looking site alone isn’t a reason to replace everything.
A clearer next step
Fix, redesign or rebuild?
Answer seven questions about your WordPress website. Get a suggested direction, the reasons behind it and practical next steps. No email required to see your result.
Start with the task that isn’t working
Try to do the thing that’s causing trouble: choose a service, find a store, send an inquiry, buy a product or update a page. Use the real site, including on a phone. Where do you get stuck?
Work through the questions below. Fix a broken form now, even if you’re planning a redesign later. A slow page, dated styling or a long plugin list deserves a closer look, but doesn’t tell you on its own that you need a new site.
Can you fix this part and keep the rest of the site working well?
If not, look at the layout those pages share.
If yesRepair or improve
Fix the broken task, update the content or improve the page. Agree how you’ll check that it works.
Would changing one shared page layout solve the problem?
If not, look at what’s limiting the whole site.
If yesRedesign in phases
Try the new service, product or location layout on a small group of pages. Check menus, forms and styles before using it elsewhere.
Is the underlying setup blocking several things your site needs to do?
If not, investigate another cause before committing to a rebuild.
If yesCompare a rebuild
Find out what’s causing the problem, then compare rebuilding with the full cost of repairs. You can rebuild and stay on WordPress.
Still unsure? Agree a focused review to find the cause, compare options and decide how success will be checked. You don’t need to choose a rebuild before you know what’s wrong.
What can you keep?
Even a rebuild can keep useful content and page addresses. These examples show what might change in a repair, phased redesign or WordPress rebuild. Green marks the part being changed; the other parts stay or need checking before you decide.
Focused repair
- changeForm connectionRepair the failed delivery.
- keepPage templatesKeep the working layouts.
- keepContent and URLsKeep the useful destinations.
Phased redesign
- changeService-page templateImprove the layout service pages share.
- checkEditing and formsCheck editing and inquiry delivery.
- keepOther page familiesKeep the reliable sections.
Rebuild on WordPress
- changeTheme and editing systemReplace the setup causing the problem.
- checkForms and integrationsRetest before reconnecting.
- keepUseful content and URLsRetain unless change is justified.
Keep: retain it and test it. Check: find out whether it will work with the change. Every replacement should have a reason.
Example: buyers can’t choose a service
Imagine a B2B supplier whose service pages attract relevant visitors. Buyers struggle to choose a service, and inquiries arrive without the location details sales needs. Staff can still edit the site. Nobody has found a technical reason it needs rebuilding.
Start by making the services clearer, collecting the missing details and checking they reach sales. Then see whether inquiry quality improves. If that doesn’t solve the problem, use what you learn to decide what needs more work.
Start with improvement
- Observed problem
- Unclear service labels and missing information for sales routing.
- What to change
- Rewrite priority service pages and repair the form-to-CRM mapping. Keep useful page addresses.
- How to check it
- A buyer can select the right service on mobile; a labeled inquiry reaches the intended CRM record and owner.
What would justify more work?
- Phased redesign
- Several service pages need a common structure the current template cannot express.
- Rebuild review
- An unsupported plugin or underlying setup blocks several important tasks, and a focused repair won’t resolve it.
- Business review
- If delivery works but inquiry quality stays weak, investigate the audience and offer before changing platforms.
Who does what?
Marketing supplies service detail, the developer implements the agreed pages and connection, and sales owns routing rules and receipt checks. Review real inquiry quality separately from test delivery.
When keeping the site updated becomes the problem
A rebuild is easier to judge when you can name what it will change for your team. “Give us a newer design” is vague. “Let staff update products, promotions and store details without fighting the site” describes an everyday problem worth solving.
During the November 2023–February 2025 engagement, AV Social Strategies replaced Share’s difficult-to-maintain Antilles website with WordPress and connected ecommerce, catalog and local-search work. The delivered menu, location and rewards pages supported shopping and store discovery.
This case shows why publishing and customer tasks belong in the brief. It does not establish that every dispensary needs a platform move or that WordPress alone caused the wider business results.
Find the selection
Categories organize the shopping task. Review how your team maintains that structure as the catalog changes.
Understand a product
Product information needs an agreed source and update process across the content site and commerce system.
Continue the journey
Rewards and store information belong in the customer path, with clear owners for the connected tools.
Keep the routes your customers already use
Customers may arrive through an old search result, a bookmarked product, an ad or an email. After a redesign, those links still need to take them somewhere useful. Sending every old page to the homepage leaves visitors searching again.
Keep useful URLs where possible. For necessary changes, Google’s site-move guidance covers mapping old pages to relevant replacements, redirects, internal links, sitemaps and monitoring. Search rankings can fluctuate during a move.
Protect these through every release
- Links: keep useful page addresses. If one must change, send visitors straight to its closest replacement.
- Customer tasks: test inquiries, shopping, account access and store or service selection.
- Your team’s work: check that records, editing tools and system connections still work, and agree who looks after them.
- If something goes wrong: have a usable backup, someone who can make the launch decision and a plan to restore the important functions.
Compare what each option will actually solve
A repair can leave your team working around old problems. A rebuild can replace things that already work. Ask each agency what its approach fixes and what you’ll still be dealing with afterward. Include content, design, development, moving the site, integrations, testing and staff training in the comparison.
Add hosting, licenses, support and the time your staff will spend on updates. Who supplies the copy and data? Who approves changes? What happens if either arrives late? Our custom WordPress cost guide walks through those questions.
For a phased redesign, agree which pages change first, how the old and new layouts will work together and who maintains them. Start with a small, meaningful part of the site. If you’re also considering a different platform, read our WordPress, Shopify and BigCommerce comparison.
Know why you’re choosing the work
You should be able to explain what’s wrong, what you’ll change and how you’ll know it helped. If the content is the problem, Google’s helpful-content questions are a useful starting point. A new theme won’t answer a buyer’s question for you.
The WordPress website assessment can help you organize what you’re seeing. You can read your result without giving an email address; it’s based on your answers, not a site scan. If you need help finding the cause, we can scope a paid audit or include that investigation in ongoing management.
Before you commit, check these five things
- Can you show someone the problem a customer or staff member is having?
- Do you know what’s causing it—and what you still need to find out?
- Have you agreed what changes, who does it and what stays?
- How will you check the fix, then review whether it helps the business?
- What would make you change the recommendation?
Sources and further reading
The decision tree and scope map guide investigation; they do not diagnose a website. The B2B scenario is illustrative. Share is a documented client example. Google’s guidance supports the search and content recommendations.
