Schema Markup Checker

What is the Schema Markup Checker?

Schema markup is one of those things that many website owners add once and never look at again. That is a problem because broken or incomplete schema does not just sit there quietly. It actively stops your pages from qualifying for rich results in Google search.

The Schema Markup Checker is a free online tool that scans any webpage or raw JSON-LD code and tells you exactly what schema is present, what format it uses, whether each block is valid, and what is missing that could hurt your rich result eligibility. It detects all three major schema formats: JSON-LD, Microdata, and RDFa. It checks every schema block individually, flags missing required properties like @context and @type with plain-English explanations, and when a JSON-LD block has fixable problems, it uses AI to rewrite that block into a clean, Google-ready version in one click.

SEO professionals use this tool during technical audits to catch schema errors before they affect rankings. Developers use it to verify that schema code they have written actually parses correctly. Content managers use it to check pages before publishing. The tool works on any publicly accessible URL and also accepts pasted code directly, so it fits into almost any workflow.

How to Use the Schema Markup Checker (Step by Step)

Step 1: Choose your input mode

The tool opens with two tabs at the top. The first tab is Check by URL. The second is Check by Code. Click the tab that matches how you want to work.

Step 2: Enter a URL or paste your schema code

If you selected Check by URL, paste the full web address of any publicly accessible page into the input field. The tool will fetch that page’s HTML from the server and scan everything automatically, including JSON-LD script blocks, Microdata attributes, and RDFa markup.

If you selected Check by Code, paste your JSON-LD directly into the textarea. This mode is useful when you want to validate schema before adding it to a page, or when a site blocks automated fetching. Note that code mode checks JSON-LD only. Microdata and RDFa require URL mode because those formats live inside HTML attributes and cannot be submitted as standalone text.

Step 3: Click Check Schema

Press the green Check Schema button. A loading indicator will appear while the tool processes your request. For URL mode this includes fetching the page HTML and running all detection logic. For code mode it goes straight to validation.

Step 4: Read the Detection Summary

The result area opens with a status pill at the top showing Valid, Needs Improvement, or Invalid based on what was found. Below that the Detection Summary box shows you the input mode, the URL if one was submitted, the total number of schema blocks found, how many valid JSON-LD blocks were detected, and whether Microdata and RDFa were present.

Step 5: Check the Detected Formats section

This box shows badges for each schema format that was actually found on the page. If JSON-LD, Microdata, or RDFa is present it appears here as a labeled badge. If none are found the tool explains that no schema formats were detected.

Step 6: Browse individual schema blocks

The Schema Blocks section is split into two panels. The left panel lists every schema block found, showing the format, the detected @type, and whether it is a valid JSON block. Click any block in the left panel to open it on the right side.

The right panel shows three detail chips for the selected block, format, type, and whether the JSON is valid. Below that it shows any block-level warnings such as a missing @context, a missing @type, or an @graph structure that needs manual review. The raw schema code appears formatted in a dark code block so you can read it clearly.

Step 7: Copy or fix the selected block

Every selected block has a Copy Schema button that puts the formatted code onto your clipboard. If the block is a JSON-LD block with valid JSON and has fixable problems, a Fix Schema (AI) button appears. Clicking it sends the schema to an AI model that rewrites it with the correct @context, a proper @type, and commonly required properties for rich result eligibility. The fixed version appears below in a second code block with options to copy it or download it as a .json file.

Step 8: Review warnings with explanations

The Warnings section lists every issue found across all blocks. Each warning includes the problem description, a plain-English explanation of why that property is required, what impact missing it has on rich result eligibility, and a specific recommendation for how to fix it.

Step 9: Read the AI Quality Review

If an OpenAI API key is configured on the site, the AI Quality Review box shows a structured HTML assessment of the entire page’s schema. It identifies patterns that could prevent Google from generating rich results and gives actionable suggestions for improvement.

Step 10: Export the report

The Copy Report button copies all warnings in a tab-separated format that pastes cleanly into Excel or Google Sheets. The Export CSV button downloads the same data as a properly formatted CSV file. The Export Excel button downloads a tab-separated file with an .xls extension that opens directly in Microsoft Excel.

Key Features of the Schema Markup Checker

Two input modes for flexible workflows: The URL tab fetches a live page and scans its full HTML for all three schema formats. The Code tab accepts pasted JSON-LD for direct validation. Both modes share the same results interface so switching between them requires no learning curve.

Detection of all three schema formats: The tool checks for JSON-LD inside script tags, Microdata using itemscope and itemtype attributes tied to schema.org URLs, and RDFa using vocab, prefix, typeof, and property attributes that reference schema.org. Detection is scoped specifically to schema.org so common HTML attributes that happen to use similar naming do not trigger false positives.

Individual block inspection: Every JSON-LD script block found on a page gets its own entry in the left panel of the Schema Blocks section. Each entry shows the block name, format, and @type. Clicking one opens the full formatted schema code on the right along with block-specific warnings and detail chips for format, type, and JSON validity.

