Automated tools produce hundreds of warnings with no sense of which ones matter. A useful manual SEO audit review, or technical site audit, starts from one defined business question, such as why a key page lost visibility after a redesign, and gathers only the evidence needed to answer it.
01
Questions that justify an audit
Most engagements begin with one of these situations:
- Visibility fell after a site change
- Two pages compete for one commercial query
- A migration is planned or just happened
- Earlier tools or agencies disagree
02
Facts in one column, explanations in another
SEO is full of plausible stories. A drop in impressions might be a technical fault, seasonality, a reporting change or a new competitor. The evidence register records what was found, when and where; interpretation sits in a separate, labelled column. You, or another specialist, can then check the reasoning instead of simply trusting it.
03
Ranked by impact and confidence
Each recommendation carries an estimate of impact, confidence, effort and dependency, plus a way to verify it worked. Some audits finish with three actions. Implementation is quoted separately, so you can take the brief to your own developer.
04
Delivered across Canada
The work runs remotely using Search Console exports, crawl data and read-only access, so location does not limit who we can help. Southern Ontario businesses, from London to Brampton and Whitby, and companies in other provinces follow the same written scope and fixed fee. We do not sell SEO by the hour.
05
A brief another developer can use
The final document should let the next owner reproduce the important finding. A recommendation includes the affected URL or template, the observation, the supporting export or test, the proposed action and the acceptance check. Where there are several plausible explanations, we state what additional evidence would distinguish them. A warning that cannot be connected to a meaningful decision does not become a priority simply because a tool labels it red.
Before the engagement, we agree whether the handover includes a written question round, a walkthrough or a later verification check. Access restrictions and unavailable historical data are recorded as limitations. Implementation, new content and ongoing monitoring are separate unless the scope explicitly includes them. You can commission those steps from us or give the same evidence brief to your existing team; the audit remains a usable deliverable either way.
06
What we ask for before starting
Read-only access to Search Console, a list of recent site changes, the question you want answered and any earlier audit reports. We need no passwords for your hosting or email. If something cannot be shared, we record it as a limit of the investigation.
07
What an audit cannot do
An audit cannot promise a ranking, predict traffic or prove why a past change happened. It can narrow down the likely causes, show which ones the evidence supports and rank the work worth doing. Where the evidence is thin, the report says so.
