Israel–Palestine
Rafah offensive
Language openings contradict each other on something important.
Something to inspect — not a judgment of bias or bad faith.
Overview
Use this briefing to choose what to inspect. The tabs contain the underlying comparisons.
Open the live English Wikipedia article ↗L1 ran on this article and exact checking did not confirm a durable rewrite. This does not mean the article never changed.
Different websites cited: 70 → 86. We do not rate those sites. See Citations.
Compared around the rewrite window. See Framing.
Did editors fight over it?
The page was not dominated by back-and-forth undoing. A quiet rewrite can still matter — it just means few people fought it on the page. About 2,238 recorded revisions in the measure.
Who wrote today’s text?
Half of the wording still on the page is about 1.9 years old or newer. 100.0% was written in the last 3 years. The ten most active accounts wrote 92.9% of what is there now (most of the current text comes from a small group of accounts; 157 different accounts overall). Snapshot data on this page runs through 2026-07-01.This is background only — a small group of writers is common on specialist pages.
Available evidence: Rewrite (no candidate found), Vocabulary, Citations, Framing, Versions.
Not available in this export: Facts. Missing coverage is not a negative finding.
No candidate rewrite window was confirmed
The exact L1 check ran, but no candidate showed the required durable-spine drop. This is a completed negative result for that detector, not a claim that the article never changed.
Persistence-weighted changeThe share of wording lost, weighted so text that survived more snapshots counts more. by interval
Each row reports established wording lost, standing wording gained, and paired change as a replacement lead. The bar shows loss for continuity with earlier reports. Below-floor anomalies remain descriptive evidence but cannot receive exact confirmation. A coverage gap is shown descriptively but excluded from detector decisions. Candidate-window labels report the exact revision-level decision for the broader window containing that interval.
How the detector reached this state
- 1 · Coarse scanA snapshot comparison that finds candidate windows for closer inspection.No candidate signalNo measured interval crossed the detector's candidate threshold.
- 2 · Interval scoring4 intervals scoredThe bars below show persistence-weighted wording loss for each interval.
- 3 · Exact checkA revision-level test of whether a candidate window's durable spine collapsed.Not neededNo coarse candidate was sent to revision-level checking.
- 2025-01-01Loss 0.8%473 removed · 0 added PWRMeasured: no anomaly threshold crossed
- 2025-07-01Loss 1.2%2,152 removed · 0 added PWRMeasured: no anomaly threshold crossed
- 2026-01-01Loss 1.7%5,281 removed · 0 added PWRMeasured: no anomaly threshold crossed
- 2026-07-01Loss 0.1%298 removed · 0 added PWRMeasured: no anomaly threshold crossed
Which words grew or shrank?
Words that became more common or less common between the compared versions. Handy for noticing a shift in topic or tone — not a score of bias.
Comparing 2024-07-01 -> 2026-07-01 (no L1 pivot — whole history). Rough word count: 6,360 → 13,039. Overall: small vocabulary change.
Used more afterward
- july0 → 43
- september0 → 41
- august0 → 39
- november0 → 36
- december0 → 35
- january0 → 34
- april0 → 28
- janina0 → 22
- adas0 → 10
- recovered0 → 10
- october2 → 50
- khirbet0 → 9
Used less afterward
- events3 → 1
- accepted2 → 1
- closing2 → 1
- necessary2 → 1
- relating2 → 1
- resulted2 → 1
- sought2 → 1
- million6 → 4
- almost3 → 2
- evacuated3 → 2
- impact3 → 2
- present3 → 2
These are the standout words, not a full dictionary of the article. Boring markup words are filtered out. Treat this as a hint, not a conclusion.
How the footnotes changed
How the article's own footnotes changed across the rewrite: which websites and books were cited more or less. We only show the mix — we do not rate sources as good or bad.
Looking at 2024-07-01 → 2026-07-01 (no L1 pivot — whole history): 40 websites were cited more (or newly), 4 less (or dropped). Number of footnotes: 506 → 1014. Different websites: 70 → 86.
Mix of citation types: web 79%, news 21% → web 62%, news 38%.
| cited more often | before → after |
|---|---|
| aa.com.tr | 3 → 99 |
| reuters.com | 64 → 145 |
| understandingwar.org | 5 → 85 |
| timesofisrael.com | 53 → 124 |
| jpost.com | 28 → 69 |
| aljazeera.net | 0 → 15 |
| jns.org | 3 → 17 |
| aljazeera.com | 130 → 140 |
| ynetnews.com | 7 → 14 |
| bbc.com | 16 → 22 |
| apnews.com | 11 → 16 |
| haaretz.com | 8 → 12 |
| cited less often | before → after |
|---|---|
| amp.theguardian.com | 2 → 1 |
| aje.io | 1 → 0 |
| wsj.com | 5 → 4 |
| archive.is | 1 → 0 |
Counted from the article’s own footnotes. We list domains only — we do not call any source trustworthy or untrustworthy.
Cross-language lead comparison
How the opening of the article presents the topic in different languages. Disagreement is a reason to read carefully, not a final answer.
The editions diverge significantly in framing, scope, and factual emphasis. EN presents a military-operation narrative with a timeline including the 2025 ceasefire and resumption of hostilities. AR emphasizes Israel's rejection of Hamas-accepted ceasefire proposals, differing from EN's statement that negotiations failed. HE frames the event as a tactical battle with detailed IDF unit compositions and casualty and tunnel-destruction claims absent from EN. DE includes international legal context and hostage-related motivations absent from EN. BN describes deliberate ethnic cleansing, destruction in Rafah, and global political reactions not found in the other selected leads. These are differences for further inspection, not a judgment about which edition is correct.
Languages compared: en, ar, he, bn, de.
contradict opposite claims · differ different emphasis · missing only one side mentions it
| topic | how they compare | English says | other language(s) say | languages |
|---|---|---|---|---|
| Nature/framing of the event | differ | Military offensive with goals of defeating Hamas and securing border/crossing | HE frames it as a 'battle' (קרב) between IDF and terror organizations; DE frames it as pressure tactic for hostage negotiations and cites international condemnation; BN frames it as deliberate destruction/depopulation of Rafah city and ethnic cleansing of Palestinians | HE, DE, BN |
| ICJ ruling on genocide/ceasefire order | missing in English | not mentioned | South Africa filed a case against Israel for genocide convention violations; ICJ ordered Israel on 24 May 2024 to halt its military offensive on Rafah, which Israel ignored “Das Gericht wies Israel am 24. Mai 2024 an, seinen Militärangriff auf die Stadt Rafah einzustellen. Trotz dieser Anordnung setzte Israel die Offensive fort.” | DE |
| Ceasefire negotiations and Hamas acceptance | contradict | Ceasefire negotiations brokered by Egypt and Qatar failed before the operation began “The operation began as ceasefire negotiations brokered by Egypt and Qatar failed.” | Hamas accepted the Egypt/Qatar-brokered ceasefire proposal on 6 May, but Israel rejected it and continued the offensive, having already rejected an earlier ceasefire proposal accepted by Hamas “أعلنت حماس قبولها اتفاق وقف إطلاق النار الذي اقترحه كلا من مصر وقطر، لكن إسرائيل لم تقبل بالاتفاق” | AR |
| Casualty and destruction figures | missing in English | not mentioned in lead (casualty figures) | HE states IDF killed over 2,000 militants and destroyed 13km of tunnels; BN states 60 sq km of Rafah destroyed, home to 300,000 people, completely razed | HE, BN |
| Israeli military units involved | missing in English | not mentioned | Detailed listing of IDF units: Steel Formation (162nd Division) under Brig. Gen. Itzik Cohen, including 401st Armored Brigade, Givati and Nahal infantry brigades, Oz and Negev brigades; moved to northern Gaza in October 2024 “הכוח הצה"לי העיקרי במבצע היה עוצבת הפלדה (אוגדה 162) בפיקוד תא"ל איציק כהן” | HE |
| Global protest and Saudi threat of oil embargo | missing in English | not mentioned | Palestine called for global strike on 7 April 2025 in protest; Saudi King warned US that Arab world would consider reinstating a 1973-style petroleum embargo if Israel does not agree to a peaceful solution | BN |
Differences are invitations to read both sides — not a score of who is right.
Versions we used
These are the exact public Wikipedia versions behind the checks on this page. Open any link to read the original. Wikidata item: Q124512668.
| language | comparison point | article title | version | when | text used (chars) |
|---|---|---|---|---|---|
| en | saved | Rafah offensive | open version 1357159391 | 2026-06-01T02:12:34Z | 138,834 |
| he | saved | קרב רפיח (2024) | open version 43466530 | 2026-06-21T11:28:33Z | 24,271 |
| ar | saved | هجوم رفح 2024 | open version 74208236 | 2026-04-08T18:04:03Z | 18,997 |