# Visibility Agent

> Understand how Selfwin turns stored tracking evidence into classified gaps, proposed actions, and reviewed drafts.

- Product: Selfwin
- Section: Take action
- Updated: 2026-09-06
- Canonical: https://docs.selfwin.co/visibility-agent
- Keywords: visibility agent, GEO agent, content gaps, AI actions

The Visibility Agent reviews recent tracking evidence and prepares work for prompts where your brand is weak. It is a closed-loop workflow: evidence becomes a gap, a gap becomes an action, and an action can later be measured against new tracking results.

## When a prompt is flagged

The agent reviews active prompts over its analysis window. A prompt can be flagged when your visibility is below the configured threshold or when the leading competitor is sufficiently far ahead.

It records a snapshot of the brand standings, URLs, citations, and fanout evidence used for the decision.

## Gap types

### Absent

Your brand does not appear in enough answers for the prompt. The agent may propose a new page or another way to establish a relevant answer surface.

### Leak

Your content or domain contributes to an answer, but another brand receives the visible credit. The evidence links the source visibility to the brand-visibility gap.

### Out-sourced

Models rely on a third-party source where competitors are present and your brand is missing or weak. The agent may propose editorial, community, directory, or outreach work.

### Entity owned

An owned page exists but does not win the expected retrieval or brand result. The agent may propose retargeting the page or fixing indexing.

## Action types

Depending on the evidence, the agent can prepare:

- Retarget an existing page.
- Create a new page.
- Produce a video brief.
- Draft a community reply.
- Draft outreach.
- Create an indexing ticket.
- Create a leak-resolution ticket.

## Drafting and linting

On-domain drafts use the project brief, competitors, source URLs, and observed fanouts. They pass through Selfwin’s content linter before the run reports them as ready.

Expensive research and drafting pipelines are budgeted per run. The agent can still create evidence-backed template actions when a provider is unavailable.

## Run behavior

Runs can be started manually, on schedule, or through MCP. A completed scheduled run is idempotent for its project and week. Run history preserves status, configuration, summary, errors, and timestamps.

The agent does not publish. Continue with [Action queue](./actions) to review and approve its output.