Understand workspace identity, loading, onboarding, and proof states

Confirm the operating context before reading a figure

The active organization and workspace determine access, stored records, billing context, and every query that reaches Home. The host shown in the domain band identifies the property the briefing can currently name. These are related identifiers, not interchangeable ones. A workspace can exist before it has a domain snapshot, and Site Audit can supply a host while domain metrics remain unavailable.

Home deliberately avoids repeating the host in the page header. Use the workspace switcher and route context to confirm the tenant, then use the band to confirm the property. If either is wrong, stop before comparing, exporting, requesting paid data, or assigning work.

Keep each identity layer explicit

A familiar host name does not prove that the same list, schedule, market, or crawl configuration is active. Record the smallest identity that matters for the decision. A ranking statement usually needs the schedule. An issue statement needs the site and run. A cost statement needs the organization and operation.

Let the two loading stages finish

Home first shows a full-page skeleton while the workspace, role permissions, accessible keyword lists, and accessible Site Audit sites are unresolved. Once those foundations exist, the page can render while secondary sources continue loading. Keyword aggregates, selected-list tracking, the workspace opportunity layer, Site Audit run history, and issue trends belong to that second stage.

A value appearing after the frame is visible is normal. Do not record an early setup prompt as a durable empty state or compare a partly populated screen with a later completed one. If the page never resolves, capture the workspace, role, visible modules, time, and the specific area that remains missing before troubleshooting its owning query.

Understand when fresh-workspace onboarding appears

The onboarding panel replaces the domain band when Home has neither a usable completed Site Audit for the primary site nor usable keyword evidence in the available keyword context. It offers a crawl path, a keyword path, or both according to the current role's permissions. The keyword path links to manual import and to discovery; the audit path links to Site Audit setup.

Onboarding is an orientation state, not proof that every workspace table is empty. A role can lack access to one side. A workspace can contain an own domain without a usable organic snapshot, a Site Audit site without a completed run, or tracking setup that has not produced the values this state checks. Open the named tool when the distinction matters.

Read the optional balance card as organization context

The onboarding area can show an EUR balance card when the usage service explicitly enables balance display for the active organization. The amount comes from current usage context and links to Billing. If the card is absent, do not infer a zero balance or free operation; the display may simply not be enabled or the usage response may not have resolved.

The card is neither an invoice nor a quote for the next operation. Its introductory wording cannot guarantee that a particular crawl, research run, enrichment package, or tracking schedule fits the remaining amount. Use the confirmation shown by the paid operation and reconcile reservation and settlement in the owning records.

Leaving onboarding does not mean setup is complete

Home leaves the fresh-workspace state as soon as either the audit side or keyword side supplies the required evidence. The other side can still be unconfigured. Domain Overview, competitors, opportunities, tracking, and Activity can also remain empty. This transition means the workspace has enough evidence to show the normal briefing layout, nothing more.

Use the dashed setup panels and the workflow strip to identify what remains. Do not create paid data merely to fill every empty space. Configure the next source only when its evidence can change a known decision.

Read the populated band as a multi-source index

The host comes first from the latest usable own-domain snapshot and can fall back to the primary Site Audit host. The date marked As of belongs to that domain snapshot. Site Health and open issues can come from a different completed crawl; collected keywords from a materialized workspace counter; average position from list or schedule tracking; opportunities from the workspace decision layer.

A cell with Set up has no defensible value from its source. Other cells can still be measured. Follow the cell link rather than treating the band as one row from one database. For external reporting, carry each chosen cell's source, market, scope, date, unit, and missing-value semantics separately.

Treat the workflow strip as a proof map

The six segments represent domain analysed, competitors found, opportunities evaluated, keywords imported, tracking activated, and progress check available. Complete means the corresponding persisted condition exists. Current marks the first condition not yet proved. Ready marks the next unproved condition, while later ones are visually blocked. The segment remains a link even when its state is not complete.

The map preserves out-of-order proof. For example, imported keywords and active tracking can already exist without a domain snapshot. The strip does not rewrite that history to make it linear. It also disappears entirely when all six conditions are met; absence of the strip on a populated Home page can therefore mean all workflow proofs are present rather than a rendering failure.

Do not turn workflow labels into operational states

Current, ready, and blocked describe the visual next-step sequence in the briefing. They do not say that a backend job is running, that a feature is authorized, that a person approved the work, or that balance has been reserved. Likewise, complete proves only the condition listed for that segment. It does not prove data quality or business success.

The next-check date comes from the earliest active tracking schedule time available to the summary. It is useful for orientation, but the tracking schedule and run ledger own dispatch, status, coverage, failure, and settlement evidence.

Build a briefing another person can reproduce