Each game gets a row in the meeting_log JSON array with date, home team, away team, score, and venue. A derived view sums wins per team and renders the all-time record card. Editors add one row per new meeting after the game, and the all-time record card updates automatically on the next cache cycle.

Some rivalries (Michigan-Ohio State football, Auburn-Alabama Iron Bowl) have one continuous trophy series. Others (Canadiens-Bruins, with multiple Stanley Cup playoff meetings) carry no single trophy but layered playoff series. A trophies JSON array on each row supports multiple trophy entries with year ranges, and the rendering picks the current holder per era.

Dodgers-Giants started in Brooklyn vs Manhattan, moved to Los Angeles vs San Francisco in 1958, and continues in both cities. A relocations field on each team identifier surfaces a relocation note within the rivalry page so the historical context renders without breaking the modern record card.

Some rivalries (Nebraska-Oklahoma) lost regular-season meetings after conference realignment. A status field on the row can flag the rivalry as dormant, conference-restricted, or active. The base template renders status context so the page does not surface misleading recent-meetings strips for dormant rivalries.

Yes. A multi_league boolean on the row drives a conditional context block for cross-league rivalries. The Manning brothers Peyton-Eli meetings, USC vs Notre Dame in football and basketball, and historical NCAA-NIT championship meetings all render with the right cross-league framing without breaking same-league templates.

Append one row to the meeting_log JSON array with the new game's date, score, and venue, flush the cache, and the page reflects the new all-time record within minutes. The most-recent-meetings strip refreshes from the same array. Editorial can also add a defining_games entry after a particularly notable result, all from the same data feed.

Each page carries two unique team identifiers, a unique all-time record, a unique meeting log, and unique defining-games entries. The shared structure is the template and the schema shape, not the content. Google treats per-rivalry pages as distinct entities, the same way Sports-Reference and Wikipedia treat rivalry articles.

Each generated page carries SportsEvent JSON-LD with the rivalry name, both team SportsTeam shapes, and the most recent meeting as the current event instance. The defining games sit as Dataset markup with citation links. Google's knowledge graph picks up the SportsEvent shape for rivalry queries.