Appearance
Markup lifecycle
ReferenceStructured data is not a one time task. This workflow covers the full lifecycle from the first decision through ongoing monitoring.
Lifecycle diagram
flowchart TD A[Identify the primary entity] --> B[Select the most specific type] B --> C[Map page content to properties] C --> D[Choose a syntax] D --> E[Write the markup] E --> F[Validate] F -->|errors| E F -->|clean| G[Deploy to production] G --> H[Confirm in production] H --> I[Monitor for errors over time] I -->|template or content change| C I -->|stable| I
Stages
- Identify the entity. Decide what the page is fundamentally about.
- Select the type. Use the type hierarchy to find the most specific accurate type.
- Map content to properties. List every visible fact you want machines to read, then map each to a property.
- Choose a syntax. See the choosing a format workflow.
- Write the markup. Follow the relevant SOP.
- Validate. Resolve all errors.
- Deploy and confirm. Verify the production page emits the markup that you validated.
- Monitor. Templates and content edits can change output. Re validate after changes.
Done when
- Production pages emit validated markup.
- A monitoring or re validation step is in place for future content changes.