Review of Justin's April 17, 2026 Technical Assessment
Justin's report (dated April 17) used data collected before our emergency fixes went live on April 9. Several critical items have already been resolved:
Source: TLH SEO Fix Report (April 9)
Details: Removed 111 broken images (f8f1457). Optimized homepage JS to reduce execution time by ~1.35-1.5s: deferred Google Tag Manager until page load, consolidated 3 inline scripts into /js/main.js, added preconnect hints (2305b12). Expected improvement: 3.6s → 2.1-2.25s (37-42% faster).
Justin's analysis correctly identifies the mobile-specific collapse (Apr 12-15) as the core issue. While we fixed canonical tags and GA4 tracking on April 9, the mobile quality score problem remains unresolved and is actively bleeding traffic.
Source: Google Analytics 4 + Google Search Console data
Justin reported all pages declaring GitHub Pages URL as canonical.
✓ This was already fixed on April 9. Current state:
All 101 HTML files were updated in commits 41e7f67 (canonical/OG/schema) and cd863ec (GA4).
Status: ✅ Complete | Fix Report
✓ 125 URLs submitted, 0 indexed
Sitemap URLs are correct (verified April 21), but Google still refuses to index. This may resolve naturally as Google re-crawls after the April 9 fixes, but needs monitoring.
Action needed: Request re-indexing in Google Search Console for top 10-15 pages (was already recommended on April 9).
Source: GSC Sitemaps API
The pattern is unmistakable:
This means Google is showing the site to fewer mobile users — not ranking it worse. This is an exposure/visibility cut, which points to mobile-first indexing re-evaluation or Core Web Vitals failure.
Source: GSC device-level performance data
Source: Ahrefs site audit (CSV exports available)
Note: "158 bad canonicals" may be outdated — needs re-crawl to verify after April 9 fixes. "106 broken images" fixed April 21 (commit f8f1457).
✓ Mobile-first indexing re-evaluation triggered the collapse
The site migration changed URL structure and introduced technical issues. Google's mobile crawler re-evaluated the site and downgraded its mobile quality signal. Since Google uses mobile-first indexing, this affects all visibility — including desktop, paid search quality scores, and organic reach.
With canonical tags already fixed, the revised priority is:
Justin correctly flags this as urgent:
This is actively losing TLH leads and revenue. The April 9 fixes should start reversing the trend within 1-2 weeks, but mobile issues need immediate attention.
Automated checks completed April 21. Manual browser testing required to complete:
Instructions: See ~/Desktop/tlh-mobile-diagnostics-guide.md
Since canonical tags were fixed April 9, tell Google to re-crawl the top pages:
42 × 404 errors, 42 × other 4xx errors. Justin has CSV export ready.
Action: For each URL — add 301 redirect to closest relevant live page, or redirect to homepage if no match exists. Do this at Cloudflare Worker level.
Verify "158 bad canonicals" number after April 9 fixes.
Action: Re-crawl site via Ahrefs to get updated audit report. The canonical count should drop significantly.
GA4 was installed April 9. Verify conversions are now being tracked properly.
Action: Check GA4 for form submissions over past 2 weeks (since April 9 install). Should see consistent event tracking.
Internal links point to old URLs that redirect (dilutes link equity, slows crawl).
Action: Find/replace across codebase — update old URL patterns to new ones (e.g., /hummel-figurines/ → /blog/hummel-figurines).
Direct channel sessions doubled (10K → 27K) with 96% bounce rate — likely bot traffic hitting static origin.
Action: Enable Cloudflare Bot Fight Mode. Verify proxy passes through Referer header so GA4 can attribute sessions correctly.
Action: Add Ahrefs Web Analytics script to site <head> for ongoing monitoring.
April 9 fixes addressed the canonical/GA4 crisis. Those issues are resolved.
April 21: Removed 111 broken WordPress images from 43 blog posts (commit f8f1457). Fixes 404s and improves page load speed.
The mobile quality score problem remains. 52% mobile click drop in 3 days (Apr 12-15) points to Core Web Vitals or rendering issues.
Expected recovery timeline: 1-2 weeks for traffic to start recovering from April 9 fixes, 2-4 weeks for full recovery — but only if mobile issues are also resolved.
Justin's analysis is correct. The canonical/GA4 work is done. Now focus on mobile diagnostics and cleanup work (broken pages/images/redirects).
Analysis by Clark (OpenClaw) | April 21, 2026
Based on Justin's Technical Brief (April 17) + April 9 Emergency Fixes