PublicationIssue

PublicationIssue is a CreativeWork subtype for a single issue of a serial: "Issue 2" of a quarterly journal's 2026 volume, a specific Monday morning newspaper edition, a numbered trade magazine issue. It adds 4 properties: issueNumber, pageStart, pageEnd, and pagination. Its only subtype is ComicIssue.

Issues usually chain up via isPartOf to their PublicationVolume, and down via hasPart to the articles inside (ScholarlyArticle, NewsArticle, or bare Article). Scholarly indexers (CrossRef, Google Scholar) read the Article → Issue → Volume → Periodical chain to resolve citations.

Full example of schema.org/PublicationIssue json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional

schema.org/PublicationIssue

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PublicationIssue",
  "issueNumber": 2,
  "datePublished": "2026-06-15",
  "isPartOf": {
    "@type": "PublicationVolume",
    "volumeNumber": 3,
    "datePublished": "2026",
    "isPartOf": { "@type": "Periodical", "name": "Xoo Code Quarterly", "issn": "2693-0000" }
  },
  "pageStart": 149,
  "pageEnd": 310,
  "hasPart": [
    {
      "@type": "ScholarlyArticle",
      "headline": "Canonical JSON-LD patterns for e-commerce Product-Offer-AggregateRating hierarchies",
      "pageStart": 152,
      "pageEnd": 174,
      "author": { "@type": "Person", "name": "Dr. Priya Chen", "affiliation": "Xoo Code Research" }
    }
  ]
}
</script>

Minimal valid version

The smallest markup that still produces a valid PublicationIssue entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/PublicationIssue (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PublicationIssue",
  "issueNumber": 2,
  "datePublished": "2026-06-15",
  "isPartOf": { "@type": "PublicationVolume", "volumeNumber": 3 }
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

No dedicated rich result (used by scholarly indexers)
Google docs

Common PublicationIssue mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

01
Issue number with prefix text
Wrong
```
"issueNumber": "Issue 2" or "No. 2"
```
Right
```
"issueNumber": 2 (integer) or "issueNumber": "Winter 2026" (Text for themed issues)
```
issueNumber accepts Integer or Text. Plain integers are preferred; reserve Text for genuinely non-numeric labels ('Winter 2026', 'Special Edition'). Prefixes like 'Issue ' belong to the renderer, not the data.
02
Flattening the Article-Issue-Volume-Periodical chain
Wrong
```
ScholarlyArticle with publisher = journal name and no isPartOf
```
Right
```
Chain Article → PublicationIssue → PublicationVolume → Periodical via isPartOf for each
```
Scholarly indexers parse the full serial hierarchy. Flattening it into publisher loses the volume, issue, page-range, and ISSN links that make citations resolvable.

Schema properties in this example

PublicationIssue CreativeWork issueNumber datePublished isPartOf PublicationVolume volumeNumber Periodical name issn pageStart pageEnd pagination hasPart ScholarlyArticle headline author Person affiliation ComicIssue

About the example data

Issue 2 (June 2026) of the Xoo Code Quarterly, volume 3, containing six scholarly articles across pages 149-310.

Comments

Loading comments...