Google Employees Petition to Let Students Search Without AI

Google Employees Petition to Let Students Search Without AI

I watched a short clip of students standing outside Google’s Chicago office, phones up, voices low but fierce. One student unlocked a school-issued Chromebook and the screen said: Search is not available. That single line turned a corporate policy into a personal emergency for dozens of classrooms.

I want to walk you through what happened, why more than 500 Google employees signed a petition, and what it means for districts, teachers and families. You’ll see the stakes are both practical and reputational—and you’ll understand why the petition is bluntly titled “Let Students Search.”

Students swarmed a Google office and held signs — the protest became a moment of clarity.

That scene helped crystallize a growing conflict: Google says Search and its AI features are tightly linked; many districts say they want no student-facing generative AI in classrooms. The result is a policy gap that now has Google staffers publicly asking executives to change course.

The petition, organized by the Alphabet Workers Union, names Google executives Chris Phillips, CEO Sundar Pichai and Search head Elizabeth Hamon Reid and asks them to let schools choose how they use AI tools. Parul Koul, the union president and a Google software engineer, put it plainly: decisions about classroom tools belong to educators, not company leadership.

Can schools use Google Search without AI?

Google has said schools will be able to toggle access to standalone products like the Gemini chatbot and Gemini Notebook, and that the rollout will happen early next year. But the company also told The New York Times that if a school bans AI, students trying to use Search may see a message from their school saying Search isn’t available. That selective blocking is the wrinkle teachers and districts are racing to understand.

Reports and lawsuits created an immediate, emotional reaction — the public pressure forced a rapid news cycle.

Last month’s New York Times stories flagged the policy and its consequences, and a separate lawsuit added urgency. A North Carolina couple sued after alleging their 13-year-old used Gemini and Google’s embedded AI features on a school Chromebook in a way that led to a suicide attempt. The suit claims the AI features were triggered whenever a student searched, creating unsafe conversations.

That combination—national reporting, a lawsuit and city-level pushback—has three big effects: city officials and parents mobilize, districts begin contingency planning, and many Googlers worry their work will be judged by decisions made above their teams. Rob Rose, a Google Education engineer and union member, warned that those reputational costs can ricochet back to the people who build and support products.

Why are schools banning generative AI?

Educators cite interrupted learning, cheating, privacy concerns and untested safety guardrails. New York City, Los Angeles and Chicago all enacted moratoriums or strict limits, and at least some districts are now exploring alternative search providers. For school leaders, the calculation is simple: reduce unknown risks to students—even if that means cutting an industry-standard tool.

Inside Google, employees see the policy as a blunt instrument — workers worry it will erode trust.

More than 500 employees signed the petition arguing that forcing an all-or-nothing approach will push schools away from Google entirely. The union letter says: “It is our job as Googlers to respect the user, and listen to them when they have concerns about our products.” That is a direct appeal to authority and to a familiar company value: user trust.

The union also admitted reporting around the policy was sometimes unclear, and Google tried to clarify via posts on X (formerly Twitter). Still, the hard part remains unanswered: what happens to the AI features baked directly into Search—AI Overviews, AI Mode and integrated Gemini—that are not separate toggles?

The situation feels like a library where half the shelves are suddenly painted over; teachers and students are being asked to trust a system while not being given a clear map of what they can access. Those mixed signals are pushing districts to consider alternatives.

Districts are weighing switching search providers — the change would ripple through procurement and classroom tech.

Three major districts—New York City, Los Angeles and Chicago—are reportedly considering non-Google options. For IT managers who stock Chromebooks and approve LMS integrations, the choice is less symbolic than operational: a new search vendor means new settings, retraining and potential privacy reviews.

From the outside, the risk is simple: if districts move away from Google, the company could lose contracts and long-term relationships. For the employees who signed the petition, that loss isn’t abstract—it could threaten the jobs of people who build education products and want the tools to be used responsibly.

How can districts block AI but still allow Search?

Technically, districts can impose policies at the account or device level, and Google says it will give schools switches for certain products. But embedded AI features complicate that approach because they are integrated into the core Search experience. Districts are demanding precise, granular controls—something the union wants Google to deliver so that schools can choose without losing basic Search functionality.

Workers framed their plea as a trust issue — their petition presses for granular controls, not a ban on AI.

The petition’s ask: allow schools to turn off AI features in Search without disrupting their ability to use Search as a whole. That language aims to protect both student safety and students’ access to information. Parul Koul argued the decision of how and when to use AI should rest with educators.

You’ll notice how power and perception play out here: Mayor Zohran Mamdani accused Google of trying to force AI into public schools, and parents and teachers marched in several cities. The optics matter. For engineers who shipped features, the concern is reputational harm that could shrink product adoption and revenue—tensions that were on display in internal messaging and public statements.

The debate has the texture of a faucet suddenly turned off: one policy change and a long, familiar workflow stops, forcing people to improvise. It’s also a reminder that product decisions echo far beyond the office floor.

What happens next — schools, Google and the public all have choices to make.

Google says the rollout will include options for schools to individually turn on or off Search, Gemini and Gemini Notebook. The union and many districts want clearer, enforceable controls for the AI features that are embedded and always-on.

I don’t pretend to have a silver-bullet answer. But I do think this is a moment when company policy, educator authority and student safety need to be reconciled without turning classrooms into collateral damage. If Google won’t offer granular controls, will districts play hardball and replace the search engine they have relied on for years?

Subscribe to our daily AI newsletter
The 5-minute AI newsletter. The stories that matter, in your inbox every weekday morning.
Subscribe Now

The Alphabet Workers Union has framed the request as a narrow technical fix and a broader trust repair: let schools flip off specific AI features without losing Search. Will Google accept that compromise, or will cities and districts push forward with alternatives that rewire classroom tech for good?