Cloud blogs + template

The 25-blog network, the Elias Cloud template, and how to run it (one URL).

The centerpiece of the link-building side. Set up once per client (sticky clients) or per niche (high-churn), then run the template whenever you push a page.

Per-client vs per-niche

Joshua's situation (generalist): build per-niche networks — a "Health Services" net (med spa + chiro + mental health) and a "Home Services" net (HVAC + plumbing + electrical + pool). ~2 days of setup buys a reusable asset for every client in the bucket.

Build 25 cloud blogs

25 configs × 12 cloud APIs = ~300 sites. For each config:

1. NEO → Cloud Blogs → Create Cloud Blog.
2. Name = a niche target keyword (Health: "Med Spa Tips," "Skin Health"; Home: "Pool Cleaning," "HVAC Repair").
3. Social links = client's (per-client) or agency's (per-niche) socials — branded backlinks as a side effect.
4. About/Contact = generic but with branded backlinks to money sites.
5. Author bio = the rewritten bio from Platform setup.
6. NAP = HTML format from setup.
7. Generate.

Build the Elias Cloud template (once)

The Cloud Content Poster wizard only takes ONE cloud site per campaign. The Elias Cloud diagram has ~150 tier slots in one campaign — fill them once, duplicate per run.

1. Diagram Editor → find Elias Cloud.
2. Create Campaign named [client/niche]-cloud-template.
3. Placeholder values to clear the wizard: URL https://www.google.com, keyword Google, Account Templates Default, anchor % 100.
4. At the diagram step, for each tier slot (Tier 1 = 5, Tier 2 = 25, Tier 3 = 125) assign one of your 25 cloud blogs. You will have overlap — that's the point.
5. Save.

Why overlap is the feature: the same blog in Tier 1 AND Tier 3 means Tier 3 links point at your own Tier 1 cloud sites — you're interlinking the network, which keeps it alive past the 90-day mark when others' networks die.

Per-run usage

1. Duplicate the template (copy icon).
2. Target = ONE URL. Not multiple.
3. Keywords = anchor text (see the anchor map below).
4. Content bucket = the per-client/niche bucket.
5. Run.

RD100 or cloud, not both. For a page, run the stripped RD100 or the cloud template — both only on a hard keyword.

What the cloud sites are for: on a new client they exist to give the money page referring domains — new sites with authority borrowed from the domains they sit on, getting stronger as you interlink them.

Set your anchors — Tier 1 & Tier 2 (SOP)

After you duplicate the template and set the one target URL, configure the anchors. Same Tier 1 Keywords and Tier 2+ Keywords screens as RD100, same safety gradient — brand at the money page, keywords one layer down. Full system + manual deep-tier pyramid on the Anchor text page.

Tier 1 — Primary Keywords at 100% (brand + brand partial match)

Check Primary Keywords → 100%, brand anchors only, one per line — brand exact + a brand partial-match:

Tier 1 for Adam's Pool: Adam's Pool and Spa Service + Adam's Pool and Spa Service servicing Long Beach, CA customers, at 100%. Leave Generic / Branded / Partial-Match / Plain-URL unchecked — DAS already built that pillow.

Only add a city to the brand if the homepage is optimized for it; don't lock the brand to one city if the client is expanding.

Tier 2 — Primary Keywords at 100% (exact + variations + entities)

On the Tier 2+ Keywords screen, same 100%, but the keyword layer — exact match + variations (related terms) + entities:

Tier 2+: exact match + variations + entities. Cloud campaigns are full articles, so they carry entities well — capture them the fast or right way. No real cap; 50–100 anchors is plenty.

Exact match lives in Tier 2, never Tier 1 — Google is sensitive to exact-match anchors, so the brand stays safe up top and the keyword pressure sits one layer down.

Fix-ups

It's a "link weapon" — point it at anything later (Facebook, LinkedIn, even your own backlinks). Messed it up? Delete the buckets and start over, no harm.