✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

Solar eclipse pages by city in the path

NASA GSFC publishes the path of totality and annularity for every solar eclipse. SleekRank reads that path, mounts /astronomy/solar-eclipses/{slug}/, and renders one page per eclipse and city with contact times, obscuration percent, duration of totality, and a path map for each city.

€50 off for the first 100 lifetime licenses!

SleekRank for Solar eclipses by year and city in the path

One solar eclipse path point becomes one indexed city page

The April 2024 total eclipse passed over more than 200 US cities. The August 2026 total over Europe will pass over another 150. The October 2023 annular crossed about 60 US cities. Across the next two decades, NASA's path data covers thousands of city points for the eclipses the public will travel to see.

SleekRank reads the path data as a CSV where each row is one eclipse and one city on the centerline or nearby. The route mounts at /astronomy/solar-eclipses/{slug}/ with slugs like 2026-08-12-bilbao or 2024-04-08-dallas-tx. The page renders first contact, second contact, maximum, third contact, fourth contact, duration of totality or annularity, sun altitude, and obscuration percent.

Eclipse traffic is bursty. The week before totality, search demand for "eclipse times in Carbondale" or "obscuration in Boise" peaks. Hand-writing per-city posts a week before the event is impossible. SleekRank publishes the full grid the day the path is finalized, then refines as NASA updates the prediction.

Workflow

From path coordinates to indexed per-city pages

1

Build the path-city CSV

For each upcoming eclipse, list the cities on or near the centerline along with their contact times, duration, and obscuration. NASA GSFC publishes the underlying path; a small script samples cities and writes the CSV.
2

Mount the SleekRank page group

Configure urlPattern as /astronomy/solar-eclipses/{slug}/, point at the CSV, and choose a base page that holds the template. The plugin handles the route registration.
3

Write one Twig template for total, annular, and partial

Branch on the eclipse type field to label durations correctly. Surface contact times in the city's local time zone, duration in seconds, obscuration percent, and a map of the path through the city.
4

Flush rewrites before the pre-eclipse traffic spike

Run wp rewrite flush a week before totality, regenerate the sitemap, and submit it to Search Console. The full set of city URLs gets crawled in time for the demand peak.

Data in, pages out

Sample row from the NASA solar eclipse path

Each row carries the eclipse date, eclipse type, city name, latitude, and duration of totality or annularity at that point.
Data source: NASA GSFC solar eclipse path data
slug eclipse_date eclipse_type city totality_seconds
2024-04-08-dallas-tx 2024-04-08 Total Dallas, TX 230
2026-08-12-bilbao 2026-08-12 Total Bilbao, Spain 108
2027-08-02-luxor 2027-08-02 Total Luxor, Egypt 381
2023-10-14-eugene-or 2023-10-14 Annular Eugene, OR 264
2024-04-08-cleveland-oh 2024-04-08 Total Cleveland, OH 238
URL pattern: /astronomy/solar-eclipses/{slug}/
Generated pages
  • /astronomy/solar-eclipses/2024-04-08-dallas-tx/
  • /astronomy/solar-eclipses/2026-08-12-bilbao/
  • /astronomy/solar-eclipses/2027-08-02-luxor/
  • /astronomy/solar-eclipses/2023-10-14-eugene-or/
  • /astronomy/solar-eclipses/2024-04-08-cleveland-oh/

Comparison

City-by-city blog posts vs SleekRank for solar eclipses

City-by-city blog posts

  • Coverage stops at maybe 20 cities even though the path crosses 200
  • Contact times pasted in once and never updated as NASA refines path data
  • Obscuration percent often missing or copied from a neighboring city
  • Pre-eclipse traffic spikes hit pages that were written months ago and never reviewed
  • Each post invents its own structure, so comparisons across cities are impossible
  • Old eclipse posts linger and confuse visitors searching for the upcoming event

SleekRank

  • Path-of-totality CSV drives per-city URLs at /astronomy/solar-eclipses/{slug}/
  • Contact times localize per city using time zone field on the row
  • Duration of totality or annularity renders to the second on each page
  • Obscuration percent and sun altitude come from the same row
  • Related cities along the path render via a shared eclipse date field
  • Event schema and OG image fully populated from the row

