Private · Accelerator

ResoClinx workspace

Enter your password to continue.

ResoClinx × AI Ranking Accelerator · Cohort II

The Operating
System
Build.

Client · Surinder Ahitan
Coach · Nico Gorrono
Window · 07 Apr — 16 May 2026
Cadence · Tuesdays, 60 min
I.

The six-week north star

Outcome

Rebuild ResoClinx on Astro, launch on Cloudflare, and walk away with a repeatable workflow for rebuilding any clinic client's site — your new upsell.

i.
Approved ✓

Keyword research & site architecture

Done. 37-page structure locked in the Google Sheet. Homepage primary keyword set to ai receptionist for aesthetic clinics. New SEO for Medspas Solution added.

ii.
In progress

Rebuild ResoClinx on Astro

Design system in Claude Design next. Three screens by Session 04, then scaffold Astro and scrape GoHighLevel copy into content collections.

iii.
In progress

Claude Code proficiency

Terminal fluency, agents, CLAUDE.md project memory, automation workflows — enough to run builds independently.

iv.
Weeks 5–6

Repeatable client-site workflow

Agents, instructions, and a template repo so every future clinic site can be stood up in hours, not weeks. This becomes the GBP upsell.

II.

The meeting log

Session · IntakeDuration · 60 min

Onboarding: background, goals, plan

  • Walked through ResoClinx business model and target market
  • Agreed the six-week plan and four outcomes
  • Confirmed Tuesdays at UK time, crypto payment track
Session · Week IDuration · 60 min

Foundations: Claude Code, DataForSEO, first keyword pass

  • Claude Code CLI set up in a dedicated ResoClinx folder, VS Code wired up
  • DataForSEO MCP installed and connected to your new account
  • Initial services keyword research completed and exported to Markdown
  • Insight: "AI receptionist" trending up, "virtual receptionist" declining
  • GSC flagged 65 unindexed pages on the old WordPress blog subdomain
Session · Week IIDuration · 60 min

Refining the foundation: keywords, structure, project setup

  • Reviewed refined services keyword list and locked priority terms
  • Kicked off industries keyword research (aesthetic, med spa, laser)
  • Started the site structure Google Sheet: URL · H1 · intent · parent
  • Created CLAUDE.md for the ResoClinx project folder
Session · Week IIIDuration · 73 min

Homepage keyword locked, site structure approved, new Solution added

  • Reviewed the vidIQ-sourced KW file: confirmed it is YouTube content, not site content (volumes were US, not UK)
  • Homepage primary keyword changed from ai receptionist to ai receptionist for aesthetic clinics, with med spas and laser clinics as long-tail variants
  • New Solution page added: /solutions/seo-for-medspas, primary KW seo for med spas (320 US vol, commercial, LOW comp)
  • Full 37-page site structure reviewed and approved in the Google Sheet
  • Industry page principle agreed: each industry page must include vertical-specific services (e.g. laser clinics focus on hair removal) to differentiate content
  • Site structure visualised in FigJam diagram, colour-coded by page category
  • Surplus surfaced: Surinder authored a book (How Med Spas and Aesthetic Clinics Automate, Scale, Win) — flagged as knowledge-base and trust asset for the site
  • Blocker parked: DataForSEO MCP install on Claude Desktop (Windows) did not surface the connector — Nico to follow up with DFS support
  • Design tool decision: use Claude Design (not Stitch / Figma) for the new visual system
Session · Week IVStatus · Today

Design system, Astro scaffold, and the build kit

  • Review Surinder's design drafts in Claude Design (Homepage, Solutions Hub, Solution detail)
  • Walk through the new Build Kit: itshover, GSAP Skills, Lobe Icons, plus pre-filled schema and a starter service page template
  • Run the Day-1 install block to scaffold the Astro project locally with the kit included
  • Optional staging deploy on Cloudflare Pages for review
  • Close out DataForSEO MCP install on the desktop app once DFS support replies
