Scope
This guide covers setup & configuration 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.
Add domain, verification and crawler configuration.
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
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Add domain, verification and crawler configuration.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Track issue status, site health and organic movement.
- Record owners and avoid marking unresolved evidence as complete.
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.