JSON-LD Structured Data Builder

Create structured data from facts you can support

1. Choose Article, BreadcrumbList or Organization. Load that type’s fictional example to see the supported input shape.
2. Replace every example fact and URL. Omit optional fields that do not apply; leave unknown dates out.
3. Build the script, review it, and copy or download the exact displayed markup. Add it to the relevant page yourself, then test that page with the appropriate external validation service.

Supported input fields

Type	This builder requires	Optional facts
Article	headline, url	description, images, datePublished, dateModified, authors, publisher
BreadcrumbList	items, containing 2 to 20 named items in order. Every item except the last needs a URL.	The last item’s url
Organization	name, url	description, logo, sameAs, legalName, alternateName, email, telephone, address

These minimum fields belong to this builder’s workflow. Google’s Article and Organization documentation currently lists recommendations rather than required properties. A locally accepted model is not a promise that Google will display a particular result.

Article authors, publisher and dates

An authors array can contain up to ten objects with type (Person or Organization), name, and an optional url. A publisher object accepts name plus optional url and logo. Up to five images URLs are supported. Add only authors and imagery that represent the article. This tool cannot inspect the image, its dimensions, crawl access, or the page itself.

Article dates use a real calendar date and a time with Z or an explicit offset, such as 2025-01-15T09:30:00+01:00. Seconds and up to three fractional digits are supported. The builder rejects an earlier modification timestamp than publication timestamp. Its explicit-zone requirement is a local choice that avoids ambiguous times. No current date is inserted automatically.

Breadcrumb order and organization details

Breadcrumb positions are assigned from the order in items, starting at one. The last URL may be omitted, matching Google’s breadcrumb format. Represent a useful user path. The builder does not derive a hierarchy from URL slashes or add missing pages.

An optional organization address is an object with streetAddress, addressLocality, addressRegion, postalCode and addressCountry. Supply only applicable values. Country text must contain two uppercase letters; assignment of that code is not verified. Telephone and email are facts you supply, not verified contact channels. sameAs accepts up to ten URLs. Reviews, ratings, offers, LocalBusiness subtypes and other schema types are outside this builder.

Schema vocabulary and search eligibility are different checks

Schema.org defines a vocabulary. Search engines support selected features with their own content, technical and eligibility requirements. Matching the vocabulary or passing a test does not guarantee indexing, a rich result, or a ranking change. Check the published page using Schema.org Validator and, for Google-supported features, Google’s Rich Results Test . This tool does not submit anything to either service.

Escaping, optional fields and limits

Input is capped at 30,000 characters, depth eight and 500 values; output is capped at 60,000 characters. Unknown fields and duplicate decoded JSON keys are rejected. Optional empty strings, empty arrays and omitted values are not invented in the output. URLs must be absolute HTTP(S), without credentials, whitespace or invalid percent escapes. Standard URL serialization may encode Unicode or normalize a host. Text remains JSON data: characters such as a less-than sign are escaped so a supplied closing-script string cannot terminate the generated script. The result appears as text and is never installed as schema on this site.

Current official references: Google Article , Google Breadcrumb , Google Organization , and the Schema.org Article vocabulary .