Schema planning sheet

• Page URL and visible purpose
• Primary entity and type
• Required and recommended properties
• Stable @id
• Connected organization, website, author, breadcrumb, product, or service entities
• Source of each property
• Implementation owner
• Validation result
• Review trigger

the service presents the template as indexable HTML. A production version can add downloadable files without removing the accessible web version.

1. 01

   Name the record

   Identify the website, project, client, owner, and purpose of the schema planning sheet.

2. 02

   Complete facts before conclusions

   Capture visible entities, page purpose, JSON-LD graphs, identifiers, relationships, required properties, and consumer-specific eligibility before writing recommendations or commitments.

3. 03

   Separate required and optional fields

   Preserve the minimum operating record while allowing specialists to add discipline-specific evidence.

4. 04

   Review and approve

   Record who reviewed the document, what was accepted, what remains open, and the effective date.

5. 05

   Maintain the record

   Update the template when the website, scope, evidence, owner, or decision changes.

• Every decision has an owner and date.
• Every material claim is supported by a source, observation, or explicit assumption.
• Every task has scope, acceptance criteria, status, and verification evidence.
• The completed record avoids treating valid syntax as proof of search-feature eligibility or display.