techcrunch.com web signal

Google AI Overviews Misspells Its Own Brand Name

google hallucinations ai-limitations llm-behavior search-ai

Key insights

  • Google's AI Overviews misspells basic words including its own name due to structural tokenization limits in transformer architecture.
  • Every major transformer-based LLM shares the same tokenization constraint, making this a cross-industry limitation rather than a Google-specific bug.
  • Google confirmed the issue to TechCrunch and said it is working on a fix, but offered no timeline.

Why this matters

Tokenization is not a surface-level bug but a foundational property of every transformer-based LLM in production today, meaning the same failure mode exists across ChatGPT, Gemini, Claude, and every other system in this class. Google's public confirmation that the issue is active in a flagship consumer product shifts this from a known theoretical limitation to a documented, live reliability gap with user-visible consequences at search scale. For AI practitioners shipping products on top of these models, the incident establishes a concrete precedent that character-level reasoning requires explicit architectural investment, not just prompting or fine-tuning.

Summary

Google's AI Overviews is misspelling words in live search, including its own company name spelled with two p's. TechCrunch documented failures across multiple terms and got Google to confirm the bug on record, with additional cases involving the U.S. president's surname and common words like 'journalism.' The cause is architectural: transformer LLMs tokenize text into subword chunks rather than individual characters, making letter-counting and spelling verification non-trivial operations that production systems have not fully engineered around. Essentially: (Google, every major transformer vendor) ships with this constraint built into the base architecture. - Google confirmed it is working on a fix, with no timeline given. - Tokenization affects all transformer-based models, so this is not a Google-specific issue. - Spelling errors in live search are immediately visible, accelerating trust erosion among general users. A product misspelling its own company name in live results is a concrete illustration of how LLM reliability still lags LLM capability.

Potential risks and opportunities

Risks

  • Google's search market share could accelerate its decline to rivals like Perplexity and Bing if AI Overview spelling failures become a sustained media narrative through Q3 2026.
  • Enterprise customers using Gemini for document generation or customer-facing content face undisclosed liability if character-level spelling errors propagate into regulated, legal, or compliance contexts.
  • Every major LLM vendor including Anthropic, OpenAI, and Meta now faces heightened media and regulatory scrutiny for the same tokenization limitation in their own production systems, with no architectural fix available on a short timeline.

Opportunities

  • Post-processing spell-check and grammar API vendors such as LanguageTool and Grammarly gain a clear enterprise upsell path as infrastructure-level spelling reliability becomes a documented gap in LLM-native products.
  • Character-aware or hybrid retrieval-generation architectures from structured generation startups have a concrete, publicly validated failure case to lead with in enterprise sales cycles.
  • Competitors including Perplexity and Microsoft Bing could run targeted reliability-focused campaigns capitalizing on Google's on-record acknowledgment that its own AI search product misspells basic words.

What we don't know yet

  • Whether Google's planned fix involves post-processing spell-check layers, character-level model components, or retrieval augmentation, and whether competitors have equivalent solutions already in progress.
  • Scale of exposure: how many Google search users encountered misspelled AI Overview results before TechCrunch's report, and whether Google tracks spelling error rates in its internal quality metrics.
  • Whether third-party products built on the Gemini API inherit this spelling limitation at the same rate, and what disclosure or SLA obligations Google has to those downstream developers.