A production content platform migrated off AWS, brought into AdSense policy compliance, and debugged with real user-behavior data instead of guesswork.
WizardsTower.com ran on AWS ECS Fargate behind an Application Load Balancer. In July 2026 it moved to GCP Cloud Run, sharing a single global HTTPS load balancer and Terraform-managed infrastructure with two sister sites (WickedAwesome.tech and TekMage.com itself) under one GCP project. The payoff wasn't just a cloud switch — it was cost control: Cloud Run's min-instance scaling was set to zero during low-traffic windows and restored to a warm instance only around major content pushes, instead of paying for an always-on ECS task regardless of load.
Like a lot of sites, WizardsTower hit Google AdSense's generic "Low value content" rejection — a message that names no specific page and no specific fix. Rather than guessing, the remediation was evidence-first: auditing real page word counts, fetching rendered HTML to check what was actually crawlable versus JavaScript-only, and reviewing session recordings for dead-click and rage-click patterns. That surfaced concrete, fixable problems — copyrighted images used without rights, a cookie-consent flow that wasn't actually wired to Google's Consent Mode v2, and thin JS-only sections with no static fallback content for crawlers. Each was fixed and verified before resubmitting, rather than resubmitting and hoping.
A breadcrumb UX bug is a good example of why "verify after every deploy" isn't optional. Breadcrumb trails on guide pages styled the current page as a clickable link even though it did nothing when clicked — a classic dead-click pattern. The first fix reduced the link's opacity to signal it was inactive, and shipped.
Real Clarity session-recording data told a different story: dead clicks on that exact breadcrumb pattern kept showing up days after the fix went live. Comparing the two sister sites' implementations side by side found the actual gap — WickedAwesome's equivalent fix already included cursor: default alongside the opacity change; WizardsTower's didn't. A visually dimmed element that still shows a pointer cursor still reads as clickable to a user's hand, even if their eyes register it as disabled.
The fix was scripted across all 47 affected template files, verified with an automated cursor-style check plus a visual screenshot diff, deployed, and confirmed against fresh session recordings afterward — not just assumed fixed because the code looked right.
Not because the first fix was wrong to try — because the second pass is what actually matters. Infrastructure and UX work that isn't checked against real production data is a guess wearing a deploy log. TekMage treats "verified" as a status you earn with evidence, not one you claim on completion.
We run on Proton
Encrypted email, VPN, Drive & Calendar — Swiss-based privacy, trusted here for 10+ years. Get 1 month free when you sign up.