Did Linn County's Tougher Data-Center Rules Push Google Toward Palo?

Google left negotiations with Linn County and pursued annexation into Palo after the county adopted new requirements for water, community benefits and large-scale development. Whether those protections influenced the company's decision remains one of Eastern Iowa's biggest unanswered questions.

Google's proposed Eastern Iowa data center did not move.

The land remained roughly 545 acres near the Duane Arnold Energy Center outside Palo.

What changed was the government that could regulate it.

Google initially negotiated with Linn County over building the project in unincorporated territory. County officials spent months developing a new zoning framework specifically for large-scale data centers—one that required an independent water study, a binding water-use agreement and an economic-development agreement outlining community benefits.

Then, just days after that ordinance was approved, Google informed county officials it would instead pursue annexation into the City of Palo.

Annexation would place the project under city authority rather than Linn County's newly adopted regulations.

Linn County officials have been unusually direct about what happened.

"We gave Google a clear, workable path to build," Board Chair Kirsten Running-Marquardt said after the decision. "We were not trying to block this project."

Google has not publicly explained in detail why it chose the annexation route, and no formal project application has yet been filed with Palo.

That leaves one question hanging over one of Eastern Iowa's largest proposed economic developments:

Did stronger county oversight encourage Google to seek a different jurisdiction?

The public record has not yet answered that question.

A Different Path

Linn County estimates the proposed project represents more than $1 billion in private investment.

For months, county officials negotiated with Google over the rules that would govern the development if it remained in unincorporated Linn County.

On February 18, supervisors unanimously approved the county's new Data Center Overlay District.

The ordinance required developers to demonstrate adequate water availability, enter into a water-use agreement with the county and negotiate an economic-development agreement describing community benefits.

County officials also said Google had agreed during negotiations to fund up to $500,000 toward an independent regional water-balance study while discussions continued regarding infrastructure, community investment and long-term operating commitments.

Then, on February 26, Google notified the county it intended to pursue annexation into Palo instead.

Supervisor Sami Scheetz viewed the decision as a warning about what can happen when neighboring governments operate under different rules.

"We negotiated in good faith," Scheetz said. "And Google's response was to go find a local government that will ask for less."

That reflects the county's position—not an independently established explanation of Google's decision.

Whether Google shifted because of regulatory requirements, infrastructure, taxation, utility access, annexation strategy or some combination of factors remains unknown.

Palo's Different Framework

Following Google's announcement, Palo began developing its own data-center ordinance.

The proposal addresses zoning, setbacks, traffic, noise and reporting requirements, but differs from Linn County's ordinance in several important ways.

Rather than requiring an independently negotiated county water agreement before approval, Palo's draft ordinance relies largely on state permitting through the Iowa Department of Natural Resources, with additional project-specific conditions potentially negotiated later through a development agreement.

That distinction matters because no development agreement has yet been released publicly.

Until one exists, residents cannot compare exactly what protections, monitoring requirements or community commitments Google would have accepted under Linn County's ordinance versus those it may ultimately accept in Palo.

Water Remains the Central Question

Throughout public hearings, one issue has consistently dominated discussion:

Water.

Records reviewed during the public process indicate the proposed facility could be designed to withdraw up to 14 million gallons of water per day from the Cedar River, although that represents a potential permitted capacity rather than expected daily consumption. Google's final cooling design has not been publicly released.

Without that information, residents say they have no way to evaluate long-term impacts on private wells, river levels or surrounding communities.

During Palo's public hearing, resident Jennifer Leaven asked the question many neighbors continue asking today.

"How do we prove that all of this water usage is the reason our wells go dry if we don't do any water surveys ahead of time?"

Her concern reflects a broader issue.

Water does not recognize city limits.

Neither do road impacts, emergency response demands or electrical infrastructure.

A project inside one jurisdiction may produce effects well beyond its boundaries.

Can a Smaller Government Oversee a Bigger Project?

Palo has approximately 1,400 residents.

Unlike Linn County or Cedar Rapids, it does not have large planning departments, engineering staffs or extensive legal resources.

That does not mean the city cannot negotiate an effective agreement.

Small communities regularly oversee major industrial projects.

But it does raise legitimate questions about oversight.

Who will independently evaluate projected water demand?

Who will verify infrastructure costs?

Who ensures long-term compliance?

Who enforces commitments twenty years from now?

Those questions are not arguments against development.

They are questions every taxpayer should expect local government to answer before construction begins.

Linn County Hits Pause

On July 1, Linn County supervisors voted to impose an 18-month moratorium on accepting additional applications under the county's Data Center Overlay District.

The pause applies only to unincorporated Linn County.

Cities such as Cedar Rapids and Palo remain free to consider their own projects.

Supervisor Brandy Meisheid, who supported the moratorium, said additional technical work is needed before more projects move forward.

"It is my opinion that we cannot move forward without knowing what our community can sustain."

Supervisor Scheetz disagreed.

He argued the county had already created one of Iowa's strongest regulatory frameworks and warned that pausing applications could simply encourage developers to pursue projects inside neighboring municipalities instead.

Whether that prediction proves accurate remains to be seen.

What We Know—and What We Don't

Several facts are no longer in dispute.

Linn County negotiated with Google.

The county approved a new data-center ordinance.

Google then informed county officials it would pursue annexation through Palo.

Palo began developing its own regulatory framework.

Linn County later paused additional rural data-center applications.

What remains unresolved is why Google changed course.

The answer may involve infrastructure.

It may involve taxation.

It may involve utility access.

It may involve the county's new regulatory requirements.

Or it may involve all of those factors together.

Until more records become public, assigning a single reason would go beyond the available evidence.

More Than One Project

The debate now unfolding is larger than Google.

Eastern Iowa is rapidly becoming a destination for data-center investment, bringing the promise of billions of dollars in private construction, new tax revenue and long-term economic growth.

It also raises difficult questions about water resources, electrical demand, infrastructure costs, emergency services and public accountability.

The central question is not whether Linn County was right to demand more or Palo is wrong to negotiate differently.

It is whether a company seeking to build one of Eastern Iowa's largest developments was able to change jurisdictions before the public could see exactly which protections, payments or obligations were left behind.

That answer should be contained in the public record.