Posts on Observability.
7 posts tagged "Observability".
ga-telemetry shipped the same morning as the Phase 1.6 sitemap push — they're the same job
Two pull requests landed on 2026-06-20: a stdlib-only GA skill and an operator-side sitemap push. One queried Google Analytics. The other filed Request-Indexing nudges. Underneath both was the same question — did Google see this? That's one discipline, not two.
I wrote gsc-telemetry with no pip dependencies. It found six invisible pages in four days.
Building ga-telemetry and gsc-telemetry as stdlib-only Python skills removed the friction that keeps monitoring tools from running reliably. The daily digest surfaced six pages showing “URL is unknown to Google” four days after deployment. The ultracode audit found no technical blockers. The fix was a crawl path, not a configuration error.
Two weeks of silent cron failures. One Saturday-morning digest read.
Nightly GSC and GA data pulls had been silently killed by launchd TCC every night since 20 June. No alert, no log noise anywhere I was watching. Fourteen nights of missing numbers, surfaced by the telemetry digest during a routine Saturday-morning review.
Googlebot had the sitemap for weeks. Six pages were still unknown. The fix was editorial prose.
Six URLs stuck at ‘unknown to Google’ for weeks after sitemap submissions, IndexNow pings, and twelve manual Request-Indexing nudges. The ultracode audit of all six pages found no technical blocker. Footer-only pages on a lower-authority site need editorial prose links — Googlebot follows editorial paths, not manifests.
Telemetry surfaced six invisible YMYL pages. The operator-side fixes didn't move them. Internal linking did.
After ga-telemetry and gsc-telemetry made six stranded YMYL pages visible, Phase 1.6's first move was operator-side: sitemap canonical fixes, IndexNow, twelve Request-Indexing nudges. The technical audit cleared every blocker. The pages stayed unknown. Internal linking — crawl-weight transfer from body prose — was the diagnosis the data forced.