A server-side step pulls a fresh ISS TLE (Celestrak's stations.txt, refreshed roughly twice daily) and runs SGP4 propagation against each city's coordinates, returning the next N visible passes. Visibility filtering requires the pass to occur during astronomical darkness and the ISS to be sunlit at the pass time. The result merges into the city row before SleekRank caches it.

Yes. List mappings render the next 5 to 10 passes per city as repeated items, each with start time, duration, peak elevation, magnitude, and entry / exit azimuth. Most sites show 7 days; some condense to next 3 with an explicit 'check back tomorrow' note. The trade-off is data freshness (longer windows drift as TLE updates) versus content depth.

During low solar elevation seasons or unfavorable orbital geometry, some cities go a week without visible passes. The base page renders a 'no visible passes in the next 7 days' state with the next future pass date, so the URL still serves real information. Don't 404 these pages; they still answer the visitor query.

Yes. The SGP4 propagation handles all coordinates equally; visibility filtering is purely geometric. Cities near the equator see more passes per month than higher-latitude cities because the ISS orbit (51.6 degree inclination) covers them more frequently. The base template doesn't assume hemisphere.

Yes. Use additional page groups (/tiangong-passes/{slug}/, /hubble-passes/{slug}/) reading from the same city list with different TLEs. Most space-station-tracking sites publish ISS, Tiangong, and the brightest Hubble passes as parallel page groups. Each one earns its own search surface for the corresponding query family.

Event schema with eventSchedule references for each upcoming pass works. Some sites use Place schema to anchor the city itself with the event series rendered as repeated entries. The schema enhances SERP appearance with calendar-style results for queries like 'ISS pass Toronto'.

Set the pass-data cache to 6 hours and the underlying TLE refresh to twice daily. The combination keeps pass times accurate to within seconds for visible-pass time, well inside what visitors care about. For exact-time queries (astrophotographers planning shots), the page recommends a real-time refresh check at T-1 hour.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page. New cities added to the source roster appear on the next cache refresh. Most sites cap at a few hundred cities (the major search-volume targets) rather than aim for every settlement, to keep the page group focused and high-quality.