Measurement and maintenance · Branch M.A, Core Search telemetry
M-01 Search Console must be a continuous operations tool
Indexing, performance, Core Web Vitals, manual actions, security issues and release effects must be monitored regularly in Search Console.
- Scope
- All public content
- Priority
- High priority.
- Quality bucket
- Measurement and experiment readiness
- Legacy coverage
- SEO-59
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.
How to implement
- Verify the domain property in Search Console.
- Put a weekly review of indexing, performance and Core Web Vitals in the calendar.
- Switch on alerts for Manual Actions and Security Issues.
- After every release, compare the affected templates and query cohorts.
Checklist
- Verify the domain property.
- Review indexing, performance and Core Web Vitals every week.
- Set up alerts for Manual Actions and Security Issues.
- Monitor template and query cohorts after each release.
How to audit
- Check that the domain property is verified.
- Check that weekly reviews and alerts are in place.
- Check that template and query cohorts are monitored after releases.
How UltimateSEO checks this automatically
Partly automated. BLOCKED until Search Console is connected; once connected the platform checks that the property exists and is returning data. The crawl gives a signal; a person decides the final state with business evidence.
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.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.