Schema Validator: Schema Markup Checker
Free structured data validator: enter a URL or paste code and we extract every JSON-LD, Microdata and RDFa item, report JSON errors with line numbers, check types and properties against the schema.org vocabulary (release 30.1) and test the required and recommended fields for Google rich results — with fixes ready to copy.
Or paste code: JSON-LD or HTML
Datos clave
The validator checks a page’s structured data: JSON-LD, Microdata and RDFa syntax, types and properties against the schema.org vocabulary and Google’s required fields. Paste a URL or code and you see errors with line and column. Markup added by JavaScript is not visible, and only Google’s official test can confirm a rich result in search.
- Precio
- Gratis
- Registro
- No necesario
- Procesamiento
- On our server: for a URL it downloads the page (guarded against internal-network requests) and extracts the markup; pasted code is parsed on the server and not stored
- Entrada
- The URL of a public page or pasted JSON-LD, Microdata or RDFa code (up to 512 KB)
- Límites
- No sign-up; up to 20 pasted-code checks and 12 page loads per minute per IP, no daily limit; a URL result is cached for 10 minutes; code up to 512 KB
- Resultado
- A list of blocks and types found, a node tree, JSON errors with line and column, warnings against the schema.org vocabulary and Google’s required/recommended fields, duplicates and @graph/@id issues
- Última actualización
Código abierto en GitHub
Ejecuta la misma comprobación en tu propio equipo: una herramienta de línea de comandos de Node.js, una biblioteca y una GitHub Action. Código abierto con licencia MIT.
Schema markup validator for JSON-LD, Microdata and RDFa
The validator finds every structured data item on a page or in pasted code — JSON-LD, Microdata and RDFa — and checks it in three layers. First syntax: if the JSON is broken, you get the line, column and reason (trailing comma, curly quotes, a line break inside a value) plus a repaired block. Then the schema.org vocabulary: unknown types and properties with a "did you mean" hint, properties used on the wrong type, superseded terms, invalid enumeration values, dates and durations that aren't ISO 8601, dangling @id references and duplicate entities. Finally Google's rules: required and recommended fields for articles, products, reviews, breadcrumbs, organizations, events, recipes, videos, software apps and job postings.
Cómo usar
- Enter a page URL or paste JSON-LD / HTML into the code box
- Start with errors: JSON syntax and Google required fields
- Copy the fixes, update the page and validate again
FAQ
PromoPilot frente a alternativas: comparación
Comparamos solo lo que está confirmado en las páginas de cada servicio. Donde no pudimos confirmar un dato, la celda muestra "—".
| Parámetro | PromoPilot | Google Rich Results Test | Schema Markup Validator |
|---|---|---|---|
| JSON-LD, Microdata, RDFa | ✓ | — | Formats are not named on the page |
| Confirms eligibility for Google rich results | ✗ | ✓ tests which rich results a page can generate | ✗ |
| JSON errors with line and column, auto-fix | ✓ | — | — |
| Executes the page’s JavaScript | ✗ | Tests run with the Google Inspection Tool (smartphone or desktop) | — |
Desplaza la tabla hacia los lados
Dónde somos más débiles: we do not execute the page’s JavaScript or confirm eligibility for Google rich results; we check only public pages and code up to 512 KB.
Cuándo elegir PromoPilot: When you want to quickly find syntax errors and extra or missing fields in markup and see the node tree and duplicates. For a final answer on whether a page qualifies for Google rich results you need the Rich Results Test.
Comprobado el: . "—" significa que no está confirmado en la página oficial; las condiciones y los precios cambian, así que consulta los sitios de cada servicio.