Skip to content

Methodology: Sources, Transliteration, and Tajweed Review

This page explains how the reader should be used, which sources are treated as reference points, and how corrections are handled. The goal is to make the project useful without overstating what transliteration can do.

Primary Source Policy

Quranic text, verse numbering, and recitation claims should be checked against established Quran and hadith references. Useful public reference points include:

  • Quran.com for Quran text, translations, and verse navigation.
  • Tanzil for Quran text verification and verse data.
  • Sunnah.com for checking hadith references mentioned in learning guides.

Review Status

Each SEO and learning change must preserve the reader as the core product, keep source claims conservative, and avoid presenting transliteration as a substitute for Arabic recitation. Pages that mention hadith, recommended recitation times, or religious practice should include enough context for a reader to verify the claim in a recognised reference.

Current baseline review date: 2026-04-28. Expert scholarly review should be added as a named reviewer only when a real qualified reviewer has approved the material.

Transliteration Limits

Transliteration writes Arabic sounds with Latin letters. It is useful for beginners, but it cannot perfectly encode Arabic articulation points, throat letters, emphatic letters, or all Tajweed details. For this reason, the site consistently presents transliteration as a bridge toward Arabic reading, not a replacement for it.

Tajweed Colour Coding

The reader preserves the colour-coded page images and pairs them with plain-English explanations of common rules such as Madd, Ghunnah, Qalqalah, Ikhfa, Idgham, Tafkheem, and silent letters. When a rule is uncertain or outside beginner scope, the guidance should avoid overclaiming.

Correction Process

  1. Log the affected page, surah, verse, or guide URL.
  2. Compare against primary references and the printed source page.
  3. Make the smallest correction possible.
  4. Rebuild, run tests, and verify the route remains crawlable.
  5. Keep corrections transparent through the project history.

Correction Log

Public corrections should be recorded with the affected URL, the reason for the change, the source used for verification, and the date the page was rebuilt. That history lets readers and search engines see that accuracy is maintained over time.

Latest sitewide SEO and reader-readiness review: 2026-04-29.