Did the website work?
Show uptime, confirmed incidents, form tests, email delivery, and any customer path that failed.
For business owners
If you pay for website support but still cannot explain what changed, what is working, or what needs attention, the problem is not that you are bad at technology.
Written by Blake Mitchell from a real multi-site handover and the controls Wired Builder now uses. Reviewed .
You should not need to know what DNSSEC, a conversion action, or a tracking container is to know whether your website is being looked after.
A useful website provider report should answer four ordinary questions. Is the website working? Is it helping people contact the business? What changed? What should happen next?
If you only receive an invoice, a list of technical tasks, or a dashboard full of numbers, you still do not have those answers. You have activity without understanding.
I recently reviewed a handover for a local service business with multiple websites, advertising accounts, analytics tools, domains, and years of provider history. The owner was frustrated. He was paying substantial bills, but he could not get a clean answer to what he owned, what was measured, or what had improved.
The audit found years of advertising without reliable lead measurement. Later campaigns counted page views and engagement as conversions, which made the results look better without proving that a customer called or submitted a form. The business did not control the analytics properties collecting its history. Some customer enquiry forms still copied a former provider.
The websites also carried stale offers, old tracking tags, unclear privacy coverage, and a domain that was close to expiry without a confirmed renewal plan. One site had recovered from a security incident, but the owner still lacked a simple record of the cause, the repair, and the remaining risk.
There was good work too. The previous provider restored the compromised site and did not bill for the recovery. The websites still produced demand. A fair review has to show that evidence as well.
During the rebuild, I also recorded three short-lived mistakes in my own work. We corrected them the same day. That matters. Trust does not come from pretending nothing ever goes wrong. It comes from showing what happened, what was fixed, what was verified, and what remains open.
One of the biggest gaps in the handover was expectation. The provider described its job as hosting, backups, software updates, security monitoring, and Google Ads management. The owner believed the relationship covered much more. Nobody had a shared, current explanation of the boundary.
That is how a website can stay online while the content gets old, the analytics remain inaccessible, and nobody improves the customer path. The provider may be doing the work it agreed to do. The owner may still be paying for something different in his head.
A monthly report should repeat the scope in plain English. It should also name important work that is not included, especially when the business assumes someone is handling it.
The question is not “Do I have maintenance?” Ask which of these jobs you are paying for, who owns each one, and what proof you will receive.
Think of it as a small business system, not one screen on the internet.
A provider may manage some or all of these parts. Your report should say which ones are in scope and who owns the rest.
More numbers do not create confidence. Better answers do.
Did the website work?
Show uptime, confirmed incidents, form tests, email delivery, and any customer path that failed.
Did it create opportunities?
Show verified calls, form submissions, booking starts, quote requests, or purchases. Do not label every page view a lead.
What changed?
List the work completed, the reason for it, and the live check that proved the change reached customers.
What needs attention?
Name the risk, explain the business effect, assign the next action, and carry it forward until it closes.
If the data is missing: the honest status is “insufficient data.” That is useful because it tells you what must be measured next. Missing data is not a green checkmark.
You should understand the first page in under a minute.
The website is online and enquiries are arriving. Conversion tracking is incomplete, so advertising results cannot yet be judged reliably.
The summary should link to the evidence. That can include a dated form test, a deployment record, an analytics event, an account ownership list, or a screenshot with private information removed.
Hours and task counts can help explain effort, but they are not the result. “Updated six plugins” means little without knowing whether the site was backed up, checked afterward, and still accepts enquiries.
What changed this month? Ask for the business reason and the live proof.
How many real enquiries can we verify? Separate calls, forms, bookings, and sales from visits.
What is not being measured? A provider should name the blind spots.
What does my business own? Confirm the domain, hosting, analytics, advertising, recovery, and billing.
What are you responsible for? Hosting is not automatically content, SEO, advertising, or strategy.
What is currently at risk? Ask about domains, email, forms, security, privacy, and spending.
What is the one next decision? A useful report prioritizes instead of handing you another list.
A business owner should not have to become a developer to manage a website provider. You should know what you own, what you are paying for, what the website produced, what failed, and what happens next.
That is the standard I want to build around. Not a report that makes the provider look busy. A report that helps the owner make a better decision.
Free one-page PDF
Use it before approving a monthly invoice, a website launch, or a provider handover.