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 IV (impromptu, 29 Apr)Duration · 93 min

Site walkthrough, Cloudflare migration, resoclinx.com is live

  • Walked the full Astro build locally: Homepage, all Solution pages (AI Reception, Lead Capture, etc.), Solutions Hub, Industries Hub + 5 industry pages (Med Spas, Aesthetic, Medical, Cosmetic Surgery, Laser), Resources (Scorecard + 7 Structural Leaks), Compare hub + per-competitor pages (Podium, BirdEye, Rosie, Smith AI), FAQ, Pricing (wired to existing GHL checkout), Framework (R6 + SELF), About
  • Praise: clean build, professional schema, all images already WebP, Astro load speed is excellent — homepage H1 only weak spot, needs secondary keywords (AI receptionist + clinic marketing direction)
  • About page: Surinder's photo (built in ChatGPT, dropped into Claude Code as PDF reference) + book "How Med Spas and Aesthetic Clinics Automate, Scale, Win" linked to Amazon. Lever to layer in next: Colasers franchisor backstory (9 UK branches, 20 years industry, sold ~2023) — a trust signal no competitor can copy
  • Resources: Scorecard currently links out to Score App (third-party, free up to 10 leads then paid). Plan: rebuild as a native on-site quiz later (Step 2) so traffic stays on resoclinx.com
  • Old WordPress blog cleanup: agreed to delete all old content and 301-redirect every indexed old URL to the new /blog hub on launch — captures aged URL equity without rewriting every post
  • Surinder upgraded to Claude Max ($200/mo) day before session — budget unlocked for heavier Claude Code + cron usage
  • Deployed to Cloudflare via Wrangler from Claude Code — first run accidentally created two Workers, deleted the duplicate, kept resoclinx-website-staging
  • Domain migration: Namecheap nameservers pointed from HostM → Cloudflare. Cloudflare auto-imported existing DNS records (preserved replies., mail., links., MX so GHL email + CRM still flow)
  • Custom domain attach blocked twice by conflicting DNS records — deleted the legacy A resoclinx.com → 166.x and CNAME sites.ludicrouscloud rows (HostM + Squarespace residue), all GoHighLevel records left intact
  • Site is live at resoclinx.com on Cloudflare by end of session, fully proxied + SSL
  • Surinder added Nico to the Cloudflare account (member invite) for collab access
  • SEO depth play agreed for next 2 weeks: pull People Also Ask via DataWise per Solution page, add 5–10 PAA-answers to each FAQ block (FAQPage schema). Spillover questions become the supporting blog cluster (5–10 posts per Solution / Industry page) — this is the EEAT engine
  • Action items captured below in §V — to close before next Tuesday
  • Next session preview: blog automation cron (video-to-blog + scheduled writer pulling from a CSV of titles) + 3–6 month content plan per Solution / Industry page
Session · Week V (05 May)Duration · 88 min

