For an ordinary blog post, use BlogPosting in JSON-LD and describe only what a visitor can see on the page: the headline, the author, the image and the two dates. Fill those fields in order, then test the published URL.
Use Article for editorial pieces that are not blog posts, and NewsArticle only for genuine news reporting. The steps are the same on WordPress, Shopify, Wix, Squarespace, Webflow and hand-built sites, because the code describes the page rather than the platform.
That holds whether you are adding markup to a new post or fixing one where a validator reports the author or a date as wrong. The example below uses made-up names on example.com, so replace every value with a fact from your own page.
Choose BlogPosting, Article or NewsArticle
All three are Schema.org types that sit under CreativeWork, and Google says its Article structured data accepts Article, NewsArticle or BlogPosting (Google Article structured data). The type should describe the visible content, so the choice is about what the page is, not about which label might perform better.

BlogPosting fits an individual post published as part of a blog. Article fits guides, essays and other editorial content that is not more specifically classified. NewsArticle fits news reports and current-affairs coverage, and it is the wrong label for an evergreen post, even a well-researched one.
Keep the blog itself separate from its posts. A blog homepage or archive can use Blog, while each entry uses BlogPosting. Do not mark the archive page as a BlogPosting, and do not use any of these types on product, category or contact pages, because those pages are not articles.
Fill the fields in the order you enter them
Google says the Article feature currently lists no required properties, so the fields below are recommended where they apply. They also describe your page well for any other system that reads Schema.org markup. Work through them in this order.
headline: the exact visible title of the post, kept concise.image: a relevant, crawlable image of the post, not a logo or a caption. Google recommends high-resolution versions in 16:9, 4:3 and 1:1 ratios.datePublished: the first publication date, in ISO 8601 format with a timezone.dateModified: the latest meaningful content change, added only once there is one.author: aPersonwhosenamematches the byline, with aurlthat identifies them.publisher: theOrganizationbehind the blog.
Schema.org also defines useful properties such as mainEntityOfPage, isPartOf and inLanguage. Google's Article page does not list them as Article-feature properties, so treat them as optional for that feature and include them when they are accurate. Google's general structured data guidelines also say the markup must represent visible page content and that image URLs must be crawlable and indexable.
If you would rather fill in a form than write JSON by hand, the Article schema generator builds this markup from the same fields.
A complete BlogPosting example
This example puts the post, its author, the publisher and the blog into one @graph, joined by stable @id values. It is code to copy and adapt, and the names, dates and URLs are all fictional.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"@id": "https://example.com/blog/bright-gardens/#blogposting",
"mainEntityOfPage": "https://example.com/blog/bright-gardens/",
"headline": "How to Plan a Bright Indoor Garden",
"description": "A practical guide to choosing plants, light, and containers for a bright indoor garden.",
"image": [
"https://example.com/images/bright-garden-16x9.jpg",
"https://example.com/images/bright-garden-4x3.jpg",
"https://example.com/images/bright-garden-1x1.jpg"
],
"datePublished": "2026-04-10T09:00:00-05:00",
"dateModified": "2026-06-18T14:30:00-05:00",
"author": { "@id": "https://example.com/about/jordan-lee/#person" },
"publisher": { "@id": "https://example.com/#organization" },
"isPartOf": { "@id": "https://example.com/blog/#blog" },
"inLanguage": "en-US"
},
{
"@type": "Person",
"@id": "https://example.com/about/jordan-lee/#person",
"name": "Jordan Lee",
"url": "https://example.com/about/jordan-lee/",
"sameAs": ["https://example.org/profiles/jordan-lee"]
},
{
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Garden Journal",
"url": "https://example.com/",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/images/example-garden-journal-logo.png"
}
},
{
"@type": "Blog",
"@id": "https://example.com/blog/#blog",
"name": "Example Garden Journal",
"url": "https://example.com/blog/",
"publisher": { "@id": "https://example.com/#organization" }
}
]
}Replace the @id and mainEntityOfPage URLs with the real address of your post, and swap the headline and description for the words visitors read. Point the three image URLs at real files, replace both dates, and change the Person and Organization details to your own author and publication. Delete dateModified if the post has never been materially changed.
On a live page this JSON sits inside a script element, so the final markup looks like the short wrapper below.
<script type="application/ld+json">
{ "@context": "https://schema.org", "@graph": [ ... ] }
</script>The ... stands for the entities from the full example. If you want to see how the entities refer to each other, the guide to the JSON-LD graph explains @id references in more detail.
Connect the author and publisher
An author reference works best when it points to a real, visible identity. Use a Person for an individual writer and an Organization when the organization itself is the stated author. Show the author's name on the page, and keep the name in the markup identical to the displayed byline.
Google's Article documentation says author.url should link to a page that uniquely identifies the author, such as an author page or biography, and that Google also understands sameAs for authoritative identity references. Give each author a stable @id, and reuse it on every post they write so each one points to the same entity. A generic staff list or an invented author identity does not meet that goal.
If the author page is an internal profile, you can consider ProfilePage structured data for that page. The Person and author schema guide covers author identity in more detail, and the Organization schema guide covers the publisher side. Here, the only job is to make each post point to the right author and publisher.
Set datePublished and dateModified to match the page
Use datePublished for the first publication date and dateModified for the most recent meaningful change. Write both as ISO 8601 values. A timezone is preferred, for example 2026-06-18T14:30:00-05:00, which Google also recommends in its Article documentation.

