Run your URL through Google's Rich Results Test at search.google.com/test/rich-results. Paste the URL or raw HTML, and Google shows you which structured data it found, whether it's valid, and if it qualifies for rich snippets like FAQ panels, product cards, or review stars. This is the definitive check because it uses Google's actual parser. For a broader validation that covers non-Google schema types, use the Schema Markup Validator at validator.schema.org, which checks compliance against the full schema.org vocabulary. To inspect markup directly, view your page source and search for "application/ld+json" to find JSON-LD blocks, or look for itemscope and itemprop attributes if you're using microdata. JSON-LD is easier to audit because it sits in a script tag rather than being woven into HTML elements. Browser extensions like the official Schema Markup Validator or SEO Pro extension surface schema on any page in one click, helpful when auditing competitors or checking live pages quickly. Common issues we catch at Ottawa SEO: missing required properties (like "offers" in Product schema without a price), mismatched types (putting Organization schema on a product page), or duplicate markup from conflicting plugins. Google Search Console's Enhancements report flags schema errors that affect your actual indexed pages, not just test scenarios, so check that monthly for AggregateRating, FAQ, or HowTo warnings. For large sites, crawl with Screaming Frog and enable the Structured Data extraction under Configuration > Spider > Extraction. Export the results to see which pages have schema, which types are deployed, and where coverage is thin. On a 200-page site, if only 15 pages have Product schema when 180 are product pages, you've found a templating gap. We typically validate one template per page type in Rich Results Test, then spot-check 5–10 live URLs to confirm deployment, especially after CMS updates that sometimes strip JSON-LD blocks.