Structured data QA works when you check the live page, confirm that every declared fact matches visible content, and test eligibility for the search features you want. You can check JSON-LD and schema markup on a web page by extracting every markup format, parsing each entity, validating its properties, and testing the rendered URL for Google rich result requirements.
Schema markup gives search engines clear, machine-readable details about your product, article, business, or service. Valid code improves technical SEO clarity and rich result eligibility, while inaccurate markup sends false signals that need fixing. You can also use schema data to reinforce entity details used by AI search systems.
Use a Layered Live-Page Validation Workflow
Validate schema in layers because valid JSON-LD alone doesn’t confirm valid Schema.org markup or eligibility for Google rich results. Check the rendered page, raw HTML, object structure, property rules, and feature-specific requirements before you close out the QA task.
Inspect the Rendered Page and Raw HTML
Start with the canonical, indexable live URL. Review the page source and rendered DOM because JavaScript, tag managers, and CMS plugins can inject JSON-LD after the initial HTML loads.
Check that @context uses https://schema.org and that each @type fits the page’s purpose. Also remove tracking parameters such as utm_, gclid, and fbclid before comparing canonical URLs, @id values, and schema URLs.
A live-page audit is handy here because it checks the markup actually present in the browser you’re viewing, including staging pages and pages behind a login wall. Check Page SEO includes schema markup validity alongside canonical, robots, links, images, and indexability checks.
Extract JSON-LD, Microdata, and RDFa
Extract every <script type="application/ld+json"> block, then inspect HTML attributes for Microdata and RDFa. JSON-LD is easier to maintain on most modern CMS platforms, but older templates can still contain itemtype, itemprop, typeof, or property attributes.
Record every schema type you find. Duplicate markup is a common headache on ecommerce sites where a theme emits Product schema and an SEO plugin adds a second Product object with conflicting price, availability, or review data.
Use a structured data publishing checklist to confirm that factual fields, nested entities, image URLs, and canonical-page placement all match the live page.
Parse Every Object, Including @graph Nodes
Parse each JSON-LD block as JSON before judging the schema. A missing comma, quote, bracket, or escaped character can create syntax errors that stop crawlers from reading the object.
Pay close attention to @graph. A graph can hold an Organization, WebSite, WebPage, BreadcrumbList, Article, and Person entity in one block. Review every node independently, confirm unique @id values, and make sure references point to the right entity.
A schema checker should show validation results at the object level. That makes it easier to find missing properties tucked inside nested Offer, Review, ListItem, Question, and Answer objects.
Separate Syntax Checks From Schema and Google Feature Checks
Treat validation as three separate tests:
- Syntax validation confirms that JSON-LD parses.
- Schema validation checks that types, properties, and value formats align with Schema.org.
- Google feature validation checks required fields for supported rich results.
Passing the first two tests doesn’t guarantee rich snippets. Google Search chooses search features based on page quality, query context, and eligibility rules. Use Google-focused rich result validation guidance alongside your own page QA, then test again after publishing.
Interpret Findings and Fix Markup That Matters
Prioritize schema that describes the page’s main visible purpose and supports a relevant Google Search feature. Fix misleading entities first, then fill required properties and monitor changes through Google Search Console.
The most valuable checks focus on page-type alignment, factual values, nested objects, and live-page consistency. Your technical SEO audit should also verify that the page is indexable, canonicalized correctly, and backed by content that answers the search intent.
Match Schema Types to the Visible Page Purpose
Choose schema types based on what users can see and use on the page. A product detail page fits Product with Offer data. A guide fits Article or BlogPosting. A service page can use Service, while a software landing page can use WebApplication when the visible content supports it.
Don’t add FAQPage schema to a page with hidden, duplicated, or unrelated questions. And don’t mark every page as an Article. Search engines assess content and markup together, so type inflation adds risk without adding visibility.
Check headings and body copy during this review. If your markup claims a complete guide or product comparison, the visible page needs enough detail to back up that claim. Use a content-gap review when schema exposes missing sections or weak topical coverage.
Fix Product, Offer, and Review Data Carefully
Product schema needs a clear Product name and should reflect the item offered on the page. When you use Offer markup, validate price, priceCurrency, availability, and the landing-page URL against the visible purchase information.
Review markup requires the review content to be available to users. Keep aggregateRating, ratingValue, and reviewCount current, and make sure they represent the same product or business entity named in the schema.
Star ratings and product snippets are search features, not guaranteed display treatments. Accurate data gives Google a reliable basis for eligibility, while false prices, stale availability, and copied reviews create a markup quality problem.
Validate Editorial, FAQ, and Navigation Markup
For Article or BlogPosting schema, check the headline, author, publication date, modified date, image, and main entity URL. Your Person entity should match the visible byline and author page details.
FAQPage markup requires a Question and Answer for each visible FAQ item. Keep answers complete, and remove questions that no longer appear after a template update.
BreadcrumbList markup needs ordered ListItem nodes with accurate names and URLs. Confirm that the breadcrumb trail reflects your real site hierarchy, since breadcrumb errors often pop up after category changes or canonical URL migrations.
Verify Business Entities and Monitor the Outcome
Organization and LocalBusiness markup should use your exact business name, website URL, logo, contact details, sameAs profiles, and geographic details. For a LocalBusiness, validate the address, phone number, opening hours, geo, and service information against your Google Business Profile and visible contact page.
Run your schema markup check after template releases, CMS migrations, pricing changes, product-feed updates, and major content edits. To be fair, markup failures often arrive through automated deployments rather than manual SEO edits.
After fixes go live, inspect the URL in Google Search Console and track impressions, clicks, click-through rate, average position, and relevant search features over comparable periods. For repeatable checks across live pages, install the Check Page SEO Chrome extension and review schema validity alongside page-level technical signals.
