Data Sources

Where CFBTrack data comes from and what each source category is used for.

CFBTrack mixes curated internal tables with synchronized external feeds and manually reviewed enrichments. Different public pages draw from different source sets, so this page groups the major inputs by the work they support.

What this page covers

  • Curated core tables

    Teams, players, schedules, stadiums, and historical season facts anchor most public pages.

  • Synchronized feeds

    Stats, recruiting, roster, and game-level records are refreshed from supported source pipelines when available.

  • Page-specific enrichments

    Media, video, graphics, and geography surfaces can layer their own focused datasets on top.

Primary source categories

Most CFBTrack pages are built from a small set of repeatable source groups so data can be reused across teams, seasons, and analytics routes without one-off scraping logic on every page.

  • Curated CFBTrack team, player, venue, and conference tables.
  • Synchronized game, roster, stat, and recruiting feeds where coverage is available.
  • Reviewed media, video, and geography datasets for specialized route families.

How sources map to pages

Team pages usually combine program metadata, season records, recruiting, roster, and venue context. Player pages pull from player, roster, usage, and historical season tables. Analytics pages often blend traditional and advanced season stats into a compact route-specific view model.

  • Schedule and game pages prioritize date, venue, and result integrity.
  • Recruiting and transfer pages depend on the availability and freshness of those feeds.
  • Blog and video pages use their own publishing metadata in addition to the core football dataset.

Coverage and attribution

Unless a page states otherwise, CFBTrack public dataset outputs are intended for personal, editorial, and research use with attribution and a link back to the original page. Coverage varies by route, so the page-level data notes remain the most specific source statement.

  • When a page ships a structured-data block, the visible content should still match the public page.
  • Coverage years can differ between route families; check page-level notes when precision matters.
  • Some specialty pages intentionally hide or defer sections when a supporting source is missing.