Fred Espenak's NASA eclipse canon is the canonical reference, free to use with attribution, covering eclipses from -2000 to +3000 with precise geometry. Derived CSVs are available from multiple academic sources. The data is fully static so a one-time import covers everything; only the editorial layer needs ongoing maintenance.

Compute the central path geometry from the catalog and intersect with a global cities database (GeoNames or similar) to find cities within 10 km of the centerline. The resulting cities array is stored on the eclipse row and rendered via list mapping. For major eclipses, this list is the single most-searched piece of content.

Yes, as a second page group: /eclipses/{eclipse}/{city}/. The source joins the eclipse row with a cities-in-path list, producing one URL per (eclipse, city) combination. This is where the highest-volume search queries live (April 2024 Dallas, August 2027 Cairo, etc.) and where indexable per-city geometry pays off.

Past eclipses earn evergreen reference traffic for years. The same template renders both upcoming and historical events; a status column distinguishes them. Historical pages often add a postEclipseSummary column with photos, viewing reports, and notable observations linked from the canonical data.

Event schema with eventSchedule (the precise UTC contact times), location (Place with the central-line geometry), and image (a path map). Some publishers also use Article schema layered on top for the editorial coverage. Google's SERP has rendered Event panels for major eclipses in past indexing cycles.

Yes. The catalog distinguishes total, annular, hybrid, and partial; the template can branch on type to render the appropriate geometry block (annularity ring for annular, magnitude percentage for partial). Lunar eclipses (penumbral, partial, total) use a parallel page group with different geometry.

For eclipses with no central path on land (open-ocean totalities) or with very low magnitude in the page's target locale, set a meta robots=noindex via a mapping. Better still, exclude them from the page group entirely with a source query filter. Quality over quantity wins for SEO on this topic.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page. The catalog is fully static so all URLs are known up front; the sitemap doesn't grow unexpectedly. For new major eclipses approaching, manually requesting indexing in Search Console accelerates discovery.