GOS Scoring

The Golden Opportunity Score (GOS) is a triage metric. It is computed by scs score, stored in keywords.csv, and shown in the brief. It does not choose what to write.

Formula

n_sv     = sv / max(sv for the site across all workspaces) * 100
n_kd     = kd  # KD is already 0–100
gos      = (n_sv * (100 - n_kd)) / 100
gos_tier = P1 / P2 / P3 / P4

Tiers

gos_tier	GOS range	Meaning
P1	70+	High triage signal
P2	50–69	Worth reviewing
P3	30–49	Possible cluster/supporting candidate
P4	below 30	Low triage signal

warning

gos_tier is not a priority verdict. The human decision field is. A low-GOS keyword can be go for cluster coverage or business value; a high-GOS keyword can be no for competition, knowledge, or E-E-A-T reasons.

Normalisation scope

SV is normalised against the per-site maximum across all workspaces, not just the current workspace. This keeps the score stable when a new workspace is created and avoids one high-volume site flattening another.

What GOS does not include

GOS is a relative triage score, not an estimate of traffic, ranking probability, or return. Since n_sv is normalized to the highest tracked search volume for a site, adding a higher-volume keyword can change other rows' normalized scores and tiers. Treat tiers as review cues; inspect the raw inputs, source, and date before making a decision.

• business value
• SERP fit
• knowledge/experience
• cluster gaps
• existing-page leverage
• effort

Those are recorded in decision, decision_factors, business_value, serp_fit, existing_page_action, and the cluster coverage fields. They are reviewed by the operator, not folded into GOS.

Recompute

scs score --workspace bs

Adding a keyword can change the per-site maximum and therefore other rows' n_sv and gos. Re-run after imports.

Selection

A row can move to Selected only when decision=go. GOS is evidence, not the gate. See Decision Model.