WebSite schema

Where to use it

Every page, once, in the sitewide graph.

A complete example

Valid as written, with every required property and the recommended ones that carry real information.

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "@id": "https://www.seoforsolos.com/#website",
  "url": "https://www.seoforsolos.com/example",
  "name": "Acme Reference",
  "publisher": {
    "@id": "https://www.seoforsolos.com/#organization"
  },
  "inLanguage": "en-US",
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://www.seoforsolos.com/search?q={search_term_string}"
    },
    "query-input": "required name=search_term_string"
  }
}

Generate a WebSite node with your own values in the schema generator, and lint what your page actually ships with the schema validator.

Properties

The three mistakes this type attracts

1. 01Adding a SearchAction for a search route that does not exist.
2. 02Omitting publisher, which leaves the site unattached to its organisation.
3. 03Duplicating the node per page without a stable @id.

Related types

• Service
• Review
• AggregateRating
• Person
• ProfilePage
• ImageObject

Where this appears in the playbook

• Structured data: what each type is for and which ones earned their place.
• The schema graph: composing types into one graph with stable identifiers.
• One JSON-LD script per page, holding one @graph
• Stable @id anchors that cross-reference rather than duplicate
• Optional fields are omitted, never emitted as empty strings
• Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.