53
Fields
In every finding, in 9 groups.
Ask a chat assistant to write up SEO audit findings so they can be scored, sorted and handed over. Every finding has the same 53 fields, and its priority is computed from six judgments, not asserted.
https://mcp.jakelabate.com/finding-recordHelp me write up SEO audit findings so they can be scored and put in order. Show me what a finding needs, then check mine one at a time. Do not fill in a field I have not given you.No sign-in. It checks and scores the findings you send, and keeps nothing.
53
Fields
In every finding, in 9 groups.
6
Judgments
What the priority score is computed from.
33
Register columns
Each with a note for the reader.
5
Tools
None of them changes or stores anything.
get_record_specvalidate_findingscore_findingsscore_findingsfind_duplicatesexport_register4 findings from a made-up shop, sent to score_findings. Two of them wait on the first. This is the server's own answer, run when this page was built.
{
"findings": [
{
"finding": "IDX-001",
"score": 55,
"band": "P1",
"wave": 1,
"arithmetic": "3 x (5 x 0.75 x 1 x 3) x 1.15 / square root of 0.5 = 54.89, rounded to 55"
},
{
"finding": "SD-001",
"score": 9,
"band": "P2",
"wave": 2,
"arithmetic": "3 x (4 x 1 x 1 x 1) x 1.1 / square root of 2 = 9.33, rounded to 9"
},
{
"finding": "PERF-001",
"score": 5,
"band": "P3",
"wave": 3,
"arithmetic": "3 x (3 x 1 x 0.8 x 1) x 1.05 / square root of 2 = 5.35, rounded to 5"
},
{
"finding": "LINK-001",
"score": 3,
"band": "P4",
"wave": 4,
"arithmetic": "3 x (2 x 1 x 0.8 x 1) x 1.05 / square root of 3 = 2.91, rounded to 3"
}
],
"how_bands_were_set": "A band is a position among the 4 client-facing findings that were scored: P1 is the top 15%, P2 the next 25%, P3 the next 30%, P4 the rest. Findings that score the same share a band."
}
The first finding scores highest partly because two others cannot start until it lands. That is leverage, and it is read off what depends on what, not typed.
A finding is one claim, written as a record. Because every finding has the same fields, a set of them can be sorted by score, filtered to an owner, grouped by template and exported, without being retyped.
ref, title, pillar, raisedurls_affected, templates, marketsmeasurements, source, collected_from, collected_to, confidence, confidence_reasonimpact_type, metric_at_risk, quantity_value, quantity_unit, impact_basis, time_horizon, affectsaction, steps, owner, effort_days, dependencies, depends_on, external_blockers, waveblast_radius, failure_likelihood, reversibilityseverity_weight, reach, confidence_factor, leveragestatus, verification_method, verify_by, verified_on, closed_noteexposure, decision, decided_at, decided_by, decision_note, acceptance_checks, last_check_at, last_check_result, implemented_on, outcome_note, outcome_value, outcome_unit, outcome_measured_onEach field is supplied one of five ways, which is what tells a person or an assistant what they may fill in.
get_record_spec returns every field with its type, its allowed values and when it is required.
The fields answer 5 questions in order. A finding that cannot answer all of them is not finished.
titlemeasurements, source, confidenceimpact_type, metric_at_riskaction, owner, stepsverification_methodThe rules a finding is held to. validate_finding checks each one that can be checked without judgment, and says what it was not given enough to check.
quantity_value is set, impact_basis has to be. The number is what gets quoted back six weeks later.confidence_reason.verification_method is filled in when the finding is raised, not after something has shipped and needs a check that flatters it.closed_note is required when status is fixed, verified or accepted risk. verified_on goes with verified, and only with it.The tools never write a value into a field. A verification method or an owner that nobody agreed to is worse than a blank.
score = 3 x (severity x reach x confidence factor x leverage)
x risk factor / square root of effort days
risk factor = 1.3 - (blast radius + failure likelihood) / 20
- reversibility / 20
Six judgments go in. The score comes out, from 0 to 100.
Severity and effort are never assumed: without both there is no score. When another input is missing, reach, confidence factor and leverage count as 1 and each fix-risk input as the middle of its scale (2, 2, 1), and the answer says so each time.
The same inputs always give the same order. When someone argues with the order, the argument is about one input that two people can look at.
A band is a position inside its own audit, not a fixed score. It is the share of the client-facing findings that score the same or lower.
Cutting at fixed scores meant only a finding that was severe, high in leverage and near total in reach ever reached P1, so an audit where nothing was catastrophic read as though nothing mattered. The band answers what to do first here. The score is what compares one audit with another.
Findings that score the same always share a band. Internal findings are not ranked against, so they cannot push a client-facing finding up. With one finding, or a set that all scores the same, there is nothing to rank against and fixed cuts are used: P1 at 80 or more, P2 at 55 or more, P3 at 30 or more.
An audit written in passes, by several people or by a model, collects the same finding twice. find_duplicates compares the words of titles and fixes, weighted by how rare each word is in the set, and returns the pairs that read alike with the words they share.
It is a short list to read side by side, not a verdict. Two findings can share words and be different problems, and the same problem can be written in different words and be missed.
The register is one row per finding, highest score first, as CSV, a Markdown table or JSON. Each column carries a note, printed under its header, because a bare header such as Reach tells a reader who was not in the audit nothing.
Those 14 are on by default. 19 more can be added: Pillar, Markets, Kind of harm, Metric at risk, Exposure, When it bites, Confidence, Data window, Sources, Steps, Blocked by, External blockers, Severity, Reach, Leverage, Fix risk, Decision, Verified on, What changed.
Internal findings are left out unless asked for. A cell that a spreadsheet would run as a formula is written as text.
get_record_spec Returns the record an SEO audit finding is written as.validate_finding Checks one finding against the record.score_findings Computes the priority of each finding in a set and puts them in order.find_duplicates Finds pairs of findings that may be the same finding written twice, or two findings that one fix would close.export_register Turns a set of findings into the register.This is the record AuditBuilder stores, with its scoring ported line for line and checked against the scores of its sample audit. The connector keeps nothing. AuditBuilder is where findings are stored, with their history, the client's decisions and the checks that confirm a fix.
A scored register tells you what to fix first and why. Getting each fix owned, shipped and verified against the check written for it is the work. That is what an engagement is for.