Sponsor

Structured Data Tester

Validate JSON-LD structured data and Schema.org markup. Check required and recommended properties, rich result eligibility, and syntax errors. alternative to Google Rich Results Test.

Reviewed by Olgun Ozoktas

Load Sample

How to Use Structured Data Tester

  1. Paste Your Markup

    Paste your JSON-LD structured data or a full HTML page. In HTML mode, the tool automatically extracts all JSON-LD script blocks.

  2. Review Validation Results

    Each detected schema type is validated against required and recommended properties. Green checkmarks indicate present properties and red marks flag missing fields.

  3. Check Rich Result Eligibility

    See whether your structured data qualifies for Google rich results like article snippets, product cards, FAQ dropdowns, and more.

  4. Fix and Re-validate

    Use the feedback to fix missing properties in your markup, then validate again. Use the JSON-LD Generator or Schema.org Generator to create compliant markup from scratch.

Who Needs a Structured Data Tester?

SEO Professionals

Validate structured data before deploying to production. Catch missing required properties, verify rich result eligibility across 15 schema types, and ensure your markup meets Google's latest requirements without waiting for Search Console errors.

Web Developers

Debug JSON-LD syntax errors and missing properties during development. Paste raw JSON-LD or full HTML pages to validate all embedded schema blocks at once, saving round-trips to external validation services.

Content Teams

Verify that article, recipe, FAQ, and how-to markup includes all the fields needed for rich snippets. Ensure your content investments translate into enhanced search listings that drive higher click-through rates.

E-Commerce Managers

Check Product schema markup for required fields like price, availability, and review ratings. Properly validated product structured data unlocks star ratings, price ranges, and availability badges in Google Shopping and organic results.

Why Use Structured Data Tester?

Validate JSON-LD structured data and Schema.org markup instantly without sending data to external servers. Check required and recommended properties across 15 schema types, verify rich result eligibility, and catch syntax errors before they cost you search visibility.

Structured data tells search engines exactly what your content represents. When implemented correctly with JSON-LD, it unlocks rich results like FAQ dropdowns, recipe cards, product ratings, event listings, and knowledge panel entries. The vocabulary itself is maintained at schema.org by a consortium that includes Google, Microsoft, Yahoo, and Yandex; Google Search Central publishes the per-type requirements that govern actual rich-result eligibility. A single missing property or syntax error can silently disqualify your pages from these enhanced search features, and Google Search Console often takes days to report the problem.

This Structured Data Tester validates your JSON-LD markup instantly against 15 Schema.org types: Article, Product, FAQPage, HowTo, Recipe, Event, LocalBusiness, Organization, Person, BreadcrumbList, Course, JobPosting, SoftwareApplication, VideoObject, and Review. For each type, it checks required properties, flags missing recommended fields, and tells you whether the markup qualifies for Google rich results. You can paste raw JSON-LD or a full HTML page, and the tool extracts and validates every embedded schema block automatically. For a deeper double-check, run the same markup through Google's Rich Results Test (URL-based; tests one page at a time) and schema.org's official validator (syntax compliance only). Bing Webmaster Tools also surfaces structured-data errors in its Markup Validator and SEO Reports panels.

Use this tool alongside the FAQ Schema Generator to create compliant FAQPage markup, the JSON-LD Generator to build any schema type from scratch, the Schema.org Generator for a guided builder, and the SERP Preview to see how your title and description render alongside whatever rich result the structured data unlocks. Generate your markup with those tools, then validate it here before deploying to production.

How it compares

Google Rich Results Test is the most common validation tool, but it requires sending your markup to Google's servers, only tests one URL at a time, and has been intermittently unavailable since its migration from the legacy Structured Data Testing Tool. Schema.org's own validator checks syntax compliance but does not evaluate rich result eligibility or flag missing recommended properties that Google specifically looks for. Merkle's Schema Markup Generator helps create markup but does not validate existing code or check for errors in hand-written JSON-LD.

This Structured Data Tester runs entirely in your browser with no data sent to any server, making it safe for pre-launch pages and confidential content. It validates both required and recommended properties for each of 15 schema types, provides clear rich result eligibility verdicts, and supports pasting full HTML pages to extract and validate multiple JSON-LD blocks at once. Unlike URL-based testers, you can validate markup before it goes live on any public URL.

