Your Website, Protected
Hacked sites, lost sites, broken sites and the checks that catch them before customers do, explained for business owners, with what to check this week.
Your website has brought in calls for years, and one morning it is gone, defaced or quietly sending visitors somewhere else. Attacks on the software that runs many small business sites happen every week, and most owners only learn their site was exposed after the damage is done. This topic is written for those owners, in plain words.
The posts cover the risks that sit under a typical service business website: an old plugin nobody updated, a hosting account with one shared password, a backup that was never tested, and server software with a published flaw. Each post names the risk, shows how to tell whether your own site has it, and says what to ask your web person or your host. Others cover the checks that belong before a site goes live or a job is trusted: how the site behaves on real phones, what a speed audit should report, and why a backup or an alert that says all is well still needs a look.
We also compare the common ways small business sites are built. A site that runs plugins, a database and server code has more doors for an attacker than a site that is served as finished pages. Where we say one approach is safer or faster, we show why and link the source, and where something is our opinion we say so.
Start by checking when your site's software was last updated and whether you can restore it from a backup today. If you would rather have a site built with fewer of those doors, our web design page shows how we build sites for service businesses.
Start here
What your website runs on, and the five minute check that tells you
If you cannot say what your site is built on, you can get a first answer in five minutes from your own browser. Written answers from the builder come later.
Three doors into a hacked WordPress site
Plugins, a database behind your forms and code that builds each page on every visit are three doors an attacker can try. Here is each one, in plain words.
Every post in Your Website, Protected
Someone else is running your website: the first hour
A strange page or a wrong number on your site is not the moment to start deleting. Here is the first hour in a fixed order, and the note to hand whoever fixes it.
What your website runs on, and the five minute check that tells you
If you cannot say what your site is built on, you can get a first answer in five minutes from your own browser. Written answers from the builder come later.
Lighthouse: the audit a new build should pass first
The audit belongs before launch, and four plain questions make a builder show it.
Three doors into a hacked WordPress site
Plugins, a database behind your forms and code that builds each page on every visit are three doors an attacker can try. Here is each one, in plain words.
Did the scheduled job run, or only fire?
A scheduled job can start on time and leave nothing behind. Here is the one quick check per job that separates fired from done.
Test your site on phones before it ships
A site that looks right on a laptop can slide sideways or hide its call button on a small phone. Here is how to check before launch.
An alert that cries wolf stops being read
Our own update scanner kept flagging a tool that was never behind. We fixed the check instead of muting it, and you can do the same.
PHP2Shell isn't a WordPress bug. Your WordPress site still runs the thing that broke.
The defenders are right: it is a PHP bug, and WordPress builds its pages with PHP. What to ask your host this week, and why a site that only gets leads may not need a PHP server at all.
What belongs in a video on a service website
The rule we use before any video goes on a page: it moves in a way CSS cannot, and every word and number stays in the page itself.
Want to talk through your marketing?
Tell us where things stand and we'll tell you plainly what we'd do next.