Identical work gets funded or rejected depending on whether the proposal says "SEO" or "generative engine optimization," and a new analysis argues that this labeling gap — not the underlying economics — is what's breaking search budget decisions.

The piece, published by Search Engine Journal's contributing editor, frames the problem through two hypothetical pitches to the same executive team. Both request money for technical SEO debt, content architecture, and machine-accessible product information. The second, dressed as a GEO initiative, "sounds considerably sexier and may have a better chance of securing funding, even though much of the proposed work is identical."

The author's verdict: "The perceived value of the work can change dramatically depending on which budget it comes from, even when the underlying business benefit is substantially the same."

What does Google actually say about GEO vs. SEO?

The analysis leans on a confirmed policy point. Google's guidance on its AI search features, published via Google Search Central, states that established SEO fundamentals remain relevant: pages still need to be accessible to Google, meet technical requirements for appearing in Search, and provide useful content.

Notably, Google does not prescribe a separate set of technical optimizations exclusively for its AI features. The author is careful to separate this official guidance from speculation: the guidance does not prove every AI platform operates like Google, nor that SEO and GEO are interchangeable.

The practical implication is blunt: "If a company has unresolved crawlability problems, inconsistent product information, weak internal linking, and outdated content, a new AI visibility platform will not make those deficiencies disappear. The fundamentals did not become obsolete when someone introduced a new acronym."

How would a restructured budget actually look?

The centerpiece is a worked example: a hypothetical ecommerce company with declining informational traffic, executive pressure to fund AI discovery, and a standing $1.2 million SEO budget. Instead of requesting more money, the SEO leader reallocates the existing spend around business outcomes:

• Shared discovery infrastructure — technical foundations, structured product information, architecture: $420,000 (35%)
• Commercial search — high-intent content and product/category optimization: $360,000 (30%)
• AI discovery experimentation — platform evaluation, brand representation, controlled tests: $180,000 (15%)
• Measurement and operations — reporting, monitoring, tooling, specialist support: $240,000 (20%)

The author flags these as illustrative allocations, not recommended ratios. The total budget does not increase — the financial case changes. "Instead of defending $1.2 million as the cost of generating organic traffic, the SEO leader can explain how the investment supports commercial acquisition, protects existing revenue, maintains discovery infrastructure, and addresses uncertainty about emerging platforms."

The reclassification also forces trade-offs into the open: funding AI experimentation consumes resources that could support commercial search or infrastructure, and management can weigh those choices directly.

Why migration spend needs a different business case

The analysis draws a sharp line between revenue generation and revenue protection. Consider an ecommerce company generating $10 million annually in organic revenue that requests $100,000 for migration planning and technical validation.

The right justification is not a traffic forecast. It is risk math: a hypothetical 10% revenue decline lasting three months represents $250,000 in exposed revenue. That figure alone doesn't justify the spend — management still weighs the probability of loss, contribution margin, and mitigation effectiveness. But a successful migration that shows "very little visible change in organic performance" is often the desired outcome, and measuring it only against incremental traffic makes it look worthless.

Which financial standard applies to which spend?

The author proposes classifying investments by economic purpose:

• Generate revenue — expected incremental commercial return (expanding high-intent product coverage)
• Protect revenue — expected loss avoided relative to mitigation cost (preserving visibility during migration)
• Maintain or improve capabilities — operational value versus implementation and maintenance costs (product data and content infrastructure)
• Reduce uncertainty — value of information produced relative to experiment cost (testing AI platform visibility)

The categories overlap, and the author warns against counting the same return twice. The discipline cuts both ways: "A revenue initiative without a plausible return should face scrutiny. The same is true of an infrastructure project with limited operational value or an AI experiment without a defined learning objective."

What about opportunity cost?

The uncomfortable section: "an investment can be valuable and still not deserve funding." If a publisher's informational content no longer attracts enough monetizable traffic to cover production costs, continuing under the same strategy may be irrational — the publisher needs to rethink its portfolio or revenue model, not request more money to recover rankings.

Verticals diverge. An ecommerce company with the same traffic declines might reach a different conclusion if commercial pages still generate profitable transactions. Enterprise software adds another calculus entirely, given long sales cycles and the relationship between visibility and branded demand.

The same skepticism applies to GEO itself: "An executive team's enthusiasm for AI does not establish that every proposed AI visibility initiative deserves funding."

Measurement gets equal scrutiny. AI citations and visibility scores carry their own limits — "A mention in a generated response does not prove that the exposure caused a purchase." The author's standard for accountability: distinguish what has been observed, what can reasonably be inferred, and what remains unverified.

What to watch next

The closing logic sets the monitorable question: whether organizations fund overlapping technical foundations as a shared pool or keep spinning up separate AI-visibility budgets while letting that infrastructure decay. As the author puts it, "If the same work suddenly becomes easier to fund when it is called GEO, the problem was never the SEO budget. It was how the organization understood the investment."