Owner-to-specialist evidence brief
Build a schema markup evidence brief
Define the search feature and pages in scope, then record the evidence needed to approve the work, check the live result and decide whether maintenance is worthwhile.
How to use it
Use the five gates as a hand-off
This isn't a do-it-yourself technical audit or a readiness score. Agree the purpose and business outcome first, then ask the person doing the work to supply the page, validation and reporting evidence. An unchecked point is a question to resolve rather than proof that the website has failed.
Supported purpose
Has the proposal named a current search feature and a useful reason for targeting it?
Page and data match
Does the proposed markup describe the visible page without invented or stale values?
Valid delivery
Can Google reach and process valid markup on the preferred live page?
Live appearance
Has the intended search appearance been observed after Google processed the change?
Value and maintenance
Will the result be measured and kept accurate after launch?
Project record
Keep the target and evidence together
Use these notes to keep the business decision beside the technical evidence. Your entries stay in this browser and are included in the CSV export.
Reading the brief
A complete brief doesn't guarantee a rich result
The completed checklist shows that the proposal has a supported purpose, matches the page, can be processed and has a plan for observing and measuring the result. Google still decides whether a rich appearance is useful for each search, so judge the work by the evidence at every gate rather than by valid code alone.