Before rebuilding an online shop, find the part that is costing you sales. A new theme is not a fix if the problem is slow checkout, poor product data or missing stock information.
Open the store on a phone and go through a real order. Note every point where you hesitate, wait or need to go back.
Sign 1: mobile shopping is difficult
If product selection, cart or checkout is awkward on a phone, fix that before changing platforms.
Mobile problems include:
• tiny controls • difficult menus • intrusive popups • poor filters • broken payment elements
Sign 2: the store is consistently slow
Performance problems can come from:
• hosting • theme • plugins • database • images • scripts
Diagnose before rebuilding. A faster server will not fix a badly coded front end, and a new theme will not fix an overloaded database.
Sign 3: the platform blocks business requirements
A rebuild becomes more reasonable when you cannot reliably implement:
• B2B pricing • subscriptions • complex shipping • multilingual selling • integrations • custom product logic
Sign 4: maintenance is unsafe
Warning signs include:
• abandoned plugins • unsupported PHP • updates constantly breaking the site • heavy custom code nobody understands • no staging environment
Sign 5: checkout conversion is poor
Do not assume design is the only cause.
Review:
• traffic quality • shipping cost • product information • payment failures • trust • checkout fields
A rebuild cannot fix a poor offer.
Sign 6: the catalogue has outgrown the navigation
As product ranges grow, categories and filters may need restructuring.
This can justify a broader UX redesign.
Optimise or rebuild?
Optimise when:
• platform is healthy • problems are isolated • theme is maintainable • checkout works • technical debt is limited
Rebuild when:
• architecture is blocking growth • theme is obsolete • platform is unsupported • technical debt is severe • required features cannot be added safely
Protect SEO during ecommerce redesign
Before changing URLs:
• export indexed pages • identify top landing pages • map old products/categories • preserve metadata • plan 301 redirects • check canonicals • test sitemap
Product and category URLs can have years of search history and external links.
Protect customer and order data
Migration planning should cover:
• products • variations • customers • orders • coupons • subscriptions • tax settings • shipping • media
Take backups and test the migration before launch.
Need an ecommerce website review?
SiteForge can review an existing WordPress/WooCommerce site and help decide whether optimisation or a rebuild makes more sense.
Request a website review.
When a platform migration may be justified
A migration is a larger decision than a theme redesign.
Consider it when the current platform creates persistent problems with:
• integrations • international selling • staff workflow • development availability • ownership requirements • operating cost
Do not migrate only because a competing platform has a fashionable feature.
Build a migration inventory
Before touching production, document:
• products • categories • URLs • orders • customers • coupons • tax • shipping • integrations • emails • analytics • SEO metadata
This becomes the migration checklist.
Frequently Asked Questions
Should I redesign if conversion rate is low?
Investigate first. Poor conversion can come from pricing, traffic quality, shipping, product information or payment problems rather than visual design.
Can I keep the same URLs during a redesign?
Often yes, and preserving useful URLs can reduce SEO migration risk.
Should I change platform and design at the same time?
Sometimes it is unavoidable, but doing both increases risk. Plan data migration, SEO and UX as separate workstreams.
How do I know whether optimisation is enough?
If the platform remains supported and the problems are isolated, optimisation may be more economical. Rebuild when technical limitations consistently block the business.