Schema Validator

JSON-LD should be valid JSON inside a script type application/ld+json. @type names the schema.org entity, such as Article or FAQPage. This tool parses what you paste and surfaces those types when the JSON loads.

What you get from Schema Validator is concrete. Broken JSON is reported as a parse error instead of a success message. Readable JSON lists the @type values found in the object. The snippet stays in the browser. Read those results before you paste them into a template, a file, or a ticket. A copied mistake is harder to see later than a mistake still on this page.

A careful pass on Schema Validator looks like this. Start with real input, not a placeholder you do not understand. Paste the JSON-LD, with or without a script tag if the box accepts the object. Then check the middle of the form, because that is where optional fields change the output. Run Validate. Finish by reading the whole result, not only the first line. Fix any invalid JSON the error line names, then validate again.

The limit is the part people skip on Schema Validator. Match the output to the input you actually typed, then decide whether it belongs on the live site. The JSON parser fails and the screen shows an invalid JSON message. Readable JSON lists the @type values found in the object.

A second reading of Schema Validator is worth it because the first pass is easy to rush. Say out loud what the output is claiming. Broken JSON is reported as a parse error instead of a success message. Readable JSON lists the @type values found in the object. The snippet stays in the browser. Then say what it is not claiming. No. It only parses the JSON-LD you paste. The JSON parser fails and the screen shows an invalid JSON message. That the JSON parsed, and the @type values detected in it. If those two speeches disagree, change the input or pick a different tool. Schema Validator will not resolve the disagreement for you.

Read Schema Validator once more as a single job. Part 1: Paste the JSON-LD, with or without a script tag if the box accepts the object. Part 2: Run Validate. Part 3: Read the parse result and the detected @type list. Part 4: Fix any invalid JSON the error line names, then validate again. You should be able to point at this in the result: Broken JSON is reported as a parse error instead of a success message. You should be able to point at this in the result: Readable JSON lists the @type values found in the object. You should be able to point at this in the result: The snippet stays in the browser. Does the schema validator fetch my site? No. It only parses the JSON-LD you paste. What happens with a missing comma? The JSON parser fails and the screen shows an invalid JSON message. What does a successful check list? That the JSON parsed, and the @type values detected in it. Who is Schema Validator for? Schema Validator is for someone already doing technical seo work who needs validate your schema markup against Google's rich result guidelines. JSON-LD should be valid JSON inside a script type application/ld+json. @type names the schema.org entity, such as Article or FAQPage. This tool parses what you paste and surfaces those types when the JSON loads. The first field was filled with a real value: Paste the JSON-LD, with or without a script tag if the box accepts the object. The result was read: Broken JSON is reported as a parse error instead of a success message. Optional fields were either filled or left empty on purpose. The copy went into the place the last step names. The boundary in the guide was respected before anything was published.

Keep Schema Validator as this step only. When the job moves on, the Schema Markup Generator is the next page: Schema Markup Generator writes JSON-LD for the type you pick, such as Article, FAQ, Local Business, Product, Recipe, or Event. The Robots.txt Generator covers a different piece of the same work: Robots.txt Generator builds a robots.txt file from an allow or disallow default, optional paths, a crawl delay, and a sitemap URL.