Battle of Wadi al-Laban
1558 battle in Morocco
The Battle of Wadi al-Laban (Arabic: معركة وادي اللبن) occurred in March–April 1558 between Saadians and Ottoman Algerian forces under Hasan Pasha, the son of Hayreddin Barbarossa. It took place north of Fes, at Wadi al-Laban, an affluent of the Sebou River, one day north of Fes.
Background
This conflict took place in a context of tensions between Algeria and Morocco. Hasan Pasha son of Hayreddin Barbarossa, the ruler of the Regency of Algiers on behalf of the Ottoman Empire, captured Fes from the Saadians in early 1554 and installed a Wattasid client. The Saadian ruler Mohammed al-Shaykh recaptured the city later that year. Following the return of the Saadians, numerous conflicts broke out between Algeria and Morocco, which tried to annex the Algerian city of Tlemcen. Mohammed al-Shaykh subsequently sought an alliance with the Spaniards who were occupying Oran at the time and were fighting the Ottomans as well, but the agreement failed to materialize.
Hasan Pasha, the son of Barbarossa, was reappointed beylerbey of Algiers by the Ottoman sultan Suleiman I in June 1557. The Ottomans sent the Saadian sultan an embassy demanding he recognize the overlordship of the Ottoman sultan, which Mohammed al-Shaykh refused. Mohammed al-Shaykh was then assassinated in October 1557 by Turkish officers sent by Istanbul and entered into Saadian service under the pretense of being deserters.
This brief starts where responsible research should: with the source description of “Battle of Wadi al-Laban” as 1558 battle in Morocco. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as 1558 battle in Morocco. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Aug 20, 2026. The linked authority identifier is Q4117011. Authority coordinates are 34.300, -4.900. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1558, 1554 and 1557.
Institutional narratives can privilege the records that survived while minimizing voices that were never formally collected. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Battle of Wadi al-Laban”, its source revision and the description used here.
- Expand the search: follow Battle of Wadi al-Laban primary sources, Battle of Wadi al-Laban archive and Battle research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Battle of Wadi al-Laban”?
- Who created the surviving record, and for what administrative purpose?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “Battle of Wadi al-Laban” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.