Jake Labate

Schema Page Types

Real pages use several rich result features at once. These builders produce the whole connected graph for the most common kinds of page, linked by @id and validated.

Why Page Types

Each framework in the collection covers one Google feature. A real page uses several at once: a product page needs the product, its variants, its offers, the store's return and shipping policies, the brand and the breadcrumb, all pointing at each other.

Getting those links right is where most markup goes wrong. Nodes get repeated with slightly different details, policies are copied onto every product, and nothing says the author of one article is the same person as the author of the next.

These pages show the whole picture for the most common kinds of page. Each has one builder that produces the full connected graph, the input it ran on, the output, and the validator's verdict.

One Graph Across The Site

The page types share one design: define a thing once, where it belongs, and point at it everywhere else.

  • The homepage defines the Organization, the WebSite and the store-wide policies, each with a stable @id.
  • Product pages reference the Organization as seller and price against loyalty tiers by @id; the store-wide return and shipping policies cover every offer.
  • Article pages reference the Organization as publisher and use the author's profile page @id, so every article names the same person.
  • Location pages point at the Organization as parentOrganization, so many stores read as one brand; job postings and events use the store's @id as their location.
  • Recipes and articles share the author's Person @id, and forum threads point at the product they ask about.

Page Types

All 8 use the same example store, Harbor & Pine, so the @id links line up from one page to the next.