How we verify property tax information

PropertyTaxCalendar is an independent guide operated by MCKE Enterprises Worldwide LLC. County pages are built from cited data. Missing information stays unverified.

Official sources and supporting quotations

Each tax fact must have a value, an official source URL, a short verbatim quotation supporting that value and a verification date. We use county tax offices, state revenue departments, statutes and county-authorized payment vendors. A non-government domain needs an explicit allowlist entry explaining its official role. Ellipses in quotations indicate omitted text, not a rewritten source.

Automated validation rejects missing citations, unapproved domains and implausible dates before a build can publish. It checks record structure and arithmetic; it cannot prove that a quotation supports an interpretation. Source review remains necessary.

Dates retain their meaning

An announced date comes from the county’s publication for that cycle. A statutory date comes from a cited statute or ordinance. We do not roll last year’s deadline forward, infer a weekend extension or turn a notice-dependent appeal period into a guessed date. If a deadline is missing, it is not yet announced here; follow the official link.

“Last verified” describes checks of the tax facts. “Updated” uses the latest cited verification date among the page’s data; it is not the build date and does not mean every source was checked together. Each citation retains its own date. Facts older than 400 days are labeled “Re-verifying”; stale county records are excluded from indexing. Date-relative labels use the daily build’s US Central date.

Daily source watching

The normal daily pipeline checks cited county and state sources for changed content and broken links. Changes and retrieval failures are queued for review; they do not automatically change facts or advance verification dates. A blocked page can prevent a check. Fast deployment runs skip source watching. Census imports and editorial audits are separate checks, not live tax-account feeds.

Census comparisons and examples

County, state and US comparisons use the same ACS five-year vintage. Median annual real estate taxes paid divided by median owner-occupied home value gives an effective-rate estimate. State and US benchmarks use their own medians, not averages of county rates. These are historical survey estimates with sampling error, not statutory rates or individual bills. Missing and bounded estimates are not treated as exact numbers.

Worked penalty examples use an explicitly recorded percentage and unit with an illustrative $1,000 balance. They show that percentage component only. They do not infer elapsed periods, minimum charges, compounding, exceptions or a full payoff balance. Metro links come from Census CBSA county membership, including areas crossing state lines; they do not imply identical tax rules.

Published accuracy audits

An audit records the facts selected, their sources, the date and each outcome. The observed error rate is confirmed errors divided by facts for which a source-based conclusion was reached. Unresolved retrievals are counted separately. A small targeted sample is not a sitewide error estimate; automated validation or a matching quotation alone is not an accuracy audit.

Corrections policy

Send the county, page URL, disputed detail and an official supporting link to [email protected]. We check the source and scope, then correct or remove unsupported information. An unresolved report is not silently counted as accurate. A correction records the date, affected page, what changed and why in the public corrections log. Source updates can change a previously correct fact; we distinguish those from errors and presentation fixes.

We do not publish a reporter’s private information. Historical audit results remain tied to their original sample, even after a correction.

Not tax or legal advice; confirm with your county.