- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper proposes Nash-GEO, a game-theoretic framework that helps platforms to set policies to reduce the gain from presentation GEO edits from the publishers. It formulates the interaction between the publisher and the platform as a Stackelberg game, where the platform designs defense policies, and publishers modify content to increase citation exposure based on the platform's policies. Nash-GEO aims to discourage presentation edits while rewarding useful supporting material through adaptive strategy evaluation and policy refinement.
Critical strengths
- The paper adapts the game theory strategy in the GEO framework. This application could potentially solve the arm-race GEO game between the platform and the publisher. This Stackelberg formulation opens up a new direction in the GEO regulation field.
Critical weaknesses
-
The assumption is unrealistic. Nash-GEO assumes it has access to the original document before and after edits. In reality, the platform would not know whether the current version of the website has been edited for GEO or not, which keywords were added recently, or which content belongs to presentation manipulation. So the screening stage will fail in the real world.
-
There is no threat model section to clearly identify the platform and publishers. What are their capabilities and goals? Are Internet users involved in the framework?
-
In the introduction Section, it is better to give examples of presentation edits using common keywords. The main result presented in the introduction section is not briefly explained. Are the metrics higher the better or lower the better? This helps improve readability, even though there is a more detailed explanation in the experiment section, because this metric is not that common.
-
Some sentences are too short and not self-explanatory. For example: "The platform moves first, the Stackelberg setting (Conitzer & Sandholm, 2006)", "strategic classification studies rules that subjects adapt to (Hardt et al., 2016; Milli et al., 2019)". The related work section or background section is designed to help readers understand the basic knowledge that is connected to this paper, but not just listing the academic papers' names.
-
"Earlier citations receive more exposure." This sentence needs a citation since the framework uses ranking-related metrics below.
-
3 metrics are introduced here: normalized reciprocal rank, discounted cumulative gain, and rank-biased precision, but only Unnormalized Reciprocal Rank is used. This is inconsistent.
-
Some mathematical notations have no explanation, which will confuse readers. What is the value of , the editing cost , revealed by the platform, , ,engine probability, , , , etc.? Every mathematical notation in the paper needs to have a formal definition. The paper introduces too many mathematical notations. It would be better to simplify it and help improve readability.
Questions for authors
See the weaknesses;
-
The whitespace-only normalization also has a low manipulation advantage. Does Nash-GEO also include the whitespace-only normalization operation? It seems there is no benefit from Screening. Can you clarify what additional benefits Nash-GEO provides beyond simple text preprocessing?
-
Why do you only compare to SafeGEO-L1? SafeGEO has a complete framework from L1 to L5. If you choose SafeGEO as your main benchmark, it is better to have a complete comparison rather than just comparing with the basic SafeGEO-L1.
3 comments
Response to Reviewer JhPP (Quesitons)
Q1. Benefit beyond whitespace and text preprocessing
Yes. The full normalizer includes whitespace normalization. On the same two searched edits, whitespace alone leaves a 1.94% advantage and our policy 0.51%. The paired reduction is 1.43% (submitted Appendix D.10, Table 18).
In a separate exploratory analysis on the same 200 questions and four engines, we used engine scores to choose edits against each policy rather than giving them the same edits. The advantage was 3.27% under whitespace and 0.68% under ours. Whitespace explains about two-thirds of the original reduction. The difference on the fixed nine-edit set is unresolved.
The policy is preprocessing by design. Nash-GEO evaluates and selects such policies against publisher responses, not only a fixed edit list. In the submitted label-repair study, renewed search found no established advantage for a promising revision, so it was not adopted (Section 5.2 and Appendix D.4).
The screen makes no difference to the headline. It improves the gap by 0.98% in the separate QAMPARI test of added query terms (Section 5.3). That is why we report the screen separately rather than make it a requirement for using the normalizer.
Q2. Comparison with SafeGEO-L1 to L5
The submission used L1 as a prompt-level baseline, not a test of the whole SafeGEO framework. We now include L2–L5. Each policy saw the same edits on the 200 ASQA questions and four engines.
| Policy | Manipulation advantage (%) |
|---|---|
| No defense | 8.32 |
| SafeGEO-L1 | 8.40 |
| SafeGEO-L2 | 8.13 |
| SafeGEO-L3 | 6.58 |
| SafeGEO-L4 | 8.27 |
| SafeGEO-L5 | 8.06 |
| Our policy | 1.06 |
Thanks for your clarification; here is my response.
W2: Your response did not fully resolve my concerns about the reality assumption. Showing "Deletion only" matches the full policy (0.51%) on the two searched edits does not prove that the screen is optional in reality. In your Appendix D.3, it says every admissible submission passes the screen by construction, and Appendix D.9 constrains searched candidates to survive it. In practice, publishers have no such constraints. So, skipping the screen exposes the platforms to an unconstrained environment. In your experimental setup, the screen adds a +0.98% improvement in Table 8. Or are you trying to claim that "screen" is not that helpful?
Without the original document, both the screen and Proposition 2 become undeployable. Then the only thing left is the rule-based deletion normalizer. In Proposition 2(b) and Proposition 11, it says rule-based methods suffer from fundamental theoretical limitations and can sacrifice the citation reward for useful supporting material.
W3: I can't find the content that you said was added to section 1.
Response to Reviewer JhPP (Weakness)
We thank the reviewer for raising the distinction between the policy's inputs and what we need to measure an edit's effect. We respectfully clarify that the screen, but not the normalizer, needs a reference copy. Differences below use the paper's absolute percentage scale.
W1. Access to the document before and after editing
Section 4.2 now distinguishes what the two components need. The normalizer reads only the submitted text. The screen also needs a reference copy and the declared supporting sentence. A previous crawl is not necessarily an unmanipulated reference.
Section 5.3 now reports the “Deletion only” result from Table 17 of the submission. This runs the full normalizer without the screen, not just whitespace normalization. On the original 200 questions, four engines, and two searched edits, it lowers manipulation's advantage from 4.99% to 0.51%, the same result as the full policy. Thus, for the headline comparison, a platform without a reference copy can use the normalizer and skip the screen.
Comparing edited with unedited outcomes measures an edit's gain. The normalizer does not read both versions. Proposition 2's recovery benchmark does assume the original source and correct support identification, unlike the normalizer.
W2. Threat model: publishers, platform, and users
We agree that the actors' roles should be stated together. Section 3.2 now opens with a threat-model paragraph that describes the publishers, the platform, and the users.
W3-W7. Examples, metrics, related work, and notation
We recognize that these passages were too compressed.