XooCode(){

GameServer

GameServer describes a live multiplayer server hosting a specific VideoGame. Server directories, hosting providers, and game-launch menus publish GameServer to tell consumers which instances are online, how many players are connected, and what game they're running.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/GameServer
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "GameServer",
  "name": "Dunmore East — PvP",
  "game": {
    "@type": "VideoGame",
    "name": "XooQuest: Season 4"
  },
  "playersOnline": 42,
  "serverStatus": "https://schema.org/Online",
  "provider": {
    "@type": "Organization",
    "name": "Dunmore Interactive"
  }
}
</script>

Direct properties (3)

  • game: VideoGame being hosted.
  • playersOnline: current Integer count of connected players.
  • serverStatus: GameServerStatus enum — Online, OnlineFull, OfflineTemporarily, OfflinePermanently.

Often nested inside the VideoGame it hosts via gameServer, or listed independently under a hosting Organization.

Minimal valid version

The smallest markup that still produces a valid GameServer 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/GameServer (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "GameServer",
  "name": "Dunmore East",
  "playersOnline": 42,
  "serverStatus": "https://schema.org/Online"
}
</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 (game-directory / launcher signals)
    Google docs

Common GameServer 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

    serverStatus as free text

    Wrong
    "serverStatus": "online"
    Right
    "serverStatus": "https://schema.org/Online"

    GameServerStatus is a closed enum; use the canonical URL.

  2. 02

    playersOnline updated rarely

    Wrong
    Static playersOnline value stale by hours
    Right
    Recompute on every render or rely on a live endpoint

    Stale counts mislead consumers; directories deprioritise servers whose stats don't match their probes.

  3. 03

    GameServer without game reference

    Wrong
    Server with no game property
    Right
    Always include game (VideoGame reference)

    Without the game, the GameServer can't be filtered into the right game directory.

Schema properties in this example

GameServerIntangibleVideoGamegameplayersOnlineserverStatusGameServerStatusproviderOrganizationname

Also mentioned in 2 other examples

GameServer also appears in GameServerStatus, and VideoGame. See the full GameServer schema page for every reference.

About the example data

A live XooQuest Season 4 PvP server hosted by Dunmore Interactive — "Dunmore East", 42/64 players online, accepting connections.

Comments

Loading comments...

Leave a comment