Article schema generator.
Fill in the headline, authors, dates, images, and publisher to generate Article, BlogPosting, or NewsArticle JSON-LD. The tool checks that dates follow ISO 8601 and that every address is complete, and it points out the properties Google recommends. Paste the result into the page that shows the same article.
The title of the article.
Optional. The full address of the article.
Optional. A sentence or two.
One full address per line. Google recommends 16x9, 4x3, and 1x1 versions.
ISO 8601, with a timezone.
Optional. When the article last changed.
Optional. The organization behind the site.
Optional.
Google lists no required properties for Article markup, only recommended ones. See its guidance on Article structured data.
This tool runs in your browser. Nothing you enter is sent anywhere or stored.
How to use it
- Choose the type Use BlogPosting for blog posts, NewsArticle for news reporting, and Article for everything else.
- Fill in the details Add the headline, the page address, the dates, and 1 image address per line. Several images in different shapes are welcome.
- Add the authors List every author shown on the page, with a link to a page about them where you have one. Tick the organization box when a company is the author.
- Copy the JSON-LD Place the code on the article page, then check it with Google's Rich Results Test.
Why it matters
Article markup tells search engines which text is the headline, who wrote the piece, and when it was published and updated. Google says it can use this to show better title text, images, and date information in results. It also notes that no property is required, so you add the ones that apply, and the more recommended ones you include, the clearer the signal.
Dates are where most markup goes wrong. Both datePublished and dateModified should use ISO 8601 and include a timezone, for example 2026-10-08T09:30:00-04:00. Without a timezone, Google falls back to the one Googlebot uses. The modified date should change when the article changes in a real way, and it should never come before the published date, which the tool checks.
List every author as its own entry, with a type and a url or sameAs link to a page that identifies them, and keep the name field to the name alone, with no job title and no words like posted by. Give Google images in 16x9, 4x3, and 1x1 shapes when you can. Publisher is not on Google's list of recommended Article properties but is valid schema.org markup, so it is optional here. The markup has to match what readers see on the page.
Sources
Questions
Which type should I pick?
Google lists the same properties for Article, NewsArticle, and BlogPosting. Pick the one that matches the content, and use Article when you are unsure.
Does this guarantee a rich result?
No. Article markup helps Google understand the page, and Google decides what to show.
Do I have to include dateModified?
No. It is recommended when the article has been updated. Skip it if the page has never changed.
Where does the code go?
In the head or body of the article page, inside a script tag with the type application/ld+json. Most CMS plugins and tag managers can add it to a single page.
Keep going
Read the Doily guides for step-by-step playbooks. To track results over time, see Doily's SEO tools.
