Protecting an established local business while modernising its website

The situation

Ben the Plumber had built a strong local reputation over many years, supported by excellent customer reviews and a business name that people already recognised and searched for.

Behind that reputation, however, the website setup had become increasingly complicated.

The original main website was around 15 years old. A separate mobile website had later been created on WordPress.com using an m. subdomain, and that site had itself been running for approximately six years.

Over time, the domain, hosting, security certificate, mobile site and email arrangements had become spread across several different systems. Some of the original login routes no longer worked as expected, and it was not immediately clear which parts of the setup were still active, which were historical, and which depended on one another.

This was not the result of anyone doing something wrong. It was the kind of complexity that can accumulate naturally when a website has been updated in stages over many years.

The priority was therefore not to replace everything immediately. It was to understand the existing arrangement, protect the business assets already working well and modernise the setup carefully.

What needed protecting

The most valuable part of Ben's online presence was not the website technology. It was the reputation the business had already earned.

Ben had a strong Google review profile, with a high average rating and a substantial number of customer reviews. Those reviews provided trust, reassurance and evidence of many years of good service.

The website also already appeared in search results for the business name, so any technical work needed to avoid unnecessary disruption to existing visibility.

The aim was to improve the underlying setup without creating avoidable risk.

What was discovered

The investigation found a fragmented but recoverable website arrangement.

The main domain was connected to an older hosting account containing files from the original website. Separate rules were being used to direct mobile visitors towards the WordPress.com m. website.

The WordPress.com site had become the version Ben wanted to retain, but the relationship between the main domain, the mobile subdomain, the hosting account and the security certificate was not straightforward.

The login trail was also outdated. Some of the expected account routes no longer led clearly to the correct controls, so access had to be traced carefully before changes could be made.

The investigation covered the historic website files on the original hosting account, redirects between the main domain and the m. website, SSL certificate coverage, domain settings, DNS records, email-related DNS records, the WordPress.com connection and the possible effect of changes on existing search visibility.

An SEO audit also identified a wider range of technical and content issues. Rather than presenting these as hundreds of separate warnings, the findings were grouped into practical priorities.

This made the audit easier to understand and turned a long technical report into a realistic sequence of actions.

The work completed

A secure credential collection process was introduced so that login details did not need to be sent through ordinary email or messaging.

Before significant changes were made, backups were taken of the available website files and relevant settings. This created a recovery point and reduced the risk of making changes to a long-established system.

The existing redirect behaviour was then reviewed and adjusted carefully so that visitors reaching the main domain could be directed safely to the retained WordPress.com website.

SSL and DNS issues were investigated across the domain, hosting and WordPress.com setup. Particular care was taken not to overwrite or remove email-related DNS records while the website configuration was being changed.

The domain was connected to WordPress.com as part of simplifying the arrangement and reducing reliance on the older fragmented setup.

Throughout the process, the changes were approached incrementally. One part of the system was checked before the next was altered, rather than making several major changes at once.

This staged approach helped protect email delivery, existing search visibility, customer access to the website, the business's established domain and the content Ben wanted to keep.

The outcome

The SSL problem was fully resolved, allowing the website to load securely.

Email continued working normally throughout the changes.

Existing search visibility also remained stable, confirming that the transition had not caused an immediate loss of the visibility the business had already built.

The most important outcome was that the website setup became more understandable and manageable without sacrificing the reputation, reviews or online recognition already associated with the business.

The work also established a clearer foundation for future search improvements.

No claims are being made at this stage about increased rankings, additional traffic or new enquiries, as those results would need to be measured over a longer period.

"Michael fixed some issues with my company website and also gave some helpful advice after analysis of the site. Fantastic to deal with and made the process very easy and straightforward. Not salesy or pushy like so many I've encountered in this field. I would highly recommend to anyone needing website work."

Ben Snowdon, Ben the Plumber, Google review

Next steps

The next stage is gradual improvement rather than unnecessary replacement.

Future work can now be approached in a more measured way: monitoring search visibility after the technical changes, reviewing indexed pages and redirects, improving page titles and search descriptions, and strengthening service-specific content where it would help customers.

There is also room to make contact information more consistent, review older pages that may no longer reflect the current business, improve the presentation of existing photographs and project examples, and simplify the remaining domain and hosting arrangements where appropriate.

Any search performance improvement would need to be measured over time rather than assumed from the technical recovery alone.

Any future work should continue to treat Ben's reviews, business name and long-standing local reputation as the central assets.

The website should support that reputation, not compete with it or attempt to reinvent it.

Lessons for other small businesses

Older website setups are not necessarily bad setups. Many have simply evolved gradually as new services, mobile websites, hosting providers and security requirements have appeared.

A business may have an old hosting account, a newer website elsewhere, several domain records, a mobile subdomain, email connected through another provider, redirects added at different times and login details that no longer follow the original route.

Changing one part without understanding the others can cause unexpected problems.

The safest approach is usually to begin with what customers are currently using and what is already performing well. From there, protect email, domain ownership and search visibility before collecting access details securely, taking backups, mapping the setup and making changes in stages.

Monitoring the result before moving on matters because older website arrangements often have dependencies that are not obvious at the start.

For established local businesses, the goal should not automatically be to replace everything old.

The better question is: What is already valuable, and how can the technology be improved without putting that value at risk?

Related Local Roots guidance includes help deciding whether to fix or rebuild an existing website, search visibility support and a first look through your customers' eyes.