Presence Ops.org An open definition of the discipline

Reference

Glossary

These are working definitions: versioned, sourced where sourcing applies, and open to correction. Terms marked as experimental (Presence Score) do not yet have external validation, and we say so.

Presence Ops
The discipline of keeping a product accurately, freshly, and verifiably present across the web — head platforms and long tail — for humans, search engines, and AI assistants alike. See the definition. Full definition →
The head
The small number of surfaces where attention and community are concentrated: Reddit, Hacker News, Product Hunt, the launch moments. Per the power-law structure of the web, the head carries most of the reward — and it demands authentic, personal, disclosed participation. Human work.
The long tail
The hundreds of directories, tool lists, review sites, niche aggregators, and databases where a product should be present. Each surface is individually minor; collectively they form the product’s footprint in the corpus that search engines and AI assistants read. Delegate to operations.
The Head-and-Tail Rule
The assignment rule of Presence Ops: humans run the head, automation maintains the tail. The boundary is defined by delegability — a function of agent technology and each platform’s tolerance for disclosed automation — not by a fixed list. Surfaces requiring genuine human participation stay human regardless of technology.
Presence graph
The full set of entries that describe a product on surfaces it does not control: listings, profiles, mentions, entity records. The asset that Presence Ops maintains. Its state — accurate, alive, fresh, consistent — is the deliverable.
Presence debt
The accumulated cost of unfixed presence: every listing that still describes the old version, every dead link, every wrong category. In the lineage of Ward Cunningham’s technical-debt metaphor — it accrues interest until paid.
Presence decay
The tendency of the presence graph to degrade without maintenance, in the lineage of Lehman’s first law of software evolution: a used system must be continually adapted, or it becomes progressively less satisfactory. The tail also regenerates: new surfaces appear, old ones die, roughly a fifth of each day’s search queries have never been seen before.
Presence Score
The discipline’s working metric: coverage, live-link rate, freshness lag, and consistency across the presence graph. In the lineage of excess share of voice (eSOV) and share of search — directional, leading, and to be treated like any leading indicator: watched over time, never worshipped. External validation is pending; treat as experimental.
Disclosure-first participation
The only acceptable mode of agent-assisted presence on community surfaces: official identities, disclosed affiliation, no fake reviews or vote rings. A structural constraint, not a policy aspiration — regulators fine both sides of undisclosed endorsement, and platforms ban what they detect.