It generates one WordPress page per row in your source. Each page is a real URL with its own title, meta description, schema, and Twig template. The shower name, peak date, radiant, ZHR, moon phase, and city all come from the row, so the page is fully populated the moment the row exists.

Yes. SleekRank reads CSV, JSON, REST endpoints, and custom post types. Most astronomy sites store the AMS calendar as a CSV in the theme or as a fetched feed, define the route, and let SleekRank build the URLs. You can switch sources later without editing pages.

The slug column on each row is the authoritative URL fragment. Most sites combine the shower name, year, and a normalized city like perseids-2026-portland-or. SleekRank does not auto-generate slugs, so you keep full control of URL shape and history.

Edit the row, clear the SleekRank item cache, and the affected page rebuilds with the new peak window and any derived fields like moon phase. Other pages are untouched. There is no per-post editorial flush across the site.

Each page reads its own row, so title, meta description, Open Graph, and Event schema are filled in with that shower and city. SleekPixel can render a per-row OG image with the shower name and date burned in, so social previews are also unique.

Either drop expired rows from the source or add a status field and exclude pages where the peak date is past. SleekRank reads the filter on every cache cycle, so dropping a row removes the page and any internal links the theme generated to it.

Yes. SleekRank exposes a related entries helper that filters the same dataset by a category or tag field. You can show other cities for the same shower, or other showers active in the same month, from the same row data without manual cross-linking.

SleekRank generates real pages in the WordPress page hierarchy, so SEO plugins read them like any other post. Title tags, meta descriptions, canonicals, and sitemaps are populated from the row, and Yoast or Rank Math sees them as native content.