Position: Generative Engine Optimization Creates Underexamined Risks, Governance Must Target Concentration, Disclosure, and Academic Blind Spots
arXiv:2606.12439v1 Announce Type: cross Abstract: Large language model (LLM) answer engines are increasingly used for information seeking, shifting visibility from ranked lists to synthesized answers. This enables Generative Engine Optimization (GEO), which targets LLM answer engines' evidence pool and generation. We analyze the search engine optimization (SEO) to GEO transition to identify two risks: (i) concentrated influence from low contestability and system sensitivity, and (ii) undisclosed commercial influence embedded in evidence and reasoning. We then formalize a general GEO pipeline t
As LLM answer engines become dominant for information seeking, the methods for influencing information visibility are rapidly evolving from traditional SEO to Generative Engine Optimization (GEO).
This transition introduces new systemic risks, including concentrated influence and undisclosed commercial biases, which will fundamentally alter how information is consumed and trusted.
The mechanisms for information dissemination and influence are shifting, making the source and neutrality of information less transparent and potentially more manipulable by powerful actors.
- · Sophisticated GEO practitioners
- · Large AI model providers (LLMs)
- · Content creators adept at GEO
- · Traditional SEO agencies
- · Independent journalism without GEO
- · Average information seekers (increased bias)
- · Platforms reliant on traditional ranking
The credibility and neutrality of LLM-generated answers will be undermined by strategic optimization.
Public discourse and decision-making could be distorted due to biased information presented as fact by AI.
Governments and regulatory bodies will face new challenges in ensuring information integrity and preventing manipulation at scale.
This signal links to a primary source. Continuum Brief monitors and indexes it as part of the live intelligence stream — we do not republish source content.
Read at arXiv cs.AI