Schema.org types

A Clog post carries a schemaType field that selects which Schema.org variant the post is — BlogPosting, Recipe, HowTo, Event, Product, Review, and ~45 more. Pages carry a smaller pageType enum. The chosen type drives:

• The fields the dashboard wizard shows in the Post details section (for posts).
• The shape of the structuredData payload Clog validates and stores.
• The structuredBlocks projection Clog derives on read (recipe card / how-to steps / etc. as the 13-block vocabulary).
• The @type and graph of the assembled jsonLd payload on every read response.

This page is the lookup table — pick a row when you need to know the exact @type, what fields the wizard surfaces, and what the JSON-LD looks like.

For the authoring-side walkthrough (the type wizard, smart suggestions, switching types), see SEO → Schema.org variants.

Tier overview

The catalogue ships in three tiers — picking a type is a 3-step wizard (or one Skip click for the default BlogPosting).

Tier 1 — the most-used variants

Tier 2 — specialised subtypes

Tier 3 — long-tail variants

Creative works

Vehicles, accommodation, travel

LocalBusiness subtypes

All inherit LocalBusiness fields (address, telephone, openingHours, etc.) plus a few specialised ones:

Discussion & QA

How a type maps to jsonLd

On every content read response, Clog assembles a Schema.org @graph rooted at the entity's type, with the workspace's publisher Organization (or Person) and a BreadcrumbList (when enabled) as sibling nodes. The shape is:

{
  "@context": "https://schema.org",
  "@graph": [
    { "@type": "<schemaType>", ...entity-typed-data },
    { "@type": "Organization", ...publisher },
    { "@type": "BreadcrumbList", ...trail }
  ]
}

Drop into a <script type="application/ld+json"> tag verbatim. See API → SEO and JSON-LD for the rendering recipe.

The graph's first node is the entity itself, populated from the merge { ...post.structuredData, ...post.seo.schemaData } (per-field override semantics — see SEO → Type-specific SEO overrides). Embedded nodes (Person for the author, MediaObject for images, Place for an Event location) are inlined when relevant.

Page-type variants

Pages carry a smaller pageType enum picked from the page editor's right sidebar. There's no wizard — pick the closest match; WebPage is fine when nothing else fits.

Pages don't carry structuredData — their pageType solely drives the jsonLd @type. If you need rich structured content on a page (a FAQPage with mainEntity[], for example), the workaround in v1 is to author the equivalent as a post — pages are designed to be simpler.

Category, Tag, and Author defaults

Three entity types pin their Schema.org type without a picker:

The Author's person scaffold (jobTitle, worksFor, knowsAbout, alumniOf, awards, honorific prefix/suffix) is edited in the Author drawer's Person section — see Authors → Person (JSON-LD scaffold).

Skipping the type wizard

Clicking Skip on the create-time wizard ships the post as the workspace's defaultPostType (usually BlogPosting). The smart-suggestion banner may later prompt to switch — see SEO → Smart suggestions.

Skipping is the right answer for most posts. The wizard's value is highest for posts that genuinely are how-tos, recipes, reviews, or events — where structured-content rendering and richer SERP previews are worth a minute of authoring effort.

Related

• Dashboard guide → SEO — the wizard, structured-content fields, the live score engine.
• API → SEO and JSON-LD — how the type translates to structuredBlocks + jsonLd on the read response.
• Block types — what structuredBlocks is made of.