The Saturday customer who trusted the website
A dog grooming shop owner called me on a Monday morning, thoroughly annoyed. Two days earlier, a customer had stood outside her locked front door at 8 a.m. with a nervous terrier in the car, waiting for an appointment that was never booked. The shop had dropped Saturday hours nearly a year ago, but the website still announced Saturday hours from 8 to 2 in bold text across the header. The owner asked me if the site was broken.
I opened the site on my screen while we talked, and it loaded immediately. The layout was intact, the photos rendered cleanly, and the phone number worked when I clicked it. Yet as I clicked around, the groomer who had quit the previous spring was still smiling on the team page, a nail-trim package they had eliminated months ago was still listed with an old price, and the copyright line in the footer read 2022. Then I pulled the public domain registration records. The administrative contact was a personal Gmail address belonging to her nephew, who had built the original layout over a long weekend and moved on to another state. Nobody at the shop had logged into that mailbox in 2 years.
Why a finished website keeps decaying anyway
The site was not broken in a technical sense, but a website nobody maintains stops working because it keeps speaking for a business that has moved on. We tend to treat a build as a finished product, like a newly painted wall or a printed brochure sitting in a box. In reality, a site behaves like an active customer service channel that runs around the clock without supervision. When nobody touches it, it decays along 3 distinct lines: information that goes stale, account credentials that expire quietly in the background, and software that falls out of sync with the servers hosting it.
On the day the nephew launched that site, the setup was entirely sound. The WordPress theme was modern, every plugin had received its latest patch, the web host ran an actively supported version of PHP, and the SSL certificate was configured to renew itself without human intervention. Two years later, not a single line of that original template had been altered, but the environment around it had kept marching forward. The web host upgraded its server software, modern web browsers altered their security rules, and the plugins stopped receiving maintenance patches. When a business gets visits but the telephone never rings, that silent drift is often the culprit, which is why investigating why a website doesn't get leads usually starts with checking for decay rather than buying a new layout.
Whenever I inspect an old installation, the first place I look is the copyright year at the bottom of the page. To be fair, almost no consumer reads that small line before deciding whether to call, and search engines do not downgrade a ranking purely because a date is old. Still, checking the footer has become an ingrained habit of mine because it works as a quick tell for me. If the footer still lists a date from 3 years ago, it usually suggests to me that nobody in the organization has opened the administrative templates or reviewed the page structure since that year closed.
The 30-minute website decay check to run today
Catching this drift does not require an engineering background or a week of downtime. It requires 30 focused minutes, a notepad, and a willingness to look at the business through the eyes of someone trying to spend money with you today.
- Minutes 0 to 10: Reality check on your phone. Open your homepage on your smartphone using a cellular connection rather than office Wi-Fi. Walk down the page and compare your listed hours against your actual operating schedule for every day of the week. Verify that your core service list matches what you currently deliver, that every listed price reflects what you charge right now, and that every employee shown on the staff page still works for your company.
- Minutes 10 to 15: Security and domain ownership. Tap the padlock icon next to your URL in the browser bar and verify that the security certificate is valid and not nearing its expiration date. Next, log into your domain registrar, such as GoDaddy, Namecheap, or Google Domains, and locate the expiration date along with the renewal notification email. Make sure the renewal notice goes to an inbox your office actually monitors daily, and confirm that the credit card on file has not expired.
- Minutes 15 to 25: WordPress dashboard audit. Log into your administrative dashboard and click directly to the Updates screen. Count the pending updates across WordPress core, active themes, and plugins, noting which ones have fallen behind. Open Tools, select Site Health, and look for any warnings regarding the underlying PHP version or server software. Do not click the update buttons today; simply write down what is outdated so you have an accurate inventory of the software debt.
- Minutes 25 to 30: Contact test and the footer. Scroll down to the footer, note the copyright year, and then navigate to your main contact form. Fill out the form with your personal email, submit an inquiry, and verify that the notification lands in your primary business inbox within 2 minutes without landing in a spam folder.
When the timer reaches 30 minutes, put down your notes. You should have a clean sheet of paper split into 2 distinct columns: simple items you can correct in the editor this afternoon, and technical items you do not feel qualified to judge. When I run this inspection for an owner, the second column is almost always filled with outdated plugins, PHP compatibility warnings, or confusing hosting records. If your review turns up technical questions you cannot safely resolve on your own, request a free website audit from our team at kohl.digital, and we will send back a clear punch list detailing what to address first without pitching an unnecessary rebuild.
But updates break things, and Google already has my hours
A reasonable business owner will often push back against this process with 2 valid arguments. First, running updates on an aging WordPress installation carries genuine risk, because updating an old plugin can easily break a contact form or corrupt a page layout. Second, most local customers check opening hours directly inside a Google Business Profile without ever visiting the website itself. Leaving an old installation untouched can feel like the safest path forward.
Both concerns carry real weight. Mass-updating outdated code on an unmanaged server without a recent backup can easily knock an entire platform offline, and Google certainly surfaces contact details on the search results page before someone clicks a link. The problem arises when the two sources contradict each other. When Google states you are closed on Mondays but your website homepage claims you are open, potential clients are forced to guess which source is lying. Avoiding code updates may protect a fragile layout in the short term, but choosing not to maintain software is an active operational gamble that someone needs to consciously manage rather than an accident of neglect.
One name on the site and one recurring date
Preventing decay does not require continuous monitoring, complex software suites, or an expensive retainer. It comes down to establishing one plain operational rule that you can write down on an office calendar: one named person in the company owns the website, runs this 30-minute review on the first Monday of every month, and ensures all domain, hosting, and certificate alerts route to an active inbox they monitor personally.
The very first step in executing that rule is logging into the registrar and replacing the former developer's email address with your own. The grooming shop owner did exactly that the afternoon after our call; she updated her operating hours, removed the former employee from the team roster, and redirected the renewal notifications to her personal desk. As we hung up, she wondered aloud what might happen during the busy holiday season when nobody has 30 minutes to spare, or down the road if she decides to sell the business and the site is left to run quietly on its own again.