Article / BlogPosting Schema Missing

Issue No: 60

Category: Structured Data & Rich Results

Issue type: Issue

Priority: IMPORTANT

Description

Blog posts or news articles are missing Article, BlogPosting, or NewsArticle schema, losing eligibility for Top Stories, Google Discover, and AI citation attribution.

How do we capture it

• Identify pages matching article URL patterns (/blog/, /news/, /articles/)
• Check JSON-LD for Article, BlogPosting, NewsArticle, or TechArticle
• Validate headline, author, datePublished, image

What to store

StructuredDataAudit with schemaType = Article (or detected subtype in detectedSubtype), issueNumber = 58, plus StructuredDataField rows:

Field	Type	Comment
has_headline	boolean	headline property present
has_author	boolean	author with a Person or Organization present
has_date_published	boolean	datePublished in ISO 8601 format
has_date_modified	boolean	dateModified present
has_publisher	boolean	publisher with Organization and logo present

Core audit fields: isPresent, hasImage, rawJson

Condition for trigger

The following rules trigger this issue:

• Trigger Rule 1: Schema absent
  • Target Field: isPresent
  • Evaluation Logic: isPresent = false
  • Severity: CRITICAL
  • Diagnostic Message: "No Article type on article page"
• Trigger Rule 2: Author missing
  • Target Field: has_author
  • Evaluation Logic: has_author = false
  • Severity: CRITICAL
  • Diagnostic Message: "Critical for E-E-A-T"
• Trigger Rule 3: Date missing
  • Target Field: has_date_published
  • Evaluation Logic: has_date_published = false
  • Severity: CRITICAL
  • Diagnostic Message: "Required for freshness signals"
• Trigger Rule 4: Image missing
  • Target Field: hasImage
  • Evaluation Logic: hasImage = false
  • Severity: CRITICAL
  • Diagnostic Message: "Required for Top Stories"

Sources

• Schema.org — Article
• Schema.org — BlogPosting
• Google — Article Structured Data
• Google — E-E-A-T

Long description

Article schema enables eligibility for Top Stories carousel, Google Discover, and AI Overview citations. The author field is critical for Google's E-E-A-T evaluation — without a declared, linkable author, the article lacks a verifiable creator.

Full example:

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Implement Schema in 2024",
  "image": "https://www.example.com/image.jpg",
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "@id": "https://www.example.com/author/jane"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Corp",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.example.com/logo.png"
    }
  },
  "datePublished": "2024-03-01T08:00:00Z",
  "dateModified": "2024-03-15T10:00:00Z"
}

How to Fix

1. Add Article/BlogPosting JSON-LD to all article pages
2. Always include datePublished, dateModified, image, author, publisher
3. Link author to a Person entity via @id for E-E-A-T chain
4. Use ISO 8601 date format with timezone