What this covers
Technical audits require more than a crawl report
Running a crawl and exporting a spreadsheet is the easy part. Knowing which errors to fix first, and which ones barely affect rankings, takes experience and context.
This session works through full audit workflows using Screaming Frog 21 and Sitebulb on two live South African websites, one an e-commerce store and one a service business with 400 pages.
What each tool surfaces differently
Screaming Frog gives granular control over crawl configuration. Sitebulb produces prioritised visual reports that are easier to hand off to developers. Neither is objectively better — the choice depends on your workflow.
Sitebulb, Screaming Frog documentation, and Google Search Console Help Centre were referenced throughout this session.Connecting audit findings to Search Console data
Crawlers find structural issues; Search Console shows you what Google actually did with those pages. Using both together changes how you prioritise fixes.
- Canonical tag conflicts and their crawl impact
- Orphaned pages that are indexed but not linked
- Duplicate content patterns in large sites
- Core Web Vitals data in context
Attendees leave with a repeatable audit checklist formatted for use in Notion or Google Sheets.
Program outline
Session Outline
-
Why most audit reports get ignored by developers 10 min
-
Configuring Screaming Frog for a thorough crawl 20 min
-
Reading Sitebulb priority reports correctly 20 min
-
Combining crawler data with Google Search Console coverage reports 25 min
-
Case study: fixing a 400-page site with 60 critical errors 20 min
-
Building a prioritised fix list for your developer 15 min
-
Q and A 20 min
Tool access required
A free trial of Screaming Frog or Sitebulb is sufficient. Google Search Console access to at least one property is recommended.