Skip to main content
The Noisemaker console: one workspace, its score, and the work queued off it.

The Noisemaker console: one workspace, its score, and the work queued off it.

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.

Start locally

Configure operator credentials, create a workspace, and run the first measurement.

Learn the model

Understand workspaces, runs, signals, artifacts, credits, and operations.

Read the scores

See how the SEO and GEO views differ and where their evidence comes from.

Use the API

Choose session or bearer authentication and check the scope for each route group.

How work moves through the product

1

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.
2

Calculate repeatable results

Versioned formulas produce the score snapshots. Canonical input digests make SEO processing and report creation replay-safe.
3

Propose work

The platform ranks evidence-backed SEO and GEO recommendations. Generated copy is stored as an immutable draft with provenance and validation steps.
4

Review and verify

A recommendation moves through a fixed lifecycle. Compliance work cannot skip review evidence. Every state change is appended to the history.

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 for the custody model.
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.

Where to go next