For roughly two decades, small football websites have filled their pages with score tables they did not produce. The mechanism is an embeddable widget: a compact page hosted elsewhere, dropped into a frame on the host site, updating itself. This page explains what those widgets are, how the arrangement works for both sides, and what to check before adding one.
Please note: this page is a reference article. It is not a widget, it does not provide live scores or a data feed, and there is nothing here to embed.
What a widget actually is
A score widget is a stripped-down web page designed to be displayed inside another page. It carries no navigation of its own, minimal styling, and a single function: show current matches and update as they change. The host site includes it with a small snippet of markup, usually a frame element sized to fit a column, and the widget does the rest.
From the host's point of view this is close to free content: no data licence to negotiate, no scoring operation to run, no maintenance. From the provider's point of view it is distribution — the widget carries the provider's presentation into thousands of pages it would never otherwise reach.
What each side is really trading
The bargain is not complicated but it is often unexamined. The host gains function it could not build. It gives up control of a rectangle of its own page: the provider decides what appears there, can change it without notice, and can stop serving it entirely. If the widget goes away, the host has a hole where its scores used to be and no archive of what was shown.
The host also inherits the widget's performance. A slow or heavy embedded page slows the page containing it, and a widget that polls continuously consumes the visitor's data allowance as well as the host's goodwill.
What to check before embedding anything
- Who is behind it. An embed is a standing invitation to run someone else's page inside yours. Identify the operator before accepting it.
- What it loads. Widgets can pull in further resources — advertising, trackers, analytics — that the host never agreed to and which appear to visitors as the host's own.
- Whether it is secure. A widget served without transport security will be blocked or downgraded on a secure host page, often silently.
- How it behaves on a phone. A dense score table sized for a desktop column is frequently unusable on a narrow screen, and fixed-height frames clip content rather than scrolling.
- What happens when it stops. Every embed eventually stops. A visible fallback is worth the ten minutes it takes to write.
Feeds, APIs and the licensing layer
Widgets sit at the free end of a commercial spectrum. Above them are structured data feeds, licensed per competition and per use, priced according to latency: near-instant data is expensive and tightly contracted, while data delayed by a few minutes is far cheaper. Free widgets are generally positioned in the delayed tier and are subsidised by the distribution they generate.
This is why a free widget and a paid feed can show different numbers at the same moment. It is usually not an error; it is the latency tier you are on.
The underlying question
Before adopting any score display, it is worth understanding what is being displayed and how it was produced. Our guide to how live football scores are produced covers the chain from the stadium to the screen, including why the number is provisional and why two sources disagree. The basketball equivalent of this page is free basketball score widgets.
And if what you actually need is the live number rather than an explanation of it, a broadcaster's own coverage is the simpler answer than any embed: the BBC's football section is freely available, carries no embedding requirements, and is a reasonable reference point against which to sanity-check whatever a widget is showing you.