Scope
This guide covers daily operation for Technical SEO Audits. Availability depends on your tenant package, role and configured providers.
Purpose
Turn crawl, Lighthouse and site-quality evidence into owned work.
Run audits and prioritise technical findings by impact.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Run audits and prioritise technical findings by impact.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Schedule recurring audits and create tasks from new findings.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Track issue status, site health and organic movement.
Verify the result
Track issue status, site health and organic movement. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Record owners and avoid marking unresolved evidence as complete. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.