| name | search-console-ops |
|---|---|
| description | Uses Search Console and search operators to monitor performance and debug drops. Use when investigating traffic changes or validating indexing after deploys. |
Operate GSC as the source of truth for Search performance and coverage.
- Traffic drops, coverage reports, post-deploy validation
Not for: Replacing GSC with invented metrics.
- https://developers.google.com/search/docs/monitor-debug/search-console-start
- https://developers.google.com/search/docs/monitor-debug/debugging-drops
- Confirm property setup and date-range comparisons.
- Separate: query CTR vs impression loss vs index coverage vs sitewide bugs.
- Use URL Inspection on exemplars; request indexing only when fixes are live.
- Use search operators carefully for spot checks (
site:, etc.). - Document hypothesis → evidence → fix → re-measure.
- Pair technical fixes with domain skills.
| Rationalization | Reality |
|---|---|
| "Analytics alone explains Search drops." | Use GSC coverage/performance slices for Search-specific diagnosis. |
| "Request indexing instead of fixing." | Indexing requests do not repair noindex/canonical bugs. |
| "site: operator is proof of indexation." | It is a rough check — URL Inspection is more reliable. |
- Inventing ranking factors not documented by Google
- Skipping verification ("looks fine")
- Advising spammy shortcuts (cloaking, doorways, link schemes)
- GSC evidence cited (screenshot/export description)
- Hypothesis tied to a coverage or performance slice
- Follow-up date for re-check set