JSON-LD Type & Field Reviewer

It uses static JSON-LD objects retained by the completed crawl, flattens typed top-level and @graph objects, lists the first @type value, and compares selected types with a limited repository field table. It also selects some pages for applicability review from crawl order, URLs, titles, and captured text.

No. It does not inspect Microdata or RDFa, and JSON that failed to parse was already skipped by the crawler. It does not fully validate JSON-LD context, vocabulary, value types, nested objects, identifiers, duplicate entities, deprecated properties, rendered markup, or page-content consistency.

No. The field table is partial and can differ from current feature documentation or the exact search experience. The reviewer cannot test technical access, visible-content policies, quality guidelines, feature availability, manual actions, rendered output, or whether Google will show a rich result.

No. Add structured data only when it accurately represents visible content and serves a supported consumer use case. A page can be useful and indexable without JSON-LD, and adding irrelevant, hidden, incomplete, or misleading markup can create quality and policy problems.

Confirm the page's main visible entity, choose the most specific applicable type, and compare the complete rendered item with current consumer documentation. Use Schema Markup Validator for general Schema.org vocabulary and Google's Rich Results Test plus URL Inspection for supported Google search features. Monitor Search Console after release.

Google supports JSON-LD, Microdata, and RDFa for structured data unless a feature guide says otherwise, and generally recommends JSON-LD. Choose a supported format your system can generate accurately and maintain; the format alone does not improve ranking or guarantee a search feature.