How to Add Article Structured Data to News and Blog Posts: JSON-LD, Authors and Validation

What Is Article Structured Data?

Article structured data is a block of schema.org markup, usually JSON-LD, that tells search engines a page is an article and states its headline, images, publication and update dates, and authors.

Google supports it on news, blog and sports article pages, and says it “can help Google understand more about the web page and show better title text, images, and date information for the article” in Google Search, Google News and other Google properties (Google Search Central, Article structured data, last updated September 8, 2026). For background on schema markup in general, see our explainer on schema and structured data.

What Article Markup Can and Cannot Do

Article markup describes a page; it does not promote it. Google's documentation is explicit on four points:

• No required properties. “There are no required properties; instead, add the properties that apply to your content.”
• Not needed for Top stories. Google: “there's no markup requirement to be eligible for Google News features like Top stories”. We look at what that means for coverage in does Article markup help coverage rank?
• No guaranteed display. “Google does not guarantee that features that consume structured data will show up in search results.” Google also says it does not guarantee a byline date will be shown (byline dates).
• Not a ranking lever in Google's documentation. Nothing in the Article guide says the markup improves ranking. Google's general guidelines add that a structured-data manual action removes rich-result eligibility but “doesn't affect how the page ranks in Google web search” (General structured data guidelines).

What it does do is state, in a form Google can parse, which page is an article, who wrote it and when it was published or changed.

How to Add Article Structured Data at a Glance

Time: about 30 minutes for one page; a template or CMS change for a whole blog takes longer (our estimate). Tools: a text editor or CMS, the Rich Results Test, Google Search Console. Cost: none. Skill level: beginner to intermediate; editing a site-wide template needs developer access.

What You Need Before Starting

• Access to the page's <head> or article template, or a CMS or SEO plugin that outputs structured data.
• The article's final headline, a visible publication date and, if it has been updated, a visible “last updated” date.
• At least one representative image at a public URL, ideally in three aspect ratios.
• A profile or bio page URL for each author. Our guide to author and expert bylines covers why named authorship matters.
• Your organisation's name and home page URL for publisher; if you already have Organization markup, its @id.
• A verified Search Console property for Step 7.

Step 1: Choose Article, NewsArticle or BlogPosting

Pick the schema.org type that best describes the page. Google says Article objects “must be based on one of the following schema.org types: Article, NewsArticle, BlogPosting”, and supports the same properties for all three.

Why: Google's general guidelines say to “use the most specific applicable type”. Expected result: one type per article page. How to verify: the type describes what the visible page is. Common mistake: marking a product, category or home page as an article; Google says structured data “must be a true representation of the page content.”

Step 2: Add the Headline and Image Properties

Write headline as the article's title and image as one or more image URLs. Google says to consider “a concise title, as long titles may be truncated on some devices.”

Image rules from Google's Article documentation:

• Use images “relevant to the article, rather than logos or captions”, that “represent the marked up content.”
• Image URLs “must be crawlable and indexable”, in a format Google Images supports.
• “For best results”, provide multiple high-resolution images, “minimum of 50K pixels when multiplying width and height”, in 16x9, 4x3 and 1x1 aspect ratios. For example, 1200 × 675 is 810,000 pixels; 300 × 150 is 45,000 and falls short.

Expected result: a headline that matches the visible title and an image array of absolute URLs. How to verify: open each image URL in a private window, and check it is not blocked by robots.txt. Common mistake: using the site logo as the article image.

Step 3: Add datePublished and dateModified

Add datePublished for first publication and dateModified for the most recent change, both in ISO 8601 format with a timezone, for example 2026-10-07T09:00:00-04:00. Google recommends the timezone; without it, Google defaults to the timezone used by Googlebot.

Rules from Google's byline dates guidance:

• Show the date on the page too, labelled with text such as “Published” or “Last updated”.
• Keep visible and structured dates consistent: they must match, though time and timezone can be left out of the visible date.
• “Don't specify future dates, or the date of the action described on the page.” The date is the page's, not the event's.
• If Google picks the wrong date, consider “removing some or all other dates that appear on the page.”

Expected result: two ISO 8601 values that match the visible dates. How to verify: compare the markup with the byline on the rendered page. Common mistake: updating dateModified on every deploy without changing the article. Google's Rich Results Test does not warn about these two properties, so it will not catch it.

Step 4: Mark Up Every Author with name, url and @type

Add an author entry for each person or organisation shown as an author on the page, following Google's author markup best practices:

• Include all authors presented on the page.
• One author per entry. Use an array of separate objects; don't write "name": "Willow Lane, Regula Felix".
• Use @type and url (or sameAs). Google “strongly recommend[s]” both. author.url is “a web page that uniquely identifies the author”, such as a bio or “about me” page; if it is an internal profile page, Google recommends marking it up with profile page structured data.
• Name only in name. No publisher name, job title, honorifics or words like “posted by”. Use jobTitle, honorificPrefix or publisher for those.
• Right type. Person for people, Organization for organisations; never Thing.

Expected result: the markup's authors match the visible byline exactly. How to verify: count bylines on the page and author objects in the code. Common mistake: naming a person in the byline but the company as author in markup. Our explainer do author bylines affect credibility signals? covers what Google says bylines do and do not do.

Step 5: Add the Publisher and Place the JSON-LD on the Page

Add a publisher object for your organisation, then put the complete JSON-LD block in a <script type="application/ld+json"> element on the article page itself. Google recommends JSON-LD among its three supported formats, and says markup belongs “on the page that it describes” (General structured data guidelines). publisher is not in Google's Article property table, but Google's author best practices name it as the place for the publisher's name. If you have Organization markup, reference it by @id; our guide on adding Organization schema markup sets that up.

