The Infrastructure Audit tells you what your online presence actually runs on, how many separate vendors keep it alive, where enquiries are leaking, and which parts nobody owns. It is free, it takes me about a day, and you do not have to get on a call to receive it.
A web designer built the site. Someone added a form plugin because the original form stopped sending. Mailchimp came in because a staff member already had an account. A booking tool got bolted on. Something was added to duct-tape two of them together. Somewhere there is a CRM that three people have logins for and nobody updates.
Every piece was chosen separately, by different people, at different times, for a reason that made sense on the day. Nobody chose the whole, because the whole was never a decision anyone made.
So nothing talks to anything, every join is a place a lead can go missing, and every plugin is a supplier who can break your site or breach it. When something fails, the designer says it is hosting, the host says it is a plugin, and the plugin developer stopped answering in 2023.
None of that appears on an invoice, which is exactly why it never gets looked at. The audit looks at it.
Each section gets a rating, the evidence behind it, and what a poor result actually means for your firm. That last part is the difference between a report and a diagnosis.
What the site runs on and how far behind it is. How many plugins, from how many separate vendors, and how many are abandoned or known to be vulnerable. Backups, and whether one has ever been restored. Who actually holds your domain, DNS, hosting and ad accounts. Whether your email is authenticated with SPF, DKIM and DMARC. Mobile speed. Whether anything is watching for downtime.
Whether your firm surfaces for the query your buyers would actually use. Whether your structured data and entity signals are present and valid, which is what decides if AI engines can read who you are. Whether the site is properly indexed. If ads are running, where they land and whether that page was built to convert.
A real enquiry, submitted through your own form and timed. Where it actually lands: an inbox, a CRM, or nowhere. Whether any follow-up happens without someone remembering. What becomes of an enquiry that arrives outside business hours. How many fields your form asks for and how many it needs. The path a phone user takes to reach a call or a booking.
Whether conversion tracking exists and is firing. Whether a client can be traced from first touch to signed work. Whether ad click IDs are captured, and whether real outcomes could ever be fed back to the ad platforms. And the question that settles it: can you name where your last five clients came from?
Whether client satisfaction is measured at all, or simply inferred from nobody complaining. Your review volume, how recent it is and where it sits. And whether asking for a review is something that happens systematically or something that happens when someone remembers.
A written report. Each section rated, with the evidence and what it means in plain language. Then a prioritised list split two ways: what is exposed and should be fixed no matter who does it, and what is leaking and costing you money every month. Sent by email. No call required to receive it.
Most of what an audit turns up is technical, and technical findings are easy to file under "we should look at that sometime". This one is not technical and it is very hard to file.
"I submitted an enquiry through your contact form at 4:12pm on Friday. I heard back on Tuesday morning."
That is not an argument, and it is not a criticism of anyone on your team. It is just what happened, and it is usually the moment a principal stops thinking about their website as a design question.
I do this openly. The enquiry comes from my real name and my real email address, it says what it is, and the report tells you exactly when it was sent and when someone replied. Sometimes the answer is eleven minutes, and when it is, I say so.
The audit places you overall, and again for each of the five sections, so you can see which part of the machine is dragging the rest down.
Something here can take your business offline or lose it money without warning. Unpatched, unmonitored, or owned by someone who no longer works with you.
It works, mostly. Several vendors, nothing joined up, no single view of anything, and failures get discovered by accident or by a client.
The parts work and somebody maintains them. Still separate systems, still manual joins, still nobody who can see the whole thing at once.
One system. Enquiries captured and followed up automatically, every client traceable back to where they came from, and one person accountable for the whole.
Most firms land on Fragmented, and there is nothing embarrassing about it. It is what happens when a business grows faster than the systems underneath it.
A free audit that only exists to make you feel bad enough to buy something gets read that way within about ninety seconds, and rightly so.
So the report hands you things you can act on without hiring me. If your email authentication is missing, that is a half-hour job for whoever manages your DNS and it will improve your deliverability whether or not we ever speak. If a plugin is abandoned, you should know its name. If your backups have never been tested, that is worth more to you than anything I could sell you.
I offer a call at the end. You do not have to take it to get the report, and if the audit shows your setup is in better shape than you thought, I will tell you that too and there is nothing further to discuss.
One honest limit: it is about a day of my time and I do it myself, so I can run roughly five a week. If there is a wait, I will tell you how long when you ask.
Four fields. I will come back within a couple of days with the report, or tell you how long the wait is.
An Infrastructure Audit is a free assessment of what a firm's online presence actually runs on, how many separate vendors keep it working, where enquiries are leaking, and which parts nobody owns. Growth Rebels runs it manually and sends a written report, with no call required to receive it.
It is free. The catch, if it is one, is that I am hoping some firms read the report and decide they would rather I fixed the problems than fix them alone. Most will not, and the report is written to be useful either way.
No. Everything in the audit is checked from the outside, the way a client or an AI engine would see it. There are no logins to hand over and nothing to install. If a finding needs confirming from inside your systems, the report says so rather than guessing.
No, and it is done openly. The enquiry uses my real name and email, it identifies itself, and the report tells you exactly when it was sent and when someone replied. Response time to a new enquiry is one of the most valuable numbers in the whole audit and there is no way to measure it without sending one.
About a day of work, and I usually come back within a couple of days. I run roughly five a week because I do them myself, so if there is a queue I will tell you how long it is when you ask.
Only if you do. Grow and Scale can run around whatever you already have, and for plenty of firms that is the right call. The honest position is that the best results come with a full rebuild, because it removes most of the vendor count, most of the attack surface and most of the maintenance in one step. The audit is what tells you which of those two situations you are in.
The AI Scan answers one question in about a minute: whether AI engines can find and cite your firm. The Infrastructure Audit is broader and slower, and it runs the scan as one of its five sections. If you only want the AI search picture, run the scan. If you want to know what your whole setup is doing, ask for the audit.
Because the website is one component. What matters is whether the four stages are connected to each other, and most of the time they are not connected at all.
Free, about a day, and you keep the findings whether or not we ever speak.