SEO & Webmaster Tools

GOCO ships an SEO workbench built for site networks: it analyzes the top-10 search results into ready-to-build plans (“SEO Recommendations”), tracks keyword rankings daily, lets you apply a recommendation to rebuild a site in one click, and wires up sitemap, IndexNow pushes and other indexing settings at build time.

What it does

• SEO Recommendations: for each keyword × search engine, fetch the top-10 ranking pages and have AI distill them into a buildable plan (recommended pages, TDK, structure, Schema.org, content targets, performance targets).
• Rank tracking: tracked keywords refresh automatically on schedule; the rank trend chart shows 7-day to 1-year history.
• Apply a recommendation: plans in “Ready to use” status can be applied via “Build site with this” — linked to one of your sites and rebuilt immediately.
• Webmaster tools: connect Google Search Console and Bing Webmaster Tools to verify ownership and read back indexed pages, impressions and clicks. Whether it is exposed is governed by a runtime switch (see below).
• Automatic indexing pushes: the SEO tools in the batch wizard (IndexNow, auto-submit to search engines, multi-format sitemaps) take effect as soon as each site is built.

Open SEO ↗

Note

The SEO page unlocks once your account has at least one usable server (self-hosted or managed hosting).

SEO Recommendations: where analyses come from

Each analysis covers one keyword on one search engine (Google / Bing / Baidu / Yandex): the system fetches the keyword’s top-10 ranking pages, studies their titles, structure and content, and generates a site plan. Analyses are usually triggered automatically when you create a batch with SEO options enabled, and appear in the SEO Recommendations list when done.

The list groups rows by keyword, filterable by status and searchable by keyword. The “Latest SERP” column is when the search results were last fetched for that keyword (the tracker refreshes daily) — not when the analysis itself was rerun.

Status meanings

Status	Meaning
Ready to use	AI produced a complete plan; click “Build site with this” or “Archive only”.
Adopted	The plan has been adopted; if a build was included, the linked site was rebuilt accordingly.
Stale	SERP rankings have shifted; consider running a fresh analysis.
Draft	AI output failed validation and can’t be adopted yet (usually just wait for a newer version).

What’s inside an analysis

• Recommended pages: which pages the site should have (home / category / article / landing, etc.), each labeled with user intent; “intent coverage” flags whether informational / navigational / transactional intents are all covered.
• TDK / Structure / Schema.org: per-page title, description, keyword and structured-data recommendations.
• Performance targets: goals measured against Google Web Vitals (LCP / INP / CLS / Lighthouse SEO score) — green = good, yellow = needs improvement, red = poor.
• Sources: the top-10 URLs this analysis cites, expandable to see the fetched titles, word counts, link counts and more.

Reading the rank data

Manage auto-refreshing keywords on the “Tracked keywords” page: each row shows engine, market, frequency (Daily / Weekly / Manual only), status (Active / Paused) and last refresh, with “Run now”, “Pause / Resume” and “Stop tracking” actions. Daily refreshes fire at UTC 00:00.

Click “Timeline” to open the rank trend chart:

