Schema Markup Validator
Last updated:
Choose a live-URL scan that inventories server-returned JSON-LD and Microdata, or paste JSON-LD for a private browser-only check. Use this diagnostic before Schema.org Validator and Google's Rich Results Test.
Check a live URL or paste JSON-LD directly:
Enter a domain or full URL. Domains use HTTPS by default. Scans structured data in the HTML returned by the server; it does not render JavaScript.
Found issues? That’s exactly what our SEO audit fixes.
Our SEO Audit + Essentials package ($555, one-time) finds and fixes exactly these kinds of problems, with a prioritized plan in plain English.
Looks clean here. How is the rest of your SEO?
One passing check doesn’t make a ranking strategy. We audit the full picture: content, technical SEO, internal links, and search intent.
Want us to act on this result? Fix these findings →
Prefer the partnership route? Refer clients to us, earn 10% →
How the Schema Markup Validator Works
This tool extracts JSON-LD from pasted input or server-returned HTML, and inventories Microdata types on URL scans. Here's the process:
- Choose an input, fetch a public URL or paste JSON-LD for browser-only parsing without a server request.
- JSON-LD extraction, it finds all
<script type="application/ld+json">blocks, parses the JSON, and handles@grapharrays. - Type detection, the tool lists the
@typevalues it can parse, including types inside@graph. - Common property checks, built-in rules flag selected gaps on frequently used types. These checks are not a complete implementation of the Schema.org vocabulary or every Google search feature.
- Microdata scan, the tool also detects schema.org Microdata markup embedded in HTML attributes.
Why Schema Markup Matters for SEO and GEO
Structured data can make visible facts easier to interpret consistently. It is one layer of a broader search and entity strategy:
- Search-feature eligibility, supported types with valid properties can make a page eligible for breadcrumbs, products, events, articles, and other enhanced results. Display is never guaranteed.
- Entity clarity, stable identifiers and consistent Organization, Person, Product, or LocalBusiness facts can reduce ambiguity when they match the page and external profiles.
- Maintenance, structured fields make stale prices, ratings, authors, and dates easier to audit systematically.
- AI-search foundation, machine-readable facts may help systems interpret a source, but markup alone does not establish expertise or earn citations. Measure real prompts and cited URLs separately.
Schema works alongside your SEO and Open Graph tags ; together, they provide explicit metadata for different consumers. Need to generate a starting point? Use the Schema Markup Generator, then adapt it to the visible page and validate it. For a broader technical audit, the AI Search Readiness Checker reviews schema alongside crawler controls, headings, and standard discovery signals.
Want to go deeper? Our blog covers the full structured data topic: what schema markup is and why it matters for SEO explains the fundamentals and which types your site needs. Schema markup and AI citations discusses entity clarity and the limits of evidence linking markup to citations in AI search. And our guide to testing and validating schema markup walks through the complete validation workflow from pre-publish checks to quarterly audits.
Worked example: an Organization missing its URL
Use “Try a worked Organization example” above. The example has a context, type and business name, but no URL. The selected-property check flags that gap as a recommendation, not invalid JSON. Add the real canonical business URL when applicable, then validate again. The valid graph example demonstrates linked nodes and multiple types; the invalid example separates a malformed @type from a Google breadcrumb requirement.
- Make the JSON parse. Fix syntax before interpreting missing properties.
- Match the page. Use the actual business identity and visible facts. Do not invent ratings, offers or qualifications to satisfy a checker.
- Validate the intended feature. Use Schema.org Validator for vocabulary, and Google’s Rich Results Test for supported Google features.
- Publish and rescan the URL. A successful pasted example does not establish what your live template emits.
For implementation and launch checks, follow our schema testing workflow. A passing test does not guarantee a search enhancement or AI citation.
Google Retired the Structured Data Testing Tool. Here's What to Use Now.
For years, the Structured Data Testing Tool was the way to check schema markup: paste a URL, see every type on the page, fix what's flagged. Google announced its deprecation in 2020, and in 2021 handed it over to Schema.org, where it survives as validator.schema.org without the Google-specific checks site owners relied on.
The replacements each cover only part of what the original did:
| Validator | What it checks | The catch |
|---|---|---|
| Google Rich Results Test | Schema types eligible for Google rich results | Tests Google-supported search features; it is not a full Schema.org vocabulary validator. |
| validator.schema.org | Syntax and vocabulary of all Schema.org types | General vocabulary validation; use Google documentation for Google-specific search-feature requirements. |
| Search Console | Rich result reports for your own verified site | Only works on sites you own, and only after Google has crawled them. |
| This tool | Live-page JSON-LD inventory, parse errors, Microdata types, and selected common-property checks | Fast diagnostic only; not authoritative for the full Schema.org vocabulary or Google eligibility. |
In short: use the Rich Results Test to confirm a specific rich result, and use a general schema checker like this one for a quick live-page inventory. No validator can predict an AI citation. For the complete validation workflow, read our guide to testing schema markup.
Common Schema Types, Chosen by Page
There is no universal checklist. Choose the narrowest types that accurately describe the visible page:
- Organization, your business name, logo, URL, social profiles. The foundation of your online identity in search.
- WebSite, site name, URL, and publisher identity.
- BreadcrumbList, a real navigation path (Home → Category → Page) that can support breadcrumb display.
- Article / BlogPosting, for editorial content with visible author and accurate publication dates.
- FAQPage, only for visible FAQ content that complies with current search policies. Google retired FAQ rich results in May 2026; FAQPage remains a Schema.org type.
- WebApplication, for tool pages (like this one). Describes the app, its category, pricing, and provider.
- Product, for product pages. Google Product snippets require name and at least one of offers, review, or aggregateRating; merchant listings have additional requirements.
- Service, for service pages. Describes what you offer, the provider, and the service area.
Schema Type Reference: Properties to Review
Different consumers and search features have different requirements. Use this as a starting reference, then confirm the current requirements for the specific feature in Google's documentation and validate the general vocabulary at Schema.org.
| Schema type | Use it on | Common properties to review |
|---|---|---|
| Organization | Site identity, commonly anchored from the home page | @id, name, url, logo, and accurate sameAs profiles. |
| LocalBusiness | Local business or store pages | name, real address, telephone, openingHours, and geo when those facts are visible and accurate. |
| Article / BlogPosting | Blog posts and news articles | headline, image, datePublished, author. Add dateModified and publisher for full eligibility. |
| Product + Offer | Product and e-commerce pages | name, image, plus offers with price and priceCurrency. Add aggregateRating or review for star ratings. |
| FAQPage | Pages with a real FAQ section | mainEntity as a list of Question items, each with a name and an acceptedAnswer (Answer with text). |
| BreadcrumbList | Any page with a navigation path | itemListElement as ordered ListItem entries, each with position, name, and item (the URL). |
| WebSite | Home page (site-wide identity) | @id, name, url, and a consistent publisher reference. |
Rules reviewed on 7 September 2026 against Google’s Article guidance, Product snippet requirements, breadcrumb requirements, and the FAQ retirement announcement. Article properties are recommendations; Product snippets accept offers, review, or aggregateRating; the final breadcrumb can omit item.
Requirements can change. Valid markup can make eligible content understandable; it does not guarantee a rich result, ranking, Knowledge Graph panel, voice answer, or AI citation.
Next steps
Schema Markup Validator related tools and articles
Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.
Schema Markup Validator: FAQ
What do JSON-LD blocks, schema items, and total types mean?
What do the issue messages validate?
How should I fix a JSON-LD parse error?
How are @graph, nested objects, and Microdata handled?
Why can the result say no schema when I can see markup elsewhere?
Which validation tool should I use next?
What are the fetch and display limitations?
Are the checked URL and page markup stored?
Free 48-Hour Website Audit
Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.
Need Help With Your Structured Data?
We implement accurate structured data that matches visible content and test it through the appropriate official validation workflow.