XooCode(){

ComicStory

ComicStory is a CreativeWork subtype for any indivisible, re-printable unit of a comic: a single interior story, a variant cover, a backmatter piece. It adds the 5 core comics creative-team properties:

  • penciler (Person): Drew the primary narrative artwork.
  • inker (Person): Traced over the pencils in ink.
  • colorist (Person): Added colour to the inked drawings.
  • letterer (Person): Added lettering, speech balloons, and sound effects.
  • artist (Person): Primary artist for media other than pencils/line art (often used when the other specific roles do not apply).

Its only subtype is ComicCoverArt. Stories link up to their ComicIssue via isPartOf.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/ComicStory
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ComicStory",
  "name": "The Lost Property",
  "datePublished": "2025-02-01",
  "isPartOf": { "@type": "ComicIssue", "issueNumber": 4, "isPartOf": { "@type": "ComicSeries", "name": "Tag Cloud Heroes" } },
  "author": { "@type": "Person", "name": "Jane Xoo" },
  "penciler": { "@type": "Person", "name": "Lena Vasquez" },
  "inker": { "@type": "Person", "name": "Rahul Singh" },
  "colorist": { "@type": "Person", "name": "Priya Chen" },
  "letterer": { "@type": "Person", "name": "Nora Lindgren" },
  "pageStart": 3,
  "pageEnd": 22
}
</script>

Minimal valid version

The smallest markup that still produces a valid ComicStory 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/ComicStory (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ComicStory",
  "name": "The Lost Property",
  "author": { "@type": "Person", "name": "Jane Xoo" },
  "penciler": { "@type": "Person", "name": "Lena Vasquez" }
}
</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.

Common ComicStory 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.

  1. 01

    Stacking all credits on a single 'creator' property

    Wrong
    "creator": [penciler, inker, colorist, letterer]
    Right
    Separate penciler, inker, colorist, letterer properties; use creator for the overall creative team or lead

    Comics have specific, indispensable roles. Collapsing them to 'creator' loses the craft. Use the specific properties so credits render correctly and royalty systems can identify contributors.

  2. 02

    Using ComicStory for the cover

    Wrong
    ComicStory for a standalone cover
    Right
    ComicCoverArt (the ComicStory subtype) for covers

    ComicCoverArt is the specific subtype for cover images. It carries the same creative-team properties plus cover-specific semantics.

Schema properties in this example

ComicStoryCreativeWorknamedatePublishedisPartOfComicIssueissueNumberComicSeriesauthorPersonpencilerinkercoloristlettererartistpageStartpageEndComicCoverArt

About the example data

"The Lost Property", the lead story in Tag Cloud Heroes #4, written by Jane Xoo with pencils by Lena Vasquez.

Comments

Loading comments...

Leave a comment