Key takeaways
- The site still loads, but inquiries keep dropping and it's unclear whether content or the site is the problem
- Internal teams disagree on whether to rebuild, and rebuild budgets are not small
- A previous vendor change just repackaged the same issues without solving them
Why this decision is hard to get right
The site still loads, but inquiries keep dropping and it's unclear whether content or the site is the problem
Internal teams disagree on whether to rebuild, and rebuild budgets are not small
A previous vendor change just repackaged the same issues without solving them
Start with a website diagnosis
Share your current site and business stage. We will judge whether to optimize, migrate, or rebuild before recommending scope.
Why "the site looks old" is the wrong test
Dated visuals do not equal poor conversion—many legacy sites mainly lack information architecture and content
A rebuild fixes messaging, but skipping access and tech-debt issues means the new site repeats old problems quickly
Migration and rebuild costs differ significantly; a wrong call wastes a full quarter of budget and time
Four dimensions to judge the decision
Access and control: Whether source code, deployment, domain, and data are fully controlled determines if you can optimize in place.
Tech debt and framework: Whether the current framework can still be maintained, extended, and wired to SEO and tracking.
Page messaging and conversion: Whether hero, product pages, and form paths clearly communicate value and drive action.
Content assets and search performance: Whether legacy URLs, blog content, and rankings are worth preserving determines migrate vs. rebuild.
FAQ
Traffic is still decent—does that mean we don't need to change anything?
Traffic volume does not equal conversion capability; check whether the conversion path and content assets can still support growth.
Budget is limited—can we just rebuild part of the site?
Yes. If the overall framework is controllable, rebuilding the homepage, core product pages, and form path first is often more cost-effective than a full rebuild.
How do we know if tech debt is already too heavy?
If the framework is unmaintained, can't support basic SEO and tracking, or even small edits require working around legacy code, tech debt is likely already limiting growth.
Will migrating old content hurt rankings?
With proper redirects and content mapping, migration usually avoids major ranking loss—but it needs to be planned ahead, not fixed after launch.
Can the site still take inquiries during a rebuild?
Yes. A phased launch or parallel environment keeps the old site capturing inquiries until the new site is verified stable.
Start with a website diagnosis
Share your current site and business stage. We will judge whether to optimize, migrate, or rebuild before recommending scope.
About the author
Edwin Lou
Head of Architecture & Implementation
Edwin leads system architecture, operations, and technical implementation diagnosis at Seatevo. With 20 years of hands-on experience, he helps B2B export teams assess tech debt, deployment stability, and delivery feasibility—so growth plans can actually be shipped and maintained.