Your offer has changed
Services, audiences, or priorities have evolved while the website still presents the previous situation.
For existing websites
A website redesign that starts with what already works.
An existing website often contains elements worth retaining. We identify what you can keep, what you can optimise, and what needs work across structure, content, design, or technology. We then define the project scope.
Starting without a usable foundation? View website development.
When a redesign fits
Optimise what needs attention. Retain what has value.
A redesign suits an existing website whose foundation remains partly useful, but whose content, structure, experience, or technology no longer reflects the current situation.
The structure gets in the way
Important information is difficult to find, pages overlap, or the next step is unclear.
The experience feels dated
The visual hierarchy, mobile presentation, or interaction no longer supports visitors well enough.
The technology limits change
The current foundation makes structural improvements, accessibility, or maintenance difficult.
Clear boundaries
Choose the approach that fits the request.
The right approach depends on what truly needs to change. These adjacent services each retain their own purpose.
New website
A new website project fits better when no usable foundation exists or the requested change needs a new foundation.
View website developmentContent updates, maintenance, and hosting
A few text or image changes belong to focused content updates. Hosting and technical care remain separate unless related rework is included in the redesign scope.
View managed hostingBranding
A new visual identity is a separate branding question. A redesign can work with existing brand elements.
View branding and logoOngoing SEO
SEO migration belongs in a careful redesign. Ongoing SEO optimisation remains a separate engagement.
View SEO optimisationCurrent new-website packages
Use the pricing page as context for current new-website packages. A redesign receives its own defined quotation.
View existing packagesWhat we review
First understand why the website needs to change.
The discovery focuses on the existing website and the intended next step. It determines which areas need attention and which decisions belong in the project scope.
Purpose and audience
What the website should support, who it serves, and which priorities should guide the rework.
Conversion journey
How visitors move from their initial question to relevant information and an appropriate next step.
Structure and navigation
How pages relate, where information sits, and whether the hierarchy reflects the current offer.
Content and functionality
Which text, images, forms, and functions still fit, where duplication exists, and what needs clarification.
Visual consistency and usability
Consistent use of brand elements, page hierarchy, mobile presentation, readability, and accessibility.
Technology and performance
The current build, technical constraints, loading risks, and their implications for implementation, maintenance, and migration.
Available baseline
Existing analytics or search data can add context when it is available, you have authority to share it, and the scope includes it.
SEO continuity
Indexable URLs, metadata, internal links, and potential redirects that need attention when changes are made.
This is project scoping for a redesign, not an automated scanner and not a guarantee of search positions or commercial results.
Retain and change
Make a deliberate choice for each element.
We use the inventory to select useful elements. Technical dependencies, usage rights, and the new structure limit what you can carry over.
What may be retained
Only when it remains accurate, useful, and suitable:
- Content that remains accurate
- Approved brand elements and visual assets
- Existing images and files with valid usage rights
- Logical, valuable URLs and internal relationships
- Functionality that still fits the new scope
What may change
Only where the agreed objectives require it:
- Navigation, page organisation, and information hierarchy
- Content order and presentation
- Visual design and reusable page templates
- Interactions, forms, or technical components
- Outdated, duplicate, or unsuitable content
Potential project outputs
The proposal makes the deliverables concrete.
We define the agreed outputs for each project. The proposal may include the following elements.
Redesign scope and page plan
A definition of the pages involved, priorities, dependencies, and decisions.
Structure and design
A proposal for the agreed navigation, content structure, and page templates.
Implementation of agreed work
Implementation of the pages, components, and interactions listed in scope.
Agreed content migration
Transfer and placement of the text, images, and files selected in advance.
URL and redirect plan
An overview of retained paths and relevant destinations when URLs change.
Review and handover
Project-specific checks and documentation for the agreed handover.
Migration and SEO
Plan changes to URLs and indexable content in advance.
Search engines know the existing pages and paths. We add the transition to scope when you change pages, paths, or content in a material way.
- 1Inventory existing indexable URLs
- 2Retain useful paths where that is logical
- 3Map changed URLs to a relevant destination
- 4Update internal links, canonicals, and metadata where needed
- 5Review indexing signals and the sitemap around the transition
- 6Keep test and staging variants out of search results
These measures limit avoidable technical disruption, but cannot guarantee search positions or results.
Approach
From the current situation to a defined redesign.
The exact approach follows from the website and the agreed scope. These steps make decisions and responsibilities visible.
Share the context
You share the current website, intended change, and known obstacles so the first conversation can stay focused.
Inventory and decisions
We organise what remains useful, what needs reworking, and which technical or content dependencies exist.
Scope and design
The pages involved, structure, design work, migration, and excluded items are defined.
Staged implementation and migration
The agreed work can be built, reviewed, and migrated in defined stages when that suits the scope.
Review and transition
Before the transition, the agreed pages, interactions, technical signals, and handover are reviewed.
What helps in the first conversation
Bring this information to help us place the request correctly:
- The URL of the current website
- What works today and what does not
- Which services, audiences, or priorities have changed
- Which content or brand elements you want to consider retaining
- Known functionality, connections, or technical constraints
- Who approves content and decisions within your team
FAQ
Common questions about website redesign.
Practical answers about scope, retention, migration, and the boundary with other services.
Have a different question?
We answer all inquiries within 24 hours.
Next step
Tell us what is getting in the way today.
Send the link to your current website and describe what you want to change. In the conversation, we determine whether a redesign, a focused update, or a new website project best fits the request.
Discuss your website