Keep Your WordPress Dental Website Up-to-Date!
WordPress is very popular but still prone to hacking if you neglect maintenance
Over 40% of all websites are powered by WordPress which is undeniably the “go to” tool for professional websites these days. This is also the case in the dental sector with designers and website owners preferring the enhanced portability and technical capabilities of WordPress over hosted web builders such as Wix and Squarespace.
There’s no doubt that WordPress is an excellent website content management system (CMS) but it has a history of being compromised i.e. hacked. This is due to two main reasons – the first is that it is so popular and hence attracts a lot of attention from nefarious hacker groups. The second reason is primarily due to the “plugins” which WordPress uses to enhance core functionality. These are developed by a whole range of 3rd party coders and unfortunately the quality and maintenance varies considerably.
A typical WordPress website may use 6 or 7 plugins in addition to the core installation and it is these which are very often the root cause of hacking problems. Even reputable and popular plugins can be hacked as there is typically no overview regarding how secure or indeed how well coded they are in the first place.
How we select plugins to use with dentist’s websites
To be clear, there is no guarantee that a WordPress plugin will always be secure, even where you do your very best to make sure it is reputable and fully-supported. All we can do is be diligent to check the track record of the plugin, how widely it is used and its maintenance and security record before we consider using it for client’s websites.
Even after careful analysis and due diligence, things can still go wrong and unfortunately this has happened to most web companies, ourselves included. Whilst this is fortunately a very infrequent event here at Dental Media, just a few weeks ago a very popular and highly regarded website plugin we used on a few clients’ websites was hacked, even though we’d diligently kept it up-to-date. We spotted this very quickly and intervened to stop any permanent damage, but had we not had monitoring tools and mitigation processes in place, the effects could have been significantly worse.
We immediately reported the issue to WordPress and the developer who took fast corrective action; however, other than an apology and a retrospective fix, that’s all you get.
