> ## Documentation Index
> Fetch the complete documentation index at: https://docs.checkthatfield.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What readers see

> Every state the widget can be in, the exact words readers see, and what to do about each.

The widget never shows a browser error or a blank box. When it has nothing to show, it says why in one sentence, under the heading "Development likelihood nearby", with a "Powered by Check That Field" link.

## Scores to show

The usual answer. Readers see:

* **The nearest field with a score**, for example "The nearest field with a score, 140 m away", with its band in large text, its score ("52 out of 100") and a bar.
* **Next 5 years** and **Next 15 years**: the outlook over each.
* **The main reasons**: up to three, each marked as making building more or less likely.
* **Fields nearby**: up to five, nearest first, with distance, size and band. Bands are written as words, not shown by colour alone.
* **A map** of the same fields, numbered as in the list.
* **See the full report**, which opens the nearest scored field's report on checkthatfield.com in a new tab.
* **The data credits**, which you must not hide.

## Being checked

Fields we haven't scored yet show "Being checked" in the list, with the note "Fields being checked have their score in a few minutes." Asking about them queues them for scoring, so a later visit shows their scores.

If none of the nearby fields has a score yet, the top of the widget says:

> The fields here are being checked. Their scores will be ready in a few minutes.

The link then reads **See these fields on the map**. See [Pending scores](https://docs.checkthatfield.com/api/pending-scores.md) for how scoring on request works.

## Messages

> [accordion] This widget isn't set up for this site.
>
> The key is missing, unknown, revoked, or not issued for the site the widget is on. Check that `data-key` is your publishable key (`ctf_pk_live_…`), and that the page's domain, or a domain it is a subdomain of, is one of your key's sites. It also appears when your page sends no `Referer`: see the note on referrer policy in [Install the widget](https://docs.checkthatfield.com/widget/install.md#strict-content-security-policies). To add a site, email [hello@checkthatfield.com](mailto:hello@checkthatfield.com).

> [accordion] This widget has been used as much as it can be this month. It will be back on the 1st.
>
> Your key has used its monthly quota. It comes back at the start of next month (UTC). Ask us for a bigger quota if you need one. See [Quotas and limits](https://docs.checkthatfield.com/api/quotas-and-limits.md).

> [accordion] This widget is busy. Try again in a minute.
>
> Your key has gone over its rate limit of 600 widget loads a minute. This passes within a minute.

> [accordion] We don't have open fields to show close to this place. Check That Field covers fields in England.
>
> There are no open fields within 500 m, the place is outside England, the postcode wasn't found, or no place was given. Check the `data-postcode`, or the `data-lat` and `data-lng`. See [Coverage](https://docs.checkthatfield.com/concepts/coverage.md).

> [accordion] This widget needs a postcode or a place to look at.
>
> The coordinates aren't numbers, or are outside the ranges in [Options](https://docs.checkthatfield.com/widget/options.md).

> [accordion] We can't check the fields here just now. Try again later.
>
> Something went wrong on our side, or the answer took too long. It is usually brief. If it lasts, tell us at [hello@checkthatfield.com](mailto:hello@checkthatfield.com).

> [!NOTE]
>
> Views and clicks are counted only when the widget shows fields. A widget showing one of the messages above isn't counted as a view. See [Security and privacy](https://docs.checkthatfield.com/widget/security-and-privacy.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.