Sherdog and UFC Stats publish per-bout records with method, round, time, judge scorecards, and significant-strike counts per round. Editors can scrape either source into a sheet with a slug column and JSON columns, or connect SleekRank's REST data source directly to a feed.

Each judge's per-round scores live in a scorecards JSON array. A list mapping renders the scorecards table with judge name, three round scores, and a fight total. Split and majority decisions show all three judges' totals so the disagreement is visible at a glance.

When a positive test or a fence-grab review overturns a result, edit the method column and add a notes JSON array describing the ruling. A conditional selector mapping surfaces an overturned banner on the live page, and the original result moves into a notes block.

Each page carries unique fighters, a unique result, a unique scorecard, and unique schema. The shared structure is the template, not the content. Search engines treat individual fight pages as distinct entities, much like individual game recap pages.

Set cache duration to 600 seconds during a fight night and 86400 outside the event window. Manual flushes via wp rewrite flush handle the case where an editor wants a corrected score live within minutes of an athletic-commission update.

Yes. UFC Stats publishes per-event JSON that maps cleanly to SleekRank's REST data source type. One event fetch returns all bouts for a card. SleekRank caches the JSON and refreshes per the cache duration. Editors do not maintain a sheet.

Add an event column and one column per fighter. Two sibling SleekRank page groups read the same source filtered by event or by fighter and render per-event and per-fighter hubs. The hubs auto-update as new fights land in the source.

Each bout carries a number suffix when rematches happen. Holloway vs Volkanovski 1, 2, and 3 are three distinct slugs. The base slug pattern bakes the version number into the URL so search engines treat each fight as distinct, with cross-links.