How we verify

The numbers on the homepage are computed from the records we actually publish at page render time. They are never typed by hand, so they cannot drift from the data.

A record can be confirmed as a whole while one field is still unknown. Time, price and accessibility are the fields that most often go stale, so each carries its own state. Only a confirmed field is emitted into structured data.

Community directory assembled from local business records and manually verified listings. Listings drawn from printed material stay unconfirmed at the field level until someone checks them, and the listing says so.

Every listing carries a “report an error” link next to the listing itself. When a correction lands, the record keeps an append-only, timestamped entry naming the fields that changed and the value before and after — so the history of a fact is part of the fact. The guide currently keeps 7 logged corrections across 6 records.

A correction never widens what we publish on its own. Each changed field carries its own certainty afterwards, and only a confirmed field on a publishable record is emitted as a structured-data claim; anything still reported or unconfirmed appears in the history and on the page as uncertain, and stays out of the machine-readable claims. Here is a real record’s history, rendered exactly as it appears on the record itself:

Found something wrong? Send a correction.

The long-term asset is the local graph, not the page. These are the record types the guide maintains, with the schema.org type each one publishes as.

Lake Wales Guide is an independent local guide covering Lake Wales and the surrounding Polk County Ridge communities. Lake Wales is the center; the Ridge is the expansion layer. “Polk County” is a coverage scope, never a city value on a record.