Search Visibility
Most Guides Describe a Checklist. Almost None Describe the Job
A real audit includes a crawl that flags thousands of issues of which maybe nine matter, and the work of writing findings in language someone can actually act on. This is the process as it runs, stage by stage, with honest hour ranges — not four, not forty.
The Shape Of It
Start with a question, end with a plan
An audit without a question is a document nobody reads. Before opening a single tool, get clear on what you actually want to know: what changed and when — a traffic drop, a redesign, a migration all narrow the search enormously — and which pages actually make money, not just which get traffic. Everything you look at afterward is in service of answering that.
And an audit ends with a plan, not a data dump. The two stages worth protecting are the first and the last — deciding what you're really asking, and turning findings into an ordered set of things to do. Those are where the judgment lives. The stages in between are mostly pulling data and formatting the same tables again, and that's the part worth automating.
The Stages
Where the time actually goes
Access comes first, and it's where audits stall. Most of the calendar time isn't work — it's making sure you can actually read your own Search Console and analytics history. A common trap: if the site was only verified recently, there may be no history before that date, so you simply cannot audit a drop from last year. Better to know that on day one than to invent a story.
The crawl finds the structural issues. A crawler will produce a large number of flags, and most are noise. The job is triage: which pages are set to "no-index" or blocked that you actually want ranked (this is where the expensive mistakes hide), which internal links point at dead pages, and which duplicate titles are really one template problem rather than two hundred content problems.
Search Console is the highest-value hour-for-hour work. It's the only dataset showing what Google actually did with the site, not what a tool estimates. Compare the last few months against the same months a year earlier — year on year, so seasonality doesn't fool you — and look for pages that lost clicks while impressions held, pages shown a lot but rarely clicked, and terms sitting just off page one.
Technical, content, and links round it out. Verify the things a crawl can't see — real-user speed, how the site renders on an actual phone, valid structured data. Then the part no tool does well: reading the actual search results for your top commercial pages and asking, honestly, whether your page is the right shape and genuinely better than what outranks it. That judgment is why a person still beats a plugin.
The Honest Total
What a full pass really costs
A first audit of a mid-sized site runs roughly fourteen to twenty-five hours of actual work, spread across two to three weeks of calendar time — most of which is waiting on access, not working. Under ten hours, you're producing a tool export with a cover page. The tedious middle — pulling data, joining exports, reformatting the same tables every month — is the part worth handing off. The scoping and the prioritising are the part worth keeping.
What ARIA takes off the pile: the middle. It connects to your Search Console, pulls the performance data, and produces a plain-English audit you can edit rather than assemble from CSVs — the click-loss comparisons, the just-off-page-one shortlist, the shown-but-not- clicked outliers, already done. The scoping question at the start and the prioritising at the end stay yours, because that's where the judgment is.
Search Console is the connector that ships today; others are on the roadmap and we'll say so when they land, not before.
Related In This Guide
Where to go next
For the ordered list of exactly what to check and what a bad result looks like, see the SEO audit checklist. For the Search Console stage specifically — the highest-value hour — read Search Console, read like a practitioner. The patterns you'll spend that stage hunting are your striking-distance keywords, any rank decay, and the CTR gaps.
The technical stage names the faults; fixing them — speed, crawlability, structured data — is hands-on work on Audry's side: Audry's Site Audit.
Skip the tedious middle
The process above works perfectly well by hand — it just takes longer. Connect your site and let ARIA do the data-pulling and the pattern-finding, so you can spend your hours on the parts that actually need judgment.