A complete example for a company blog post:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "@id": "https://example.com/blog/q3-results#article",
  "mainEntityOfPage": "https://example.com/blog/q3-results",
  "headline": "What Our Q3 Customer Survey Found",
  "image": [
    "https://example.com/images/q3-survey-1x1.jpg",
    "https://example.com/images/q3-survey-4x3.jpg",
    "https://example.com/images/q3-survey-16x9.jpg"
  ],
  "datePublished": "2026-10-07T09:00:00-04:00",
  "dateModified": "2026-10-07T09:00:00-04:00",
  "author": [
    {
      "@type": "Person",
      "name": "Willow Lane",
      "jobTitle": "Head of Research",
      "url": "https://example.com/team/willow-lane"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "@id": "https://example.com/#organization",
    "name": "Example Company",
    "url": "https://example.com/"
  }
}
</script>

For a news story, change "@type" to "NewsArticle". For several authors, add one object per author to the author array.

Expected result: the script block appears in the page source, or in the rendered HTML if your site injects it with JavaScript, which Google says it can read. How to verify: view the page source and find the block. Common mistake: leaving comments in the JSON. The Rich Results Test ignores them, but Google says comments are not supported by the JSON-LD standard and “might result in errors in actual usage” (Rich Results Test help).

Step 6: Test the Markup in the Rich Results Test

Run the page through the Rich Results Test. Before publishing, choose Code instead of URL, paste the HTML and click Run test; after publishing, enter the full URL (Rich Results Test help).

What to read: the detected structured data section lists every item found, “whether good, with warnings or errors, or unparseable”; expand an item and click an issue to jump to the code. Google's Article guide says to fix critical errors and to consider fixing non-critical issues, which are not required for rich-result eligibility. For checks beyond Google's features, the Schema Markup Validator tests general schema.org syntax.

Expected result: an Article item detected with no critical errors. How to verify: the tool shows the page “crawled successfully” when testing a URL. Common mistake: testing a page behind a login or firewall; Google says all page resources must be reachable by an anonymous user.

Step 7: Inspect the Live URL in Search Console

Open the URL Inspection tool in Search Console, enter the article URL and click Test live URL. Google's Article guide recommends deploying a few pages first and using this tool “to test how Google sees the page”, making sure the page is not blocked by robots.txt, noindex or a login.

What to check: the page is indexable, and the Enhancements section shows the structured data Google found. If the page looks right, you can click Request indexing; for many pages, Google recommends submitting a sitemap instead (see how to submit a sitemap to Google and Bing).

Expected result: an indexable page with its structured data detected. How to verify: re-inspect after Google recrawls; Google says it “may take several days after publishing a page for Google to find and crawl it.” Common mistake: inspecting a URL outside your property; for those, use the Rich Results Test.

How to Verify It Worked

• Rich Results Test: the URL test detects the Article item with no critical errors.
• URL Inspection: the live test reports the page as indexable and lists the structured data under Enhancements.
• Page source: one application/ld+json block with the right @type, and dates and authors that match the visible byline.
• Search Console reports: no new entries for the page in the Unparsable structured data report (it appears only if Google finds structured data it cannot parse), and no structured-data issue in Manual Actions.
• Search results: optional, and not proof either way. Google may or may not show the title, image or date you marked up.

How to Choose a Markup Method

Common Problems and Fixes

What Not to Do

• Do not mark up content readers can't see. Consequence: Google's quality guidelines forbid it, and violations can block rich results or be treated as spam. Correction: describe only what is on the page.
• Do not put several authors in one name. Consequence: Google cannot tell the authors apart. Correction: one object per author.
• Do not set future dates or the date of the event described. Consequence: Google's byline-date guidance is broken. Correction: use the page's publication and update dates.
• Do not impersonate a person or organisation. Consequence: Google forbids misrepresenting “ownership, affiliation, or primary purpose”, and can apply a manual action. Correction: list only real authors and your own organisation as publisher.
• Do not block the page from Googlebot. Consequence: Google cannot read the markup. Correction: no robots.txt block, noindex or login on marked-up pages.
• Do not add markup expecting higher rankings. Consequence: misplaced effort. Correction: treat it as accurate labelling, alongside good content and clear bylines.

Frequently Asked Questions

Sources and Methodology

This guide is built from Google Search Central documentation, Search Console Help and schema.org type definitions, read on October 7, 2026. We checked that the JSON-LD example parses as valid JSON; we did not run it through the Rich Results Test or deploy it, so we make no claim about how Google displays it. The time estimates are ours. Google's documentation does not say Article markup affects ranking, and we found no Google statement that it does. Interface labels are quoted from Google's help pages on that date and may change.

1. official Google Search Central, Article (Article, NewsArticle, BlogPosting) structured data, last updated September 8, 2026. Types, recommended properties, image rules, author best practices, troubleshooting. Read October 7, 2026.
2. official Google Search Central, General structured data guidelines, last updated July 10, 2026. Read October 7, 2026.
3. official Google Search Central, Introduction to structured data markup in Google Search. Formats and JSON-LD. Read October 7, 2026.
4. official Google Search Central, Influence your byline dates in Google Search. Read October 7, 2026.
5. official Search Console Help, Rich Results Test. Read October 7, 2026.
6. official Search Console Help, URL Inspection tool. Read October 7, 2026.
7. official Search Console Help, Unparsable structured data report. Read October 7, 2026.
8. official schema.org, Article, NewsArticle and BlogPosting. Read October 7, 2026.