Can I choose BlogPosting instead of Article?
Yes. The Article Schema Builder supports both Article and BlogPosting schema types, so you can match the markup to the kind of page you are publishing.
Does this pull metadata from a live URL?
No. The builder stays form-based and local; you enter the fields manually and it generates JSON-LD in your browser without fetching a live page.
Is the Article Schema Builder free?
Yes. It is free to use with no signup, and the JSON-LD is generated entirely in your browser so nothing you enter is uploaded.
What do I do with the generated JSON-LD?
Copy the generated block and paste it into your page head or your CMS schema field. It is ready to use, and you can validate it with a structured-data testing tool before publishing.
Article or BlogPosting, which should I pick?
For Google Search it makes no practical difference; all Article subtypes are handled identically. BlogPosting is the more precise type for a dated post in a blog, and precision costs nothing, so use it there and use Article for evergreen pages. Do not spend time agonising over it.
Why does my published date have no time on it?
The form uses a native date input, which produces a date without a clock time or a timezone. For most articles that is fine. For news, where ordering matters, replace the value in the output with a full ISO 8601 string such as 2026-07-11T09:30:00+02:00 before you ship it.
Do I need a publisher logo?
The builder emits a publisher name without one, and that produces a valid block. Google's Article guidance treats publisher fields as recommended rather than required, and the old AMP-era logo requirement is gone. If another consumer of your schema wants a logo, add a logo ImageObject to the publisher object by hand.
Does the headline have to match the page title?
It should match the visible headline of the article, the H1 in most templates. Structured data that contradicts what a user sees is against Google's guidelines, and a headline field stuffed with keywords that appear nowhere on the page is exactly the case that rule was written for.
Where does the JSON-LD go?
Inside a script element with type set to application/ld+json, usually in the head. The builder gives you the JSON object; the script wrapper is yours to add. One Article block per article page is enough.
Is anything uploaded?
No. The schema is assembled in your browser from the fields you type. Nothing is sent anywhere, so drafting markup for an unpublished post is safe.