Verification methodology
How Mosque Database verifies mosque records
Mosque Database verifies mosque records by collecting structured public source signals, checking names and addresses, validating websites and contact fields, preserving coordinates, marking lifecycle status, and routing uncertain records for human review.
Directory coverage signals
- 872 reviewed public mosque profiles
- 48 state browse pages
- 559 city browse pages
- 825 mapped mosque profiles with coordinates
- 866 profiles with official website links
- 838 profiles with phone numbers
Evidence-first records
A useful mosque profile starts with fields that visitors can verify: address, phone, website, public profile links, map coordinates, official schedule links, and public community pages. The system treats these as product data, not loose content.
Lifecycle status
Records can be verified, need confirmation, require human review, or be treated as inactive candidates. This makes uncertainty visible instead of silently presenting weak records as canonical places.
What is not inferred
Mosque Database does not add inferred imam names or size buckets as core directory data. Those fields were removed because they were too correlation-based to trust as public directory facts.
FAQ
What counts as a verified mosque?
A verified mosque has enough reviewed source evidence to present as an active canonical directory record.
How are bad records handled?
Questionable records are routed through review states and correction reports instead of being promoted automatically.