Schema.org type fields lookup

The properties included with that type determine whether search engines and other consumers can understand the page. This lookup accepts a familiar type name such as Article, Product, Recipe, or FAQPage and returns a practical field checklist immediately. It separates commonly required properties from recommended enhancements, uses canonical property names, and rejects unknown types clearly so automated workflows never proceed with a silent guess.

Start with the exact type your page represents

Structured data works best when the selected type describes the page's main subject, not merely one small element on it. Enter a Schema.org type such as Product for a purchasable item, Recipe for cooking instructions, Article for editorial content, or LocalBusiness for a physical business presence. The lookup is case-insensitive and also accepts a full schema.org type URL, which makes it convenient when values arrive from an existing JSON-LD document. The response returns the canonical type name and URL alongside two ordered property lists. If the name is not in the supported catalog, the capability returns an input error rather than inventing a close match. That behavior is valuable in publishing pipelines because a typo such as Productt should stop the build instead of producing markup that looks plausible but has no defined meaning. Select the narrowest accurate supported type, while remembering that a specialized type still inherits the broader meaning of its Schema.org parents. The lookup focuses on popular types used in SEO implementations, not every class in the complete Schema.org vocabulary.

Interpret required and recommended as an implementation checklist

Schema.org is a vocabulary and does not universally mandate properties in the way a database schema does. Search features, validators, and downstream consumers impose their own eligibility rules, which can change by platform and presentation. For that reason, the required list in this result means properties commonly treated as the minimum useful set for SEO implementation, while recommended fields usually improve completeness, eligibility, or the quality of a displayed result. Begin by mapping every required property to real, visible page information. Then add recommended properties when trustworthy source data exists. Never fabricate a rating, price, author, image, availability state, or date simply to fill the checklist. A shorter object grounded in page content is safer than rich markup that contradicts what visitors see. Some listed properties contain nested objects: for example, offers on Product, author on Article, location on Event, and mainEntity on FAQPage. This lookup names those top-level properties but intentionally does not generate nested values or validate an entire JSON-LD graph. Use it to scope the data you need before generation and validation.

Use deterministic results in audits and publishing workflows

Because the lookup uses a fixed in-memory catalog with no network requests, model calls, randomness, or clock-dependent behavior, the same supported type always produces the same ordered result. That makes it suitable for repeatable content audits, form builders, schema templates, migration scripts, and continuous integration checks. A CMS can request the checklist when an editor selects a content type, mark missing required inputs, and present recommended enhancements separately. An audit tool can compare existing JSON-LD keys with the response and report gaps without deciding that every recommendation is an error. A generator can use the canonical schema URL while preserving the ordered fields for a predictable interface. Treat the result as a practical starting point and recheck the current documentation of any search platform whose rich result is business-critical, since platform-specific policies are outside this offline catalog. The API request costs $0.002, while the browser experience can use the same pure logic. Error handling is deliberately explicit: an unsupported type returns an invalid-input response containing the submitted name and the supported choices, allowing a person or calling program to correct the request quickly.