Make the reasons for change explicit.
A redesign should solve identifiable problems. Perhaps visitors cannot find a service, the portfolio is outdated, phone enquiries are difficult to make, or publishing new work takes too long. Your team may also be receiving enquiries that do not fit the business.
We collect those observations and review the current site before proposing changes. The resulting brief links design decisions to a purpose. It also separates essential improvements from ideas that can wait until the new version has launched.
Identify what the current website already does well.
The existing site contains more than a visual design. It may have useful service copy, established page addresses, incoming links, valuable downloads and enquiries from particular pages. Those assets need to be understood before content is removed or reorganised.
Where available, analytics and search reports help identify important pages and journeys. We combine that information with a content inventory and technical review. Access to the existing platform and records helps produce a more informed plan than a screenshot-based redesign.
Decide between a focused refresh and a rebuild.
A complete rebuild is not always the best use of the budget. If the technical foundation is sound, improvements to navigation, key pages, photography and contact routes may address the main problems. More extensive changes may be justified when the system prevents needed functionality or makes maintenance impractical.
We explain the proposed approach and the trade-offs in keeping the current platform or changing it. That discussion includes future editing, integrations, support and any data that must move with the site.
Restructure services around the questions customers ask.
The new content plan should make the offer easier to understand. Separate service pages can address different requirements, while projects provide concrete examples of relevant work. The homepage introduces those routes without carrying every detail itself.
For businesses serving London and surrounding areas, location content should explain genuine coverage and relevant experience. We avoid treating place names as substitutes for useful information. Existing copy is retained, rewritten or consolidated according to its accuracy, purpose and place in the new structure.
Bring the presentation into line with your brand.
Typography, imagery, colour and spacing establish the overall impression, but the design must also work as an interface. Navigation, headings and calls to action should make it clear where to go next. We prioritise the pages and actions most important to your business.
A design review is an opportunity to agree the direction before every page is built. Approved patterns then carry through the website, with responsive layouts and appropriate adjustments for different types of content rather than repeated identical sections.
Plan the SEO migration before changing addresses.
We map existing pages to the new structure and retain established URLs where that remains sensible. If an address changes, the old page should lead to the closest relevant replacement through an appropriate permanent redirect. Redirecting unrelated pages to the homepage does not replace a proper mapping.
Titles, descriptions, internal links, canonical references and indexing settings also need review. A migration plan reduces avoidable technical risks, but search positions can still change after a redesign and should be monitored after publication.
Include media, downloads and integrations in the inventory.
A website can depend on more than its visible pages. Brochure links, forms, booking tools, payment connections, analytics and third-party services may all be part of the customer journey. Important files and image addresses may also be linked from outside the site.
We identify these dependencies during planning, confirm what will remain in use and define how replacements will be tested. Integrations require access and documentation, while licensed assets need appropriate permission for continued use on the new website.
Develop separately and prepare a controlled switch.
The new website can be built in a separate environment while the current one remains available. Content approval, device checks and functional testing happen before the publication window. The launch plan should identify who controls the domain, hosting and any systems that need a coordinated change.
A restorable backup and rollback procedure provide a practical response if a critical issue appears. After the switch, we check important live pages, contact actions, redirects and launch settings in the actual hosting environment.
Scope the work around content and migration complexity.
The price depends on the amount of content, the new design, language versions, technical changes and the condition of the existing site. Moving a catalogue or archive is different from replacing a small presentation site. Reviewing real material early helps reveal that work.
The timeline includes your approvals and the preparation of photographs, project descriptions and service information. We agree priorities and review stages so the launch does not depend on an undefined stream of last-minute additions.
Common questions
Will a redesign damage our Google rankings?
No provider can promise unchanged rankings. We reduce avoidable risks through URL mapping, content retention, suitable redirects and technical checks. Search performance should be monitored after launch because substantial design and content changes can affect how pages are assessed.
Can our current website remain available while you work?
Yes. Development can take place separately, with publication scheduled after the agreed checks. We confirm the hosting and access arrangements before starting, including how to take a backup and restore the previous version if necessary.
Can you keep our logo and general visual style?
Yes. A redesign can retain established branding while improving layout, typography, navigation and content. We agree which elements must remain and where a change would help the website communicate more clearly or work better on mobile devices.
Do all old pages need a new equivalent?
We review them individually. Useful pages may stay, related pages may be consolidated, and obsolete material may need removal. Changed URLs should have relevant destinations where replacements exist. The decision should reflect actual content and search evidence.
Can you move the site away from its current CMS?
That can be part of the project. We first review content, editing needs, integrations and export options. The new technology is selected around the required workflow, and migration work is included explicitly rather than assumed to be automatic.
What information helps you estimate a redesign?
Send the website address, the main problems, the features you need and any changes to the business. Access to a page inventory, analytics, search reports and current platform details helps us understand the existing site and its priorities.
