Deepdive on AutoBuilds

What an Auto Build actually does at each stage, what every field controls, and the math behind network sizing. For the shortest path through the workflow, see Auto Builds: Quickstart.

"Build" — One run of the Auto Build workflow, from a Link Inventory through to launched campaigns.

"Link Inventory" — A named collection of links: the URLs, crawled pages and Google Business Profiles a Build plans from. Created or selected as the first step of a Build, and reusable across Builds. Read A Guide to Link Inventories here.

"Enrichment" — The analysis run on every link in an inventory: extracting titles, assigning categories, and determining linkability, along with data-maps (locations, services, products, etc).

"Linkable" — A link that can be used as a link target. Only linkable links receive backlinks from the network. Unlinkable resources (which can be overridden if you choose to do so) include legal disclaimer pages, things like that.

"Plan" — The campaign structure produced from an inventory: campaigns, their content topics, and their Site Clusters. Reviewed and approved before anything is generated.

"Campaign" — A group of pages, content and links, published across your domains, that builds links to your URLs.

"Site Clusters (Destination Groups)" — Themed groups of sites the network publishes to. Called Destination Groups elsewhere in Publishing. Read more about Destination Groups here.

"Tiers (T1, T2, T3)" — The levels of the network: T1 pages link directly to your URLs, T2 links to T1, T3 links to T2. These mirror linking structures found everywhere, like reviews (T2) linking to products (T1).

A Build runs through seven stages: Setup → Crawl & Enrich → Plan → Review → Generate → Provision → Launch. Each stage can be expanded on the Build page, and a Retry button appears if a stage gets stuck or fails.

Two stages can wait for you:

• Review always
• Crawl & Enrich when a crawl needs page review.

The output is a tiered network: T1 pages link directly to your URLs, T2 pages link to T1, and T3 links to T2. Every page is published to sites created on your hosted domains.

• Build name — how the Build is listed; purely organisational.
• Link Inventories — the links the Build plans from. Select existing inventories or create one inline. A Build can use several inventories, and planning treats their links as one pool, but will seperate out logically distinct types of links.

When creating an inventory:

• Links — one URL per line, or a CSV upload (first column). Pages, root domains, Google Business Profile listings and YouTube videos are all valid; each type is enriched with its own method.
• Potential sites to fully crawl — root-domain links can be fully crawled to discover their pages. Checked sites are crawled; unchecked root URLs are kept as single links and enriched normally. Crawling matters when you want the Build to understand a whole site rather than one page.

Auto Builds have a monthly cap. A verified Gemini API key under Settings → API keys unlocks a much higher monthly cap.

Crawling fetches the pages of the sites you selected. For large sites, folder selection (path prefixes, with detected language folders) limits the crawl scope, and after crawling you choose which discovered pages to keep — deselected pages are deleted before enrichment.

Enrichment then analyses every link: it extracts titles, assigns a Category (with city/area and region/state where relevant), and determines whether the link is Linkable — usable as a link target. These fields drive planning: categories shape how campaigns are grouped, and only linkable links receive links. Category edits on the inventory affect new or re-planned Builds, not plans that already exist.

See [A Guide to Link Inventories] for the inventory page itself.

Planning turns the enriched inventory into campaigns and Site Clusters (Destination Groups) — the themed groups of sites the network will publish to.

Everything in the plan is editable before you approve it:

• Site Cluster fields — Name; Prompt, the instruction that steers what the group's sites are about; and Purpose, the group's role in the network.
• Campaign fields — each campaign's article topics, word counts and seed keywords. Topics become the pages of the campaign; seed keywords steer what each article targets.
• Approve / Reject — approved campaigns are generated, provisioned and launched; rejected campaigns are excluded everywhere downstream, including site creation.
• Replan — discards the current plan and plans again from the same inventory. Use it after changing inventory categories or linkable flags.

Each approved campaign runs a six-step content pipeline: AI Content → AI Enrichment → Titles & headers → AI Content Spinning → Supporting Content → Post-processing. The result is spintax content — each published page renders a unique variant.

• Open in Menterprise Content — the generated campaign is a normal Content campaign; anything editable there applies.
• Regenerate campaign — re-runs the full pipeline, replacing the campaign's content. The optional Additional prompt steers the rewrite (e.g. With additional geo-focus on Australia).

Sizing decides how many pages and sites the network gets. Three inputs:

Domains to use: How many of your hosted domains the Build may create sites on
Domain Utilisation %: What share of those domains is actually used — the rest stay in reserve
In-Network Interlinking: The tier preset: thin, normal or boosted

The math

1. Domains used = domains to use × utilisation %. At 100 domains and 50%, the network is built across 50 domains.
2. T1 pages = linkable URLs × domains used ÷ 3, rounded up. Each published page carries three outbound link slots, and every linkable URL gets a link from every domain used — so this is the page count needed to hold those links. (Minimum: one page per domain used.)
3. T2 and T3 pages are multiples of T1, set by the preset:
   Thin: T2 = 2xT1, T3=4xT1
   Normal (default): T2 = 3xT1, T3 = 6xT1
   Boosted: T2 = 5xT1, T3 = 10xT1

Higher presets mean more pages linking into your T1 layer — a stronger, denser network that consumes more content and sites.

1. Site counts (density) — each group gets the minimum number of sites that keeps its load at or under 200 pages per site. The recommended counts update live as you adjust the inputs, and the table shows each campaign's totals and average pages per site.

Sizing locks once site creation starts or sites already exist for the plan.

Each Destination Group requests its computed number of sites. You pick which domains each group's sites are created on — Auto select per group, or Auto-select all groups. Groups not referenced by any approved campaign are excluded, so no sites are created for rejected work.

This is mostly used for keeping some domains seperate from eachother. For example, if your AutoBuild focuses on a local business, you may have root domains set for local-directory style builds. In this case, you'd select those, and in non-local AutoBuilds, select other domains. You can ensure that your domains, sites (subdomains), and pages are always tethered logically.

Launch publishes the campaigns to their sites on a schedule:

• Pages per site per day — the publishing pace. Lower is slower and more gradual; the per-campaign table shows the resulting days-to-complete.
• Schedule backdate — shifts publishing dates into the past, so the network doesn't start from zero on launch day. This is mostly used on initial AutoBuilds to give the network a kickstart.

After launch, Campaigns live in Publishing and their content in Menterprise Content.

Deleting a Build removes the Build record; three checkboxes decide what else goes: the campaigns it created, the Destination Groups created for it, and the sites (subdomains) in those groups. If you choose not to delete anything checked, they keep running without the Build. Deletion cannot be undone.