Skip to main content

Getting started

GEO Platform:

https://geo.thyris.cloud

Prerequisites​

  • An organization with the GEO Services product enabled.
  • A tenant and at least one workspace.
  • Workspace membership with write access for configuration.
  • At least one project, market, language, and owned target.
  • At least one active AI provider; select one as the workspace default.
  • Competitor targets when competitive metrics are required.

First-value path​

  1. Create or select a tenant. Use a Child Tenant when a regional or operational unit needs isolated workspaces beneath the same Organization.
  2. Create a workspace and complete onboarding.
  3. Add the primary domain and allow discovery to propose targets.
  4. Confirm the owned brand/website and classify competitors.
  5. Select markets, languages, objectives, topics, prompts, and prompt sets.
  6. Configure a provider and make it the default.
  7. Review request/cost preview and run the first observation.
  8. Open Dashboard for visibility, citation, competitor, confidence, and priority findings.
  9. Assign recommendations in Action Center.
  10. Configure tracking before publishing changes so impact can be measured.

Three-minute decision view​

The workspace Dashboard answers:

  • How visible is the brand in AI answers?
  • Which providers, markets, prompts, products, or campaigns are weak?
  • Is the result supported by enough samples and evidence?
  • Which actions have the highest expected lift?
  • What changed, who owns the next step, and when is it due?

Production readiness checklist​

  • Default provider is healthy and credentials use an encrypted value or secret reference.
  • Competitors and target classifications are correct.
  • Schedule request and cost budgets are bounded.
  • Low-sample metrics cannot be presented as definitive.
  • Tracking origins, consent mode, retention and DSAR handling are configured.
  • Channel connections use HTTPS, allowlists and least privilege.
  • Approval and rollback owners are assigned before activation.
  • API keys have workspace restrictions, minimum permissions and expiration.

What to do next​

If your next goal isContinue with
Understand system/service ownershipArchitecture and service topology
Model brands, products, campaigns and relationsData model and lifecycle
Choose provider, tracking or publishing connectionsIntegration selection guide
Follow an operational rollout procedureImplementation and operations playbooks
Design a brand/product/campaign programMeasurement scenarios