Overview
Choose and implement the structured data that actually helps engines and AI understand and trust a page.
Business problem
Schema is added by plugin defaults or omitted, so pages miss the machine-readable signals that aid understanding.
Decision supported
Which schema types to add to a given page and why.
Inputs & outputs
Inputs
- Page type and purpose
- Entities on the page
- Current markup
- Validation results
Outputs
- Schema plan per template
- Validated markup
Step-by-step process
-
1
Classify the page
Identify what the page is: article, product, FAQ, organisation, person.
-
2
Select types
Choose the schema that genuinely describes it, not everything possible.
-
3
Describe entities
Mark up the real entities and their relationships.
-
4
Validate
Test the markup and keep it error-free.
Maturity model
-
L1
None
No structured data.
-
L2
Default
Plugin-default schema only.
-
L3
Selected
Schema chosen to fit each template.
-
L4
Entity-rich
Entities and relationships fully described.
KPIs
- Schema coverage by template
- Markup error rate
- Rich-result eligibility
Common mistakes
- Marking up content that is not on the page
- Ignoring validation errors
- Over-stuffing irrelevant types
SearchScore insight
Recommended next steps
Where this fits - and what's next
The SearchScore path from a problem you feel to visibility you can measure.