Spearleaf · SEO Neo Playbook v5 · 2026-06-07 Start here Changelog
Manual

Network & infrastructure safety

Run a domain network + host client sites without getting caught or trapped.

On this page

How to run a domain network and host client sites without getting caught or locked in.

Hide a network in the noise (Cloudflare name servers)

Greg-Morrison-style PBNs get caught: trash-looking sites, same IP, same registrar, no privacy. Garrett Alcott's safer method:

  1. Turn on WHOIS privacy on every domain — now the only link left is the IP.
  2. Add each domain to Cloudflare. It assigns one of ~13 different name-server sets and rotates across many IPs; millions of sites share each name server, so there's no clean way to tie your domains together.
  3. Free, and Cloudflare is worth having anyway.

Building a full Greg-Morrison PBN is a ton of work and only pays if you sell links. FoxNews owns ~17,000 domains all linking to itself — a PBN, but they're real publishers, so they're fine. Be the real-publisher version.

Exact-match domains

Own the racecourse

(James Schramko's rule.) Own your platform; don't bet a business on a free tier you don't control.

Turbo Subdomains (TSD) — optional scale tool

Garrett Alcott's subdomain-network tool. License $2K–$10K + $197/license; Clint paid ~$3K for 2 sites × 500 subdomains = a 1,000-site network at ~$500/mo. The value is auto-publishing (sites are always doing something); DIY and you own the publishing problem. System is janky — turn-and-burn for now. With Sonic + Claude you could replicate it (design → template → all subdomains → default pages → topical map per site → 150 scheduled posts ≈ 2 years of content). See Build stack.

Client reporting

Tell clients up front: no reports. Install a change-history plugin so they can see exactly what you're doing, and they already have GSC + GA. No reason to bill for restating free data (export the change log if a client insists).