Skip to content

Complete the first diagnosis

The public diagnosis is an anonymous page preview. It shows sample gaps and does not assign a real AI visibility score. Signed-in console diagnosis uses organization-authorized data. One cannot replace the other.

Applies to：Public product description as of 2026-09-28 · Updated 2026-10-24 · Maintained by Omseek documentation

Goal

The first diagnosis checks whether owned pages have the basics to be crawled, understood and cited. After this page, you should be able to tell the public preview from console diagnosis.

Before you start

  • Have a publicly reachable brand domain. The preview does not change the site.
  • Treat preview results as samples. Ongoing observation needs repeated sampling of real search and answers.
  • Console diagnosis needs organization authorization. The header sign-in entry is configured and leads to the Cloud console at app.omseek.com.

Public preview steps

  1. Open the free visibility diagnosis page.
  2. Enter the brand domain, for example yourbrand.com.
  3. Start the diagnosis. The page reveals prepared sample gaps in the browser and does not start real backend monitoring.
  4. Read “Visibility health score: not ready”. That sentence means there is no ongoing observation, so no primary score is shown.

How console diagnosis differs

Signed-in diagnosis belongs to an organization workspace. It uses authorized subjects, evidence and observation batches. A missing source is shown as not connected, not as a zero score.

Follow the live console: confirm the diagnosis subject, then read findings and evidence. Unpublished internal APIs are not written as customer steps.

Expected result

Public preview: sample gaps and a next step for a full brief. Console: findings with source and time, or an explicit not-connected or insufficient-evidence state.

If it fails

  • Empty domain: the preview does not invent a result. Enter a domain and try again.
  • Treating preview as ongoing monitoring: read how to interpret diagnosis results and evidence.
  • Login control still disabled: that deployment is missing the console entry configuration. Report it from the contact page. Do not guess another URL.

Sources

Related

Contact