Begin with an inventory, not a moodboard
Before deciding what changes, list every public URL, template, form, integration, downloadable asset and important traffic source. This reveals what can be consolidated, what must be preserved and where risk sits.
Design references are useful later. They cannot tell you whether a service page earns search traffic or whether a form writes to a CRM.
- Indexed and linked URLs
- Top landing pages and conversion paths
- Reusable templates and components
- Forms, feeds and third-party systems
- Content ownership and approval
- Accessibility and performance issues
What increases redesign scope?
Content that needs rewriting, inconsistent legacy templates, several audience journeys and undocumented integrations all add work. A visual refresh on a stable system is different from rebuilding architecture and content at the same time.
Migration also matters. Redirects, canonical tags, metadata and internal links must be checked against the new structure rather than generated from assumptions.
Where cost-cutting creates avoidable risk
Removing pages without evidence, launching without redirect testing and postponing mobile QA can damage both search visibility and enquiry flow. These are not decorative extras; they protect the value already present.
If budget is constrained, reduce the number of new features or templates before removing audit and launch safeguards.
How Arkidis approaches redesign discovery
The current site, commercial goals, audiences, proof and technical constraints are reviewed together. The resulting proposal defines what stays, what changes and how the release will be tested.
No ranking or lead result can be guaranteed. The aim is a clearer, faster and more maintainable website with a measurable foundation.