A website redesign updates the structure, visual system, content experience and technical foundation of an existing site. Lynto Labs approaches redesign as a product engineering project: understand what is working, identify what is blocking users or the business, define the right scope, then rebuild and launch with a controlled handoff.
The result should be easier to use, maintain and extend. It should also preserve valuable content and search visibility where possible rather than replacing the current site without a migration plan.
[Discuss your project](/contact) to get a scope based on your current website, goals and constraints.
When a website redesign makes sense
Redesign work is usually justified when the current site creates measurable operational or customer problems. Common signals include:
- Visitors struggle to understand the offer or find the next step.
- The site no longer reflects the company’s products, services or market position.
- Publishing content requires developer support or fragile workarounds.
- Performance, mobile usability or accessibility issues affect the experience.
- The design system has become inconsistent across pages.
- Forms, analytics, CRM connections or other integrations are unreliable.
- The existing platform limits planned features or content types.
- Marketing teams cannot create landing pages without duplicating code.
A redesign may also support a rebrand, but visual change alone is rarely enough. Navigation, page hierarchy, content ownership, conversion paths and technical constraints should be reviewed before design begins.
Redesign, refresh or full rebuild?
The right approach depends on the condition of the existing site.
| Option | Best fit | Main tradeoff | | --- | --- | --- | | Visual refresh | The structure and platform work well, but the interface looks dated or inconsistent | Faster and narrower, but does not resolve deeper content or technical problems | | Structured redesign | The site needs new navigation, page templates, content hierarchy and conversion paths | Requires more coordination across design, content and development | | Full rebuild | The platform, codebase or content model prevents reliable improvement | Creates more flexibility, but increases migration and testing work | | Incremental rollout | The site is large or cannot be replaced in one release | Reduces launch risk, but old and new sections may coexist temporarily |
Lynto Labs recommends choosing based on maintainability and business requirements rather than treating a complete rebuild as the default. An initial audit can determine which parts should stay, change or be retired.
What a website redesign can include
The final scope depends on the current website and the team responsible for operating it. A redesign engagement may cover:
- Website and content inventory
- User journeys and information architecture
- Wireframes and interface design
- Reusable page templates and components
- Responsive front-end implementation
- Content management requirements
- Content migration planning
- Form and third-party integration work
- Technical SEO migration requirements
- Performance and accessibility review
- Analytics and conversion-event setup
- Quality assurance, deployment planning and handoff documentation
If the project includes custom workflows, account areas or backend logic, it may be closer to a web application than a marketing-site redesign. Lynto’s broader [development services](/services) can be considered during scoping when the website must connect to a larger product or internal system.
How delivery works
1. Audit the current website
The first step is to document page types, content, traffic-sensitive URLs, integrations and technical dependencies. This avoids making design decisions without understanding what the existing site supports.
The audit should also identify outdated pages, duplicate content, broken paths and features that remain business-critical despite being rarely visible.
2. Define requirements and priorities
Requirements are organized around user tasks and business outcomes. This stage establishes the planned sitemap, required templates, content responsibilities, integration needs and launch constraints.
Open decisions are recorded early so they do not surface as expensive changes late in development.
3. Design the key experience
Design begins with the highest-value journeys and representative page types. Reviewing these first helps validate navigation, content hierarchy and component behavior before every page is produced.
The design should account for real content lengths, mobile layouts, form states and editing needs rather than relying on idealized mockups.
4. Build and integrate
Approved designs are implemented as reusable components and templates. CMS behavior, forms, analytics and agreed third-party systems are connected during this phase.
Implementation should include clear states for errors, empty content and loading behavior where they apply.
5. Migrate and verify content
Content migration can be manual, scripted or a combination of both. The method depends on the number of pages, consistency of the current data and differences between the old and new content models.
Redirects, metadata, internal links and media references should be checked before release. Pages that already attract qualified traffic need specific attention.
6. Test and launch
Testing covers agreed browsers and devices, page templates, forms, integrations and editorial workflows. Launch planning should define backups, domain and DNS responsibilities, redirects, monitoring and a rollback path.
After release, the team reviews live behavior and resolves launch-related issues according to the support scope.
What determines cost and timeline?
Lynto Labs does not use a single price or schedule for every website redesign. An estimate requires enough information to separate design effort from content, engineering and migration work.
The main cost and schedule drivers are:
- Number of distinct page templates, not simply the total page count
- Condition of the current codebase and content management system
- Amount of content that must be rewritten, reorganized or migrated
- Custom forms, calculators, account features or backend workflows
- CRM, analytics, payment or other third-party integrations
- Accessibility, legal or security requirements defined for the project
- Number of stakeholder review cycles
- Whether the site is launched at once or in stages
A scoped estimate should state its assumptions, milestones and dependencies. It should also clarify whether copywriting, brand identity work, photography, paid software, hosting fees and ongoing maintenance are included or excluded.
To make an initial estimate more useful, provide the current URL, target launch considerations, known platform constraints, examples of problem pages and a list of required integrations.
Protecting search visibility during a redesign
A redesign can affect organic traffic if URLs, content or internal links change without a plan. Search preservation should be treated as part of delivery, not as a final launch task.
A migration plan may include:
- Mapping old URLs to their new destinations
- Identifying pages that should remain unchanged
- Preserving relevant titles, headings and structured content
- Reviewing canonical tags, indexation rules and sitemaps
- Updating internal links instead of relying only on redirects
- Checking analytics and Search Console configuration after launch
- Monitoring crawl errors and important landing pages during the release period
No redesign can promise unchanged rankings. The practical goal is to avoid preventable losses while improving the site for users and future content work.
How to evaluate a redesign partner
When comparing a freelancer, small business website design company or web design agency, review the delivery model rather than choosing from visual portfolios alone.
Ask how the partner will:
- Decide whether the existing platform should be retained
- Inventory content and protect important URLs
- Translate design files into maintainable production components
- Handle feedback, approvals and scope changes
- Test forms, integrations and editorial workflows
- Document ownership, licensing and deployment access
- Support the site after release
Relevant work can help you assess product thinking, implementation quality and the type of systems a studio has delivered. Review Lynto Labs’ [selected product work](/work) as part of that evaluation.
Prepare for a productive first conversation
You do not need a complete specification before contacting Lynto Labs. A useful starting brief includes:
- The current website and platform, if known
- The main customer actions the new site should support
- Problems reported by customers or internal teams
- Pages or content that must be preserved
- Required integrations and access constraints
- Internal owners for content and approvals
- Any fixed business dates that could affect launch planning
With that context, Lynto can assess whether the project needs a refresh, structured redesign, full rebuild or phased release. [Discuss your project](/contact) to define the next step.