Ask Google's AI Mode who won the 2020 US presidential election and, in at least some tests, it will not tell you. TheWrap reported on October 28, 2026 that AI Mode "sidestepped a straightforward question" and pointed users to the National Archives and the Federal Election Commission rather than naming Joe Biden. The standalone Gemini chatbot, asked the same thing, answered directly with the correct electoral and popular vote totals.
The discrepancy surfaced days before the November 3, 2026 midterms. Google has not explained it. This post sets out what the test showed, what Google's earlier election policies were, and what remains unconfirmed.
TL;DR: confirmed and unconfirmed
| Question | Answer |
|---|---|
| What did AI Mode do? | Pointed to the National Archives and FEC instead of naming the 2020 winner (TheWrap's tests) |
| What did Gemini do? | Named Biden and gave correct vote totals (TheWrap) |
| Real result | Biden defeated Donald Trump 306 to 232 in the Electoral College |
| Google's explanation | None reported; no response to TheWrap at publication |
| Is it deliberate policy? | Unconfirmed |
| Political pressure involved? | Unproven; no source ties the behavior to any request |
What did TheWrap actually test?
TheWrap ran the 2020 question on Wednesday, October 28. AI Mode did not name the winner and redirected to official sources; Gemini answered. The article does not quote AI Mode's exact wording. Other social posts and outlets described similar results across other election years, but those reports are anecdotal and we could not verify them independently, so we do not rely on them here.
Two caveats matter for anyone repeating the test. First, AI systems are not deterministic: wording, location, signed-in state and time can change a response. Second, a single sidestep is not proof of a policy. It could be a classifier that treats election queries conservatively, a bug, or an intentional guardrail. Only Google can say which.
Is this new? Google's history of election restrictions
No. In early 2024 Google said Gemini would not answer election questions in the run-up to that year's elections, a policy reported at the time by outlets including LatestLY. In June 2024, WIRED reported that Gemini would not name the 2020 winner, replying along the lines of "I'm still learning how to answer this question. In the meantime, try Google Search." The reasoning given then was risk reduction: send people to search results rather than risk a wrong or inflammatory answer.
That context is why the 2026 split is interesting. Gemini now answers, which suggests the old blanket restriction was relaxed there. AI Mode, the AI-powered layer inside Search, appears to be behaving more like the 2024 Gemini. TheWrap also notes that Google said in September it was rolling out election information tools across Search, AI Mode and Gemini, and that the Trump administration's America.gov site first acknowledged Biden's victory and then declined to answer the same question, per TheWrap's earlier reporting. Whether any of that is connected is not established.
What explanations are possible?
We cannot confirm any of these, so treat them as hypotheses:
- Separate policies by product. AI Mode might use a stricter election filter than the Gemini app because Search carries more risk and scale.
- Classifier over-triggering. An election-safety classifier tuned for the midterms may be catching a settled historical fact along with live-election queries.
- A bug or rollout inconsistency. Different model versions or flags may be live in different surfaces.
- External pressure. Some commentators on social media have pointed to political pressure on Google. No evidence in the sources we read links the behavior to any request, and we would not report that as fact.
A fifth, practical point: handling a historical fact differently from a live-election query is a design choice, and a simple settled fact like an Electoral College outcome is exactly what a well-tuned system should answer. Redirecting to the National Archives is defensible as caution, but it can look evasive, and it fails the user who just wanted a fact.
Why this matters for AI answer engines
Election answers are a stress test for any assistant. The tension is plain: refuse and look evasive or politicized, answer and risk errors or manipulation. Other labs have taken different approaches, and our coverage of OpenAI's election war room before the midterms shows one company's operational approach. The Russia-linked AI videos targeting Democratic Senate candidates and the Israel election AI bots story show the threat side, which is the reason labs build guardrails at all. Midterm races also intersect with AI infrastructure politics, as our look at the data center backlash in midterm races shows.
For builders, three lessons follow:
- Consistency across surfaces matters. If your product ships an app, a search layer and an API with different safety behavior, users will compare them and draw conclusions about your intent.
- Publish your election policy. A short public page explaining what the system will and will not answer prevents speculation. Google has not published a clear explanation for this case.
- Separate settled facts from live events. Certified historical results should not be treated like predictions about a pending election.
Timeline: from blanket refusal to a product-level split
| Date | Event | Source |
|---|---|---|
| Early 2024 | Google says Gemini will not answer election questions during that year's elections | LatestLY and others |
| June 2024 | WIRED reports Gemini will not name the 2020 winner | WIRED, via TheWrap |
| September 2026 | Google says it is rolling out election information tools across Search, AI Mode and Gemini | TheWrap |
| September 2026 | America.gov first acknowledges Biden's win, then declines to answer the same question | TheWrap, earlier reporting |
| October 28, 2026 | TheWrap finds AI Mode sidesteps the 2020 question while Gemini answers | TheWrap |
| November 3, 2026 | US midterm elections | TheWrap |
How should an AI product handle election questions?
Whatever Google's reason, the case is a useful template for product teams. A sensible policy separates three kinds of questions, because the risks differ.
| Question type | Example | Reasonable behavior |
|---|---|---|
| Settled history | Who won the 2020 presidential election? | Answer directly with the certified result and cite the National Archives or similar |
| Procedural, live | Where do I vote? What ID do I need? | Answer from official sources, link to the state election office, show the date of the information |
| Predictions and live results | Who will win the Senate? Who is ahead in this race? | Decline to predict, point to official results and reputable counts, explain uncertainty |
Treating all three as the same risk produces the failure readers noticed: a system that is cautious about a pending race also becomes evasive about a certified fact. The mirror failure is just as real. A system that answers live-race questions with confident guesses can mislead voters. Good design means classifying the question, not just spotting the word "election."
Product teams can also borrow some practical habits. Log refusals on election queries and review a sample weekly so over-blocking is caught early. Keep a short public policy page that says what the assistant will and will not answer. And test across every surface where the model ships, since an app, a search layer and an API can drift apart without anyone noticing.
How can you test this yourself?
If you want to check the behavior rather than rely on a report, run a small, repeatable test and write down the results. Use the same wording each time, such as "Who won the 2020 presidential election?" Try it in AI Mode, the Gemini app, and a signed-out browser session. Record the date, the product, the exact answer, and any links shown. Repeat after a few hours and again the next day, because responses can change as Google adjusts systems, and the company has said nothing about a fix. Add a control question from a different year or a non-election historical fact to see whether the sidestep is specific to election topics. Screenshots with timestamps make the result easy for others to evaluate.
Keep the conclusions modest. One sidestep proves that a response happened, not why. If many testers across regions see the same behavior, that points to a deliberate or systematic setting. If results vary a lot, it points to inconsistency. Neither tells you anything about motive.
What should readers do?
- Go to primary sources for election facts: the National Archives for the certified Electoral College results, the Federal Election Commission, and your state election office.
- Cross-check AI answers, especially for politically charged questions, and test more than one product.
- Do not read motive into one sidestep. Wait for an explanation from Google.
- If you work on AI products, audit how your assistant handles historical political facts and document the rule.
What we could not confirm
- Exact responses. TheWrap does not quote AI Mode's text.
- Scope. We do not know how widely the behavior appears across users, regions or other election years.
- Google's position. One summary we read attributes a statement to a Google spokesperson, but we could not trace it to a source we could open, so we have left it out.
- Reason. No explanation is on record.
Accurate as of October 28, 2026, based on TheWrap's report and earlier coverage. We will update this post if Google comments.
Related reading
- OpenAI's election war room before the midterms
- Russia-linked AI videos target Democratic Senate candidates
- Israel election AI bots: claimed vs verified
- Data center backlash in the midterms
- Gemini app skills replace Gems
- Gemini 4 Carbon launch
- Official: TheWrap report, National Archives Electoral College results
