Rule (R5): cross-check GSC during known lag windows — server logs + analytics + URL Inspection live tests; do NOT make drastic site changes on stale data (Oct–Dec 2025 was the named instance)

Rule: When GSC reports are visibly lagging or stuck, cross-check before acting:

• Server logs — were Googlebot fetches actually happening?
• Analytics (GA4, Umami, or Matomo) — was Google referral traffic landing?
• URL Inspection live test — does Google currently see the URL as indexed (the live test goes around the reporting cache)?

Do NOT make drastic site changes on stale reporting data.

Why: Oct–Dec 2025 produced confirmed GSC reporting glitches — Performance report lagging 50–70+ hours, Page Indexing freezing for nearly a month (2025 GSC reporting glitches — Oct–Dec 2025 Performance report lagged 50–70+ hours; Page Indexing report froze ~Nov 21 → Dec 18 2025; Google confirmed reporting-only (didn't affect actual crawl/index/rank)). Google acknowledged these were reporting-only and did not affect actual crawl/index/rank — but anyone who made architectural decisions based on the stale data made them on bad information. Assume similar episodes will recur.

How to apply: Build the three-instrument cross-check into the standard SEO debugging workflow. Don't trust a single dashboard — particularly during/after a Google product update or core update. If GSC and server logs disagree, the server logs are usually closer to ground truth on the crawl side; URL Inspection live tests are closer to ground truth on the index side. Cross-link: GSC instrumentation — URL Inspection (live + API, 2,000/day/property cap) is ground truth for a specific URL; Page Indexing report distinguishes Discovered-not-indexed vs Crawled-not-indexed; Performance report normally lags 2–6h.