Keep the dates in the markup consistent with the dates on the page. Do not change datePublished when you refresh an old post, because it records the original publication. Do not update dateModified just because a template, analytics script, navigation element or automated build changed; those do not change the article.
A change is material when the body, the examples, the recommendations or an important fact changed. When it is, show an updated date on the page, update dateModified to match, and consider a short note on what changed if readers would benefit from it. Google says dateModified is the date and time the article was most recently modified, and Schema.org defines it as the date on which a CreativeWork was most recently modified (Schema.org dateModified).
If you cannot tell when the last real change happened, remove dateModified rather than publish a value you know is wrong. A missing optional date is accurate, and an incorrect one is not.
Add the markup on your platform
Before adding anything, view the source of a published post and look for existing article markup. Many themes, SEO plugins and apps already output some. A second block that describes the same post can disagree with the first, so update the existing markup or turn one source off instead of adding another.
On WordPress, the theme or an SEO plugin may already output BlogPosting or Article data, and the exact output differs by theme and plugin. Inspect the live page source and keep one authoritative implementation; the WordPress schema guide walks through that check.
On Shopify, the theme may generate some structured data already, and the output varies by theme, as described in Shopify's help documentation. On Wix, Wix's blog structured data article describes a custom JSON-LD workflow. On Squarespace, inspect the published page source to see whether the template already emits article markup before you add custom code.
Webflow's schema markup guide, updated January 2026, covers adding schema manually, filling it from your CMS fields and avoiding duplicates, and it notes plan and CMS constraints. For Next.js, the JSON-LD guide, updated February 2026, covers rendering JSON-LD and sanitizing it. On a hand-built site, place the script element in the post template so every post gets its own values.
Test the published URL
Test the live post, not only a draft, because platforms and plugins can change what is output. Run the URL through Google's Rich Results Test, or use the Schema Nova validator for a quick syntax and vocabulary check. For pasted code or a page address, the Schema Nova checker reports what its checks find and the scope of those checks.
Then use the Schema.org Validator for vocabulary, and Bing Webmaster Tools if the page is verified there. Bing says it recognizes Schema.org in JSON-LD, Microdata, Microformats, RDFa and Open Graph, and its Webmaster Tools URL Inspection includes markup inspection, including JSON-LD (Bing structured data guidance).
These tools answer different questions. One checks that the JSON parses, another that the vocabulary is right, and another that a specific Google feature's rules are met. None of them tells you whether a page will be shown, which is why a clean result describes the markup and makes no promise about display.
When a validator flags the author or a date, compare the markup with the visible page. A mismatched name, a dateModified earlier than datePublished and a date without a timezone are the usual causes, and the guide to fixing missing-field warnings covers reading the messages.
Make the markup readable for Bing and AI search
Bing recognizes JSON-LD and does not prefer one supported format over another, so the same block serves Google and Bing. DuckDuckGo says most of its traditional links and images are largely sourced from Bing (DuckDuckGo result sources). Yandex offers a semantic markup validator that checks requirements for its own services.
If you want ChatGPT search to be able to surface your posts, OpenAI says OAI-SearchBot is used to surface websites in ChatGPT search results, so check that your robots.txt does not block the crawler, for example:
User-agent: OAI-SearchBot
Allow: /Leave that out, or change it, if you decide to opt out. For the wider question, see whether AI systems use schema markup.
Questions people ask
Should a normal blog post use BlogPosting or Article?
Use BlogPosting for an individual post that is part of a blog. Google accepts Article, NewsArticle and BlogPosting for its Article feature, so the choice should describe the content rather than chase a result.
When should I change dateModified?
Change it when the body, the examples, the recommendations or an important fact has changed in a way a reader would notice. Leave it alone for template changes, analytics scripts or automated rebuilds, and leave datePublished as the original publication date.
Should the author be a Person or an Organization?
Use a Person for an individual writer and an Organization when the organization is the stated author. Whichever you choose, the name in the markup should match the visible byline, and author.url should lead to a page that identifies the author.
Does valid Article schema guarantee a rich result or an AI citation?
No. Google says correct markup does not guarantee a rich result, and no markup guarantees an AI citation. Valid markup describes the page accurately; whether it is displayed or cited is up to each system.
Should I add FAQ schema to a blog post?
A visible FAQ section can still help readers. Google removed its FAQ rich-result documentation in June 2026 because the FAQ rich result was no longer shown in Google Search, so do not expect a Google FAQ display. The FAQ schema guide covers the current position.
