Insights · 18 May 2026 · 2 min read
Five ways small business websites quietly break
The failures that hurt a small business most are rarely loud. They are the ones nobody complains about — because the customers who hit them just call the next firm on the search results page.
When a website fails loudly — a 500 error on the homepage, a missing logo, a typo in a headline — somebody usually mentions it. The failures that hurt a small business most are the quiet ones, because nobody complains; the customer who hit the issue just went elsewhere. Five common ones, in rough order of how often we see them on Site Health Checks.
1. The contact form silently stops delivering
A plugin update changes how form submissions are sent. The submissions still appear to go through — the user sees a "Thanks, we will be in touch" screen — but the email is no longer arriving in the inbox. You only notice when you happen to ask "have we had any enquiries this week?" three weeks later. The fix is to monitor form delivery itself, not just whether the form page loads.
2. The booking link goes to a 404
You moved from one calendar tool to another and updated the booking link on the homepage. You did not update it on the services pages, on the footer, in the meta description, in the Google Business Profile, or in the email signature template. Each one quietly sends prospects to a 404. The fix is to centralise every external link to one source of truth and rewrite from there.
3. The site is rendering as the previous deploy
You change a price, hit publish, view the page in your normal browser — it has not updated. You assume the change did not save. It did save, but the CDN is serving you a cached copy that is twelve hours old. Cache invalidation should happen automatically on every deploy; if it does not, the symptom is "I keep having to publish things twice."
4. The site is slow on mobile but fast on your laptop
You build, test, and view the site on a fast laptop with a fast connection. Your customers are checking it on a phone, on 4G, walking between sites. Pages that feel snappy to you take seven seconds for them. The fix is to test on the device profile your customers actually use, not the one you build on.
5. The site stops appearing in Google for its own name
You changed the page title to be more "marketing", or a template change moved the company name out of the H1, or you accidentally shipped a robots rule that blocks indexing. Three months later the only way to find the site on Google is to paste in its exact domain. The fix is to monitor for "site:yourdomain.com" returning the expected pages and to alert on any drop.
The pattern
None of these are exotic. They are mundane, well-understood failures, and every one of them is easy to detect if somebody is looking for them. The reason they keep happening is that nobody is.