A new client comes in, sends over the URL to their existing site, and asks for a quote. A year or so ago, my first move was always the same: crack open the theme files directly, poke around the page source and the database for twenty or thirty minutes to get a general feel for what I was actually dealing with before I could put a number on the work. There’s now a distinct step that happens before any of that, and it’s changed the accuracy of my quotes more than almost anything else I’ve adopted this year.
What the pre-audit pass actually involves
Before touching any code, I pull the rendered HTML of the key pages, the full meta setup, whatever schema markup exists or doesn’t, and the general information architecture, and walk through all of it with Claude to get a structured first pass at what’s wrong. Missing alt text patterns across the image library. Duplicate title tags repeating across multiple pages, which happens constantly on sites built with certain page builders that auto-generate titles from a template without anyone checking the output. Broken heading hierarchy, where a page skips straight from an H1 to an H4 because someone picked heading levels based on how the text looked rather than the actual document structure. Not because I personally can’t spot these issues myself — I absolutely can, and have been doing exactly this kind of audit manually for years — but because doing it by hand across a forty-page site takes a genuine hour of careful, tedious checking, and doing it this way takes about ten minutes and produces a structured checklist I can hand straight to the client without any additional formatting work.
A real example of how this changes a quote
On a recent audit for a services business with about thirty pages, the pre-audit pass flagged five pages still carrying a noindex tag left over from when the site was in staging, a redirect chain three hops deep on their most-linked blog post from an old URL restructuring nobody had cleaned up, and a completely missing Organization schema block despite the site having reasonably solid on-page content otherwise. All three of those are the kind of issue that used to surface for me halfway through a project, once I was already knee-deep in the build and had already quoted based on an incomplete picture. Now they surface in the first hour, before I’ve put a single number in front of the client, which means the quote reflects the actual scope of work from the start instead of growing awkwardly midway through.
Where this has genuinely changed my client relationships
The honest benefit here isn’t really the audit output itself — it’s what happens downstream, in the actual working relationship. I used to under-scope projects fairly regularly, not out of carelessness, but because certain deeper issues genuinely don’t surface until you’re already working inside the codebase. Noindex tags left on live pages. Redirect chains that only become obvious once you’re tracing why a specific page isn’t ranking. Now those surface upfront, which means fewer of the awkward mid-project conversations that start with “so, this is actually going to take a bit longer than we initially discussed,” which nobody enjoys having, least of all the client footing the bill.
What I still don’t hand off, and don’t intend to
The judgment calls about what actually matters for a specific business stay entirely with me, and I think that’s the part people considering a similar workflow tend to skip past. An AI-assisted audit will flag forty distinct issues on a typical site without much effort. For a local plumber’s five-page site, maybe six of those forty genuinely matter for that business’s specific goals — ranking for local service terms, converting mobile visitors calling directly from search results, that kind of thing. The rest might be technically true but functionally irrelevant to what that particular client needs solved right now. Knowing which six matter, and being able to explain to a non-technical client why those six and not the other thirty-four, is still entirely the job, and it’s the part of the work I’d actually be worried about if a tool ever tried to fully take over.
The workflow, start to finish
In practice it now looks like this: pull the site’s rendered pages and meta data, run the structured audit pass, review every flagged item personally and discard anything that doesn’t matter for that specific business, then build the client-facing checklist and the internal scope estimate from what’s left. It’s roughly a tenth of the time it used to take for the mechanical part of the process, and it’s freed up enough of my own time that I can actually go deeper on the judgment part — the part that was always the real value I was providing in the first place, even when I didn’t fully realize it.
