Issue one of AI This Week. This week the experiment subject was this site itself — seanyou.com.
What got built
1. The whole site went bilingual (ko/en)
I wanted to put the site on LinkedIn, which meant it needed an English version. I gave Claude Code the direction and let it run:
- Korean stays on the existing URLs; English lives under
/en - Middleware that auto-serves English to visitors arriving from LinkedIn (referrer + browser-language detection)
- Every component refactored to carry its copy in both languages
Hands-on time was under half a day. By hand this is a multi-day job. One interesting bug: export an array from a client module and use it in server code, and it arrives as a proxy object — .map() explodes. The server/client boundary is still something a human needs to actually understand.
2. Database migrated to Neon
A neglected Supabase project had been auto-paused by free-tier policy (unrecoverable after 90 days). Connecting Neon through the Vercel Marketplace auto-injected the environment variables, and moving the email-capture backend took under an hour of commits.
Lesson: check the "sleeps when unused" policy on any personal-project database. For low-traffic sites you want the kind that wakes up on its own (Neon does).
3. SEO/GEO infrastructure
A LinkedIn post showed a site going from near-zero to hundreds-of-times more impressions in two weeks on SEO alone. I ported the same structure here: sitemap (real dates only), robots (AI crawlers welcomed), structured data, a file-based blog engine (no CMS), RSS, IndexNow. The blog you're reading is the result. Numbers in a few weeks — per the original post's lesson, the quiet period lasts up to two months.
This week's verdicts
- File-based blog (no CMS) — keep. Publishing is "write a file, commit," which meshes exactly with an AI workflow.
- Middleware language detection — keep. But the LinkedIn app sometimes strips referrers, so the explicit
/enlink stays the primary. - Managed marketplace integrations (DB etc.) — keep. Killing manual env-var copying alone is worth it.
Numbers
- Spend: $0 beyond the AI subscription (DB and hosting on free tiers)
- Pages added this week: from 1 per language to a dozen-plus including the blog
Next week: watching for the first signals in Search Console. Get issues by newsletter.