For existing business websites
If your website looks outdated, is hard to update, performs poorly on mobile or no longer reflects the business, the next step should be a structured review — not a blind replacement.
We assess what is creating friction, what should be retained and what needs to change before recommending targeted improvements, a structural redesign or a controlled rebuild.
No meaningful website to preserve? Explore Website Design.
Diagnosis before direction
Keep what still earns its place.
Recognise the friction
One symptom does not prove that the whole website needs replacing. It does show where a proper review should begin.
Three possible routes
The right scope depends on what the current website is still doing well, what is creating friction and what risks would be introduced by changing it.
LOWER CHANGE
A possible fit when the platform and theme remain viable, the page structure is broadly usable and a limited set of issues can be corrected without creating unnecessary migration risk.
MATERIAL CHANGE
A possible fit when useful content and site value remain, but navigation, hierarchy, journeys or presentation need material reworking and the platform can be retained safely.
CONTROLLED REPLACEMENT
A possible fit when the platform, theme or codebase is a liability, the structure cannot support the business, or maintainability, security or compatibility problems justify replacement.
Starting without a meaningful existing website? Explore Website Design.
Is catalogue, cart, checkout or payment the main requirement? Explore Ecommerce Websites.
Review before recommendation
A useful recommendation connects visible problems to business, user, search and technical evidence. The review establishes that context before scope is agreed.
Explore deeper SEO supportGoals, priority services, customers and the journeys the website should support.
Page hierarchy, navigation, content quality, internal links and duplicated or competing pages.
Mobile use, forms, calls to action, trust, error states and enquiry paths.
Indexability, rankings, organic landing pages, Search Console and backlinks where evidence and access are available.
Hosting, theme and plugin condition, performance signals, ownership, admin access and integrations.
Analytics and conversion tracking where available, including whether the current data is complete enough to guide decisions.
Analytics and Search Console can be reviewed only when the client grants access. Without them, a review can still begin from visible structure, crawlable pages, content, mobile usability and platform signals, but search-equity decisions must be more conservative.
Protect useful value
Retain value intentionally rather than replacing or preserving everything automatically.
Pages may have search, referral or customer value even when their presentation needs work.
Accurate explanations, questions and terminology can be retained, consolidated or rewritten intentionally.
Linked or relevant pages need evidence-led mapping rather than automatic deletion.
Recognisable, permissioned assets can remain when they still fit the business and the revised system.
Analytics history, conversion evidence and customer behaviour can inform better decisions where reliable data is available.
Useful operational connections and recognisable navigation can be retained when they remain safe and effective.
Preserving a redesign foundation is different from planning ongoing visibility growth. Explore SEO or Local SEO.
Scope follows evidence
A redesign can affect content, journeys, presentation and implementation, but this is a review framework — not a promise that every item is included in every engagement.
LIKELY REVIEW AREA
These areas are normally reviewed because they shape whether people can understand and use the website.
PROJECT-DEPENDENT CHANGE
These changes depend on the evidence, current platform and agreed project boundaries.
SEPARATE SPECIALIST SCOPE
Some requirements change the delivery model or need ongoing specialist work and should be agreed separately.
Migration discipline
The goal is to reduce avoidable migration risk, not to claim that rankings can never fluctuate.
Inventory current URLs and identify valuable pages using business value, visible signals and analytics, Search Console or backlink evidence where access exists.
Preserve, consolidate or intentionally retire content; plan relevant destinations for URLs that will change rather than redirecting everything to the homepage.
Review internal links, metadata, canonicals and indexability so they point to the intended final URL set.
Update the sitemap, confirm final pages and redirects, then monitor crawl, indexation and search behaviour so issues can be investigated.
Important: Rankings can fluctuate after significant website changes, especially when URLs, content, internal links or technical signals change. Monitoring is risk management, not a guarantee.
Make the next step easier
A redesign can improve the clarity and usability of enquiry paths. It cannot guarantee enquiries on its own: the offer, traffic, evidence, response process and wider market still matter.
Request a Website ReviewAlign the landing page with the need expressed in search, advertising or a referral.
Make services, suitability and differences easier to grasp without searching through unrelated pages.
Place permissioned proof, useful reassurance and ownership information near the decisions they support.
Create a clear CTA hierarchy, usable mobile contact actions and forms that ask for appropriate information.
Use understandable validation, error and confirmation states so users know what happened and what to do next.
Know what you control
A redesign review can clarify admin access, provider-controlled hosting, licences, plugin dependencies, documentation and whether the website can be moved. The aim is transparency, not an assumption that every existing arrangement is unsuitable.
WordPress.org software is open source. That is separate from the services and infrastructure used to run, secure and maintain a website.
Hosting is the server service that keeps the website available. Provider, renewal cost, account ownership and moving process should be clear.
Themes, plugins, fonts or third-party services may have their own subscriptions, terms and transfer limits. Each dependency should have an identified purpose and owner.
Updates, backups, monitoring and support are services, not automatic features of WordPress. Responsibilities and response expectations should be agreed.
Strategy, design, development, content and specialist support are professional services. Scope, deliverables and ongoing charges should be documented separately.
Miliki Spot redesign
Miliki Spot is a Nigerian restaurant in New Cross, London. The redesign focused on making its menu, location, ordering and catering journeys clearer while strengthening the website's local-search foundations.
Website usage
Google Analytics shows materially higher website usage in the current reporting period. The data does not isolate the redesign as the sole cause of that change.
Local discovery
Google Business Profile recorded 22,702 profile views and 8,358 searches showing the business between March and August 2026. Relevant searches included:
Reporting-period qualification: The March–August 2026 reporting period spans both before and after the approximately May 2026 website redesign. These figures evidence genuine local-search visibility; they do not show that the redesign alone created every search or profile view, and no exact ranking position is claimed.
The observed analytics and Business Profile data are kept separate from causal claims about the redesign, rankings, revenue, bookings, calls or direction requests.
A controlled route
The exact delivery plan depends on the evidence and agreed scope. The process keeps preservation, migration and launch decisions visible instead of treating them as an afterthought.
Review the business context, visible experience, content, search signals, technology and access available for the agreed scope.
Classify useful assets and pages, gaps, duplication, technical liabilities and decisions needing more evidence.
Set the page hierarchy, navigation, content responsibilities and customer journeys before detailed production.
Create and implement the agreed responsive system around clarity, accessibility, maintainability and the approved scope.
Record URL, content, redirect, integration, tracking, access and launch dependencies before changeover.
Check the agreed pages, links, forms, responsive layouts, accessibility and technical signals before controlled release.
Review crawl, indexation, redirects, forms and agreed measurement so launch defects can be investigated and corrected.
Practical risk questions
Qualified answers about rankings, URLs, WordPress, hosting, ownership and choosing the right service route.
Rankings can fluctuate after significant changes. The aim is to reduce avoidable risk through URL inventory, content mapping, relevant redirect planning, technical checks and post-launch monitoring — not to promise that movement is impossible.
Yes, when the current WordPress setup is a viable foundation. The review checks theme, plugin, content, access and maintainability constraints before deciding whether to retain, restructure or replace it.
Not necessarily. Hosting, domain and DNS arrangements can be assessed separately, but any move depends on confirmed account access, technical compatibility, backup and migration planning.
Useful, accurate content can be retained, rewritten, consolidated or mapped into the future structure. Reuse should be intentional rather than assuming every page should stay unchanged.
Current URLs are inventoried and mapped. Where a URL changes or is retired, any redirect should go to a relevant destination; valuable pages should not be sent to the homepage by default.
Yes, targeted improvements may be appropriate when the platform and wider structure remain viable. The review helps identify whether a limited change would solve the problem without creating new inconsistencies.
Ownership, administrator access and handover are clarified in the agreement. Completed custom work and client content are distinct from third-party software, licences and services, which retain their own terms.
Timing depends on the number and condition of pages, content decisions, approvals, technical dependencies, integrations and migration risk. A delivery plan should follow the review rather than a universal timeline.
Website Redesign starts with an existing site and must assess what to preserve or migrate. If there is no meaningful existing website to preserve, Website Design is the better starting point.
The review can identify missing admin, hosting, domain, DNS or licence access. What can be transferred depends on account ownership, contracts and cooperation from the current provider, so access should be resolved before launch planning.
The review can begin from visible structure, crawlable pages, content, mobile usability and platform signals. Without historical search or behaviour data, decisions about traffic and search equity must be more conservative.
It can connect with ecommerce work, but if products, catalogue, cart, checkout, payments, stock or fulfilment are the dominant requirement, start with the separate Ecommerce Websites service.
Begin with diagnosis
You do not need to decide whether the project is a repair, redesign or rebuild before enquiring. Start with the current website and the problems you are seeing. The appropriate scope can be determined from there.