AI-powered schema fixing for JSON-LD: When a JSON-LD block has valid JSON but is missing required properties, the Fix Schema (AI) button becomes available. Clicking it sends the block to an AI model that returns a corrected version with proper @context, a correct or inferred @type, and commonly recommended properties for that schema type. The fixed output can be copied to the clipboard or downloaded as a .json file.

Warnings with practical context: Every warning entry in the Warnings section includes four pieces of information: what the problem is, why the missing property matters to Google, what rich result impact the absence has, and a specific fix recommendation. This format means you get actionable output, not just a list of error codes.

AI Quality Review for the full page: When an OpenAI API key is active, the tool generates an HTML-formatted quality review covering all schema blocks together. It looks at the combined picture, not just individual blocks in isolation, and flags patterns that could limit rich result eligibility across the whole page.

Three export options: Results can be copied in a clipboard format that pastes cleanly into Excel, downloaded as a CSV file named schema-report.csv, or downloaded as a tab-separated .xls file for direct use in Microsoft Excel. All export formats include the type, status, message, and recommendation columns from the full warnings report.

Clear and reset in one click: The Clear button resets all inputs, hides the results panel, clears the block list, dismisses any AI fix output, and resets the status pill to Ready. This makes running multiple consecutive checks fast and clean.

Benefits of Using the Schema Markup Checker

Find schema problems before Google does: When schema is broken or incomplete, Google simply ignores it. The tool catches those problems while you still have time to fix them, before a missed rich result costs you traffic.

Understand why each problem matters: Most schema validators return pass or fail with no further context. This tool explains each issue in terms of its actual SEO impact, why the missing property exists in the schema.org specification, and what rich result type it affects. That information is useful whether you are doing the fix yourself or communicating with a developer.

Save time on manual schema checking: Reading through HTML source code to find and verify schema blocks is slow and error-prone. Entering a URL and getting a structured block-by-block report in seconds is faster for routine auditing and much more reliable for catching things that are easy to miss by eye.

Fix JSON-LD issues without writing code: The AI fix feature produces corrected JSON-LD that you can drop directly into your CMS. You do not need to know schema.org property names by heart or look up documentation to add missing fields. The AI infers the correct type if one is missing and adds the properties that matter most for that entity.

Use it for audits, client work, and QA: The export options make the tool practical for sharing results. You can hand a client a CSV showing all schema issues on their site with explanations attached, or drop an Excel file into a project management system as part of a technical audit deliverable.

Check any live page regardless of platform

Because the tool fetches the page directly from its server, it works on any publicly accessible URL regardless of what CMS, framework, or templating system is behind it. WordPress, Shopify, custom-built sites, and statically generated pages all work the same way.

FAQs About the Schema Markup Checker

What is the difference between URL mode and code mode?

URL mode fetches a live webpage and scans its full HTML, which means it can detect JSON-LD, Microdata, and RDFa. Code mode only accepts pasted JSON-LD text because Microdata and RDFa are embedded in HTML attributes that cannot be submitted as standalone code. Use URL mode for full page audits and code mode for validating JSON-LD you have written before adding it to a page.

What counts as a valid JSON-LD block?

The tool parses each JSON-LD block using standard JSON decoding. A block is considered valid if it parses without errors, meaning no trailing commas, no unquoted keys, no invalid escape sequences, and no other formatting issues that would cause a JSON parser to fail. Invalid blocks get flagged and the AI fix button is not offered for them because AI-based fixing requires parseable input.

When does the Fix Schema (AI) button appear?

The button appears on JSON-LD blocks that have valid JSON and at least one fixable issue, specifically a missing @context or a missing @type. It does not appear on blocks that pass all checks, on Microdata or RDFa blocks, or on JSON-LD blocks that fail JSON validation.

What does the AI Quality Review actually check?

The AI Quality Review looks at all detected schema blocks together along with whether Microdata and RDFa were found. It evaluates the combined schema picture for a page and outputs structured recommendations in HTML list format covering problems that could prevent rich result eligibility and properties that would strengthen the markup.

Can I check competitor pages or pages I do not own?

Yes. The URL mode will fetch and analyze any publicly accessible page. If a server blocks automated requests the tool will return an error message, but most standard web pages work without any issues.

What are the export file formats used for?

The Copy Report option puts tab-separated data on your clipboard that pastes directly into Excel or Google Sheets with columns intact. The CSV download uses proper comma-separated formatting for import into analytics tools or spreadsheet software. The Excel download is a tab-separated file with an .xls extension that opens natively in Microsoft Excel without any import configuration.

Does the tool require an account or login?

No. The tool runs entirely in the browser through the WordPress shortcode. There is nothing to install, no account to create, and no files to upload. You enter a URL or paste schema code and the results come back in the same page.