5
Components in the finished document
Structured Data Strategy
Which entities the site will describe, how markup will be produced and governed, and who owns it afterwards.
Where This Sits
1
Measured directly, not asserted
3
Pieces that carry my judgment
This is a Direction deliverable, which means it turns findings into a sequence. It is the unit of scope: it can be commissioned on its own, priced on its own, and accepted on its own, whether or not anything else is bought alongside it.
It is not a package and not a retainer. It is one document with 5 components, and the list below is the whole of it.
What Is Inside It
Every component is listed with the one sentence that says what it is. They are grouped by how each one is produced, because the difference between a number a tool gave me and a number I decided matters more than most reports admit.
Measured
Pulled straight from tools and logs. No interpretation, so you can re-run any of it yourself and get the same numbers.
- Owner assignment table
- The named person accountable for each item, on the client's side and mine.
Computed
Built by combining the measurements above. Every figure states the inputs it came from.
- Schema coverage matrix
- Which schema types appear on which templates, and which are missing.
Judged
My reading of the evidence. This is the part you are actually paying for, and the part you are entitled to argue with.
- Entity map, target state
- The entities the site should describe and how they should connect, as a specification to build against.
- Sequenced initiative list
- Every initiative in execution order, each with its dependency and its reason for sitting where it sits.
- Assumptions statement
- Every assumption the analysis rests on, named so a reader can challenge it.