The structure still works
If positioning, route hierarchy and CMS are sound, targeted content, performance or UI fixes may be enough.
Website redesign and migration
Website redesign with a migration plan—not a cosmetic reskin
AMS Digital helps owners decide what should be repaired, restructured or replaced, then carries the approved route, content and technical decisions into a controlled relaunch.
A redesign can apply documented migration controls, but it cannot guarantee that rankings, traffic or leads remain unchanged.
- Diagnosis
- Route mapping
- Launch controls
Redesign or repair?
Start with the smallest intervention that solves the real problem.
Visitors cannot find the decision path
Information architecture and content hierarchy may need redesign without replacing every visual or technical layer.
The system blocks routine change
A broader redesign is justified when templates, CMS, responsive behavior and migration needs are tightly coupled.
Migration inventory
Protect what must survive the redesign.
- 01
Content and URLs
Inventory current pages, decide keep/merge/remove outcomes and map changed paths.
- 02
Metadata and crawl controls
Carry intentional titles, canonicals, robots decisions, internal links and structured data into the new system.
- 03
Measurement and integrations
Record analytics, consent, forms, booking, embeds and ownership before old code disappears.
- 04
Media and permissions
Retain only assets with a clear role, correct dimensions, useful alt treatment and publication rights.
Approval checkpoints
A redesign proceeds through evidence, not momentum.
- 01
Audit
Reconcile business facts, analytics available, content, routes, technical constraints and proof.
- 02
Choose the intervention
Approve what stays, what changes and which problems remain outside scope.
- 03
Design and prove templates
Resolve a representative route and mobile behavior before scaling.
- 04
Migrate and validate
Build content, test links and redirects, and record unresolved launch risks.
- 05
Monitor after launch
Check crawl, indexing, conversion paths and operational ownership after deployment.
Illustrative scope
Example: migrate a 20-page marketing site.
This scenario explains scope logic; it is not a price, timeline or client result.
The page count is only the beginning
Unique templates, CMS relationships, redirects, proof permissions, integrations, content readiness and approval cycles usually matter more than the raw URL count.
Frequently asked questions
Questions connected to this decision.
How do I know whether I need a redesign?
A redesign is easier to justify when the current structure, CMS or responsive system prevents clear content and routine change. A smaller repair may be better when those foundations remain sound.
Can a redesign preserve SEO?
It can preserve and test important controls such as URL mapping, redirects, content, internal links, metadata and crawl directives. Search performance cannot be guaranteed.
What affects redesign cost and timing?
Content readiness, unique templates, migration volume, integrations, proof review, responsive complexity and stakeholder approvals shape the scope.
Do old pages always redirect?
Only when there is a genuinely relevant replacement. Removed pages without an equivalent should return an appropriate 404 or 410 instead of being redirected indiscriminately.
Sources and basis
What supports this page.
Official sources support migration and accessibility controls. They do not promise stable rankings or commercial outcomes.
- How to move a site with URL changes
Google Search Central · Verified 2026-07-19
Primary guidance for URL mapping, redirects, internal-link updates, sitemaps and monitoring during a migration.
- How do I set up redirects in Webflow?
Webflow Help Center · Verified 2026-07-19
Current Webflow workflow for permanent redirects and route testing.
- Web Content Accessibility Guidelines overview
W3C Web Accessibility Initiative · Verified 2026-07-19
The accessibility standard used to frame semantic, keyboard, contrast and responsive review controls.
Related decisions
Choose the route that matches the job.
Next step
Start with the current site and the reason it must change.
The first step is to separate cosmetic frustration from structural, content, CMS and migration problems.
Discuss a redesign