NOAA Space Weather Prediction Center (SWPC) publishes free Kp, Hpo, and OVATION auroral oval forecasts in JSON. The data updates every 30 minutes. A server-side step pulls SWPC data and combines with each city's geomagnetic latitude to compute a city-specific viewing-odds score, written into the page HTML.

Aurora visibility depends on geomagnetic latitude, which differs from geographic. Tromso is at 70 N geographic but 66 N geomagnetic; Cleveland is at 41 N geographic but 49 N geomagnetic. Geomagnetic latitude is more aurora-relevant and should anchor every city page. The conversion uses the IGRF model and is stable year to year.

Both. Today's forecast lives in the hero (Kp, odds, viewing window). A list mapping renders the next 3 days from SWPC's longer-range forecast. Best-months calendar lives below as static editorial. The hero refreshes on the cache cadence; the calendar refreshes annually.

Forecast methodology is the same; expected rates differ. During solar minimum, even high-latitude cities see fewer activity nights; during maximum, mid-latitude cities catch occasional shows. The historical-odds column on each city row reflects the long-term average, while the tonight number reflects current conditions.

Yes. Add an operatorIds column listing tour operators serving each city, and render a list of operators on each city page (linking to /tour-operators/{slug}/ pages from a parallel directory page group). This funnels SEO traffic into a booking flow without per-page editing for the operator roster.

Place schema for the city itself, with a forecast field linking to GeoCoordinates and a hasMap field linking to a static auroral-oval map. Some sites add Event schema for the forecast window itself (eventStatus=EventScheduled, startDate=tonight). The Place pattern is more durable.

Add a hemisphere column and a parallel /aurora-australis/{slug}/ page group for southern destinations (Hobart, Stewart Island, Ushuaia, South Georgia). Same template, different cities, with the SWPC forecast remapped for southern auroral oval position. The southern audience is smaller but underserved.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page. New destination cities added to the source roster appear on the next refresh, usually within hours. For storm-driven sudden traffic, sitemap freshness rarely matters; the existing URLs already rank.