Measurement, control 1 of 17
M-01 Operate Search Console continuously
Use first-party Search data to investigate indexing, performance and site issues, while retaining report limits and the exact property scope.
- Priority
- High priority.
- Hard gate
- No
- Change class
- READ_ONLY: Inspect authorised evidence.
- Quality bucket
- Measurement and experiment readiness
Why it matters
Problems with indexing, speed, penalties or security can sit unnoticed for weeks if nobody looks, and users and search engines pay the price in the meantime. Releases can also change how templates and queries perform without anyone linking the cause. Regular review in Search Console is how those issues are caught early.
Evidence to review
- Actual report snapshots, collection dates and a maintained review log.
How to implement
- Confirm property identity and permissions.
- Review indexing, performance, experience, manual actions and security signals where available.
- Annotate releases and compare relevant template or topic cohorts.
- Record missing access instead of simulating reports.
How UltimateSEO checks this
Automated. A check in the scan sets PASS or FAIL for this control, and reports UNKNOWN or BLOCKED when its input is missing.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.