Verified factual records
100%- Coverage
- 3,232 / 3,232
- Gate
- Core signal
- What it means
- Race entities with at least one verified event, race or course fact from a stored source.
Loading
Loading data coverage
A live coverage report for the running race dataset. This page separates sourced facts, derived route geometry, scoring, cost modelling, finisher distribution and reviewed summaries so missing signals are visible.
Freshest data as of| Signal | Coverage | Gate | What it means |
|---|---|---|---|
| Verified factual records | 100% 3,232 / 3,232 | Core signal | Race entities with at least one verified event, race or course fact from a stored source. |
| Race-character enrichment | 100% 3,232 / 3,232 | Informational | Structured scenery, terrain, atmosphere, elevation or record fields derived from verified facts. |
| Course geometry | 46% 1,474 / 3,232 | Informational | Race entities with a stored route trace from a verified downloaded route geometry source. Coordinates are never invented. |
| Elevation and GAP profile | 25% 806 / 3,232 | Informational | Race entities with derived ascent, grade buckets and GAP factor from elevation-bearing geometry. |
| Cost model | 7% 217 / 3,232 | Informational | Race entities with a modelled total cost to the start line. Travel and lodging remain labelled estimates. |
| Latest finisher count | 1% 32 / 3,232 | Informational | Race entities with an organiser/result-source finisher count on the latest edition record. |
| Aggregate finisher distribution | 0% 5 / 3,232 | Quality gate | Race entities with aggregate-only median/percentile finish-time distribution. Individual finisher rows are not stored. |
| Overall score | 0% 0 / 3,232 | Quality gate | Race entities with a composite score computed by the published methodology. |
| PB potential score | 0% 5 / 3,232 | Quality gate | Race entities with PB-potential scoring from course, field and conditions inputs. |
| Publishable race summaries | 85% 2,763 / 3,232 | Quality gate | Race entities with summary copy that passes grounding, contradiction, freshness, methodology, helpfulness and originality gates; tier-1 pages still require human review. |
These gates are the minimum production-readiness checks used by `/readyz`. A blocked row means the public site must continue presenting the affected signal as unavailable rather than implying complete coverage.
| Gate | Status | Current / required | Remediation owner |
|---|---|---|---|
| Overall score coverage | Blocked | 0 / 1 | Run the scoring pipeline after prerequisite route, cost, conditions and field signals are populated. |
| PB potential coverage | Ready | 5 / 1 | Populate PB-potential inputs and rerun scoring so speed-course comparisons can publish a score. |
| Aggregate finisher distribution coverage | Ready | 5 / 1 | Import aggregate-only finisher distributions from result sources; do not store individual finisher rows. |
| Publishable race summaries | Ready | 2,763 / 1 | Generate source-grounded race summaries, publish only copy that passes all copy gates, and keep tier-1 pages on human review. |
Composite race scores publish only when every required source-backed input is present. This table separates the missing inputs from the score display state, so a pending score does not imply a hidden or unpublished ranking.
| Input or gate | Coverage | Supports | What unlocks it |
|---|---|---|---|
| Course profile | 25% 806 / 3,232 | PB potential + composite score | Derive GAP and route-gradient profiles from elevation-bearing verified route geometry. |
| Finisher distribution | 0% 5 / 3,232 | PB potential + composite score | Import aggregate-only finish-time distributions from result sources. |
| Race-day conditions model | 94% 3,035 / 3,232 | PB potential + composite score | Populate typical race-day temperature, precipitation or wind inputs. |
| Entry-fee input | 7% 217 / 3,232 | Value + composite score | Import organiser-published entry fees or reviewed cost-model inputs. |
| Reputation aggregate | 0% 0 / 3,232 | Organisation + composite score | Populate aggregate reputation inputs without storing individual review text. |
| PB-potential publication gate | 0% 5 / 3,232 | PB potential score | All course profile, finisher-distribution and conditions inputs must be present. |
| Composite-score publication gate | 0% 0 / 3,232 | Overall 0-100 score | All PB inputs plus entry-fee and reputation aggregate inputs must be present. |
| Inputs complete; score not published | 0% 0 / 3,232 | Operational score recompute | Run the scoring pipeline for races whose source-backed inputs are complete but no composite score is stored. |
| Published composite score | 0% 0 / 3,232 | Public score display | Composite scores publish only when the current score row and every publication prerequisite pass. |
These counts show the active race summaries that can participate in public sort, filter and comparison surfaces, including elevation grade, GAP, ascent, cost and scenery features.
| Signal | Coverage | Used by | Remediation |
|---|---|---|---|
| Mapped route | 46% 1,474 / 3,232 | Route-evidence filters, race maps, comparison evidence chips | Run verified route-geometry discovery and ingest official GPX/KML/route JSON candidates. |
| Elevation profile | 25% 806 / 3,232 | Elevation filters, GAP/ascent/grade ranking, elevation charts | Derive profiles from elevation-bearing geometry or source official elevation data where allowed. |
| Flat grade share | 25% 806 / 3,232 | Flattest by grade share sort, flat race facets | Populate grade buckets from verified elevation geometry. |
| GAP factor | 25% 806 / 3,232 | Lowest GAP factor sort, PB/course-speed comparisons | Derive GAP factors from trusted elevation profiles. |
| Total ascent | 25% 806 / 3,232 | Lowest ascent, most ascent and hilly-course sorts | Derive ascent from elevation-bearing geometry and review outliers. |
| Climbing density | 25% 806 / 3,232 | Most climbing per km sort, climb-density filters and head-to-head comparisons | Derive total ascent from trusted profiles; density is calculated from ascent and official race distance. |
| Total descent | 25% 806 / 3,232 | Most descent sort and minimum-descent filters | Derive descent from elevation-bearing geometry and review outliers. |
| Net elevation | 25% 806 / 3,232 | Net-downhill sort and signed net-elevation filters | Derive start/finish elevation deltas from trusted elevation profiles. |
| Max absolute grade | 25% 806 / 3,232 | Steepest grade sort and advanced grade filters | Derive max grade from sampled elevation profiles and keep sanity clamps active. |
| Entry fee | 7% 217 / 3,232 | Lowest entry fee sort, race cards, cost comparison | Import official entry-fee facts or organiser registration prices. |
| Estimated true cost | 7% 217 / 3,232 | Lowest true cost sort, cost calculator, value comparisons | Run the cost model once entry, travel and lodging prerequisites are populated. |
| Overall score | 0% 0 / 3,232 | Best overall sort, featured ranking, comparison tables | Run scoring after route, cost, field, condition and character inputs clear gates. |
| PB potential | 0% 5 / 3,232 | Best PB potential sort, PB predictor, course-speed comparisons | Populate PB model inputs and rerun scoring. |
| Beginner score | 0% 5 / 3,232 | Best for beginners sort and beginner-friendly comparisons | Populate support, field, cutoff, terrain and logistics signals, then rerun scoring. |
| Conditions score | 94% 3,035 / 3,232 | Best race-day conditions sort, finder priority and conditions-led comparisons | Populate typical race-day temperature, wind and rain inputs, then rerun scoring. |
| Scenic score | 94% 3,041 / 3,232 | Most scenic sort and scenic race comparisons | Review scenery facts and source-grounded race-character enrichment. |
| Race date | 95% 3,063 / 3,232 | Next race date sort, upcoming filters, event timing chips | Import latest edition dates from organiser or registration pages. |
| Terrain tags | 75% 2,427 / 3,232 | Terrain filters, race cards, comparison context | Extract and review terrain facts from official course descriptions. |
| Scenery tags | 100% 3,232 / 3,232 | Scenery filters, scenic comparisons, race-character panels | Extract and review scenery facts from route/course descriptions. |
raceindex.org publishes a segmented XML sitemap and crawler discovery metadata. These checks describe whether canonical URLs are discoverable or ready for search-engine submission; they do not report whether any URL has been crawled, indexed, ranked or shown in search results.
| Surface | Status | What it means |
|---|---|---|
| XML sitemap index | Published | 31 sitemap segments expose 8,291 unique canonical URLs for crawler discovery. |
| robots.txt sitemap pointer | Published | The crawler policy advertises https://raceindex.org/sitemap.xml as the sitemap index. |
| llms.txt sitemap listing | Listed | The AI-readable discovery file is included in the sitemap URL set. |
| Duplicate sitemap URL guard | Clear | 0 duplicate URL entries were found across generated sitemap segments. |
| IndexNow notification set | Batch-ready | 8,291 same-origin sitemap URLs fit into 1 IndexNow batch at the 10,000-URL protocol limit. Endpoint receipt is not an indexing guarantee. |
| Bing Webmaster URL batches | Batch-ready | 8,291 sitemap URLs would submit in 17 Bing Webmaster batches once account verification and the API key are configured. |
| Google Search Console sitemap | Ready | https://raceindex.org/sitemap.xml is published for manual URL-prefix property submission; this site-side check does not confirm Google crawl or index status. |
These counts classify the same sitemap-listed canonical URLs by useful page family. They prove crawl-surface composition, not third-party indexing or traffic.
| URL family | Canonical URLs | What this proves |
|---|---|---|
| Race entity pages | 3,232 | Event-distance race pages carrying source-backed facts, route evidence and provenance. |
| Event hubs | 949 | Event hub pages grouping sibling race distances and shared event-level evidence. |
| Distance catalogue hubs | 13 | Clean distance landing pages for marathon, half marathon, 10K, 5K and other race discovery. |
| Route-map collections | 485 | Verified-route collection pages built only from races with stored route geometry. |
| Elevation-profile collections | 31 | Collection pages for races with publishable elevation, ascent and GAP profile evidence. |
| Ranking and facet pages | 141 | Qualifying ranking pages for route, value, conditions, date, region and character intent. |
| Cut-off time guides | 7 | Running race cut-off time guide pages built only from source-backed race-edition cutoff data. |
| First-race guides | 4 | First-race planning pages built from source-backed cut-off, route and entry signals. |
| Walker-friendly guides | 2 | Walker-friendly marathon and half marathon candidate pages built from source-backed generous cut-offs and route evidence. |
| Qualifier guides | 1 | Boston qualifier marathon planning pages built from source-backed qualifying status and route evidence. |
| Calendar guides | 1,649 | Source-date month, season, year, date-distance, date-place and date-place-distance running race guides. |
| Place guides | 402 | Region, city and non-UK location guide pages built from source-backed place data. |
| Comparison pages | 187 | Curated comparison hub and head-to-head race decision pages. |
| Race-character guides | 274 | Terrain, scenery, atmosphere and elevation-character guide pages backed by race-character evidence. |
| Decision tools | 3 | Clean canonical tool pages for race finding, PB prediction and race cost planning. |
| Trust and methodology pages | 10 | Coverage, methodology, evidence, answer, sitemap, robots and AI-readable discovery pages. |
| Enabled vertical pages | 898 | Cycling and triathlon pages when those verticals are enabled. |
| Other canonical pages | 3 | Canonical URLs outside the primary running-race SEO portfolio families. |
These route-readiness figures use active race entities as the denominator so discontinued races do not hide operational gaps. Candidate discovery and durable no-route attempt logs are tracked by the geometry audit pipeline; this public table keeps the mapped-route denominator separate.
Browse public route-map collections built only from stored route geometry
| State | Count | What it proves |
|---|---|---|
| Stored route geometry | 46% 1,474 / 3,232 | Active race entities with at least one stored route trace from a fetched route geometry source. |
| Mapped or route-reviewed | 100% 3,232 / 3,232 | Active race entities that either have stored route geometry or have a durable no-route attempt log for the missing distance. |
| Elevation-bearing geometry | 35% 1,133 / 3,232 | Active race entities whose stored geometry includes raw elevation values suitable for profile derivation checks. |
| Derived geometry profile | 25% 806 / 3,232 | Active race entities with a current or legacy derived ascent, grade-bucket and GAP profile. |
| Stated elevation character | 53% 1,719 / 3,232 | Active race entities with organiser/source-derived elevation character, even when full GPS geometry is unavailable. |
| No stored route geometry | 54% 1,758 / 3,232 | Active race entities with no stored route trace yet. This does not prove no official route exists. |
| Missing route reviewed | 100% 1,758 / 1,758 | Missing-geometry race entities whose official route sources have been checked and recorded in durable attempt logs. |
| Missing route unreviewed | 0% 0 / 1,758 | Missing-geometry race entities without an applicable durable route-attempt log. This should stay at zero during maintenance. |
| Geometry without raw elevation | 11% 341 / 3,232 | Active race entities with stored coordinates but no raw elevation-bearing geometry row. |
| Elevation geometry missing profile | 10% 327 / 3,232 | Active race entities with elevation-bearing geometry but no derived profile currently published. |
| Missing mapped sibling races | 5% 175 / 3,232 | 116 active events have at least one mapped race and at least one unmapped sibling distance. |
| Distance | Mapped | Missing route reviewed | Elevation-bearing geometry | Derived profile | Missing geometry |
|---|---|---|---|---|---|
| Half Marathon | 379 / 821 (46%) | 442 / 442 (100%) | 285 / 821 (35%) | 191 / 821 (23%) | 442 / 821 (54%) |
| 5K | 210 / 601 (35%) | 391 / 391 (100%) | 156 / 601 (26%) | 97 / 601 (16%) | 391 / 601 (65%) |
| 10K | 231 / 560 (41%) | 329 / 329 (100%) | 178 / 560 (32%) | 111 / 560 (20%) | 329 / 560 (59%) |
| Marathon | 256 / 469 (55%) | 213 / 213 (100%) | 192 / 469 (41%) | 138 / 469 (29%) | 213 / 469 (45%) |
| Ultramarathon | 151 / 260 (58%) | 109 / 109 (100%) | 119 / 260 (46%) | 110 / 260 (42%) | 109 / 260 (42%) |
| Relay | 111 / 211 (53%) | 100 / 100 (100%) | 88 / 211 (42%) | 65 / 211 (31%) | 100 / 211 (47%) |
| Other | 81 / 182 (45%) | 101 / 101 (100%) | 69 / 182 (38%) | 60 / 182 (33%) | 101 / 182 (55%) |
| 10 Mile | 16 / 34 (47%) | 18 / 18 (100%) | 15 / 34 (44%) | 10 / 34 (29%) | 18 / 34 (53%) |
| 5 Mile | 9 / 24 (38%) | 15 / 15 (100%) | 7 / 24 (29%) | 5 / 24 (21%) | 15 / 24 (63%) |
| 8K | 9 / 22 (41%) | 13 / 13 (100%) | 7 / 22 (32%) | 5 / 22 (23%) | 13 / 22 (59%) |
| 12K | 10 / 20 (50%) | 10 / 10 (100%) | 8 / 20 (40%) | 7 / 20 (35%) | 10 / 20 (50%) |
| 15K | 10 / 17 (59%) | 7 / 7 (100%) | 8 / 17 (47%) | 7 / 17 (41%) | 7 / 17 (41%) |
| Mile | 1 / 11 (9%) | 10 / 10 (100%) | 1 / 11 (9%) | 0 / 11 (0%) | 10 / 11 (91%) |
These quality-gated signals currently have zero coverage and are not implied on race pages until populated:
Coverage counts come from the same read layer that renders public pages. Route geometry follows the no-fabrication rule: stored trackpoints must come from a fetched route geometry source, while pages display unavailable values as unavailable rather than inferred.
This coverage page lists 1,474 of 3,232 active race entities with stored route geometry. Public route-map collections include only those stored-geometry races.
No. Missing route geometry means raceindex.org has not stored a route trace for that race entity. If official route sources have been checked without a fetchable route, the race is counted as missing route reviewed rather than treated as mapped.
Score and ranking surfaces stay unavailable until the required source-backed route, cost, conditions, finisher, reputation or copy gates are populated. The score publication bottleneck table shows which input is missing instead of publishing placeholder scores.
The methodology page explains the route-profile, scoring, cost and copy-grounding rules; the coverage tables here show the current counts produced by the same read layer that renders public race pages.
No. Sitemap-listed URLs are the canonical URLs raceindex.org exposes for crawler discovery and search-tool submission. They do not prove that Google or Bing has crawled, indexed, ranked or shown those URLs in search results.