A decision-ready diagnosis, not an unfiltered tool export.
01
Define the question the audit needs to answer
An unexplained traffic decline, a new website, weak local visibility, and a stalled campaign require different investigations. We start with the business problem, recent changes, and available access. The review can include technical health, content intent, local profiles, and measurement, but its scope should be explicit. A broad checklist without a defined question can produce a long report that still does not explain what the business should do next.
02
Separate evidence from assumptions
A crawler finding, a Search Console report, and a ranking observation each provide different evidence. We identify affected URLs, reproduce important issues, and state where access or data is incomplete. Correlation does not establish that a single change caused a decline. Competitor results also do not prove how they achieved their positions. The report should make those limits visible so your team can make decisions without treating every hypothesis as a confirmed fact.
03
Prioritize by impact, dependencies, and effort
A blocked service page may deserve attention before a minor description issue. An architecture change may need to happen before content expansion. We group recommendations into urgent access fixes, useful near-term improvements, and longer-term opportunities. Each item needs an explanation, an owner or skill requirement, and a verification method. The audit should help you choose a sequence, not simply sort findings by the severity labels a software tool assigns.
04
Know what happens after the report
An audit and implementation are separate deliverables unless the agreed scope says otherwise. We explain what your team can handle, what may need a developer, and what should be checked after changes go live. A useful baseline allows a later review to distinguish completed work from performance outcomes. We do not attach an invented delivery deadline or guaranteed growth percentage to the report. The scope and schedule should follow the site’s actual complexity.