Features

What SleekRank gives you for Solar eclipses by year and city in the path

Path data as the canonical source

NASA publishes path coordinates and contact times for every solar eclipse. Save that as a CSV with one row per city near the centerline, plus duration and obscuration. SleekRank reads the file and renders one URL per row, so the full path coverage exists on day one of publication.

Built for the pre-eclipse traffic spike

Search demand for path cities peaks in the week before totality. SleekRank pages are cached at the row level and served from WordPress like any other page, so the spike is handled by the existing CDN and cache layer instead of a per-page editorial sprint.

City-level detail without per-page work

Each row carries city name, latitude, longitude, time zone, contact times in UTC, duration in seconds, obscuration percent, and sun altitude at maximum. The same Twig template surfaces all of it, so adding a new city is one CSV row, not a new WordPress post.

Use cases

Where eclipse-focused publishers use SleekRank

Astronomy news sites

Cover every city on the path of the next totality from one CSV. As NASA refines the path, the pages refine with it. After the event, the archive remains searchable by city.

Travel publishers

Pair city contact times with hotel and lodging recommendations on the same page, all driven by the row. Visitors planning travel get the data and the booking link in one URL.

Education and outreach groups

Local libraries, schools, and planetariums embed their nearest path-city page into their own outreach pages, knowing the data matches the NASA prediction exactly.

The bigger picture

Why per-city pages outperform a single eclipse hub post

Eclipse traffic is intensely local. Visitors search for the contact time in their city, not the global summary, and they search in the week or two before the event. A site that publishes one hub post and a handful of major-city posts captures only a sliver of that demand, because the long tail of intent is hundreds of smaller cities along the path.

SleekRank closes that gap structurally. The path data describes the cities. The site renders the pages.

The editorial team writes one explainer about the event itself and leaves the city detail to the dataset. The same model applies to every future eclipse. The 2027 total over North Africa and the Middle East will cross hundreds of cities the average Western publisher has never written about.

With SleekRank, those cities exist on the site the day the path is finalized, indexed in time for the pre-event traffic spike. Years later the archive remains useful for historical lookup, since the rows do not need maintenance to keep serving correct historical times.

Questions

Common questions about SleekRank for Solar eclipses by year and city in the path

A CSV or JSON with one row per eclipse-city pair, carrying date, type, city name, latitude, longitude, time zone, UTC contact times, duration in seconds, obscuration percent, and sun altitude at maximum. NASA's path data plus a city list with time zones provides everything you need.

 

Yes. Add rows for cities with partial obscuration above whatever threshold you choose, like 50 percent. The same template handles both totality and partial cases. The page can read the eclipse type field and adjust copy and visualization accordingly.

 

Each city row carries a time zone identifier. SleekRank converts UTC contact times to that zone at render time, including daylight saving handling. Readers in Dallas see CDT, readers in Cleveland see EDT, all from the same UTC source.

 

Most sites keep the pages live with a status field that flips them into archive mode. The page still shows the historical contact times but hides the countdown and adds a back-link to the next upcoming eclipse on the same path or in the same region.

 

Yes. The related entries helper sorts the dataset by latitude and longitude proximity, so the page for Dallas links to the next cities east and west along the path. Visitors planning a drive to a clearer-sky spot get the option without leaving the page.

 

Yes. The eclipse type field distinguishes total, annular, hybrid, and partial. The template branches on type to label durations correctly. An annular eclipse page calls out duration of annularity. A partial page omits the duration block and emphasizes obscuration.

 

Yes. Either pre-render a path image keyed by city slug and store the URL on the row, or pass the city's coordinates to a map tile service at render time. SleekRank does not lock you into either approach. Sites with their own mapping stack drop it in.

 

Some sites add a climatological cloud cover field from NOAA's historical data and surface it on the page. Others link out to a live weather widget for the city. Both are template choices, since the underlying row already carries latitude and longitude.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€99

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€179

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Launch Offer

€299

€249

EUR

once

Get started

further 30% launch-discount applied during checkout for existing customers.

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView