It generates one WordPress page per row in your normals source. Each page is a real URL with its own title, meta description, schema, and Twig template. The station name, elevation, monthly means, and prior-period deltas all come from that row, so the page is fully populated the moment the row exists in the dataset.

Yes. SleekRank reads CSV, JSON, REST endpoints, and custom post types. Most climate sites keep the NCEI bulk CSV in the theme at a path like src/pages/climate/normals.csv, point SleekRank at it, and let the route generate pages. Switching to a different source later does not change the URLs.

The slug column on each row is the authoritative URL fragment. Most sites combine the ICAO or station identifier with the city, like kpdx-portland-or. SleekRank does not invent slugs, so airports, cooperative stations, and CRN stations in the same city each keep distinct stable URLs.

Replace the source CSV with the new release and clear the SleekRank item cache. Every station page rebuilds with the new monthly means and an updated delta against the prior period. Retired stations drop from the source and the corresponding pages and internal links disappear with them.

Each page reads its own row, so title, meta description, Open Graph image, and Place schema are filled in with the station name, code, and location. SleekPixel can render a per-station OG image with the station id and city burned in, so social previews for KPDX and KBOS look distinct.

Add a status field to each row and exclude pages where the station is inactive or below the data completeness threshold NCEI publishes. SleekRank reads the filter on every cache cycle, so disabled rows produce no page and the related-stations grid skips over them.

Yes. SleekRank exposes a related entries helper that filters the same dataset by a category or state field. Each page can show other stations in the same state, the same climate division, or the same elevation band, sourced from row data rather than handwritten cross-links.

SleekRank generates real pages in the WordPress page hierarchy, so SEO plugins read them like any other post. Title tags, meta descriptions, canonicals, sitemaps, and JSON-LD all populate from the underlying row, and Yoast or Rank Math see the URLs as native theme content.