Predicted line-ups are not betting predictions

A predicted line-up is an expected starting eleven, sometimes with a formation, published before the official team sheet. It helps readers anticipate tactical choices and gives fantasy players a sense of who is likely to start. Our predicted line-ups family returns these for selected leagues only.

It is a forecast, and forecasts are sometimes wrong. A late injury, a rotation decision or a tactical surprise can change several names. Presenting the expected eleven as anything firmer than an estimate misleads readers.

Treat each expected selection as provisional data with a clear lifecycle: published, then superseded by the confirmed line-up, then archived.

FootballAPI.net does not publish betting tips, outcome probabilities, odds or form-based selections. There is no odds feed and no prediction engine. This is a product decision, not an oversight. Outcome predictions invite users to act financially on them, which brings regulatory and ethical responsibilities that a data platform should not take on casually.

If your product does involve wagering, you will need your own regulated sources and your own compliance process. Our data can supply context, such as fixtures and squads, but nothing on our platform should be presented as betting advice.

Use the word expected or predicted in the heading itself, not only in small print. Show when the prediction was retrieved. Visually distinguish expected players from confirmed ones, for example with a muted style and a label, so screenshots shared on social media keep their context.

When the confirmed line-up becomes available, replace the expected one and say so. A small note that the team has been confirmed, with the time, reassures readers that the page is current.

It is tempting to advertise how often predicted line-ups are right. If you do, measure it properly: compare each expected eleven with the confirmed team over a meaningful sample and report the figure with its sample size and period. Avoid rounding to impressive numbers or cherry-picking competitions.

Most sites are better off not making accuracy claims at all, and simply presenting expected teams as helpful context.

Fantasy players care intensely about who starts. Expected line-ups help them plan, but they also create frustration when a predicted starter is benched. Make the uncertainty visible, and link to confirmed line-ups as soon as they arrive. Our fantasy tools guide covers how to combine expected selections with player statistics without implying certainty.

Avoid labels such as guaranteed starter. Even a regular first-choice player can be rested or injured in the warm-up.

Store predicted line-ups separately from confirmed ones, keyed by match identifier and retrieval time. Keep the history if you want to analyse accuracy later. Never overwrite a confirmed line-up with a later predicted one, which can happen if jobs run out of order.

Add a simple rule in your code: once a confirmed line-up exists for a match, predicted data for that match is no longer rendered on the main view.

Words shape how readers act. Prefer expected to will, likely to certain, and describe selections rather than outcomes. Keep result predictions, if your editorial team writes any, clearly separated as opinion with a byline, and never generated from or attributed to our data.

These small choices protect readers and your publication, and they keep the useful part of predicted line-ups, informed anticipation, without the harmful part.

On the eve of a match in a supported competition, your job retrieves the expected line-ups and stores them with the match identifier and retrieval time. The preview page shows them under a heading such as expected line-ups, in a muted style, with a note explaining that teams are confirmed about an hour before kick-off.

When the confirmed line-up appears in the match detail feed, a second job stores it and the page switches automatically. The heading changes to confirmed line-ups, the styling becomes standard, and a short line records when the switch happened. The predicted version remains in storage for later analysis but no longer appears on the page.

If the confirmed line-up never arrives, perhaps because the competition's detail coverage is thin, the page keeps the expected label indefinitely rather than quietly promoting the prediction to fact.

Before shipping, check that every place a predicted line-up appears carries a label, that no page converts expected selections into result forecasts, that confirmed teams always take precedence, and that your copy avoids certainty words. Review shared images and social cards too, since they travel without the surrounding page.

Some readers will ask for tips regardless. A short, polite page explaining that you publish data and context rather than betting advice sets expectations and points them to responsible gambling resources if your audience needs them.