RankWella logo

CLONING PROMPT

RankWella Site Migration

Click the button to copy the whole prompt. Then paste it into a fresh AI session to run a clone shift — our Ippei-built sites re-hosted on our own Cloudflare Pages as previews. Never any DNS changes, and nothing is ever deactivated in Ippei.










What this is


The Cloning Prompt is the operating prompt that runs a RankWella site clone. Paste it into a fresh AI session and it works a batch of our own sites: each site that was built in the Ippei builder is re-hosted on our own Cloudflare Pages account as a static site — same content, same URLs — with technical SEO baked in. It is the exact prompt the fleet clones (RW001–RW046) were run with, driven by the pipeline programs in the site-clones folder.


Why we clone


Ippei hosting costs $10 per site per month. A clone on Cloudflare Pages costs nothing to host, keeps identical content and URLs, and puts the site fully under our control. Cloning is a hosting move — it is not a redesign, a rewrite, or a content change.


The hard rules


    

  • Never any DNS changes. Cutover is Sean's decision, made separately, after his review.
    • 

  • Never deactivate or alter anything in the Ippei builder. The original site stays live in Ippei the whole time.
    • 

  • The Ippei lead-tracker script is stripped from every clone, unconditionally — it is built into the cloning program.
    • 

  • Never change years-in-business claims, license/insurance claims, or testimonials. Flag them for Sean.
    • 

  • Never invent copy for wrong-market or placeholder content found in an original. Flag it for the web team.
    • 



What it needs, and what comes out


Inputs: the site list (site-ids.csv — only rows marked Published are cloned) and the clone queue state file, which tracks what's done so nothing is cloned twice or silently skipped.


Outputs: a noindex preview per site (named like rw001-allen-preview), and after each batch of 4, a post-migration audit with the Website Audit Prompt plus a Fleet Cop doorway-risk check. Sean gets a morning report per batch: preview URLs, audit verdicts, every fix applied, every flag with evidence.


Step by step


    

  1. Copy the whole prompt from the Cloning Prompt tab into a fresh AI session.
    2. 

  2. The AI reads the queue and the site list and picks the next Published sites not yet cloned.
    3. 

  3. Per site: clone → SEO upgrade → verify zero "ippei" strings remain → deploy the noindex preview → record the result.
    4. 

  4. After every 4 sites: post-migration audit + Fleet Cop check. Safe migration fixes are applied directly; everything else is flagged, never silently fixed.
    5. 

  5. The batch is reported to Sean. Nothing goes live from this prompt.
    6. 



After the clone — the publish path


A clone is not "done" at the preview step. Before any DNS cutover: full audit → Three Wisemen panel (unanimous 3–0) → Pam's review → Sean's publish approval. Only then does a site move.


Current caution: five originals carry defects in the Ippei originals themselves — RW018 Mooresville Elite Tree Care, RW033 San Marcos Elite Metal Gates, RW040 Sioux Falls Premier Hardwood Flooring, RW041 The Villages Concrete Masters, RW044 The Villages Elite Drywall. For those five, the clone either waits until the original is fixed, or is cloned as-is and fixed on our side — that call is Sean's, stated neutrally either way.