QueryRev Terms
Typed Decision
A typed decision is QueryRev’s term for a recommendation stored as a structured object rather than as text: one of a fixed set of decision types, such as Update, Merge or Protect, with the same fields every time, including its evidence, a modeled value range, effort, risk and priority. Language explains the decision; the object is the decision.
- QueryRev’s own term
By QueryRev ResearchPublished Updated6 min read
Why it matters.
Most SEO advice arrives as a sentence in a document. A sentence cannot be sorted, filtered, assigned, approved or checked against a policy, and it carries its evidence only as far as its author remembered to write it down. A typed decision is the same advice as an object with the same fields every time, so all of those things can be done with it.
The word “typed” has an ordinary meaning in data work. JSON Schema describes itself as a declarative language for defining structure and constraints for JSON data, with which the structure, constraints and data types of data are described, and a validator checks that data conforms[1]. A typed decision is typed in the same plain sense: a fixed shape that every instance has to fit. QueryRev is not described here as built on that standard, which is named only to explain the idea.
Evidence has to be traceable. The W3C’s PROV documents describe provenance as information about the entities, activities and people involved in producing a piece of data, which can be used to form assessments about its quality, reliability or trustworthiness[2]. The evidence of a decision works the same way: each line leads back to the rows it came from, so a person can judge it before approving.
The fixed set is nine types: Update, Expand, Create, Merge, Protect, Internal Link, Technical, Conversion and Earn Citation, in five named families. A fixed set lets a queue be filtered by kind and lets a policy say which kinds need whose approval. Each decision carries search and business evidence, technical state and history; a value range with its kind, never a single guess; effort, risk and time to impact; and its place in one prioritised queue. Confidence is shown as product confidence only once it has been calibrated against verified outcomes.
A fixed set of states is also how QueryRev’s own study keeps its data. In the study, 1,339 of the 6,294 sites whose robots.txt could be read, 21.3%, name at least one AI crawler[3]. For each crawler the study records the rule as one of a few fixed states, such as blocked or partly blocked, and not as a sentence, so that the counts add up and can be read again next month.
How it is measured.
By completeness. Count the share of decisions with every field filled: type, target, evidence, value range with its kind, effort, risk and priority. A decision with no evidence is incomplete, whatever its text says.
By traceability. Take a sample of decisions and follow each line of evidence back to its row. Every claim should lead to a figure, and every figure to its source. A line that cannot be followed back is a sentence, not evidence.
By outcome, once the change is made. Set the verified result beside the value range the decision gave, by type. Whether results land inside their ranges is the check on the estimates, and it is how confidence can be calibrated over time.
Measured by
- Fields filled
- Evidence lines traced to rows
- Result against the value range
A worked example.
Illustrative: an invented site, to show the method.
A software company has two setup guides that compete for one query and trade places between positions 5 and 11. An SEO writes in a ticket: “merge the two setup guides, should help.” That sentence cannot be ranked against anything else.
Stored as a typed decision, the same advice has a type, Merge, and a target. Its evidence is a set of known figures that lead to the rows they come from. Its value is a modeled range of $1.1k to $1.7k a month. It has an effort, a risk and a place in the queue. A person can approve, edit, assign, snooze or reject it, and nothing changes on the site while it waits.
What to do, step by step.
Write every recommendation with the same fields: type, target, evidence, value range, effort, risk and owner.
Choose the type from a short fixed list, so that the queue can be filtered by kind and a policy can say who approves which kind.
Attach evidence as rows, not adjectives. Each claim should lead back to the data it came from.
Give the value as a range with its kind, and put effort and risk beside it.
Rank decisions in one queue by priority, which weighs value, evidence, effort and risk, and not by the traffic a page gets.
After the change, set the verified result beside the range the decision gave, and keep that record by type.
Mistakes to avoid.
Writing the recommendation as a paragraph. A paragraph cannot be sorted against others, assigned, approved by rule or checked later. Keep the explanation in words, and the decision in fields.
Letting types multiply. A new type for every idea makes the queue impossible to filter and a policy impossible to write. A short fixed set is what makes the object useful.
Giving a single figure as the value. A modeled value is a range, and its midpoint alone is never the answer. The range is what a verified result is later set beside.
Sorting by traffic. A page with 600 visits a month can outrank one with 10,000 when its visits are worth far more. Rank by priority, not by the visits a page gets.
Showing confidence nobody checked. A confidence a model states about itself is not product confidence. Show it as such only once it has been calibrated against verified outcomes.
How QueryRev treats it.
“Typed decision” is QueryRev’s own name. Every recommendation in Decisions is one: a type from a fixed set of nine, in five named families, with evidence you can open, a value range with its kind, effort, risk, time to impact and a place in one prioritised queue. Language explains a decision; it is not the decision. Approving one does not change your website: it sends the proposed change to governed execution, where your policy decides whether it may be applied. Afterwards the verified outcome is set beside the range the decision gave, and the change is written to the Change Ledger. See the guide to SEO ROI.
Questions people ask.
What is the difference between a typed decision and a recommendation in a report?
A recommendation in a report is a sentence. A typed decision is a structured object with a type, evidence, a value range, effort, risk, an owner and a lifecycle, so it can be prioritised against every other decision, approved, executed under policy and verified afterwards.
What types of decision are there?
Nine: Update, Expand, Create, Merge, Protect, Internal Link, Technical, Conversion and Earn Citation, in five named families. The set is fixed so that a queue can be filtered by kind and a policy can say which kinds need whose approval.
Does an AI model make the decisions?
No single model does. Numbers are computed from your data, bounded questions are answered by rules and statistics, and a model explains the evidence and drafts the proposal. A person approves every decision that needs approval.
Sources and citation.
Primary sources only: the search engines, the AI vendors, standards bodies and QueryRev’s own research. Each is cited in the text by its number.
What is JSON Schema?JSON Schema ·
PROV-Overview: An Overview of the PROV Family of DocumentsW3C ·
State of AI crawler access, October 2026QueryRev Research ·
Cite this definition
A suggested citation. Its link goes to the definition, whose anchor does not change.
QueryRev Research. “Typed Decision.” QueryRev AI glossary, 24 October 2026. https://queryrev.com/glossary/typed-decision#definition
Related terms