Visual refresh
Modern layout, type, colour, spacing and reusable page sections that match your business.
A visual improvement should not remove useful landing pages, break existing links or hide enquiry actions. The redesign plan should record what is staying, what is changing and how every important journey will be tested.
List current service, location, article and campaign URLs before layouts change. Keep a useful URL when its purpose remains the same, rather than changing every address for appearance.
Where a page genuinely moves or combines, document the closest new destination and the redirect required. Preserve relevant titles, headings and copy instead of replacing them with generic design text.
Check forms, phone links, WhatsApp actions, navigation and analytics on real desktop and mobile widths. A redesigned page is not ready if visitors cannot complete its primary action.
Recheck redirects, canonicals, indexability, sitemap URLs and tracked enquiries after the new version is live. Record any issue and its owner so launch-day mistakes do not remain unnoticed.
Still deciding how much should change? Use the redesign-versus-rebuild guide, then compare the wider website design scope.
A redesign is more than changing colours and spacing. The scope should protect useful content, search signals, customer journeys and business-owned access while improving the parts that are genuinely limiting the website.
Record the live URLs, page purpose, important search queries, enquiry routes, analytics events and integrations before layouts change. This creates a reference for deciding what to retain, improve, merge or retire.
Assign one clear purpose to each important page and plan how visitors reach it from navigation and contextual links. Approved copy, calls to action and content ownership should be settled before final page construction.
Define reusable headings, spacing, buttons, forms, cards and mobile behaviour instead of styling every page differently. Review representative screens at real breakpoints before extending the system across the site.
Preserve useful URLs where possible. For every necessary URL change, prepare the closest relevant destination, redirect, canonical, sitemap and internal-link update before the redesigned site is released.
Test calls, forms, WhatsApp actions, checkout or booking steps, confirmation messages, analytics and required third-party connections. A polished page is incomplete when its primary action cannot be verified.
Recheck indexability, redirects, metadata, mobile layouts, performance and enquiry tracking after launch. Document administrator access, licences, backups and the tasks that remain with the client or another provider.
A redesign fits when the platform and core structure remain usable but the content, navigation, templates or mobile experience need improvement. A rebuild is more appropriate when the underlying system cannot safely support required features, editing, performance or integrations. The decision follows a review of the existing site; it is not assumed from appearance alone.
Compare redesign and rebuilding in detail →Send the existing website URL, the problems you want solved and any launch constraint. The written scope will confirm deliverables, exclusions, responsibilities and the custom quote before work starts.
No agency can guarantee rankings. A careful redesign can reduce avoidable risk by inventorying valuable URLs, preserving useful content, mapping redirects, retaining consistent canonical signals and monitoring Search Console after launch.
No. When a page still serves the same purpose, keeping its useful URL is often safer. URLs should change only for a documented structural reason, with the closest relevant redirect and updated internal links.
A rebuild may be justified when the current platform cannot safely support required editing, performance, security, integrations or customer journeys. The decision should follow a technical and content review.
The quote depends on the number of templates and pages, content responsibility, platform work, integrations, migration, redirect planning, testing and handover. The written scope confirms these items before work starts.
QUICK CONTACT