Article schema markup: a complete BlogPosting example

Check whether your blog already creates Article markup

Before installing a plugin or pasting a snippet, open an existing article's page source and search for application/ld+json. Look for Article, BlogPosting or NewsArticle.

You may find a graph containing several items, such as the publication, breadcrumbs and the article. Several items are not inherently a problem. The problem is when two systems describe the same article with conflicting headlines, authors or dates.

Write down what supplies the current markup: the publishing platform, theme, SEO plugin or custom code. Choose one maintained source for the article's facts before adding another.

If your existing system already outputs correct article data, use its fields. Adding a second copy is not an improvement by itself.

Choose the type that describes the page

Google's Article documentation supports Article, NewsArticle and BlogPosting. It currently lists recommended Article properties rather than a set of required properties.

For a normal business blog tutorial, BlogPosting is a sensible descriptive choice. A service landing page is not automatically a blog post because someone added a publication date. Reserve news-specific labeling for actual reporting.

The schema.org BlogPosting definition describes the vocabulary. Google's feature documentation describes what Google supports. Those are related references, but they do not make every schema.org field a Google ranking requirement.

Map the visible article before writing JSON-LD

Consider an invented example: a print shop publishes a guide called “How to prepare a banner print file.”

This exercise catches errors a JSON parser cannot: a technically valid string can still identify the wrong author or an image that does not exist.

Author and publisher are separate roles. An organization can author an article; do not manufacture a person, job title or credential to complete a field. Put the author's name in the name field rather than appending “written by” or a role.

A complete illustrative BlogPosting object

The following JSON-LD object matches the invented fact sheet. The domain, image, organization and article are examples. Replace every example value with the real visible information before using it.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "@id": "https://example.com/blog/banner-artwork#article",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/blog/banner-artwork"
  },
  "headline": "How to prepare a banner print file",
  "description": "Prepare banner artwork, check the file and approve the proof before production.",
  "datePublished": "2026-10-15T09:00:00-05:00",
  "dateModified": "2026-10-20T10:30:00-05:00",
  "author": {
    "@type": "Organization",
    "name": "Example Print Editorial",
    "url": "https://example.com/about#editorial"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Print",
    "url": "https://example.com/"
  },
  "image": {
    "@type": "ImageObject",
    "url": "https://example.com/images/banner-artwork-checklist.jpg",
    "width": 1200,
    "height": 800
  },
  "inLanguage": "en-US",
  "isAccessibleForFree": true
}

In an HTML implementation, JSON-LD is placed inside a script element with type="application/ld+json". If your CMS generates the wrapper, follow its interface rather than nesting another script inside its JSON field.

JSON requires double quotes, no trailing commas and no explanatory comments. Keep instructions outside the code. The fragment above is an illustrative object, not a claim that example.com hosts this article or that Google has approved it.

Treat images and dates as real editorial facts

Use a representative article image that exists, loads successfully and is accessible to crawlers. An author avatar is a portrait of the byline, not automatically the main image of an unrelated tutorial.

Google's structured data guidelines require markup to represent the page. Do not invent an image URL or describe hidden content just to make a tool look more complete. Add the image when the article actually has an appropriate one.

For dates, preserve the original publication and record a modification when the article meaningfully changes. Google's publication-date guidance recommends consistency between visible dates and structured dates. Include the correct timezone instead of guessing what an unqualified timestamp means.

For the invented guide, adding a new file-preparation method would justify a revision. Rebuilding the website with unchanged text would not. Apply the same discipline to the page's sitemap modification date.

Validate the code and the deployed page separately

First, use Google's Rich Results Test with the code you intend to publish. Resolve syntax errors, review detected items and assess recommendations against the real page.

Then publish through your normal process and test the public URL. Check that the deployed source contains the intended object, not an older cached version or both the old and new implementations.

A practical page comparison is:

1. The H1 and headline describe the same article.
2. The byline and author identity agree.
3. The visible publication and update dates agree with their timestamps.
4. The image URL loads the intended asset.
5. The canonical and article URL identify the preferred version.
6. The page is accessible in its intended publication state.

Use URL Inspection for Google's view of an eligible public page. A local syntax check cannot establish that Google has fetched the deployed version.

Troubleshoot the mismatch, not just the warning count

The last case matters: Google's general guidelines do not promise a rich result even for valid markup.

Does Article schema improve AEO?

Article markup is a useful way to describe an article accurately. Treat it as part of a sound publishing system, not a guarantee that an assistant will quote the page.

If the article's explanation is vague, correct markup will still describe a vague article. Pair the technical setup with a complete answer and worked example, then make the page discoverable through relevant internal links.

Your deliverable is a verified agreement between the article readers see and the facts machines receive. Keep that agreement intact when the content, author, image or dates change.