I handed my personal site to an AI agent: 45 migrations, a redesign, a newsletter and payments in 30 days
This is a delivery log, not a tutorial: I handed my two-month-stale personal site over to an AI agent and ran it for 30 days. Here is what actually happened.
Short version: an agent can take over operations, but it cannot take over judgment. Every call — which version to ship, whether to trust a platform, when to switch payments — was made by a human.
Starting Point: A Site Nobody Maintained
An Astro static site: 45 posts, 59 pages, on a 2-core/2GB Tencent Cloud Lighthouse instance. It looked fine, but underneath:
- Any unknown path returned 200 + the homepage (soft 404) — every broken link was hidden
- Five homepage links pointed to the wrong URLs and silently fell back to the homepage
- 37 pages had og:image URLs returning 404 — social cards were broken
- RSS had 9 dead links and 9 titles prefixed with
[undefined] - No monitoring, no backups, no newsletter, no revenue
The Four Steps
1. Audit first
A read-only audit of all 59 pages (210 requests) checked status codes, titles, canonicals, OG tags, structured data and internal links. 54 pages had at least one issue, but they clustered around three root causes: soft 404s, wrong links, broken generation. Fixing three root causes beats fixing fifty-four symptoms.
2. Back up before touching anything
Site files, nginx config, certificates and crontab were archived first, plus a local snapshot of the public site. That decision paid off when a config file with a BOM broke nginx — rollback took 30 seconds.
3. Automate what can be checked
Three small automations: a health check every 10 minutes (status, response time, certificate expiry), a weekly backup with 4 copies retained, and a weekly digest that only sends when there is actually a new post. Under 100 lines total, but they moved “remember to check” out of my head.
4. Deliver, not just ship
Shipping a redesign is not delivery. Delivery means: where the backup is, how to roll back, and who maintains it later. Every change shipped with a rollback command.
Three Real Problems
1. Personal accounts cannot send email
The newsletter was built, but sending was blocked: Tencent Cloud disabled SMTP for individually verified accounts activated after March 2026. Switching to QQ Mail SMTP took ten minutes. Check account eligibility before building the pipeline.
2. Do not assume platform stability
I planned to use Afdian for payments; halfway through verification the platform went down — connection refused from one network, Cloudflare 521 from another. The plan changed to a WeChat reward QR code plus a self-hosted download link. The payment channel can change; delivery must stay in your own hands.
3. DNS changes have consequences
Email verification required MX, SPF, DMARC and DKIM records. Pointing MX at Tencent's mail servers rerouted inbound mail for the whole domain. DNS is not scary; changing it without knowing what it affects is.
Results
- 11 production issues fixed; all 59 sitemap URLs return 200
- Redesigned from “magazine” to a personal blog: article stream, TOC, archive, search, favorites
- Newsletter working end to end: double opt-in, unsubscribe, weekly digest
- A template pack (5 brief templates + 7 cron scripts + a token ledger) with QR-code payment
- 45 generated article covers; social cards finally have images
Can This Be Copied?
Yes, with three conditions: you must be the one who decides; you must give the agent clear boundaries (goal, scope, acceptance criteria, reporting, rollback); and you must accept slowness — the technical work took two or three days, the rest was waiting for verification, review and platform recovery.
Read the 45 free essays at manyou-zhe.com, or grab the template pack at /pro/.
Found this useful? Get the template pack · 中文版