I killed my WordPress site and rebuilt it solo on Next.js.
I took holisticseo.co off WordPress and rebuilt it from scratch as a Next.js app on Vercel — Sanity driving the blog, Cloudflare on DNS — by directing Claude Code. No dev team, no design shop. Shipped in days, on a stack I own end to end.
WordPress couldn't keep up with the repositioning.
Slow to change. Heavy to maintain. Built for a positioning I’d outgrown.
The old holisticseo.co was a generic-agency WordPress site. I was niching the whole business down to wellness and optimization clinics — hormone, TRT, anti-aging, med spas, weight loss.
The site had to match the new direction: fast, technically clean, easy for me to publish to, and built from the ground up to be readable by both Google and the LLM answer engines I sell against.
Patching WordPress wasn’t the move. I wanted a stack I controlled end to end and could ship on in days — not a CMS I had to fight every time I changed something.
Direct the build. Don't hand-write it or outsource it.
I made Claude Code the build partner: I set the direction, the information architecture, the copy, and the design intent, and drove the code through the agent rather than a keyboard or an agency brief.
Hosting went to Vercel, DNS moved to Cloudflare, and the content layer went to Sanity so the blog and media live in a headless CMS instead of a WordPress admin. The whole site is built around the agency’s “Six Surfaces + Foundation” framework — Map Pack, LSAs, PPC, Meta, content, AI answers, with technical SEO and digital PR underneath — and every path points to a single Calendly booking entry.
Because I sell AEO and GEO, the site had to practice it: structured data, AI-friendly robots, and clean crawlable architecture were baked in — not bolted on.
— Design principle · the site as its own proofThe new topology.
A visitor hits Cloudflare at the edge, which routes to a Next.js app on Vercel. The app pulls blog and media content from Sanity’s headless CMS and CDN, and every path resolves to a single Calendly booking endpoint. The old WordPress install is retired.
A visitor’s request flows through Cloudflare to a Next.js app on Vercel, which renders server-side with JSON-LD schema, AI-friendly robots, sitemaps, and OG cards. Blog and media come from the Sanity headless CMS over its CDN, so I publish without touching code. Every path resolves to a single Calendly booking entry. The prior WordPress install was retired entirely.
Framework & Hosting
Content Layer
DNS / Edge
SEO / AEO Layer
Conversion
Build Tooling
One migration. One operator.
Verified from the live site source and the Apr 2026 Slack rebuild record.
The capability shift is the real number: from shipping a site in weeks with a dev team to shipping and maintaining a modern, schema-rich, AI-search-ready site solo — by directing Claude Code — on a stack I own end to end.
What shipped — and what I'm not claiming.
The left is what exists and works today. The right is the honest boundary on what this build proves.
A fast, schema-rich, AI-search-ready site on a stack I own.
- holisticseo.co is live on the new stack — Next.js on Vercel, Sanity CDN assets, Cloudflare DNS.
- Positioned cleanly for the wellness-clinic niche with the six-surface framework.
- Structured data + AI-search-ready technical foundation baked into the build.
- Sanity-managed blog — I publish without touching code.
- A single Calendly conversion path across every page.
- The WordPress site it replaced is gone; the team’s operating baseline reset to “Next.js/Vercel + Cloudflare, site-first publishing.”
A capability win — not a traffic or lead-gen claim.
- This is an agency marketing site, not a high-traffic application.
- It’s continuously iterated, not a frozen finished product.
- The win is the capability: modern, schema-rich site shipped and maintained solo by directing an AI build tool.
- It is not a claim of a large engineering system, and not a claim of client-acquisition outcomes from the site yet.
Next.js, Vercel, Sanity, Cloudflare, and Claude Code are third-party tools. The work is the architecture, the direction, and the delivery — not the tools themselves.
The migration, at a glance.
Direction to live in days.
Chose Next.js + Vercel + Sanity + Cloudflare. Set the information architecture, the six-surface framework, the copy, and the niche positioning myself.
Drove the code through the agent — pages, components, blog wiring — while making every design and structure call.
MedicalClinic, FAQ, and Breadcrumb JSON-LD, AI-friendly robots, and clean crawlable architecture — the site practicing the AEO/GEO I sell.
DNS moved to Cloudflare, deploy on Vercel, Sanity CDN serving blog and media. Publishing now flows through Sanity — no code required.
Both this site and agenticworkforcecompany.com were confirmed up from the ops side, resetting the team baseline to site-first publishing on the new stack.
I conceived it, directed it, and shipped it.
I owned the whole thing — the decision to leave WordPress, the stack choice, the architecture, the six-surface framework, the copy, and the conversion flow.
I directed Claude Code to produce the code rather than hand-writing it or outsourcing it, and I made every design and structure call. I’m the operator who conceived, directed, and shipped it — on a stack I own end to end.