Any method the upstream API or precomputed dataset supports, since SleekRank reads fields rather than computing times itself. Aladhan handles MWL, ISNA, Egyptian, Karachi, Diyanet, UAQ, JAKIM, Tehran, MOON, and Singapore. Storing the method per row means each city renders with the method its local community follows, which is what local search expects.

Qibla in degrees from true north is a deterministic calculation from coordinates, so it can be precomputed once per city and stored as a number on the row. Render it via a selector mapping into the page body alongside an SVG compass that points to the same angle, so users see the direction as both text and visual.

Yes. Hanafi and Shafi methods produce different asr times, so store the chosen juristic method per row (Hanafi or Shafi) and have the source pass it to the API. The page renders the chosen method explicitly so users know which asr they are seeing, and a separate page group can serve the alternative method at /prayer-times-hanafi/{slug}/ if needed.

IANA time zones handle daylight saving automatically. The astronomy and prayer calculations always run against UTC and convert to local clock time via the stored time zone, so the displayed times shift correctly on the night the clocks change. Some regions use special prayer-time rules around DST; store any exceptions as flags on the row.

Yes. The same data source that powers today's row can deliver a full month of upcoming times. Render today's times prominently in the hero, then list the upcoming month as a table via a list mapping. The page stays useful for both immediate-intent users and planners.

Daily refresh is appropriate, with a cacheDuration of 86400. The math is deterministic for a given date and location, so there is no need for hourly updates. The meta description should reflect today's maghrib so the page always feels current when seen in search results.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page so only city URLs get crawled. New cities added to the feed appear in the sitemap on the next cache refresh, which matters when expanding into new audiences.

Either store a mosque list per city row and render it via a list mapping on the same page, or run a separate page group at /mosques/{slug}/ that shares the city slug. Internal links between prayer times and mosque pages compound topical relevance for the city, which helps both URLs rank for related queries.