SEO Runbook

Schema Markup Brief

Produce a structured-data implementation brief from visible content, eligible schema types, property sources, and validation requirements.

Try this Runbook

Goal

Produce a developer-ready structured-data brief that represents the visible page accurately and avoids unsupported properties or rich-result promises.

Success Criteria

  • Recommended types match the page’s primary visible content and entity.
  • Every property maps to an identified source of truth.
  • Required, recommended, conditional, and omitted properties are distinguished.
  • Validation, ownership, monitoring, and rollout checks are explicit.

Inputs

  • Page URL, template, or rendered content
  • Page purpose and primary entity
  • Current structured data, if any
  • Product, organization, author, review, event, or FAQ source data
  • CMS and rendering constraints
  • Search-engine guidance and validation evidence

Constraints

  • Do not mark up content that is hidden, misleading, user-inaccessible, or absent.
  • Do not invent ratings, prices, availability, authorship, dates, or entity relationships.
  • Do not promise rich-result eligibility or ranking improvement.
  • Prefer the smallest accurate graph over unnecessary schema types.

Instructions

  1. Identify the page’s primary entity, visible claims, and eligible schema candidates.
  2. Review existing markup for conflicts, duplication, stale values, and ownership.
  3. Select the minimum useful types and define their relationships.
  4. Map every property to a visible field or authoritative data source.
  5. Provide an illustrative JSON-LD shape using clearly marked example values for unverified data.
  6. Define rendering, validation, sampling, monitoring, and rollback checks.

Output

  • Page and entity summary
  • Recommended types with rationale
  • Property-to-source mapping
  • Illustrative JSON-LD with example values
  • Implementation notes
  • Validation and monitoring checklist
  • Risks and unresolved data gaps

Quality Check

Verify that each property is supported by visible or authoritative data, no conflicting entity definitions remain, and the brief does not imply guaranteed search treatment.

Stop Rules

Stop when the page content or authoritative data source cannot be inspected. Do not deploy markup or fabricate values; route legal, policy, and eligibility uncertainty to the responsible specialist.

From procedure to operation

Put this Runbook into a controlled workflow.

Learn how an SOP becomes a Runbook, choosemeaningful review points, thencompare plans and capacity.

Ready to handoff busywork?

Start my free trial