Reading your score

Every completed audit has a report page (/audit/<run id>, sign-in required) and contributes to the dashboard at /app. This article explains each element. For the arithmetic behind the numbers, see How scoring works.

The overall tile

The overall score is shown out of 100, rounded to a whole number. The colour follows fixed thresholds: green at 75 and above, gold from 50 to 74, red below 50. A dash means no category could be scored.

If a gating check failed, the tile carries a red notice: "Gating cap applied." The overall is capped at 40 and the uncapped value is shown in brackets so you can see what the score would be once the gating check passes. Category scores are never capped.

Category bars

Each of the ten categories has a bar, its rounded score and, under the name, "x of y assessable": how many of the category's rules could be evaluated out of how many ran. A category where nothing could be assessed shows a dash and is left out of the overall.

The category weights that feed the overall (15 for website foundation and local presence, down to 4 for brand consistency and AI visibility) are listed in How scoring works.

Deltas

Next to the overall and each category, a chip shows the change since the previous completed run of the same business: "first run" when there is none, "no change", or a signed number such as +6 or −3. Deltas are computed on the rounded scores, so a movement inside the same whole number shows as no change. The "Since previous run" card names the date of the run being compared.

Gating checks

A card lists the three gating checks with their result. A not-assessable gating check shows its reason, for example "Google Business Profile not connected (connect it under Integrations)". If any gating check failed, a banner at the top repeats which one and reminds you that the overall is capped at 40 until it passes.

Not assessable

The "Not assessable" card shows how many rules could not be evaluated this run. They are excluded from the score and never counted as failures. If your business type marks a rule as required and it could not be evaluated, the card lists it as "Required for this vertical, could not evaluate". Why a rule says not assessable lists every reason.

The rule table

Rules are grouped by severity (critical, high, medium, low) and sorted by id. Each row shows:

• Id, plus a "required" badge when your vertical requires the rule.
• Check, with the category, the effective weight and the sources the rule reads.
• Result as a chip (pass, partial, fail, na) and, for na, the reason in plain words.
• Evidence: up to eight key–value pairs the check read, such as a count, a query or a tag.
• Fix: the one-line action from the rule set, omitted when the rule passed.

The header records the rule set version and hash used for the run, so a score is always tied to the exact rules that produced it.

Memo and share

The sidebar links to the run's 90-day memo when it is ready, says "being written" while it generates, or "in review before release" if it was withheld. The "Share (scores only)" card creates and revokes public links; see Sharing a result.

The dashboard

/app shows your businesses, the last 20 runs with status and overall, a trend of up to 12 completed runs, the latest ready memo with its actions (tick them off there), whether Google Business Profile is connected, and the date and time of the next scheduled audit in America/Merida time. Manual runs and memo generation are started from here; see How often audits run per plan.