Can an AI Assistant Read Your Election Office? We Checked All 50 States, DC and 35 Countries.

2026-11-18来源 dev.toEnglish

People now ask AI assistants where to vote, how to check their registration and when results are certified. The assistant can answer from training data, which may be a year old, or it can read the official election office site. We wanted to know what it gets when it tries the second option.

This is not about whether AI should be part of elections. It is a narrower, practical question: can a simple AI agent read the public homepage of the office that runs them?

How we checked

On November 13, 2026 we ran our free agent-readiness check on two lists:

Each site was checked twice, one at a time. The check fetches the homepage the way a simple AI agent would, with a user agent that names us (X1Y1-Tools/1.0). It reads robots.txt rules for the AI search and assistant bots, counts the words in the raw HTML before any JavaScript runs, and looks for structured data, metadata, a sitemap and llms.txt. It scores out of 100.

The limits matter more than usual here. Our checker is not ChatGPT, and bot protection services often keep allow lists of verified AI bots, so a site that turned us away may still let OpenAI or Anthropic through. We checked homepages, not the registration or polling place lookup pages. And protecting an election site from automated traffic is a reasonable choice. This is a first look, not an audit.

The US: 16 of 51 walled our checker

16 of the 51 US sites gave our checker a wall instead of content, on both runs:

What our checker got States
Bot-protection response (HTTP 403) Arizona, DC, Florida, Georgia, Iowa, Michigan, Mississippi, New Hampshire, New York, Rhode Island
An error, and a browser-like request got a "Human Verification" or "Just a moment..." challenge Alaska, Ohio, Wisconsin
A near-empty page marked noindex Nevada, Massachusetts, Virginia

Virginia is the clearest example of the gap. Our checker got a page with 1 word of text. A browser-like request to the same address got 482.

Two states block AI bots on purpose, in robots.txt:

  • Illinois (elections.il.gov) has User-agent: * with Disallow: /. That blocks every bot, search engines included, not only AI.
  • Louisiana (sos.la.gov) allows a list of older named crawlers such as Googlebot, then disallows everyone else. ChatGPT-User, Claude-User, OAI-SearchBot and every other AI bot not on the list are blocked.

Vermont blocks PerplexityBot by name and allows the other assistant bots.

The 35 US sites we could read

Most readable state sites are plain and serviceable: real text in the HTML, open robots.txt rules, a title and description. Scores ran from 30 (Illinois, because of its robots.txt) to 80.

Top scores Score
Montana 80
Maryland 75
Idaho 75
South Carolina 75
Colorado 70

Only Maryland serves an llms.txt file. 32 of the 38 sites that returned a score have no JSON-LD structured data on the homepage. None returned Markdown when asked for it. Utah's homepage has only 120 words in its HTML before JavaScript runs.

Worldwide: the same 31%

We ran the same check on 35 national election bodies the same day. 11 of 35 walled our checker on both runs, which is 31%, the same rate as the US states.

What our checker got Countries
Bot-protection response UK, Brazil, South Africa, Philippines, Bangladesh, Thailand, Colombia, Peru, Spain, France
HTTP 525, a Cloudflare error meaning the TLS handshake with the origin server failed Turkey

Three results stood out among the sites we could reach:

  • India (eci.gov.in) allows every AI assistant bot in robots.txt, but its homepage HTML has 0 words of text before JavaScript runs. An agent that reads HTML gets an empty page from the election commission of the world's largest democracy.
  • South Korea (nec.go.kr) has a readable homepage with 989 words, but its robots.txt blocks GPTBot, OAI-SearchBot and ChatGPT-User by name, while allowing ClaudeBot, PerplexityBot and Google-Extended. That is a rule about one company, not about AI.
  • New Zealand (elections.nz) answered with a 212-byte page with no text and a noindex,nofollow tag, even to a browser-like request. It looks like the challenge pages Nevada and Massachusetts serve.

Italy and Taiwan also had 25 words or fewer without JavaScript. Nepal, Sri Lanka, Canada and Malaysia had under 100. Ireland and Mexico scored highest at 80. None of the 35 serves llms.txt.

Put together, only 15 of the 35 national bodies gave our checker a readable homepage with no AI bot blocked.

robots.txt is not where the blocking happens

Outside Illinois, Louisiana, Vermont and South Korea, robots.txt is wide open. Among the national sites we could read, 23 of 24 allow every AI assistant bot and every training crawler we check for.

The real barriers are bot protection and JavaScript-only pages. Going by the page titles our browser-like request received, about 8 of the 11 national walls look like Cloudflare challenge pages. We have not confirmed that with the agencies. If it holds, the bot settings on one vendor's dashboard decide whether an AI assistant can read election information for those countries, and the election office may never have made that choice on purpose.

Where this is overhyped

What we would not claim from this data:

  • That Georgia, New York or France "block AI". Our checker got a bot-protection response. Verified AI bots may be allowed.
  • That assistants give wrong election answers because of this. We did not test answers. A blocked site means the assistant has to rely on other sources, which may be older or less exact.
  • That llms.txt is something election offices should rush to add. A readable homepage and correct bot settings matter far more.

What an election office can check

If you run or maintain an election office site, these are cheap to check:

  1. Load the homepage with JavaScript off. Registration deadlines, polling place lookup links and contact details should be in the HTML.
  2. Bot protection rules. Check whether verified AI assistant bots get through on public information pages, while forms and lookup tools stay protected.
  3. robots.txt. A blanket Disallow: / hides the site from AI assistants and search engines alike. If the intent is to stop scrapers, a bot protection rule is a narrower tool.
  4. One test. Ask ChatGPT, Claude and Perplexity your state's registration deadline and see whether they cite your site.

Our agent-readiness check runs the first three in about ten seconds. It is free and needs no signup.

原文:https://www.a8q9.cn/en/article/can-an-ai-assistant-read-your-election-office-we-checked-all-50-states-dc-and-35-ffaca7.html

相关文章