Calculator Input
Example Data Table
| Scenario | Expected Type | Entities | Missing Fields | Warnings | Estimated Score |
|---|---|---|---|---|---|
| Article with complete publishing fields | Article | 1 | None | 0 | 96 |
| Product missing offers and brand | Product | 1 | offers, brand | 2 | 71 |
| FAQPage without mainEntity array | FAQPage | 1 | mainEntity | 2 | 63 |
| Broken JSON syntax and missing braces | Unknown | 0 | Not measurable | 1 | 0 |
Formula Used
Completeness Score = (Present Recommended Fields ÷ Total Recommended Fields) × 100
Structural Pass Rate = (Passed Checks ÷ Total Active Checks) × 100
Final Score = Syntax Score − (Critical Errors × Error Penalty) − (Warnings × Warning Penalty) + (Completeness Score × 0.24)
The calculator caps the final score between 0 and 100. Strict mode uses heavier penalties, while lenient mode reduces them.
How to Use This Calculator
- Paste your JSON-LD payload into the input field.
- Select a validation mode based on how strict you want the checks.
- Choose an expected schema type, or leave auto detection enabled.
- Set your minimum completeness threshold.
- Choose whether to require
@context,@type, HTTPS context, URL checks, and date checks. - Submit the form to generate the validation report above the calculator.
- Review the score, missing fields, warnings, and graph.
- Use the CSV or PDF buttons to export the result summary.
8 FAQs
1) What does this validator measure?
It checks JSON syntax, entity detection, schema type presence, recommended field coverage, selected URL checks, date checks, depth, and an overall heuristic score.
2) Is the final score an official search engine score?
No. It is a practical quality score built for quick auditing. It helps compare versions and spot missing elements, but it is not an official platform metric.
3) Why can valid JSON still receive warnings?
Valid JSON only means the syntax parses correctly. Warnings can still appear when important schema fields are missing, URLs look weak, dates fail checks, or the expected type does not match.
4) What happens in strict mode?
Strict mode increases penalties for critical errors and warnings. It also treats some structural problems more seriously, making it useful for tighter publishing workflows.
5) Can it validate multiple entities inside @graph?
Yes. The calculator detects nodes inside @graph and counts their entity records. It also evaluates detected types across the payload.
6) How are recommended fields chosen?
The calculator uses a type-based recommendation map. Each common schema type has a practical set of important fields used to estimate completeness.
7) Does a high score guarantee rich results?
No. A strong score improves quality signals, but visibility also depends on search engine support, page content, policy compliance, and successful crawling.
8) When should I export CSV or PDF results?
Use CSV for spreadsheet reviews or change logs. Use PDF when you need a shareable snapshot for clients, QA teams, audits, or documentation.