Technology

Google Bundles AI With Search, and Some of Its Own Staff Want a Switch

Martin HollowayPublished 4m ago4 min readBased on 1 source
Reading level
Google Bundles AI With Search, and Some of Its Own Staff Want a Switch
Photo by Click Jeth on Pexels

Members of the Alphabet Workers Union, CWA Local 9009, issued a statement on 19 November 2026 criticizing Google's handling of AI features in Search for schools. The union's objection centres on Google's decision to bundle its AI tools with Search.

Under the policy, schools must have some AI features enabled before their students can use Google's Search tools. An institution that wants students to run Search cannot opt out of the AI layer entirely. The union says this places the AI features and core retrieval behind the same switch.

The dissent goes beyond a single statement. More than 500 employees signed a petition asking Google leadership to reconsider. The petition asks that schools be allowed to turn off AI features in Search without losing the ability to use search. That is a narrow request: a configuration that separates the two functions, not a general demand to remove AI from Search.

Outside the company, the policy is raising a procurement question. School districts in New York City, Los Angeles and Chicago are considering an alternate search engine rather than cede control over student AI use to Google. The districts are weighing their options.

For IT administrators, the dispute comes down to who sets AI exposure policy in a classroom. A district that manages student accounts, content filtering and data-handling agreements typically wants granular control over which generative features run, and under what conditions. Generative features are AI functions, usually driven by large language models, that produce text, summaries or answers from a prompt. A bundled default removes that lever. Whether Google offers such granularity for schools, and on what terms, is not settled in the reporting available here, so the open question is one of design and contract rather than capability.

The broader context here is a familiar tension in enterprise software. Platforms tend to fold new features into existing products because that is where distribution already exists. Customers then discover that the convenience of a single bundle carries a cost in governance. Schools are an unusually sensitive version of that problem, because the users are minors and the procurement decisions are made by public bodies answerable to parents and school boards.

In my view, the most useful thing the petition does is make the request concrete. “Turn off the AI without breaking search” is a specification an engineer can test, and it gives districts a clear check for any vendor. Whether Google adopts it, or the districts move to another engine, will show how much control education customers can expect over generative features built into tools they already depend on.

There is also a case for optimism that the dispute does not erase. Generative features can help students with query refinement, summarization and research literacy. A school that can enable them deliberately, with logging and policy controls, gets the benefit without surrendering the decision. The technology is not the obstacle. The obstacle is whether the configuration schools need is offered as an option at all.