Quick answer
Use a supported schema type only when it accurately describes the visible page content. Validate the markup, check feature-specific eligibility and confirm that the information is current, accessible and consistent with what users can see.
Treat structured data as a way to clarify meaning and eligibility, not as a substitute for useful content, crawlable pages or sound site architecture.
What I would check first
Inventory existing JSON-LD, microdata or RDFa and identify which templates generate it. Look for duplicate markup, stale fields, missing required properties and values that do not match the page content.
Confirm that the relevant page is indexable and not blocked by robots rules or access controls. Structured data on a page that cannot be discovered or indexed will not solve the underlying visibility problem.
Decision framework
Choose schema based on the page's real purpose and the feature Google currently supports. Avoid adding a type merely because a competitor uses it or because a tool recommends it without understanding the page.
Google's structured-data policies state that valid markup can make a page eligible for a rich result but does not guarantee that the result will appear. Search presentation remains a system decision and can vary by query, device and context.
Implementation steps
Generate markup from the same reliable content source where possible, validate it with the relevant testing tools and compare every important field with the rendered page. Include structured-data QA in template releases and content changes.
Record the schema type, owning template, required fields, testing result and last review. After deployment, monitor Search Console enhancements or manual actions where applicable and fix issues that affect eligibility.
Common mistakes
Do not mark up hidden or misleading content, fabricate reviews or ratings, copy schema from an unrelated page or assume passing a test guarantees a rich result.
Do not add multiple overlapping schema blocks without a clear reason. Duplicate or conflicting descriptions can make the implementation harder to maintain and debug.
Measurement and business implications
Track markup validity, eligible pages, reported enhancement issues and search appearance changes where available. Evaluate clicks and qualified outcomes rather than counting schema properties as success.
Use the SEO migration and Search Console diagnosis guides to ensure structured data is part of a complete technical QA process.