> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noisemaker.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform overview

> Measure how a brand appears in search and AI answers, then turn the evidence into reviewed work.

<Frame caption="The ai-cmo.dev console: one workspace, its score, and the work queued off it.">
  <img src="https://mintcdn.com/auto-gtm/iXt5uMxsbIiTmJfR/images/console-workspace.png?fit=max&auto=format&n=iXt5uMxsbIiTmJfR&q=85&s=ee7e997a22c150643bf1127ea313f582" alt="The ai-cmo.dev console: one workspace, its score, and the work queued off it." width="2880" height="1800" data-path="images/console-workspace.png" />
</Frame>

The platform measures two related surfaces:

* **SEO** tracks search demand, traffic, authority, content coverage, and technical health.
* **GEO** tracks whether AI answer engines mention, position, describe, and cite a brand.

It keeps the source evidence behind each score. A team can inspect provider responses, search and analytics signals, research artifacts, technical checks, and the recommendation history before acting.

<CardGroup cols={2}>
  <Card title="Start locally" icon="play" href="/quickstart">
    Configure operator credentials, create a workspace, and run the first measurement.
  </Card>

  <Card title="Learn the model" icon="book" href="/concepts">
    Understand workspaces, runs, signals, artifacts, credits, and operations.
  </Card>

  <Card title="Read the scores" icon="chart-line" href="/dashboard">
    See how the SEO and GEO views differ and where their evidence comes from.
  </Card>

  <Card title="Use the API" icon="code" href="/api-reference/authentication">
    Choose session or bearer authentication and check the scope for each route group.
  </Card>
</CardGroup>

## How work moves through the product

<Steps>
  <Step title="Collect evidence">
    A measurement run queries the configured AI engines. SEO processing reads provider-local search, analytics, authority, and audit signals. Research runs build frozen artifacts from the workspace profile and available sources.
  </Step>

  <Step title="Calculate repeatable results">
    Versioned formulas produce the score snapshots. Canonical input digests make SEO processing and report creation replay-safe.
  </Step>

  <Step title="Propose work">
    The platform ranks evidence-backed SEO and GEO recommendations. Generated copy is stored as an immutable draft with provenance and validation steps.
  </Step>

  <Step title="Review and verify">
    A recommendation moves through a fixed lifecycle. Compliance work cannot skip review evidence. Every state change is appended to the history.
  </Step>
</Steps>

## Product boundaries

The application does not edit a customer site, publish content, or grant itself access to analytics properties. People remain responsible for implementation, access invitations, review, and verification.

OpenRouter, Exa, AgentMail, and PageSpeed credentials are operator-owned secrets. GA4 and Google Search Console access is granted per workspace to its provisioned AgentMail address. See [Connections](/connections) for the custody model.

<Note>
  A missing signal is not silently treated as a zero. Score formulas drop unavailable components and re-normalize the available weight where the relevant contract permits it.
</Note>

## Where to go next

* New operator: [Local quickstart](/quickstart)
* New teammate: [Core concepts](/concepts) and [Dashboard](/dashboard)
* Content or search owner: [Prompts](/prompts), [Research pipeline](/research), and [Recommendations](/recommendations)
* Platform operator: [Deployment](/operations/deployment), [Data model](/operations/data-model), and [Credits and billing](/credits-billing)