Skip to content

Managing sites

The Sites page is the control center of your network: every site you’ve built lives here. You can check each site’s status, health score, SSL, indexing and CDN state, and act on one site or a whole batch.

The tiles at the top are both an overview and one-click filters — click any tile to see only those sites:

  • Total sites: all sites plus the average health score; click to clear the health filter.
  • Abnormal: sites with a failing domain-health check (reachability / cert / block).
  • Warning: health score 50–79.
  • Healthy: health score 80 or higher.
  • No score: health score not computed yet (usually not deployed successfully yet).
  • Unreachable: deployed but unreachable in the latest check.
  • Push errors: the latest IndexNow push failed or the key file didn’t serve.
  • Search box: search by domain or title; pasting multiple domains (newline / comma / space separated) automatically switches to exact bulk search.
  • Bulk domain search: click “Bulk search (multiple domains)” for a dedicated input, one domain per line. After searching you’ll see “requested X · matched Y”, and unmatched domains can be copied out for review.
  • Filters: narrow by Status (Draft / Generating / Building / Publishing / Live / Failed / Paused …), Template category, Group and Server; click Reset to clear everything.
  • Columns: the “Columns” button lets you choose which columns to show (SSL / Webmaster / Indexed / Rank / CDN / Pages / Version / Domain health …).
  • Sorting: click a column header to sort; “Health” supports low-to-high so you can tackle the worst sites first.

Free basic checks (reachability / HTTPS certificate / GFW block) run automatically for every deployed site. The result shows in the “Domain health” column as the worst of all checks:

Shown Meaning
OK All checks passed
Warn Some check is in a warning state (e.g. certificate expiring soon)
Fail Some check failed (unreachable, certificate error, or blocked)
Unknown No reference data yet (this is normal)
Error The check itself errored (e.g. timeout) — not necessarily a site problem
Pending No check data yet; undeployed / test sites are not checked

The last-checked time appears under the badge. For advanced mainland-China checks (access latency, DNS pollution, WeChat / QQ blocks …), click Configure in the toolbar to connect a boce probing key and enable paid checks for selected sites.

The row’s Actions menu offers: View details, Open site (visit the live site), Edit group, and — for goco-hosted sites — Bind domain. Clicking the row itself opens the site detail.

At the top of the site detail you can:

  • Refresh / Open: reload the data, or visit the live site.
  • Origin check: verify that the content served publicly matches what was deployed (see troubleshooting below).
  • Redeploy: after confirming, queues a build + deploy job to rebuild the site. Migrated sites marked “Static archive” are read-only and cannot be redeployed.

Pause, resume and delete are done through the bulk toolbar after ticking rows — ticking a single row works fine for one site.

Tick the checkboxes to select sites; the header checkbox selects the whole current page. With a selection, the toolbar offers:

  • Edit group: move the selected sites into a group, or remove them from one.
  • Delete: deletes the selected sites. This is irreversible and asks you to type the count to confirm; it removes the site records (including build / deploy history, schedules and publish records), but deployed static files on your server are not cleaned up — handle those yourself if needed.
  • Export CSV: see below.
  • More:
    • Bulk redeploy: queues a build + deploy job per selected site; paused / building sites are skipped automatically to avoid unintended re-publishing.
    • Bulk pause: sets sites to “Paused”; automated tasks such as scheduled publishing skip paused sites. Resume anytime.
    • Bulk resume: restores only the “Paused” sites in your selection back to “Live”.
  • Configure: apply a monitoring configuration to the selection; with nothing selected it edits your account default template.

Select sites and click Export CSV. The file includes: Domain, Title, Status, Group, Theme, SSL, Webmaster, CDN, Pages, Server, Last deploy and Health. It carries a UTF-8 BOM so Excel renders non-Latin text correctly. A “Exported X, skipped Y unreadable” notice means some selected sites were deleted or are no longer readable.

  • Basic info: domain, title, brand, description, server and theme template.
  • Build info: build version, last build / last deploy times, last error.
  • Domains needing DNS setup (goco-hosted sites): the DNS records still to add and each domain’s status (Awaiting DNS / Issuing certificate / Active / Error), with a copy-all button.
  • Health score: the automatic SEO / accessibility score (out of 100) computed after deploys, listing each passing / failing check. Optimize fills missing SEO tags and can improve the title & description copy without touching articles or the template.
  • Domain health: the latest run’s per-check results (with latency); Re-check immediately reruns the free basic checks (short cooldown).
  • SEO competitor gap: structured AI recommendations from comparing against competitors.
  • Index funnel: Deployed → Reachable → Pushed → Crawled → Indexed — a five-stage funnel that shows where indexing is stuck; impressions appear after you connect Google Search Console.
  • Build config: the site’s build configuration (hidden for static HTML-template sites).
  • Build history / Deploy history: recent jobs with status, duration, bytes transferred and error message / failing stage.
  1. Click the Abnormal or Unreachable tile, sort by health score ascending, and start with the worst.

  2. Open the site detail’s Domain health card to see which check failed (reachability / certificate / block), then hit Re-check to confirm — a site abnormal at 1pm may be fine now.

  3. “Certificate error” or “Issuing” usually means a DNS record is missing or was deleted, blocking issuance or renewal: for goco-hosted sites, verify the records under Domains needing DNS setup; for self-hosted sites, check the SSL column’s certificate status and your DNS.

  4. The site opens but shows the wrong content

    Section titled “The site opens but shows the wrong content”

    Run Origin check. If it reports the public content does not match this server, the domain’s DNS / CDN origin isn’t pointing at the deployment server — the site itself was built correctly; fix the DNS records.

  5. For a “Failed” status or a last-build warning, open Build history / Deploy history in the detail view for the error message and failing stage, fix the cause, then click Redeploy.