> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noisemaker.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# GEO Score

> The versioned five-component score for AI answer visibility.

The GEO Score is a 0 to 100 summary built from measured provider evidence. Its formula version is <code>geo-score-v1</code>.

## Components and weights

| Component               | Weight | What it measures                                                                                    |
| ----------------------- | -----: | --------------------------------------------------------------------------------------------------- |
| Relative share of voice |    35% | Brand mentions relative to tracked competitors                                                      |
| Visibility              |    25% | Share of eligible responses that mention the brand                                                  |
| Average position        |    15% | How early the brand appears when mentioned                                                          |
| Modeled reach           |    15% | Coverage across configured engines, including a penalty for grounded engines that were not measured |
| Sentiment               |    10% | Normalized sentiment of brand mentions                                                              |

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.

```text theme={null}
score = sum(component value * component weight)
        / sum(available component weights)
```

This prevents missing sentiment, for example, from becoming a sentiment score of zero.

<Warning>
  Modeled reach is different. Its contract intentionally accounts for configured grounded engines that were not measured, so incomplete engine coverage can lower that component.
</Warning>

## Engine weights

Engine weights come from the versioned <code>engines.yaml</code> 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.