Tools

Monoclone Generator

Pick a framework, host, and site count — get a working monoclone starter, AI setup prompt, architecture diagram, and savings visualization. Based on the patterns documented in The $100 Network.

All Tools What's in The $100 Network

Context and background

Read the story behind this tool: Why Monoclone Gen. Exists →

Work through the tabs in order →

Pick a Framework

Each framework has a different mechanism for driving N sites from one repo. Eleventy is the reference choice for zero-JS static networks; the others are valid with tradeoffs.

Pick a Host

The deploy mechanism changes per host. Netlify is the reference — one repo deploys to N site IDs via netlify deploy --site=<id> in a loop. GitHub Pages has a hard limit of 1 site per repo and is not ideal for monoclone.

Site Count

How many branded sites do you want to spin up from one codebase? The template will pre-populate sites.json with this many placeholder entries.

or

Network Details

These drive branding and cross-linking in the generated sites.json. All values can be edited after generation.

or
Placeholder domains will look like yourniche-01.com, yourniche-02.com, etc. Replace with real domains you own after generation.

Savings vs. N Individual Repos

One codebase pushed to N deploy targets saves time, brainpower, and money. Numbers assume industry-average dev hours and public pricing as of 2026. These are estimates — your actual savings vary.

Time to Ship (hours)

Annual Cost (USD)

Architecture

Build Speed Benchmarks

Approximate per-site build times for a 500-page content site with images. Output size includes built HTML + assets. Your selected framework is highlighted. Full methodology and commentary in Static Site Generators Compared 2026.

FrameworkBuild time (500-page site)Output sizeNetwork total build (N=10)

Decision Matrix (from the SSG comparison blog)

  • Maximum build speed → Hugo
  • Content sites with some interactivity → Astro
  • Zero-JS static network (reference choice) → Eleventy
  • Full-stack app with static pages → Next.js
  • Vue ecosystem → Nuxt
  • Minimal JS output with components → SvelteKit
  • GitHub Pages with zero config → Jekyll
  • Do not start new projects with → Gatsby (declining ecosystem as of 2026)
Disclaimer: Time estimates assume a developer at intermediate skill who uses Cursor / Claude Code / similar. Build-speed benchmarks are rough ranges — actual times depend on page count, image processing, plugin config, and CPU. Cost estimates use Netlify / Vercel / Cloudflare Pages free-tier cutoffs and common domain pricing. You will exceed free tiers if any site gets real traffic — budget for that. The $100 Network book has detailed breakdowns.

One Big AI Prompt

This is the single copy-paste prompt that tells an AI coding agent (Claude Code, Cursor, Codex) to build your entire monoclone repo end-to-end — framework, host, site count, niche, and every best practice applied. Everything you need is in this one block.

Generate first.
Tip: After the agent creates the scaffold, run npm install && npm run build to smoke-test. For Netlify / Vercel / Cloudflare Pages, create the N empty projects first and paste their site IDs into sites.json.
Launch safely: Do not register all N domains from one registrar in one sitting, and do not deploy them all on the same day. Vary registrars (Porkbun, Cloudflare Registrar, Namecheap, Google Domains successor, etc.), stagger registrations across several weeks, and space deploys across the first 30–90 days. Template, IP, registrar, and burst-publishing fingerprints are what identify a network to search engines. Full fingerprint-avoidance playbook: see Chapter 3 and Chapter 25 of The $100 Network.

Individual File Previews

If you would rather drop the files in yourself instead of using the AI prompt, each one is below — ready to copy into a new folder.

sites.json

Generate first.

package.json

Generate first.

generate-all.mjs — loops sites.json, builds per-site output

Generate first.

deploy-all.mjs — host-specific deployment loop

Generate first.

src/_data/site.js (or equivalent) — per-site config loader

Generate first.

src/_includes/base.njk — shared layout with Person/Book/Organization JSON-LD

Generate first.

README.md

Generate first.

.gitignore

Generate first.

Chapters That Map to What You Just Built

Cross-referenced across three books in The Trap Series. Click any chapter to jump to its book page.

The $100 Network — network architecture, scale, and ops

50 chapters. Full TOC.

