County report card · Arizona
Graham County, Arizona
County portal uses Cloudflare bot detection which deters automated access but may be bypassed by determined actors; its robots.txt also disallows automated access to 23 paths (/activedit, /admin, /common/admin/…)
- Population
- 40,242
- Portal
- Assessor & Recorder
- Portal vendor
- Not identified
What the audit checked
Four low-cost protections every online records portal can have. How we rate counties.
- robots.txtYes — permissive
- Terms of useSilent on automation
- Bot challengeCloudflare bot detection
- Owner notificationAvailable
Portal audited: www.graham.az.gov/491/Parcel-Info-Search, www.thecountyrecorder.com/Introduction.aspx, gcwebinfo.graham.az.gov/WebPayments/PropertyInformation
Doing well
- A notification system that alerts residents when their records are accessed
- Technical barriers (cloudflare) that deter casual bulk access
Room to grow
- Expanding the robots.txt file to disallow automated scrapers
- Updating the Terms of Use to prohibit automated access
What to ask for
Three low-cost steps that have worked in other counties to close gaps like this one:
1. Adding clear robots.txt rules that disallow automated scrapers
2. Updating the Terms of Use to prohibit automated access
3. Implementing a notification system that alerts residents when their records are accessed
The full playbook is What Counties Can Do.