List the templates, markup types and code owners
Find repeated problems at their generating source.
Use this for: Sites auditing existing structured data or planning a first implementation.
Choose representative pages from your actual templates, such as the homepage, service page, article and product page. Inspect their source or use a crawler configured to extract structured data. Look for JSON-LD script blocks, Microdata or RDFa, and check the rendered page if scripts add markup.
For each template, identify the types found and the plugin, theme, tag manager or custom component that produces them. Include a normal example and a relevant unusual state. A missing type is an opportunity to evaluate, not automatically an SEO error.
Hypothetical example: An article template contains one Article block from the SEO plugin and another from the theme. The inventory identifies both owners before either is changed.
- Choose sample URLs across the actual page templates.
- Identify their markup formats, types and generating components.
- Include a relevant missing-field or recently changed example.
More help and optional notes
If it fails: Expand the sample and identify the component responsible for the missing coverage.
Retest: Update the inventory after theme, plugin or template changes.
Not applicable: No URLs or implementation in this task’s scope.
Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

