Hi everyone,
I’m currently working on a prayer-time project focused on Prayer Times in Riyadh and other Saudi cities, and I’ve started facing some scalability and indexing issues as the site grows.
The website currently includes:
Dynamic city-based prayer time pages
Daily Salah timings (Fajr, Dhuhr, Asr, Maghrib, Isha)
Automatic daily updates
Individual URLs for every city
Hijri calendar integration
Countdown widgets for next prayer
Example URL structure:
/saudi-arabia/riyadh-prayer-times/
/saudi-arabia/jeddah-prayer-times/
/saudi-arabia/makkah-prayer-times/
Right now, I’m generating pages dynamically and caching prayer data daily.
The main issue is performance.
As the number of pages increases, some pages become slower during cache refreshes and API calls. I’m trying to decide which structure would scale best long term.
I’m considering three options:
Store all prayer times inside a database
Generate static JSON files daily
Continue using external prayer-time APIs
Another issue is SEO/indexing.
Some pages get crawled by Google but remain in:
“Crawled – currently not indexed”
especially pages with frequently updated prayer-time data.
I checked a few similar projects related to namaz vakitleri and prayer schedules, and many seem to use lightweight static structures with scheduled cache generation instead of real-time API requests.
Questions:
What’s the best scalable architecture for city-based prayer time websites?
Is static generation better than APIs for SEO?
Best caching strategy for frequently updated prayer schedules?
Should daily prayer times be pre-generated overnight?
Any recommendations for improving indexing on dynamic location pages?
Would CDN caching help with prayer-time content?
Would really appreciate advice from developers who have worked on:
location-based websites
Islamic/prayer-time projects
dynamic time-sensitive content
large SEO-focused city pages
Top comments (0)