# Article Schema Markup: Add and Test BlogPosting JSON-LD

> Set up article schema markup with a BlogPosting JSON-LD example. Check authors, dates, images, and your live CMS output before rolling out changes.

Canonical: https://www.getdexseo.com/blog/structured-data-for-seo/article-schema-markup/
Author: Dex SEO, Editorial team
Published: Oct 19, 2026 · Updated: Oct 19, 2026

## Key takeaways

- Choose a schema type that fits the page you actually publish.
- Check existing CMS output before adding another article block.
- Match the headline, byline, dates, and image to the real post.
- Test a few live pages before changing a shared template across the site.

Article schema markup gives search engines a structured description of a post. The useful work is to connect it to the right title, author, dates, and image, then check what your live site sends. A copied code block can be valid while describing the wrong article.

This guide uses a fictional repair blog to show how to set up and review BlogPosting JSON-LD. It covers the article itself; see our [structured data for SEO guide](https://www.getdexseo.com/blog/structured-data-for-seo/) for the wider picture.

## Choose Article, BlogPosting, or NewsArticle

Article is the broad Schema.org type. BlogPosting describes a blog post, while NewsArticle describes a news article. Choose the type that fits the page you publish. A service blog does not become news just because its owner wants more search traffic. If the page sells an item instead of presenting a post, [choose and test Product and Offer data](https://www.getdexseo.com/blog/structured-data-for-seo/product-schema-markup/) for that different purpose.

For our example, a home repair company posts a guide to checking a drafty door. BlogPosting is a sensible fit. The company’s door repair service page has a different job. Do not use the blog template as a shortcut for every page on the site.

Write down the rule for each page template before you change code. That gives your editor and developer the same goal. It also helps avoid small exceptions that no one remembers when the site grows.

## Check the article data your CMS already outputs

Open an existing post and check its rendered markup. Look for Article, BlogPosting, or NewsArticle, including items inside an @graph. A theme or plugin may already create the article data. You may need to correct its source fields rather than add a second block.

Make a simple review sheet with four columns: field, value on the page, value in the markup, and person responsible for a fix. Start with a post whose title or author changed recently. It is a useful case for finding stale values.

If two tools publish different dates or authors for the same post, find which tool owns each output. Follow our [WordPress schema conflict guide](https://www.getdexseo.com/blog/structured-data-for-seo/duplicate-schema-markup-wordpress/) for that diagnosis. Keep useful data while you resolve the mismatch.

## Build a BlogPosting JSON-LD example

The following sample is fictional. The business, writer, dates, links, and image exist only to explain the setup. Replace every example value before using it. The image path should lead to your actual article image.

```
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Check a Drafty Door",
  "image": "https://example.com/images/drafty-door.jpg",
  "datePublished": "2026-10-01T09:00:00-04:00",
  "dateModified": "2026-10-15T11:30:00-04:00",
  "author": {
    "@type": "Person",
    "name": "Taylor Reed",
    "url": "https://example.com/team/taylor-reed/"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Home Repair",
    "url": "https://example.com/"
  }
}
```

A developer can place the JSON object in a script element with type application/ld+json. In a CMS, use the existing article tool where possible. Connect the template to post fields so that each page gets its own values. Do not hard-code this writer or headline into a site-wide setting.

## Match authors to the visible byline

Google’s Article documentation recommends a Person or Organization author, a name, and an identifying URL. Include each visible author separately when there are several. Keep job titles and words such as “written by” out of the author.name value. The publisher has a separate role. For the publisher rather than the writer, [keep the business and publisher identity consistent](https://www.getdexseo.com/blog/structured-data-for-seo/organization-schema-markup/). To review the profile side of that relationship, [connect author profiles to their articles](https://www.getdexseo.com/blog/structured-data-for-seo/person-schema-for-authors/).

For your review sheet, click the byline on the live post. Does it open the right profile? Does that profile make the writer’s role clear? Compare the name with the markup. A staff member’s departure is a good reason to review profile links, not to replace old bylines with whoever manages the site today.

If a team writes under a shared name, document how that byline is assigned. Use a real editorial identity and an accurate type. Do not invent a person to fill a schema field or suggest expertise the team does not have.

## Review dates, headlines, and images together

Google lists headline, image, dates, and authors as recommended properties, with no required Article properties. Dates use ISO 8601; timezone details are recommended. The image should represent the article and be accessible to Google. Correct markup does not guarantee a special search display.

Use the original release date for the first publication. When an editor updates a guide, record what changed in your own notes. That makes it easier to spot a template that resets dates on each visit or assigns the current date to every old post.

Check the headline against the visible article title. Avoid leaving the title of a cloned draft in the markup. Preview the lead image too: the right file URL is not enough if the picture is blank, unrelated, or cropped so tightly that it loses its meaning.

Our image SEO guide covers the wider image review. Here, keep the task narrow: make sure the article data names the right file and that a visitor can see a useful version of it.

## Test one post before changing the whole template

Run your draft code through Google’s Rich Results Test, then test the live URL after release. A local sample cannot show every change a CMS makes when it saves and renders a post. Compare the test output with your review sheet. When checking a complete post template, also [build and test a breadcrumb trail](https://www.getdexseo.com/blog/structured-data-for-seo/breadcrumb-schema/) as a separate item. If Google reports an article issue after release, [fix and validate Search Console schema issues](https://www.getdexseo.com/blog/structured-data-for-seo/structured-data-errors-search-console/) using an affected URL.

Use a small set of cases before a broad rollout: one single-author post, one post with several writers if your site has them, and one older guide with a real update. Check each headline, byline, date, and image. Save the results beside the template change.

For a multilingual blog, add one translated post to that set. Check its title and author links in that language. Do not leave an English headline in the schema of a Spanish page merely because the translation began as a copy.

If the test cannot read the page, check public access first. If it reads an old value, compare the live page with the editor and look for a cached version. Resolve the source of the stale data before making another unrelated code change.

## Use DEX Health for the broader page review

Article schema is one part of a useful post. It cannot repair a weak answer, an unclear heading, or a broken link to the service the reader needs. Review the page as a reader after you finish the code checks.

DEX Health lets you check page quality and SEO, including on the free plan. Use it alongside a dedicated schema test. The Health score helps guide a broader review; it is not proof that Google has accepted your article markup.

After a theme or plugin update, repeat your saved sample checks. Give one person ownership of the article template and one clear route for editors to report wrong data. Explore DEX if you want page checks alongside your content work. Keep the process focused on accurate pages rather than adding code for its own sake.

## FAQ

### Who should fix a wrong author in the markup?

First check the post's author setting and profile. If those are correct, ask the person who owns the template to review how it reads the author data. Fix the source rather than adding a second block.

### Should every post use the same code values?

The structure can be shared, but the values must belong to each post. A common template should read the correct headline, author, dates, and image for the page it serves.

### What should I save after testing?

Keep the sample URLs, expected field values, test results, and date of the change. These notes make it easier to compare output after a theme or plugin update.

## Sources

- [Article structured data](https://developers.google.com/search/docs/appearance/structured-data/article) — Google