Corrections and updates
This page explains what kinds of corrections are useful, what makes a report actionable, and how the site handles city issues, mosque issues, naming issues, duplicate cleanup, and update timing.
Useful corrections include city prayer-time issues, mosque naming issues, wrong mosque location, wrong owner city, duplicates, service details, and mosque-specific Friday or iqama information when that belongs on the mosque page.
Arabic and English naming improvements are also valuable when the existing naming is weak, incomplete, or confusing for visitors.
The most useful report is one tied to the correct page. That is why the best path is to open the city or mosque page first, then send the update from there instead of describing the issue in a detached way.
Clear naming, map context, address clues, and a precise description of the issue all make review faster.
If the problem belongs to the city page itself, such as city naming, weak local context, or a prayer-time issue, the correction is treated at the city level so related schedules, locality links, and supporting pages benefit together.
That matters because a city-level problem can affect much more than one URL.
If the issue belongs to one mosque, the site reviews the name, services, links, and owner-city relationship. If the mosque is attached to the wrong city, the canonical page is corrected and the wrong path can be redirected to the right one.
If the report is about a service, Friday time, or description issue, the change is applied to the mosque record itself rather than creating a new page.
Some updates can appear quickly when the evidence is clear. Others may wait for a review pass, a cleanup cycle, a rebuild, or search recrawl before the full change is visible.
That means the internal correction can happen before every external signal catches up, especially during larger site moves or structural cleanup.