Google begins requiring JavaScript for Google Search

Original Article ↗ Hacker News Discussion ↗

Scope of Change and User Experience

  • Google Search now refuses queries without JavaScript, showing a “failure/degraded experience” page.
  • Some report that even after enabling JS and reloading, the “fail” page persists and the query is lost.
  • One commenter claims that command-line searching still works if the User-Agent is set to a specific “approved” value (e.g., mimicking Lynx), suggesting the effective requirement is UA + JS expectations, not strictly JS execution.
  • Many see this as yet another barrier: cookie prompts, captchas, and forced logins already make Google feel hostile.

Technical Debates: JS vs Alternatives

  • Several note there’s no fundamental need for JS for a simple search form.
  • Others propose non-JS approaches to load AI summaries asynchronously: iframes, lazy-loaded elements, multipart streaming, Server-Sent Events, declarative Shadow DOM, or clever CSS/HTML streaming tricks.
  • Accessibility concerns are raised for pure-CSS repositioning versus DOM-based solutions.

JavaScript, Privacy, and Performance

  • Strong anti-JS sentiment: JS is associated with tracking, fingerprinting, ad tech, higher data use, and making old/low-end devices unusable.
  • Others argue JS itself is not “evil”; mandating it without clear user benefit is the issue.
  • Some browse with JS off by default and report many sites (including Amazon’s core flow, DuckDuckGo, Kagi, etc.) still work well.

Search Alternatives and Migration

  • Multiple search engines that work without JS are listed: DuckDuckGo, Brave Search, Startpage, Yahoo, Mojeek, SearXNG, FrogFind, AOL, giveWater.
  • Kagi is frequently praised, though some find its $10/month price high; others say it easily pays for itself in time/money saved.
  • Several users switch their browser default away from Google after this change.

Bots, Abuse, and Motivations

  • Some argue Google is responding to rampant bot traffic, SEO spam, and query-suggestion poisoning; JS/headless-browser requirements raise attacker costs.
  • Operators of smaller sites share similar experiences with DDoS, spam, and Tor/proxy abuse, saying hardening measures are often misread as “enshittification.”
  • Skeptics suspect the primary goal is tighter ad/AI-result control and user tracking, not abuse mitigation; they point to YouTube’s anti–ad-block moves as precedent.
  • Ideas like proof-of-work or micropayments are floated but seen as imperfect or abusable via botnets.

Wider Reflections on the Web

  • Many describe Google search (and the broader web) as increasingly ad- and SEO-bloated, calling this a “last days of Rome” moment.
  • Some report shifting search and everyday tasks to AI tools (ChatGPT, WhatsApp AI) and using single-site browsers or curated sources instead of general web search.