Scenario · The bigger jobs
Audit this whole site
“Audit this whole site.” A pre-handover sweep, or just: nobody has looked at this one in a while.
Before a handover, or when a site just hasn't been looked at in a while, the useful question isn't a page-by-page inspection — it's knowing which part of the site actually needs one. This runs one sweep across the whole site, samples pages for quality, search health, redirects and images, and rolls the result into a single scorecard with a card per area, so the next step is obvious: which specific area is worth the deeper, dedicated look.
What to ask for
The one-command version of “is this site okay” — it discovers what the site runs on, samples pages across QA/SEO/redirects/images, and folds everything into one hub with a card per lane. What it is not is a substitute for depth: it is the fastest way to find out which lane needs a closer look, not the final word on any one of them.
- Start the audit from the public homepage and keep the run folder as the baseline — every later comparison, including a re-audit after fixes, reads against this.
- Read the overall verdict first, then work through the lane cards in order of severity rather than in the order they happen to render.
- Treat a lane that reports SKIPPED or BLOCKED as no evidence, not as a pass — a dependency that didn’t run or a bot wall that refused the fetch tells you nothing about whether that lane is actually clean.
- [manual] Route each real finding to the person who owns that area. A sitewide hub identifies what’s wrong; it does not fix anything, and a finding with no owner is a finding that quietly expires.
- After the scoped fixes deploy, rerun the affected lane specifically — not necessarily the whole site — and record what changed against the baseline from step 1.
Breadth first, depth on request
This is the sweep that tells you where to look, not the last check you run there. A lane reporting REVIEW is the cue to open that lane’s own scenario — broken links, a slow page, stale content — and finish the job with the tool built for exactly that question.
What this does not cover
Every page. It discovers the site's URLs, detects the stack and fans the right tools across a sample sized per lane — a sample, not an exhaustive crawl of every URL. It is also breadth, not depth: a finding that needs the full single-page treatment still routes to that page's own scenario.