Online reputation monitoring in Morocco is not a scaled-down version of European monitoring. The landscape is concentrated, multilingual and asymmetric: one Arabic-language pure player dominates online attention, French-language business press shapes the decision-makers' debate, and a massive share of how information travels never touches a news site at all — it moves through WhatsApp groups and Facebook shares. Transposing a playbook designed for Paris or Brussels wholesale produces a blind apparatus. This guide describes the method we apply at Harch Atelier to build monitoring that holds up on Moroccan ground.
It is written for communications directors, comms teams, risk officers and agencies managing brands present in Morocco. Every step is operational: sources, queries, sentiment, alerting, steering. No step requires a specific tool — but every step degrades fast without method.
Step 1 — Map the sources that actually matter
The first classic mistake is limiting coverage to the titles you personally read. The real hierarchy of attention is different: on the Arabic side, Hespress dominates volume and reactivity, followed by aggregators and the MAP news agency; on the French side, Medias24, TelQuel and Le360 set the pace of the flow, while L'Economiste and Les Éco dominate the business audience and Aujourd'hui le Maroc the generalist press; in English, Morocco World News covers the story for international readers. Above all of this, a second pan-African and international circle — Financial Afrik, Africanews, Jeune Afrique, then Le Monde or the Financial Times when the story crosses borders — can turn a local incident into an affair.
Step 2 — Build queries that survive the field
A single brand-name query is never enough. In Morocco, the same entity circulates under several spellings: variable Arabic-French transliterations, acronyms, product names distinct from the corporate name, executives quoted without the company being named. You need distinct query layers, each with its own alerting logic.
- Brand layer: corporate name, acronym, alternative spellings, name in Arabic script.
- People layer: executives and spokespeople, with their common spelling variants.
- Product layer: commercial names, campaigns, customer services.
- Ecosystem layer: sector regulators (Bank Al-Maghrib, AMMC, ANRT…), direct competitors, industry associations.
- Crisis layer: incident keywords — boycott, outage, dispute, layoffs, strike — in Arabic and in French.
Step 3 — Sentiment, in Arabic as in French
The breaking point between an artisanal apparatus and a serious one is language handling. Sentiment does not aggregate naively across Arabic and French: registers, irony and the polarity of Arabic comments — often written in Darija, sometimes in Latin script — defeat tools built for English or French media. Our house rule is simple: measure sentiment by language, by source and by cluster, and never fuse languages into a single global score before checking that they tell the same story. We devoted a full article to the Darija problem; the short version is that a single, language-blind sentiment score is a decorative score.
Step 4 — Alerts: WhatsApp first
In Morocco as across Africa, the useful alert is the one that reaches the person at the moment they can act. A daily email does not fill that role: information circulates continuously, often in the evening and on weekends, and the useful response window is measured in hours. This is why we built Harch Atelier's crisis alerts on WhatsApp: a short message, ranked by severity, with the source and the link, pushed to the phones of the people empowered to decide. Everything else — full feed, trends, history — stays in the dashboard.
- Define an abnormal-volume threshold against your baseline (never an absolute number).
- Add a sentiment trigger: fast sentiment drop within one source cluster.
- Add a source trigger: the brand appearing in a headline from a first-circle outlet.
- Route severe alerts to WhatsApp; weak signals to the daily digest.
- Review thresholds monthly: a chatty alert is an alert that gets switched off.
Step 5 — Keep the dashboard alive
Monitoring dies when nobody looks at it. A living apparatus rests on a short, kept ritual: thirty minutes a week, same time, same questions. Has the HarchIQ score moved? Which sources carried this week? Which language cluster is deviating? What is share of voice against competitors? A dashboard that answers those four questions on one screen is enough; everything else is cosmetics.
The five mistakes that cost you
- Monitoring in French only: you miss the majority of the volume — and often the earliest crisis signals.
- Counting mentions without weighting sources: three Medias24 or L'Economiste headlines outweigh three hundred blog spam mentions.
- Ignoring comment sections: Hespress threads and Facebook pages are sentiment power plants, not annexes.
- No baseline: you cannot tell an abnormal surge from an ordinary Tuesday.
- Alerts without severity ranking: the team unlearns reading them within two weeks.
“An alert nobody reads at ten in the evening is not an alert — it is a log.”— Nadia El Idrissi, Crisis Communications Lead, Harch Atelier
The ninety-day starter plan
- Days 1–15: source map validated, queries documented, volume and sentiment baselines established.
- Days 16–45: alerts in production, severity ranking, first weekly reviews.
- Days 46–75: people, product and regulator layers added; competitive comparison.
- Days 76–90: first quarterly report grounded in data, threshold review, broader-team training.
Reputation monitoring is not a project, it is a discipline. In Morocco more than elsewhere, speed and language make the difference between a team discovering its crisis and a team defusing it. Start small, keep the ritual, and let the method — not the tool — carry the apparatus.