Build with GOCO managed hosting

The easiest path: you don’t need your own server, and there’s no BaoTa to install. GOCO managed hosting hosts the sites on the platform side, with automatic domain binding and managed SSL.

Note

Managed hosting suits “launch fast, no server ops”. If you already have a server and want full control, see your own server (SSH).

Before you start

• A GOCO account (each account has 10 free build credits, shared between SSH and managed hosting; managed-hosting site capacity requires a purchased plan).
• The domains you want to build (you just need DNS control; finish the DNS step after deploy).

Steps

1. Buy GOCO managed hosting

   In the console Servers page, buy a GOCO managed hosting plan. No server of your own is required; each tier includes a site quota (Starter 50 / Standard 300 / Large 600 / XL 1000 / XL 2000 sites). It renews monthly, and Standard and above also carry an annual platform fee (the Starter experience tier is exempt — see Orders & billing).

   Buy managed hosting ↗

2. New batch (choose “GOCO managed hosting”)

   Batches → New batch. In Step 1, switch the deploy server to GOCO managed hosting, pick a hosting server (shown by region with capacity, e.g. 0/50), then choose the template-assignment mode, select HTML templates and paste your domain list.

3. Advanced config (optional)

   Configure brand (industry / region / language / tone / site type / logo), content (article count / seed / long-tail / AI OG) and SEO tools. See the shared notes in the overview.

4. Review & submit

   In Step 3 review the site list and submit. The platform bulk-generates and deploys to managed hosting.

5. Domain binding & SSL (automatic)

   After deploy the platform automatically creates a managed hostname for each domain you entered and prepares to issue SSL (via Cloudflare for SaaS). Next, just point the domain’s DNS to the hosting endpoint as shown in the next section — no BaoTa, SSH or manual certificates needed.

Resolving your domain (Method 5 · managed-hosting one-click reader)

After deploy a site starts as “Pending DNS”, so you add a few DNS records at your domain’s DNS provider. The fastest way is the console’s CF page → “Method 5 · managed hosting”, which reads and generates them in bulk.

1. Open “Method 5 · managed hosting”

   Go to the console CF / DNS page and switch to the Method 5 · managed hosting tab.

2. Enter domains and “Read records”

   Paste the domains you created on managed hosting (one per line), or click “Fill all my pending domains” to pull them in. Then click “Read records” and the system generates every record each domain needs:

   • ① Routing CNAME: @ (and optionally www) → use the record value shown in the console (it’s issued per the domain’s shard, e.g. tw1.goco.cc, and may also take a goco-host.com-style form) — the site only opens once this one is added.
   • ② Certificate DCV CNAME (one-time): _acme-challenge → <domain>.<delegation-tag>.dcv.cloudflare.com — lets us issue the HTTPS certificate automatically; keep it after issuance.
   • ③ Ownership TXT: _cf-custom-hostname → a verification value — proves you own the domain, for Cloudflare’s pre-validation.

   Tip

   Method 5 shows relative host records (@ / www / _acme-challenge / _cf-custom-hostname). These are the same record as the full hostname shown on the Sites page (e.g. _acme-challenge.example.com) — just a different notation. Most DNS providers expect the relative form in their “Host / Name” field, so either works.

3. Push in one click / copy to DNS

   Confirm, then push in one click (if the domain is in a Cloudflare account you’ve already connected, it applies the records directly); or click “Copy all records” and add them at your DNS provider. Once they propagate the certificate is issued automatically and the site moves from “Pending DNS” → “Issuing certificate” → “Active”.

Caution

If your domain is on Cloudflare, set the “① Routing” CNAME to “DNS only” (grey cloud) — do not turn on the orange proxy. An orange-cloud proxy double-proxies and breaks both resolution and certificate issuance.

Note

If a domain’s ③ Ownership TXT shows “not read yet”: if the site is already “Active”, ownership was verified long ago and that record is no longer needed — you can ignore it. Only if the site is still not active, and you’ve already added the routing/certificate records above, click “Retry” to read again.

After

On the Sites page review status and health, then enable scheduled publishing, SEO, indexing and more — identical to the self-hosted path.

Back to overview