Autonomous blog writer live, first test post published, score-app rebuild scoped

  • Site review: Surinder closed nearly every action item from last week — site verified in Google Search Console, mobile speed ~70, pricing page wired to GoHighLevel checkout via embedded script (clean integration)
  • Homepage H1 decision: swap the headline to a transactional, SEO-friendly phrase ("AI receptionist for aesthetic clinics") and demote "The Clinic Architect" to subline. Hold the "Book a call" CTA until later in the page — homepage purpose is pre-sell, not direct booking
  • Built the autonomous blog writer pipeline live in Surinder's Claude Code CLI (Windows) inside the ResoClinx Astro folder, using the replication guide + autonomous master writing prompt downloaded from this dashboard
  • Image generation: pivoted from Nano Banana Pro to GPT Image 2 skill (Surinder already had it via Fal AI + OpenAI key — works the same, just a different model call)
  • Pre-flight answered all 8 setup questions in a shared Google Doc: master prompt path, blog URL (resoclinx.com/blog), Wrangler auth (passed), GPT Image 2 (confirmed), schedule cadence (Tue + Thu, 10–11 am UK), notification (Windows pop-up not email), first-batch (dry test), reference repo (skip)
  • "ultrathink" prefix added to the install prompt to force deeper planning. Pipeline initialised cleanly first try
  • First test blog post published live to resoclinx.com/blog: correct schema, internal links to SELF framework + content capsule technique pages, external citations inline, voice match on. Surinder flagged the dark blog background hurts readability — easy fix, will swap to white-on-black blog template
  • Blog automation runs headless via Windows Task Scheduler (Mac equivalent: cron). Requires Surinder's laptop on at run time so it can hit local image-gen + WebP conversion + Wrangler. Tue/Thu 10 am chosen because he's reliably online
  • Windows pop-up notifier: Claude Code can build a native toast trigger to fire when each blog publishes (no email needed). Surinder to build this himself before next week
  • Score-app rebuild scoped: ditch third-party Score App ($50/mo after 10 leads). Surinder will copy the 20 quiz questions + result-page screenshot into Claude Code, prompt "ask me every question you need to build this", redirect to results page = on-site conversion event, GHL handles email + PDF send
  • WooCommerce question (new client he's onboarding): advise client AWAY from on-site e-commerce. Customers want consultation first, no trust at first visit. Astro + GHL handles any later transactional needs natively
  • Build-kit Q&A: for itshover icons + GSAP skills, hand Claude the URL and let it install dependencies; Surinder to skim gsap.com so he knows the animation vocabulary
  • GitHub deploy intermediate step: optional, not required. Local + Cloudflare is enough for now
  • Claude Code Desktop vs CLI: same engine, desktop uses more RAM. CLI is the recommended primary
  • Dashboard fixes mid-call: added missing Apr 29 Fathom link, fixed broken site-structure Google Sheet link (both confirmed working)
  • Bonus offer: free 30-min checkup 2 weeks after program ends to review GSC data + flag fixes
  • DataWise: Surinder hasn't used it yet. Setup videos in resource library next on his list. Fan-out queries (Day 3.2 informational keywords) flagged as must-watch for the content plan
Session · Week VIStatus · Upcoming · Final

Score-app rebuild OR new-client SEO plan + program wrap

  • Confirm autonomous blog writer fired Tue 06 May + Thu 08 May without intervention, review the two test posts
  • Branch A: build the on-site scorecard quiz in Claude Code (questions, scoring logic, results redirect, GHL PDF email)
  • Branch B: keyword research + site architecture for Surinder's new aesthetic-clinic client (rebuild from WooCommerce → Astro + GHL)
  • Final 30-day post-program checkup booked for early June: GSC data review, indexing fixes, anything that needs tightening
  • Wrap: skills checklist + handover doc so Surinder can repeat the full Astro+Cloudflare+autonomous-writer playbook on every future clinic site
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 06

Homework for 12 May.

The autonomous blog writer is live and the first test post is up. Two big builds to land before our final session: the 30-day content plan that feeds the writer, and the on-site scorecard that replaces Score App. Plus polish on the homepage and blog readability.

  1. 01Swap homepage H1 to "AI receptionist for aesthetic clinics" (or similar transactional phrase). Demote "The Clinic Architect" to subline. No "Book a call" CTA above the fold
  2. 02Generate the 30-day informational-keyword content plan as a CSV (one row per blog) using DataWise + Day 3.2 fan-out queries. No duplicates. This is what the autonomous writer pulls from on Tue + Thu
  3. 03Verify the autonomous writer fires cleanly Tue 06 May 10am and Thu 08 May 10am — leave the laptop on and let it ship two more posts unattended
  4. 04Build the Windows pop-up notifier: ask Claude Code to wire a native toast trigger that fires when a blog publishes (no email)
  5. 05Fix the blog readability: swap dark background / white text to a lighter template (one Claude prompt)
  6. 06Build the on-site scorecard quiz in Claude Code: copy the 20 Score App questions + result-page screenshot, instruct "ask me every question you need to build this", redirect to /scorecard-results, GHL handles the PDF email
  7. 07Skim the DataWise setup videos in the resource library + the gsap.com basics so the animation + reporting vocab is fluent before the new client build
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 — grab Measurement ID from Admin → Data Streams and paste into Claude CodeTech
  • 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
Group 06 · Migration cleanup

Don't lose the equity

  • Pull the full list of indexed old-blog URLs from GSC (the 65 unindexed + anything still ranking) and 301 them all to resoclinx.com/blog via the Cloudflare workerPriority
  • Audit DNS in Cloudflare: confirm GoHighLevel records (replies., mail., links., MX) survived the migration and email is still flowingTech
  • Deactivate the legacy HostM hosting once the new site is verified stable for 7 days (don't cancel before)Tech
Group 07 · About page lever

Surface the 20-year edge

  • Expand the About page with deeper experience & expertise content: Colasers franchisor story, 20 yrs in aesthetic clinics, the book — this is the trust signal no competitor can copyEEAT
Group 08 · Content engine

Stand up the blog flywheel

  • Draft a 3–6 month content plan: 5–10 PAA-driven supporting blog posts per Solution and Industry page, internal-linked back to the parentContent
  • Build the scheduled blog-writer cron: reads a CSV of titles + briefs, ticks each row as publishedAutomation
  • Build the video-to-blog cron tied to Surinder's "Clinic Architect" YouTube cloneAutomation
Group 09 · Step-2 builds

Bring the scorecard in-house

  • Rebuild the Clinics Growth Scorecard as a native quiz on resoclinx.com (currently routes out to Score App). Captures all traffic + leads on-domainStep 2