Tool

Structured data checker and generator

Check a page or pasted markup, or generate JSON-LD from facts you enter. See syntax, declared Schema.org types and the documented eligibility rules this checker can verify.

Results keep Schema.org validity separate from search-engine feature eligibility.

Search-engine support, limits and official validators

Bing reads JSON-LD and Schema.org; Yandex supports Schema.org but not every type. Each search engine decides which features it uses, and valid markup never guarantees a rich result or ranking. After publishing, verify the live page with the relevant first-party tools: Schema.org Validator, Google Rich Results Test, Bing URL Inspection, and Yandex validator. Schema.org is a vocabulary rather than a crawler; use the robots.txt validator to check Googlebot, Bingbot, Applebot and the supported AI/search crawlers separately.

Preparing checker and generator…

Enable JavaScript to check structured data or generate JSON-LD. A URL is fetched by this site’s server; pasted markup is sent to it only to be parsed.

Schema type

Choose the entity the visible page describes. Changing type starts a blank draft and clears all entered fields, validation messages and generated output. Labels distinguish direct Google feature coverage, required graph context, intentionally incomplete eligibility, and Schema.org-only output.

Current support

Covered by Google’s current organization guidance

The output uses shared Schema.org JSON-LD; Google, Bing and Yandex apply their own feature and eligibility rules.

See details, limits and sources

This is a bounded, safe subset for an organization’s home or about page. Google lists no required Organization properties; this generator still requires the visible name so it cannot emit an empty entity.

Schema.org is a shared vocabulary, not a crawler. Search engines, social preview fetchers and AI/search crawlers choose independently whether to fetch a page and which vocabulary fields they use. Check access for Googlebot, Bingbot, Applebot and the supported AI/search crawlers in the robots.txt validator.

Generated output does not guarantee that a crawler will fetch or interpret the page, that a search engine will index or rank it, or that a special result will appear. Crawler access is controlled separately. Validate for each target platform. Sources: Schema.org Validator, Google Rich Results Test, Google Search Gallery, Bing structured data, and Yandex Schema.org support.

Core entity details

Organization name

Required to generate a non-empty Organization. Google lists no required Organization properties.

Page or entity URL

Optional. Use the full public URL for this exact page or entity.

Image URL

Optional. Use a full, crawlable URL for an image that visibly represents this exact entity.

Description

Optional. Summarize what this entity is in factual language that matches the visible page. Avoid keyword stuffing.

Organization identity

Organization type

Choose Online store only for an online-only commerce organization. Use the Local business templates for physical locations.

Alternate public name

Optional. Use another common name the organization publicly uses, not a keyword variation.

Logo URL

Optional. Use a stable, crawlable URL for the organization’s real logo. Google recommends at least 112 × 112 pixels.

Official profile URLs

Optional. Add one full public URL per line, up to 20, only for profiles that identify this same organization.

Advanced Organization details

Add only public facts supported by the organization’s visible home or about page. Empty sections are omitted from the generated graph.

Registered identity and primary contact

Registered legal name

Optional. Enter the registered legal name only when it differs from the public name.

Founding date

Optional. Use the real founding date in ISO 8601 calendar form.

Primary public email

Optional. Use the organization’s public primary contact address.

Primary public telephone

Optional. Include the leading +, country code and area code.

Postal address (optional)

Add one public physical or mailing address. Any blank address is omitted; when a country is supplied, use its assigned two-letter ISO 3166-1 code.

Street address

Include unit or suite information when it is part of the published address.

City or locality

Region or state

Postal code

Country code

Use an assigned two-letter ISO 3166-1 code, such as JO, US or GB.

Additional contact points (optional)

Add up to 10 public support methods. Every contact point needs an email address or international telephone number; the contact type describes its purpose.

Generated locally in this browser. Nothing is sent or saved.

Loading the JSON-LD generator…