III.

Shared workspace

Google Drive · Primary workspace

Every artefact we touch together.

Keyword research, site structure sheets, copy drafts, screenshots, deliverables, and session notes — all in one shared folder, both of us editing.

Open shared drive
Before Session 04

Homework for 28 April.

Design first, then code. By next Tuesday we want three approved screens in Claude Design and the Astro scaffold started so Session 04 is a build session, not a setup session.

  1. 01Use Claude Design to build a design system and three screens: Homepage, Solutions Hub, and a Solution / Industry detail page
  2. 02Start the Astro tutorial and scaffold the project locally in the ResoClinx folder
  3. 03Upload your book PDF and any related manuscripts to the shared Google Drive as knowledge-base material
  4. 04Download the updated site structure sheet as CSV and drop it into the project folder
IV.

The build kit

A small, opinionated stack to drop into the Astro project on Day 1. Free, maintained, and chosen so the same toolkit works on every clinic site you build after this one.

Bonus picks

  • Tailwind CSS — design system in one config, reusable across every clinic site
  • shadcn/ui — copy-paste accessible components, you own the code
  • astro-icon — 200k+ Iconify icons on demand
  • Pagefind — instant client-side search with zero infra
  • Unpic — responsive images without thinking

What we are NOT installing

  • Framer Motion — overlap with GSAP, pick one
  • Material UI / Chakra — too heavy, fights Tailwind
  • WordPress-style page builders — defeats moving off GHL

Inside the kit folder

  • Pre-filled LocalBusiness, Service & FAQ JSON-LD schema
  • Starter service-page.astro template
  • Recommended Astro stack & folder convention
  • Pre-launch QA checklist (redirects, perf, schema, tracking)
Day-1 install block · copy + paste
# inside the resoclinx Astro project root
npx astro add react tailwind sitemap mdx cloudflare
npm install gsap @lobehub/icons
git clone https://github.com/greensock/gsap-skills.git .claude/skills/gsap
mkdir -p src/components/icons
# then visit itshover.com and copy 5-8 icons into src/components/icons/
V.

Post-launch action items

The site is live. These are the gaps we close before this becomes a real lead-generating asset. Click any item to mark it complete — state persists in your browser.

Group 01 · Homepage

Tighten the homepage

  • Update H1 to "AI Receptionist for Aesthetic Clinics" (locked LSI primary keyword from Week 3)SEO
  • Layer in secondary keywords: med spa AI receptionist · 24/7 clinic call answering · aesthetic clinic automation · missed call text backSEO
  • Add a homepage FAQ block (5–6 Qs) targeting top PAA for "AI receptionist for aesthetic clinics" — schema-marked as FAQPageSEO
Group 02 · Solutions pages

PAA-driven FAQ depth

  • For each solution page: pull People Also Ask from Google for the page's target keyword (use DataForSEO MCP)Priority
  • Add at least 5 PAA questions as a FAQ block on every solution page (FAQPage schema)SEO
  • Spillover PAAs become blog posts that internal-link back to the parent solution page (content cluster)Content
Group 03 · Brand & visuals

Identity polish

  • Design and place a logo in the header (SVG, light + dark variant if needed)Brand
  • Generate a favicon set (32×32, 180×180 apple-touch, 512×512 PWA, browserconfig.xml)Brand
Group 04 · Site shell

Header & chrome fixes

  • Fix the white bar at the top of the header (likely body margin or stray top spacer)Tech
Group 05 · Tracking & integrations

Wire up the data layer

  • Verify domain in Google Search Console (DNS TXT record on Cloudflare) + submit sitemap.xmlTech
  • Install Google Analytics 4 via Astro layout, gated by consentTech
  • Set up conversion tracking (form submissions, "Schedule a call" clicks, scorecard starts) as GA4 eventsPriority
  • Wire contact form → GoHighLevel via webhook so leads land in your existing CRM pipelinePriority