Schema Markup (JSON-LD) Generator

Continue in the tool

More pages for this tool

article schema json-ld author date published

Article schema: author, dates and images in JSON-LD

Pick Article in the generator, select the subtype and fill it in. The Now button inserts the date and time with your time zone, and the form flags author names joined in a single field.

What Google recommends in Article

The Article documentation says there are no required properties: you add the ones that apply to the content. The recommended ones are author, datePublished, dateModified, headline and image. The accepted types are Article, NewsArticle and BlogPosting, and the right subtype depends on the nature of the text: news, blog posts or articles in general. The headline should be concise, because long titles may be truncated on display, and the description of the content works better in the description field than forced into the title.
On authorship, Google asks that every author shown on the page go in a separate entry, without joining names in a single field. Only the person name goes in author.name: job title, honorific and phrases like written by belong in other properties. Each author should have a url (a page that identifies them) or sameAs, and the type is Person for people and Organization for organizations, never Thing. Dates follow ISO 8601 and the documentation asks for the time zone, for example 2026-03-10T08:00:00-03:00; without the zone, the tool issues a warning. And dateModified should not be earlier than the publication date.
For images, Google recommends high-resolution files in 16:9, 4:3 and 1:1 aspect ratios, one URL per line in the images field. On a site with more than one brand page, link the article to the rest of the graph: the publisher points by @id to the Organization, and mainEntityOfPage points to the matching WebPage. That way the publisher data lives in one place instead of repeating on every post. The generator graph example shows exactly this link, with Organization, WebSite, WebPage and Article.

Checked formats

Date with time zone

Input: 2026-03-10 08:00 em São Paulo
Expected output: 2026-03-10T08:00:00-03:00

ISO 8601 with offset.

Date without time zone

Input: 2026-03-10T08:00:00
Expected output: aviso: falta o fuso horário

Dates without a time, such as 2026-03-10, do not raise the warning.

Subtype

Input: BlogPosting
Expected output: @type: BlogPosting

The subtype changes only the @type.

Two authors

Input: Ana Lima e Bruno Reis
Expected output: author: [Person Ana Lima, Person Bruno Reis]

One entry per author, never both names together.

Modified before published

Input: publicado 2026-03-10, modificado 2026-03-01
Expected output: aviso: dateModified anterior a datePublished

Almost always a typo.

Full tool FAQ

Does Google still show the FAQ rich result?

No. Google recorded on 2026-05-08 that the FAQ rich result stopped appearing from 2026-05-07 and removed the documentation on 2026-06-15. FAQPage remains valid schema.org and other consumers may use it, but do not count on it to win space in Search. HowTo went the same way: its result was removed on 2023-09-14.

What is the difference between JSON-LD, Microdata and RDFa?

Which properties are required?

Can I mark up reviews of my own business?

How do I link several types with @graph and @id?

Which date, duration and price format should I use?

Does a lone Course show up on Google?

Can I edit JSON-LD that is already on my site?

Where do I put the JSON-LD on the page?

Does the tool send my data to a server?

Frequently asked questions

What is the difference between Article, NewsArticle and BlogPosting?

It is a matter of specificity in schema.org: NewsArticle and BlogPosting are subtypes of Article. Google lists all three in the documentation and applies the same recommendations.

Do I need the publisher?

It is not among the recommended properties in the Article documentation, but it is often useful to link the article to the organization. In the generator it is optional and accepts a link by @id.

When should I update dateModified?

Only when the content really changes. Touching the date without changing the text does not help the reader and can undermine the markup.

Next steps

{ "@context": "https://schema.org", "@type": "Organization", "name": "Example Bakery Inc.", "url": "https://www.example.com/", "logo": "https://www.example.com/logo.png", "description": "Artisan bakery with sourdough breads and breakfast.", "sameAs": [ "https://www.instagram.com/example", "https://www.facebook.com/example" ], "email": "[email protected]", "telephone": "+1 512-555-0100", "contactPoint": { "@type": "ContactPoint", "contactType": "customer service", "telephone": "+1 512-555-0100", "availableLanguage": "en-US" }, "address": { "@type": "PostalAddress", "streetAddress": "100 Main Street", "addressLocality": "Austin", "addressRegion": "TX", "postalCode": "78701", "addressCountry": "US" }, "taxID": "00-0000000" }

What Google recommends in Article

The Article documentation says there are no required properties: you add the ones that apply to the content. The recommended ones are author, datePublished, dateModified, headline and image. The accepted types are Article, NewsArticle and BlogPosting, and the right subtype depends on the nature of the text: news, blog posts or articles in general. The headline should be concise, because long titles may be truncated on display, and the description of the content works better in the description field than forced into the title.

On authorship, Google asks that every author shown on the page go in a separate entry, without joining names in a single field. Only the person name goes in author.name: job title, honorific and phrases like written by belong in other properties. Each author should have a url (a page that identifies them) or sameAs, and the type is Person for people and Organization for organizations, never Thing. Dates follow ISO 8601 and the documentation asks for the time zone, for example 2026-03-10T08:00:00-03:00; without the zone, the tool issues a warning. And dateModified should not be earlier than the publication date.

For images, Google recommends high-resolution files in 16:9, 4:3 and 1:1 aspect ratios, one URL per line in the images field. On a site with more than one brand page, link the article to the rest of the graph: the publisher points by @id to the Organization, and mainEntityOfPage points to the matching WebPage. That way the publisher data lives in one place instead of repeating on every post. The generator graph example shows exactly this link, with Organization, WebSite, WebPage and Article.

Checked formats

Date with time zone

Input: 2026-03-10 08:00 em São Paulo
Expected output: 2026-03-10T08:00:00-03:00

ISO 8601 with offset.

Date without time zone

Input: 2026-03-10T08:00:00
Expected output: aviso: falta o fuso horário

Dates without a time, such as 2026-03-10, do not raise the warning.

Subtype

Input: BlogPosting
Expected output: @type: BlogPosting

The subtype changes only the @type.

Two authors

Input: Ana Lima e Bruno Reis
Expected output: author: [Person Ana Lima, Person Bruno Reis]

One entry per author, never both names together.

Modified before published

Input: publicado 2026-03-10, modificado 2026-03-01
Expected output: aviso: dateModified anterior a datePublished

Almost always a typo.

Full tool FAQ

Does Google still show the FAQ rich result?

What is the difference between JSON-LD, Microdata and RDFa?

Which properties are required?

Can I mark up reviews of my own business?

How do I link several types with @graph and @id?

Which date, duration and price format should I use?

Does a lone Course show up on Google?

Can I edit JSON-LD that is already on my site?

Where do I put the JSON-LD on the page?

Does the tool send my data to a server?

Frequently asked questions

What is the difference between Article, NewsArticle and BlogPosting?

It is a matter of specificity in schema.org: NewsArticle and BlogPosting are subtypes of Article. Google lists all three in the documentation and applies the same recommendations.

Do I need the publisher?

It is not among the recommended properties in the Article documentation, but it is often useful to link the article to the organization. In the generator it is optional and accepts a link by @id.

When should I update dateModified?

Only when the content really changes. Touching the date without changing the text does not help the reader and can undermine the markup.