Coverage transparency

Data coverage matrix

This page explains exactly what Kickoff Lens covers today, what is planned for European club football, and which routes stay out of search until they have source-backed data. It is designed to prevent thin placeholders and make the site structure transparent.

The current live dataset is World Cup 2026. The Champions League, Premier League, La Liga, Serie A, Bundesliga, and Ligue 1 sections are indexable theme and methodology pages, not copied fixture databases.

Current World Cup coverage

LayerCoverageIndexing statusNotes
Team dossiers48 national teamsIndexableTeam pages include rank, group or knockout path, radar, squad profile, and source notes.
Player profiles1248 player records; 160 high-signal player URLs in sitemap capSelective indexingLower-signal player routes are not used for sitemap expansion.
Match pages104 match records; 104 indexable match URLsIndexable when resolved or usefulPlaceholder-only match routes are kept out of sitemap until teams are known.
Finished matches102 finished; 0 pending confirmationIndexable archiveRecaps separate final score confirmation from event timeline completeness.
Venue guides16 venue and city recordsIndexableVenue pages explain climate, travel, altitude, roof, and match context.

Club-football coverage status

CompetitionCurrent public layerStatusNext release gate
UEFA Champions League Indexable theme page Theme page live; club dossier schema ready; fixture ingestion pending Club dossiers, matchweek briefs, player context, and recaps stay gated until source-backed fields are complete.
Premier League Indexable theme page Theme page live; club dossier schema ready; fixture ingestion pending Club dossiers, matchweek briefs, player context, and recaps stay gated until source-backed fields are complete.
La Liga Indexable theme page Theme page live; club dossier schema ready; fixture ingestion pending Club dossiers, matchweek briefs, player context, and recaps stay gated until source-backed fields are complete.
Serie A Indexable theme page Theme page live; club dossier schema ready; fixture ingestion pending Club dossiers, matchweek briefs, player context, and recaps stay gated until source-backed fields are complete.
Bundesliga Indexable theme page Theme page live; club dossier schema ready; fixture ingestion pending Club dossiers, matchweek briefs, player context, and recaps stay gated until source-backed fields are complete.
Ligue 1 Indexable theme page Theme page live; club dossier schema ready; fixture ingestion pending Club dossiers, matchweek briefs, player context, and recaps stay gated until source-backed fields are complete.

Five-league maintenance status

The five major league layer now has a machine-readable maintenance status at /data/five-league-maintenance-status.json. It records product areas, source registry coverage, release candidates, sitemap boundaries, and the current release-gated-operational state used by the local automation checks.

Status fieldWhat it provesCurrent publishing effect
product areasEach major league has schedule intelligence, club dossiers, player-role layer, style/radar comparison, and post-match recap lanes.Theme pages can explain a real product structure without generating thin long-tail pages.
source registryEach major league has verification links with allowed use and prohibited use boundaries.Sources are for checking only; official fixture databases, logos, crests, article text, video, and match graphics are not copied.
freshness metadataEvery five-league product area and source registry entry has a checked timestamp, verification state, public evidence note, and refresh policy.Future automation can identify which module is reviewed, release-gated, planned, or blocked before any long-tail URL enters search.
verification stateProduct areas distinguish framework-reviewed, release-gated-not-ingested, candidate-reviewed-noindex, and planned-not-ingested states.Readers and ad-review systems can see that unfinished five-league surfaces are clearly labeled instead of being presented as live fixture pages.
maturity scorecardEach major league has a foundation score, maturity band, release blockers, and long-tail release status.The public page can show progress toward a mature league database while keeping long-tail pages blocked until release gates pass.
foundation scoreThe score measures source freshness, source registry coverage, release-candidate completeness, sitemap boundaries, and public-layer alignment.It is an operational signal, not a claim that club, player, matchweek, or recap pages are ready for indexing.
release candidatesEach major league has one structured club dossier candidate.Candidate club routes stay noindex-until-release-gate and outside the sitemap.
release-gated-operationalThe framework is usable and automatically checked, but long-tail pages still wait for source-backed fields.IndexNow and sitemap submissions keep only mature/indexable routes discoverable.

Source freshness status

The public automation contract now also publishes /data/source-freshness-status.json. It combines World Cup source freshness, event timeline incomplete notes, five-league release-gate state, AdSense public-side readiness, and the latest local maintenance run into one machine-readable file.

Status fieldWhat it provesCurrent publishing effect
fresh-with-known-gapsVerified scores can stay published while missing event timelines are shown as data gaps.The site does not block final scores just because an event timeline incomplete note exists.
World Cup freshnessTracks generated time, temporal update time, ranking update time, finished matches, pending results, and incomplete event timelines.Future agents can decide whether to sync live data, rebuild static pages, or hold for review.
five-league release gatesConfirms product areas, source registry entries, and noindex-only candidate routes remain aligned.Five-league pages can keep maturing without accidentally indexing thin club, player, matchweek, or recap pages.
public-side-ready-review-pendingConfirms AdSense readiness is only a public-site signal, not a private Google approval claim.Review-facing pages stay transparent while account-side Google status remains manually checked.

Indexing policy by route type

Route typeCurrent policyReason
/football-intelligence/, /data-coverage/, /data-dictionary/, /advertising-policy/, /methodology/, /radar/IndexableReader-facing explanation of the product system, field meanings, ad boundaries, and data limits.
/european-leagues/ and /competitions/*Indexable theme pagesContain original league-specific radar, club angles, source boundaries, and release rules.
/clubs/*Noindex prototypesUseful for product structure but not source-backed enough for search indexing yet.
Future club player pagesNoindex until release gateMust contain role, club, availability context, contribution trend, and source note.
Future matchweek pagesNoindex until release gateMust add schedule pressure, table implication, matchup context, and source timestamp.
Future post-match recapsIndexable after confirmationMust include final score, event availability note, table effect, model-read comparison, and correction timestamp.

Release gates

GateMinimum fieldsCurrent route effect
Club dossier club name as text, competition, style profile, radar axes, squad depth note, player-dependency note, source timestamp, rights boundary /clubs/* prototypes remain noindex
Matchweek brief home club, away club, kickoff window, venue or city, table implication, rotation/rest context, strength comparison, source timestamp future matchweek routes stay out of sitemap
Post-match recap final score, result confirmation source, event availability note, table effect, model-read comparison, correction timestamp future recaps require result confirmation and correction trail

Rights and source boundary

Where to go next

Open football intelligence hub Open data field dictionary Open quality standards Open advertising policy Open AdSense readiness report