JSON-LD
Describe page entities in machine-readable data.
Check JSON-LD, Schema.org types and core rich-result fields on any page.
Enter a page URL, then click Run check.
STRUCTURED DATA SEO
Schema.org structured data is a machine-readable format, commonly JSON-LD, that describes page entities such as articles, products, organizations, breadcrumbs and FAQs.
It does not guarantee rankings or rich results. Accurate, parseable data that matches visible content can reduce ambiguity when search engines interpret a page.
Describe page entities in machine-readable data.
Review fields used by search features.
Keep URLs absolute and consistent.
Template changes, plugin conflicts and hand-written JSON-LD often create invalid JSON, incorrect types, missing fields or relative image URLs. A check catches these issues before publishing.
Find syntax errors, empty blocks and missing @context or @type.
Check common Article, Product, FAQPage and BreadcrumbList fields.
Review entity types and URLs with practical SEO recommendations.
The tool requests public HTML, extracts application/ld+json blocks and performs safe JSON-LD and Schema.org checks.
Resolve public IPs and limit redirects, time, compressed input and page size.
Read JSON-LD scripts, including arrays and @graph containers.
Review @context, @type, common rich-result fields and absolute URLs.
Separate syntax, structure and field issues into practical next steps.
Valid means JSON-LD parses and its basic structure is complete. Needs attention indicates field or URL quality concerns; parsing errors and missing structure should come first.
No. Search engines decide rich-result eligibility based on content quality, policies, crawling and query intent. Structured data is only a machine-readable signal.
It can be placed in the HTML head or body inside a script type=application/ld+json element. Crawlers must be able to receive it in the server response.
@context identifies the vocabulary, usually https://schema.org. @type identifies the entity, such as Article, Product or WebPage.
Yes. Multiple entities or one @graph container are valid, but avoid duplicate or conflicting claims and keep them aligned with the page.
Continue with Meta tags, canonical, sitemap, crawl-rule and response checks.
Check search snippets, social previews and index metadata.
Validate canonical URLs, language versions and index signals.
Validate XML format, URL status and discoverability.
Check crawl rules, Disallow, Allow and sitemap signals.