// Five guest checks · no account for the first check
Fetch one public page, find static JSON-LD blocks in its HTML, parse their top-level objects, and review a limited set of fields. Use a dedicated validator for complete vocabulary or rich-result testing.
> Target_URL
5 free checks · No signup · Free
Find application/ld+json script blocks in the first 500 KB of returned HTML.
Review selected fields for a small set of commonly used top-level types.
Inspect the parsed object returned by the checker alongside its notes.
Flag blocks that cannot be parsed as JSON and show up to 500 captured characters.
Read individual objects, top-level arrays, and objects inside a top-level @graph array.
Use the detected types to choose the current Schema.org or Google testing tool.
Ways to go deeper with this site:
It fetches one public page, reads up to 500 KB of returned HTML, finds static application/ld+json script blocks, parses top-level objects, arrays and @graph members, and applies a limited field checklist.
No. It is an initial static JSON-LD check, not the Schema.org Markup Validator or Google's Rich Results Test. It does not prove vocabulary validity, policy compliance, visible-content consistency, technical eligibility, indexing or search appearance.
The check excludes Microdata and RDFa. It also does not execute JavaScript, so markup injected only after rendering may not be captured.
It means the object parsed and did not trigger this tool's small set of field checks. It does not mean the markup is fully valid or eligible for a search feature.
The checker reviews objects in a top-level JSON array and members of a top-level @graph array. It does not recursively validate every nested typed entity or relationship.
Guests can run five quick-tool checks. A free account includes 15 quick-tool checks per month, while Pro and Agency plans include unlimited quick-tool use under the current plan limits.
JSON-LD Review
Review crawl-captured static JSON-LD types, selected field checks, and pages chosen by a limited applicability heuristic
Technical SEO Signals
Review crawl-captured metadata, directives, URL patterns, statuses, links, and JSON-LD presence
SEO Checklist
Review captured titles, descriptions, headings, canonicals, image alternatives, JSON-LD presence, Open Graph fields, and link responses
The checker fetches one public URL, reads up to 500 KB of returned HTML, and looks for application/ld+json block on the page. It parses each block as JSON, identifies the schema type via @type, and validates selected fields from a small configured table. It also handles @graph arrays and inline JSON arrays, flags malformed JSON blocks, and surfaces the parsed object so you can inspect it alongside the checklist notes.
This server-side request does not render JavaScript or inspect Microdata and RDFa. The checklist does not validate the complete Schema.org vocabulary, nested relationships, value formats, page-content alignment, search policies, indexing, or rich-result eligibility. Google's requirements also vary by search feature, so compare relevant markup with the current documentation and test the live URL in the appropriate tool.
Fix JSON parse errors first, then identify the consumer and search feature each object is intended to support. Use the Schema.org Markup Validator for general vocabulary review or Google's Rich Results Test for supported Google search features. Finally, confirm that markup represents visible page content and monitor eligible pages in Search Console; correct markup does not guarantee a particular search appearance.