Your offer has changed
Services, audiences, or priorities have evolved while the website still presents the previous situation.
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 set out exactly what the project covers.
Starting without a usable foundation? View website development.
Illustrative example — not a real client website.
Redesign framework
Make the decisions first, then carry out focused work.
When a redesign fits
A redesign suits an existing website whose foundation remains partly useful, but whose content, structure, experience, or technology no longer reflects the current situation.
Services, audiences, or priorities have evolved while the website still presents the previous situation.
Important information is difficult to find, pages overlap, or the next step is unclear.
The visual hierarchy, mobile presentation, or interaction no longer supports visitors well enough.
The current foundation makes structural improvements, accessibility, or maintenance difficult.
Clear boundaries
The right approach depends on what truly needs to change. These related services each have their own purpose.
A new website project fits better when no usable foundation exists or the requested change needs a new foundation.
View website developmentA 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 hostingA new visual identity is a separate branding question. A redesign can work with existing brand elements.
View branding and logoSEO migration belongs in a careful redesign. Ongoing SEO optimisation remains a separate engagement.
View SEO optimisationThe pricing page shows our current new-website packages for comparison. A redesign gets its own, clearly defined quotation.
View existing packagesWhat we review
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.
What the website should support, who it serves, and which priorities should guide the rework.
How visitors move from their initial question to relevant information and an appropriate next step.
How pages relate, where information sits, and whether the hierarchy reflects the current offer.
Which text, images, forms, and functions still fit, where duplication exists, and what needs clarification.
Consistent use of brand elements, page hierarchy, mobile presentation, readability, and accessibility.
The current build, technical constraints, risks to loading speed, and what that means for implementation, maintenance, and migration.
Existing analytics or search data can add context when it is available, you have authority to share it, and the scope includes it.
The page addresses (URLs) search engines know, metadata, internal links, and potential redirects that need attention when changes are made.
This is scoping for a redesign project: not an automated scan and not a guarantee of search positions or commercial results.
Retain and change
We use the inventory to select useful elements. Technical dependencies, usage rights, and the new structure limit what you can carry over.
Only when it remains accurate, useful, and suitable:
Only where the agreed objectives require it:
What we can deliver
We set out what we will deliver for each project. The proposal may include the following elements.
A definition of the pages involved, priorities, dependencies, and decisions.
A proposal for the agreed navigation, content structure, and page templates.
Implementation of the pages, components, and interactions listed in scope.
Transfer and placement of the text, images, and files selected in advance.
An overview of retained paths and relevant destinations when URLs change.
Project-specific checks and documentation for the agreed handover.
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.
These measures limit avoidable technical disruption, but cannot guarantee search positions or results.
Approach
The exact approach follows from the website and the agreed scope. These steps make decisions and responsibilities visible.
You share the current website, intended change, and known obstacles so the first conversation can stay focused.
We organise what remains useful, what needs reworking, and which technical or content dependencies exist.
We define which pages are involved, what structure and design work is needed, what we migrate, and what is not included.
The agreed work can be built, reviewed, and migrated in defined stages when that suits the scope.
Before the transition, we review the agreed pages, interactions, technical signals, and handover.
Bring this information to help us place the request correctly:
FAQ
Practical answers about scope, retention, migration, and the boundary with other services.
Have a different question?
Within 4 hours on business days, usually sooner. Messages sent over the weekend may be answered on Monday.
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.
Which approach fits?
We use Google Analytics only after you consent to measuring visit statistics. Google may then place analytics cookies. More information