Pick a type, fill in the fields, and get schema.org markup as JSON-LD, ready to paste. Missing required fields and malformed URLs or dates are flagged as you type.
Runs in your browser · nothing uploaded · no signup
Google lists no required properties for Article: it asks you to add the ones that apply. It says Article markup can help it understand the page and show better title text, images and date information in search results. Google: Article ↗
Google accepts all three. Pick the one that fits the page.
The title of the article. Google suggests keeping it concise, since long titles may be truncated on some devices.
Pictures that represent the article, not logos. URLs must be crawlable and indexable. Google recommends several high-resolution images (at least 50K pixels) in 16:9, 4:3 and 1:1.
ISO 8601, like 2026-10-19 or 2026-10-19T08:00:00+08:00. Google recommends adding a timezone; without one it assumes the timezone Googlebot uses.
Same format. The last time the article was updated.
One entry per author, and list every author shown on the page. Put only the name in the name field: no job title, no “By”.
Google no longer shows FAQ rich results. Its documentation changelog says the feature stopped appearing in Search on May 7, 2026, and the FAQ documentation was removed on June 15, 2026. (From September 2023 it had been limited to well-known government and health websites.) This tool still writes FAQPage markup, but don’t expect a Google rich result from it. Google’s changelog ↗ · schema.org/FAQPage ↗
Only mark up questions and answers that readers can see on the page.
Google’s product snippet needs a name plus at least one of offers, aggregateRating or review. A page where shoppers can buy the product can also qualify for merchant listings, which need an image and a price with currency. One product per page. Google: Product snippet ↗ · Google: Merchant listing ↗
Photos that show the product clearly, ideally on a plain background. Google requires an image for merchant listings.
Not mandatory, but Google strongly recommends it.
At most one brand name.
Your own identifier for the product. No spaces.
Google lists no required properties for Organization. It recommends putting the markup on your home page or one page that describes the organization, not on every page. Google: Organization ↗
For a local business Google requires name and address, and recommends following the Organization fields too. Google: Local business ↗
Use the same name and alternate name you use for your site name.
Another common name for your organization, if you have one.
The registered legal name, if it differs from the name.
Your website’s address. It helps Google uniquely identify your organization.
At least 112×112 px, crawlable and indexable, in a format Google Images supports. Check how it looks on a plain white background.
A detailed description of your organization.
Pages about your organization on other sites, such as social profiles. Add as many as apply.
Include the country code and area code.
Fill in the fields and your code appears here.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article"
}
</script>This page only checks required fields and formats. For a real check, paste the code into one of Google’s or schema.org’s tools. Both open in a new tab. Rich Results Test: choose the Code tab and paste. Schema Markup Validator: choose the Code snippet tab and paste.
A clean result is not a promise: Google says it doesn’t guarantee that structured data will show up in search results, even when the page passes the Rich Results Test. Google: general guidelines ↗
The code goes into the page it describes. Google reads JSON-LD placed in either the head or the body, and recommends JSON-LD over the other formats whenever your setup allows it. Google: how structured data works ↗
Google’s guidelines say not to mark up content that isn’t visible to readers of the page, or anything irrelevant or misleading, such as fake reviews. The questions, prices and ratings in your code should be on the page too. Google: general guidelines ↗
An Article block belongs on that article. For Organization, Google recommends your home page or one page about the organization, and says you don’t need it on every page. Google: Organization ↗
Paste the code, or the live URL, into the Rich Results Test and the Schema Markup Validator. After Google has indexed the page, the rich result status reports in Search Console show the issues it found. Google: monitor rich results ↗
Google says it doesn’t guarantee that your structured data will show up in search results, even if the page is marked up correctly according to the Rich Results Test. Google: general guidelines ↗
Check what’s already on the page first: open the live URL in the Rich Results Test, or view the page source and search for application/ld+json. Yoast SEO writes a JSON-LD graph on every page (WebPage, WebSite and an Organization or Person) and adds an Article on single posts (Yoast ↗). Rank Math adds Organization or Person, WebSite and WebPage by default, plus the default schema type you set for posts and pages (Rank Math ↗). If your plugin already writes the type you’re about to add, change it in the plugin instead of pasting a second copy.
To paste your own block, add a Custom HTML block (WordPress ↗). WordPress strips <script> tags from it when you save, unless your user has the unfiltered_html capability: on a single site that’s Administrators and Editors, on a multisite network only Super Admins (WordPress roles ↗). Google also points CMS users to their CMS’s search engine settings page or a structured data plugin (Google ↗).
Google can only read markup on pages it’s allowed to fetch. The free audit reads your homepage, robots.txt, sitemap and llms.txt, scores five dimensions, and tells you which fix is worth the most.
5 dimensions · no signup · ~60 seconds