Structured Data Best Practices

  • Always use JSON-LD format over Microdata or RDFa. Google recommends JSON-LD because it separates structured data from HTML markup, making it easier to maintain and less prone to breaking when page templates change.
  • Include both required and recommended properties for each schema type. Required properties prevent validation errors, but recommended properties like image, dateModified, and author significantly improve your chances of earning rich results.
  • Test your markup after every template change or CMS update. A single missing closing bracket or misplaced comma in JSON-LD will invalidate the entire block, silently removing your page from rich result eligibility.
  • Use the @id property to connect related schema objects on the same page. For example, link your Article author to an Organization or Person entity so search engines understand the relationships between entities on your site.
  • Validate markup on both individual pages and category or listing pages. Many sites add structured data to detail pages but forget breadcrumb, collection, and site-wide Organization markup that strengthens overall entity signals.

Frequently Asked Questions

Does the Structured Data Tester require a signup?

No. This Structured Data Tester is available with no account creation, no login, and no usage restrictions of any kind. You can validate unlimited JSON-LD blocks, test as many schema types as needed, and download full validation reports without any cost. The tool validates fifteen Schema.org types including Article, Product, FAQPage, HowTo, Recipe, Event, LocalBusiness, Organization, Person, BreadcrumbList, Course, JobPosting, SoftwareApplication, VideoObject, and Review. Every feature is fully available including rich result eligibility checking, required and recommended property validation, syntax error detection, formatted JSON output, and downloadable reports. The entire tool runs locally in your browser, so your markup is never transmitted to any external server. This makes it completely safe for validating structured data on pre-launch pages, client websites, and confidential projects where you cannot use public URL-based testing tools like Google Rich Results Test.

What is the difference between JSON-LD, Microdata, and RDFa for structured data?

JSON-LD, Microdata, and RDFa are three different syntaxes for embedding structured data in web pages, and Google officially recommends JSON-LD as the preferred format. JSON-LD uses a standalone script tag in your HTML head section containing a JSON object that describes the page content. It is completely separate from your visible HTML markup, making it easy to add, modify, and maintain without touching your page templates. Microdata embeds structured data directly within HTML elements using itemscope, itemtype, and itemprop attributes, which tightly couples your markup to your structured data and makes template changes risky. RDFa similarly uses HTML attributes like typeof and property to annotate content inline. Because JSON-LD keeps structured data isolated from presentation markup, template redesigns and CMS migrations cannot accidentally break your schema. This tool validates JSON-LD specifically because it is the format that Google, Bing, and other search engines process most reliably for rich results.

What does rich result eligibility mean in structured data validation?

Rich result eligibility indicates whether your JSON-LD markup contains all the required properties that Google needs to display an enhanced search listing for that schema type. Standard search results show only a blue title link, URL, and text snippet. Rich results add visual enhancements like FAQ accordion dropdowns, recipe cards with cooking time and ratings, product listings with price and availability badges, event dates with venue information, and star ratings for reviews. Each rich result type has specific mandatory fields defined by Google. For example, a Product schema needs name, image, and at least one offer with price and priceCurrency to qualify for product rich results. If any required field is missing, Google silently ignores the entire markup block and your page loses its rich result opportunity. This tool checks every detected schema type against Google current requirements and clearly reports whether each block qualifies, showing exactly which fields are missing if it does not.

How often should I re-validate my structured data markup?

You should re-validate your structured data after every template change, CMS update, plugin modification, or content management system migration that could affect your page markup. Even a small change to your page template, like moving a sidebar or updating a header component, can accidentally remove or corrupt the JSON-LD script block if your CMS generates structured data dynamically. Beyond reactive validation, schedule a proactive quarterly audit of your structured data across all page types. Google periodically updates its rich result requirements, adding new required fields or changing eligibility criteria for certain schema types. What was valid markup six months ago may now be missing a newly required property. The quarterly cadence catches these specification changes before they silently disqualify your pages from rich results. For large sites with hundreds of pages using structured data, prioritize validating your highest-traffic page templates first since those drive the most search visibility impact.

What happened to FAQPage schema in 2023, and is it still worth implementing?

