Schema Markup Spec

Exactly what markup each template must emit, precise enough that two engineers would build the same thing.

Where This Sits

Components in the finished document

Measured directly, not asserted

Pieces that carry my judgment

This is a Specification and build deliverable, which means it specifies a change precisely enough to build. 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 6 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.

Per-template property table: Required and recommended properties for each declared type, template by template.

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.
Sample JSON-LD block: The literal markup to emit for one representative page of each type.
Placement diagram: Where in the template each element belongs, and what it must not sit inside.
Validation criteria: What must pass before the implementation is considered correct.
Edge case rules: What to do at the boundaries, where the general rule stops working.