The GEO Score is a 0 to 100 summary built from measured provider evidence. Its formula version is geo-score-v1.
Components and weights
Every component is normalized to 0 through 100 before weighting.
Missing components
If a component cannot be calculated, its weight is removed and the remaining weights are re-normalized.
This prevents missing sentiment, for example, from becoming a sentiment score of zero.
Modeled reach is different. Its contract intentionally accounts for configured grounded engines that were not measured, so incomplete engine coverage can lower that component.
Engine weights
Engine weights come from the versioned engines.yaml registry. They are modeling choices, not claimed traffic share. A formula result should be read with its registry and formula versions.
Date and history
The score service can resolve a specific provider-local date or the latest eligible date. The product exposes 7-day, 28-day, and all-history views for the associated time series.
GEO Score versus combined score
The combined SEO and GEO report uses the latest persisted composite visibility metric as its GEO input. It does not recalculate this five-component score. Keep the contract name with any exported value.
Interpreting change
Use the engine scoreboard and run detail to explain a score movement. A change can come from prompt coverage, provider availability, competitor mentions, position, sentiment, citation behavior, or the configured engine mix. 
