Check Your JSON-LD Schema Before You Publish
Paste JSON-LD code or enter a page URL to inspect the structured data on the page, catch JSON syntax problems, verify @context and @type, and review every detected schema block.
Why Schema Audits Matter
JSON-LD tells search engines what your content means. A broken comma can stop a JSON-LD block from being decoded, while a missing @type is reported as a structural warning.
Machine-Readable Meaning
Structured data describes your page — articles, products, FAQs, events — in a format machines can parse. This audit verifies each JSON-LD block actually decodes as JSON and carries the basic Schema.org fields (@context and @type) that give it meaning.
Catch Syntax Mistakes Early
A trailing comma, a stray quote, or a missing bracket invalidates the whole block. The audit flags invalid JSON immediately, with the parser's own error message.
See What the Page Exposes
URL mode fetches the page and lists every JSON-LD script block found in the HTML — useful after plugins or themes inject markup you didn't write.
One Workflow, Two Validators
Structured data provides machine-readable information that search engines and other systems can use alongside the page's visible content. A clean syntax + structure audit is the first step; Google's Rich Results Test and the Schema.org Validator then perform the deeper, official validation.
Schema Audit Tool
Enter a page URL or paste JSON-LD code to see the audit report here.
What This Schema Audit Checks
Every card below maps to a real check performed by the tool — nothing more, nothing less.
JSON Syntax
Checks whether the submitted JSON-LD can be decoded as valid JSON, and reports the parser message when it cannot.
Schema Context
Checks whether @context is present and refers to Schema.org.
Schema Type
Checks whether each schema object contains an @type property.
Schema Properties
Shows the properties and values found inside each schema object in a clean table.
Multiple Schema Blocks
Reports each detected JSON-LD block separately, with a total block count.
URL or Code Inspection
Audit a live page by URL, or submit JSON-LD code directly by paste or file upload.
How Structured Data Can Be Used by Search Engines and AI Systems
Structured data provides machine-readable information about a page. Search engines and other systems can use that information alongside the page's visible content when interpreting what the page describes.
Honest by Design
This tool performs a fast first-level audit. Here is exactly what it does and does not do:
- ✓ Reports JSON syntax and basic
@context/@typestructure — no hidden scoring. - ✓ Does not modify or "fix" your schema — it shows you what needs attention.
- ✓ Does not guarantee rich results, rankings, or AI visibility.
- ✓ Links to Google Rich Results Test and Schema.org Validator for deeper validation.
How to Audit JSON-LD Schema
Four simple steps from raw markup to deeper validation.
Choose a Mode
Select Page URL to inspect a live page, or JSON-LD Code to check a snippet directly.
Enter Your Data
Type the URL, or paste / upload your code. The Paste buttons pull straight from your clipboard.
Review the Report
See detected schema blocks, their properties and values, syntax errors, and structural warnings.
Validate Officially
Use the built-in links to run your URL or code through Google Rich Results Test and the Schema.org Validator.
{ }Schema Audit Summary
✔ PASS- ✓JSON decoded successfully
- ✓@context refers to schema.org
- ✓@type present on every schema object
Support for Graph & Nested Structures
Modern WordPress SEO plugins frequently bundle multi-tiered schemas inside nested nodes or an @graph array. This tool recursively processes elements, separating nested components so you can inspect individual properties cleanly.
Common Audit Results & What They Mean
If the audit reports a problem, the card below explains the most likely reason and how you can fix it.
Invalid JSON Syntax
SYNTAX ERRORThe block could not be decoded as JSON.
Solution: Look for missing commas, trailing commas, unescaped quotes, or mismatched brackets. Correct the JSON and run the audit again.
Missing or Non-Standard @context
WARNINGThe schema has no @context, or it doesn't point to Schema.org.
Solution: Use "@context": "https://schema.org" in the schema object.
Missing @type
WARNINGThe schema object does not declare what kind of thing it describes.
Solution: Add the appropriate @type for the content you're describing — for example Article for a blog post, Product for a product page, or FAQPage for a FAQ block.
No JSON-LD Found
NOT FOUNDNo JSON-LD schema content was found in the submitted input.
Solution: Confirm the page actually outputs <script type="application/ld+json">, or create markup with a Schema Generator first.
Could Not Fetch URL
FETCH ERRORThe server could not retrieve the page — it may be down or blocking requests.
Solution: Check the URL is public and online, or switch to JSON-LD Code mode and paste the markup directly.
When to Use a Schema Audit — and What to Do Next
Use the audit when you want to check JSON-LD before or after it reaches a live page. The result tells you what was found and where to go next.
@context, @type, and schema properties in your code.@context points to Schema.org.Schema Audit FAQs
Answers based strictly on what this tool does and how it works.
What can this Schema Audit Tool check?
It checks JSON syntax validity, verifies @context refers to Schema.org, confirms @type exists, lists the properties and values of each schema object, and counts the JSON-LD blocks it detects.
Can I audit a page by URL?
Yes. The tool sends the URL to the server, fetches the page, and extracts every <script type="application/ld+json"> block from the returned HTML for analysis.
Can I validate JSON-LD code without a URL?
Yes. Switch to JSON-LD Code mode and paste your snippet or upload a .json / .txt / .html file. It is audited directly, no live page needed.
What does a syntax error mean?
It means the submitted text is not valid JSON — commonly a missing or extra comma, an incorrect quotation mark, or an unbalanced bracket. The report includes the parser's message as a clue.
What does a structural warning mean?
It means a basic Schema.org field is missing or non-standard: either @context doesn't point to Schema.org, or the schema object has no @type.
Does a successful audit mean my schema is eligible for rich results?
No. A passing audit only means the JSON decodes and the basic structure looks right. Rich-result eligibility is decided by Google's own systems, which is why the official test links are provided.
Why are Google Rich Results Test and Schema.org Validator links provided?
They perform deeper, official validation. This tool is a fast first check; the official tools are the right next step for full analysis.
Does the URL audit check the whole webpage?
No. It specifically looks for JSON-LD script blocks inside the fetched HTML and analyzes only those — not the rest of the page.
Is my URL or JSON-LD sent to the server?
Yes. The URL or JSON-LD code is sent to the WordPress AJAX endpoint so the audit can be processed. In URL mode, the page is fetched by the server before the JSON-LD blocks are analyzed.