In August 2023 Google announced that FAQPage rich results would be limited to authoritative government and health websites, dramatically narrowing the rich-result eligibility for everyone else. As of 2026 the schema itself is still part of the Schema.org vocabulary and Google still parses it (Bing and Yandex still display FAQ rich results in many regions), but the visible-FAQ-accordion treatment in Google search results is now rare for general sites. It is still worth implementing FAQPage markup because the structured data signals topical depth to AI Overviews, Perplexity, ChatGPT search, and Bing Chat, all of which preferentially cite well-structured content. Google has also reversed similar narrowings in the past when authoritative implementation patterns proved out. For high-volume content sites that don't qualify for the rich-result treatment today, HowTo schema (still rich-result eligible in many cases) and Article schema with mainEntity speakable specifications are stronger near-term alternatives.

Why does my markup show 'Detected but no rich results' in Google Search Console?

This status means Google found valid structured data on the page but is not displaying a rich result for it. Several causes are common. First, the schema type may be valid but not currently eligible for rich results in your country or query type — for example, Recipe rich results show up for cooking queries but not for branded searches. Second, the page itself may have quality issues independent of the markup, such as thin content, manual penalty, low E-E-A-T signals, or being de-indexed for unrelated reasons. Third, Google may have confidence-rated the markup as inconsistent with the visible page content (a Product schema with a price the page does not display, an Event schema with a date already past). Fourth, for FAQPage and HowTo specifically, Google narrowed rich-result eligibility in 2023. To diagnose, validate the markup here, then check Search Console for any unrelated quality flags on the same page, then verify that every property in the JSON-LD has a matching value visible in the rendered HTML.

Do AI search engines like ChatGPT and Perplexity use structured data?

Yes, AI search engines and AI Overviews extensively use structured data to identify, classify, and cite content. Pages with well-formed JSON-LD are easier for AI crawlers to parse into clean entity records, which makes them more likely to be cited as sources in answers from ChatGPT search, Google AI Overviews, Perplexity, Claude with web search, and Bing Copilot. The schema types that have the largest AI-citation impact are Article (with author, datePublished, and dateModified), FAQPage (Q&A pairs map directly to AI training and citation patterns), HowTo (step-by-step content is highly extractable), Organization with sameAs cross-references (helps AI engines disambiguate which entity you are), Person for author byline information, and Speakable specifications for voice-friendly content. Implement these schemas and you also pick up the older traditional rich-result benefits where they still apply.

Should every page have BreadcrumbList structured data?

Yes for any page that lives more than one click below the homepage. BreadcrumbList markup tells Google how the page fits into your site hierarchy, and Google replaces the URL in search results with the breadcrumb trail when valid markup is present — a meaningful CTR improvement because users see semantic location instead of a long URL string. The markup is small (a single itemListElement array with position, name, and item URL for each level), and it is one of the few rich-result enhancements that has not been narrowed since launch. The exception is a true single-page-app where every URL is technically a hash-route below the root; in that case the breadcrumb has nowhere meaningful to point and is better omitted than faked.

What's the minimum required JSON-LD for a Product page to qualify for rich results?

Google's current Product structured data requirements are: name, image (at least one URL), and either offers (with price and priceCurrency), aggregateRating (with ratingValue and ratingCount), or review (with reviewRating). To get the merchant-listing experience that includes price, availability, and shipping in the SERP, you also need offers.availability (using a schema.org enum like InStock or OutOfStock), offers.itemCondition, and a brand object with name. For sites running Google Merchant Center campaigns, the markup also has to match the values in your product feed exactly — a price mismatch between JSON-LD and feed will demote both. Use the inputs in this validator to check that every required field is populated and that your offers array has at least one fully-specified offer.

Can I have multiple JSON-LD blocks on the same page?

Yes, and you should when the page genuinely represents multiple schemas. A blog post can simultaneously be an Article (with author and datePublished), a BreadcrumbList (the navigation path), and a FAQPage (an embedded FAQ section), each declared in its own JSON-LD block. Google parses every block independently and applies whichever rich-result treatment fits best. There is no penalty for multiple blocks. The only thing to avoid is duplicating the same entity across blocks (do not declare the same Article twice in different formats) — that creates ambiguity about which version is canonical and can suppress all of them. Keep each block focused on one main entity, link them with @id references where useful, and validate the full set in this tool which auto-detects every block on a pasted HTML page.

Rate This Tool

0/1000

Get Weekly Tools

Suggest a Tool