• Higher on the chart = better rank (#1 at the top), with 7-day / 30-day / 90-day / 1-year windows and Top 3 / Top 10 / All views; a shaded band marks the “Top 3 golden zone”.
• Top 10 URL table: the pages holding the top 10 at the last refresh, with “First seen / Last seen / Days in top 10” — showing how entrenched each competitor is.
• Featured snippet appearance: green = the “answer box” appeared atop results that day; question-style keywords trigger it more often, brand terms rarely do.
• ▼ markers: an SEO analysis ran at that time; click to view that plan and correlate “change → rank movement”.

Tip

Seeing “no history yet” right after tracking a keyword is normal — the first refresh is queued, and one data point accrues per day after that.

Applying an SEO recommendation

1. Open a “Ready to use” analysis

   Click into a row with status “Ready to use” and confirm the recommended pages and TDK look right.

2. Check data freshness

   If a banner says the SERP data is N days old / stale, the plan is based on older search results — click “Re-analyze” and wait for the new version before adopting.

3. Build site with this

   Click “Build site with this”, pick one of your sites (non-draft), check “Trigger a site build now” and submit — the site is rebuilt according to the plan. To adopt the plan without touching any site, click “Archive only”.

4. Wait for the build

   The analysis status flips to “Adopted”; follow the build progress on the Sites page.

Caution

“Build site with this” rebuilds the selected site according to the plan, replacing its current page structure — double-check before confirming.

Webmaster tools

The webmaster workbench connects your sites to Google Search Console and Bing Webmaster Tools to answer one question: how much of my network is actually indexed, and what is it earning in search.

Whether the page is exposed is governed by the runtime switch webmaster_dev_mode: while it is on the page shows a “under development” placeholder; turning it off reveals the full workbench. During a gradual rollout, individual users can be let through via webmaster_beta_users.

Tip

You do not have to submit anything. The platform already pushes every newly published URL to Bing / Yandex / Seznam / Naver / Yep over IndexNow on each publish, and keeps sitemaps up to date. What the webmaster tools add is reading the data back and reaching Google, which IndexNow does not cover.

Connect Google (do this one first)

1. Go to Webmaster → Google and choose Manage accounts → Connect Google. Pick the Google account that owns the sites and approve the consent screen.

2. You are returned to the workbench. Choose Add site and either pick one of your sites or type a domain.

3. Choose “DNS TXT” as the verification method. If the domain is on a linked Cloudflare account, the TXT record is written for you — nothing manual.

4. Wait for verification. DNS usually propagates within a few minutes and the page refreshes itself; if it times out, use Refresh to re-check.

Caution

Why DNS rather than file or meta: DNS verification produces a Google domain property (sc-domain:), and one domain property covers www, the bare domain, every subdomain, and both http and https. File and meta verification produce a URL-prefix property, which covers only that one exact hostname — www.example.com and example.com become two separate properties whose numbers never add up.

Once verification succeeds, the platform submits that site’s sitemap to Google automatically. You do not need to paste it.

Connect Bing

Bing’s verification code is only obtainable from Bing’s own console — there is no API for it. The path of least effort is therefore to let Bing inherit from Google:

1. Connect Google first (above).

2. Open Bing Webmaster Tools and choose Import from Google Search Console. Bing imports and inherits the verified state of every site at once, with no per-site verification.

3. Return to Webmaster → Bing, choose Manage accounts, and paste the API key from Bing’s Settings → API access.

4. Click the import icon on the account row to pull every Bing-verified property into the workbench in one action.

Note

The API key is optional. IndexNow pushes work without it — the key only unlocks Bing’s data (clicks, impressions, crawl issues, backlinks, keywords) and the daily submission quota.

If you would rather not import, do it by hand: add the site in Bing’s console, copy the verification code, and paste it into the Bing verification code field when adding the site here. Leaving it blank parks the site in “Awaiting code” until you supply it — it is not counted as a failure.

What the statuses mean

Status	Meaning	What to do
Awaiting code	Registered, but no platform verification code yet	Open the site and paste the code
Pending	Verification submitted, waiting on the platform	Wait — DNS can take a few minutes
Verified	Ownership confirmed	Nothing; data starts flowing in
Failed	The platform rejected verification	Read the message — usually a wrong code or DNS that has not propagated

Reading the data

The Overview tab rolls up every verified Google property: indexed pages, impressions, clicks and CTR.

Note

“Indexed pages” means distinct pages that received at least one impression in the last 28 days. Google exposes no direct indexed-page count, and a page must be indexed before it can earn an impression, so this is a scalable proxy — it reads slightly low, because pages that are indexed but never shown are not counted.

Per site you also get search performance (top queries and pages), URL inspection, sitemap status, and a run history — the outcome of every verification and submission, including exactly which URLs failed in a bulk submit.

Baidu and Yandex

The code is retained but the tabs are hidden for now: Baidu confirms ownership only inside its own console (there is no endpoint to poll), and no Yandex OAuth application is configured. Neither affects URL pushes — Yandex is already covered by the automatic IndexNow push.

Automatic indexing & pushes (live at build time)

No need to wait for webmaster tools — these switches under “Advanced → SEO tools” in the batch wizard take effect the moment each site is built:

• Sitemap formats: sitemap.xml is always generated; optionally also sitemap.html (human-readable) and sitemap.txt (one URL per line).
• robots.txt preset (the same set as the batch wizard’s Step 2, five presets):
  • Open (default, best for indexing): blocks only the error page /404.html, everything else allowed.
  • Moderate: on top of Open, also blocks URLs carrying utm_ tracking params.
  • Conservative: adds /search?, ?ref=, ?fbclid= and similar param / on-site search pages.
  • Fully open: no Disallow at all — the whole site is allowed.
  • Custom: write your own robots.txt with a live preview below, and risky rules (e.g. Disallow: / blocking the whole site) are flagged. Whichever you pick, the correct Sitemap URL is appended automatically; and if “AI search visibility” is set to “Block”, Disallow rules for AI crawlers are appended too.
• IndexNow: writes an IndexNow key file at the site root (self-verifying — no prior webmaster setup) and pushes the homepage to Bing / Yandex after build to speed up indexing. Strongly recommended.
• Auto-submit to search engines: after each site builds, it pings IndexNow / verified webmaster platforms; a no-op (no errors) until the domain is verified.
• Long-tail keyword tag pages: AI generates ~30 long-tail phrases, each with its own standalone page (own title / description / short article) — extra indexable URLs that widen search coverage.

Tip

Pushes only speed up discovery — whether and how much gets indexed is up to the search engines. Keeping content fresh (pair with scheduled article publishing) beats repeated pushes.

Back to overview