The $97 Launch — build your first site the right way

41 chapters. Book preview.

The $20 Dollar Agency — drive traffic to what you built

47 chapters. Book preview.

Read the three-book stack

$97 Launch builds the first site. Monoclone Generator (this tool) + $100 Network scales it to N. $20 Agency drives traffic. Together they are a complete operating system for a content network.

The $97 Launch The $100 Network The $20 Agency

Framework Pros & Cons

FrameworkGood atWeak at

Host Pros & Cons

HostGood atWeak at

Best Practices for a Monoclone Network

  • One sites.json, one source of truth. Every per-site variance (brand, colors, content slugs, analytics IDs, redirects) lives here — never in per-site config files.
  • SITE_ID env var drives the build. _data/site.js reads process.env.SITE_ID, looks up the matching entry, and exposes a merged config. This pattern works unchanged from 2 sites to 500.
  • Vary your domain registrars and stagger your launches. Do not register all N domains from one registrar in one sitting and do not deploy them all on the same day. Rotate across registrars (Porkbun, Cloudflare Registrar, Namecheap, etc.), spread registrations across several weeks, and space deploys across the first 30–90 days. Fingerprinting through registrar, IP, template, and burst-publishing is covered in Chapters 3 and 25 of The $100 Network.
  • Multi-skin rotation defeats template fingerprinting. Chapter 3 — search engines can cluster sites with identical HTML shells. Three skins (a/b/c) rotating per site break that cluster.
  • Per-site netlify.toml (or equivalent) is written at build time into dist/<site.id>/. Headers, redirects, and CSP belong to the output, not the repo root.
  • Person + Organization + WebSite JSON-LD on every page. Persistent IDs (ORCID, ISNI) plus profile URLs in sameAs — no Wikidata dependency required.
  • rel=me identity federation. Every base layout includes <link rel="me"> to each owned site and verified profile — creates a closed loop of identity signals that search engines can crawl.
  • Three-protocol indexing stack. sitemap + IndexNow + WebSub pings on every deploy (Chapter 17). Generated deploy-all.mjs includes optional IndexNow per-site.
  • Content uniqueness at the data layer. One shared articles.json, per-site filtered via site.relatedArticles — no duplicate content across sites.
  • Separate deploy from build. generate-all.mjs outputs everything; deploy-all.mjs only pushes. This lets you rebuild without deploying and vice versa.
  • Generate the full SEO file set per site. robots.txt, sitemap.xml, feed.xml (Atom) + feed.json, llms.txt, security.txt, ads.txt / app-ads.txt (if monetizing), humans.txt, and optional .well-known/* — all templated from sites.json and written into each dist/<site.id>/.
  • Per-site OG images + favicons. Either pre-generate via an image API (Ideogram, DALL-E, Replicate) keyed off site.id, or keep a script that outputs a site-branded OG card at build time. Do not share one OG image across the network — it is a template fingerprint.
  • Ads & Consent Mode v2. Load Consent Mode before any Google tag, and gate AdSense / Mediavine / Ezoic on the Consent dialog. Per-site adsenseId, gaId, clarityId come from sites.json.
  • Quality gates before deploy. Pre-deploy checks for: unique title, unique meta description, canonical present, JSON-LD valid, at least 3 sister-site internal links, no duplicate H1s across sites, og:image present. Block the deploy on failure.
  • Keep article content in a single data file, not scattered Markdown files. Easier to reshape, easier to filter per site, easier to regenerate with AI. See Chapter 11.
Legal & compliance disclaimer: Operating N sites off one brand voice is not automatically deceptive, but if you cross-promote sponsored content, affiliate offers, or AI-generated text, you must comply with FTC disclosure rules, platform policies, and any governing jurisdictions' consumer-protection laws. Chapter 47 of The $100 Network covers legal structure. This tool generates scaffolding only; you own the content strategy and legal responsibility.
Technical disclaimer: This generator outputs a minimum-viable starter. Production monoclones require additional work — image optimization, per-site favicons, Consent Mode v2, structured error monitoring, and the quality gates in Chapter 38. Do not ship to all N domains on day one. Build one, ship it, measure, then expand.