New batch Step 3: review, submit & track progress

Step 3, Review & submit, is your last look before anything is created: how many sites, deployed where, with which settings — all on one page. After submitting, the batch detail page tracks every site’s build in real time.

Before submitting: reading the review checklist

From top to bottom, Step 3 shows:

• Deploy target: whether this batch deploys to GOCO Cloud Hosting or your own server, plus the server name. Double-check this — it decides where every site is built.
• Advanced options for this batch: lists only the Step 2 fields you actually set (industry, tone, article count, long-tail, etc.); fields left at their defaults are hidden. Click Edit in the corner to jump back to Step 2.
• goco config: a summary of contact info, brand color, analytics IDs, robots.txt preset and more. Randomly generated items show “Random”; site-verification codes show only “Set”, never the value itself.
• Single-site preview: a mockup using your brand color / font / style — not the real build. With the goco v2 engine, it is a real render from the engine, using the first site to be created as the example.
• Site list table: one row per site, each with a status badge:

Row status	Meaning	What you can do
New	Fresh domain, created on submit	Remove, override this row’s template
Existing	Domain already has a site; not rebuilt by default	Click reset to overwrite-rebuild, or remove
Will reset	Existing and marked for reset; original data overwritten at build	Cancel to revert to Existing
Will migrate	Domain was on another server, migrating into this one	Cancel migration
Error	Row failed parsing (missing domain, bad format, …)	Fix in Step 1 or remove
Conflict	Unresolved cross-server conflict	Migrate / switch server / remove

The header count (“Ready to enqueue N site(s)”) counts only rows that will actually submit (New + Will reset + Will migrate).

Tip

If you see the yellow warning “Same analytics ID across every site”: a batch-level GA4 / Baidu tracking ID is stamped identically on all sites, and one analytics ID shared across many sites is a textbook site-farm fingerprint. To vary it per site, fill columns 6/7 in the site list instead.

Caution

If a red server-validation list appears (e.g. “Row 3 · Domain: invalid domain”), click an entry to jump to that row. All errors must be fixed before the submit succeeds.

Submitting the batch

1. Click “Create batch”

   A confirmation dialog appears — This will create N site(s) on server …. Continue? — confirm to start.

2. Check the result

   On success you’ll see “Batch created — N enqueued, N failed” and land on the batch detail page. If it says the batch was created but enqueueing failed and will retry automatically within minutes, do not resubmit — just wait.

3. If the submit is rejected

   Common causes and fixes: “Your account already has a batch being created” → retry in a few seconds; “Domain conflict” → follow the prompt back to Step 1 to resolve duplicates or existing domains; capacity / credit messages (hosting capacity insufficient, build credits exhausted, …) → buy capacity / credits as prompted, or switch to your own API key in Step 2.

The batch detail page: progress & statuses

After submitting you land on the batch detail page (also reachable from the batch list). While running it refreshes every 5 seconds and stops at terminal state.

• Progress bar: green = completed, red = failed; when the two segments reach 100%, everything has settled.
• Roll-up cards: Total / Completed / Failed / In progress.
• Rate & ETA: shows “N sites/min” and “~X min left”, projected from the last 10 minutes of completions.

Batch statuses

Status	Meaning
Draft	Created but not yet queued
Pending	Queued, waiting to start building
Running	Building site by site
Completed	Every site built successfully
Partial	Some succeeded, some failed (see below)
Failed	Every site failed
Stopping / Stopped	Transition and terminal state of a manual stop

Per-site status and stage

Each row in the sites table has its own status: Draft (created, not queued) → Generating / Reviewing / Building (in progress) → Live (success) or Failed. In-progress sites also show a live stage, e.g. “AI rewriting copy…”, “Picking images…”, “Uploading to server…”. A site with no progress for a long time is flagged “may be stuck” — usually no action is needed; the system times out and settles the result on its own.

Note

The Build throughput panel splits Your server from System (shared): if your server is idle but sites still queue, the wait is in the build pool shared by all users — just wait. If it says “SSH not optimized”, one-click optimize on the Servers page to speed up bulk builds.

How long do builds take?

A single site usually finishes within minutes; total batch time depends on site count and your Step 2 choices — more articles, image replacement, extra languages or long-tail pages all slow things down noticeably. Trust the live rate and ETA on the detail page; for finished batches the throughput panel shows a build summary (result, average per site, total transfer).

Retrying failed sites

1. Wait for a terminal state

   You can’t retry while the batch is still Running — wait until it turns Partial / Failed.

2. Open “Rebuild failed sites”

   In the Actions menu at the top right of the detail page, choose Rebuild failed sites. The failed-sites list shows each site’s error message — read it before picking a mode.

3. Pick a rebuild mode and submit

   Three modes: Keep original (rerun the build with the same template — good for one-off network hiccups), Random (assign a fresh template from this batch’s original pool), Specific (use chosen template(s), multi-select round-robins them). Click “Rebuild N” and those sites are re-queued.

Note

Sites whose server or template has been deleted are skipped and can’t be rebuilt. A different case is the panel “N site(s) created but failed to enqueue” — the sites exist but their jobs never reached the build queue; click Retry enqueue there instead of using the rebuild flow.

Handling a Partial batch

A Partial status means some sites are live and some failed — the two don’t affect each other:

• Completed sites work normally regardless of their failed siblings. For hosting batches, also add the DNS records (CNAME / TXT) shown on the detail page; certificates are issued automatically once they propagate — see the managed-hosting tutorial.
• Failed sites: use Rebuild failed sites above. If the same site keeps failing, note its error message — it’s usually a server connection issue (for your own server, check SSH reachability) or a template issue (rebuild with a different template).
• Sites stuck in Draft are listed separately after the batch settles; that’s an enqueue failure — click Retry enqueue.

Tip

Finished batches also support two whole-batch actions: Apply settings re-applies edited Step 2 settings to every site (no copy regeneration, fast), and Full rebuild regenerates all content (once per batch). If you submitted by mistake, use Stop batch while it runs — pending sites are cancelled, sites already building run to completion.