Emit one row in your data source per pair you want to publish. The slug field defines the URL segment, and the plugin builds one routed page per row at /yoy/{slug}/. Adding a row and clearing the SleekRank items table is enough to publish the next pair.

Yes. SleekRank supports JSON files, CSVs, REST endpoints, and WordPress custom post types as data sources in the page group config. The mappings block tells the plugin which field on each row replaces which element on the base page.

Each resolved row lives in the SleekRank items table with the cache duration you configured. Running a delete query on that table forces the plugin to re-resolve from source on the next request, so the page reflects the correction within one cache cycle.

Yes. Each /yoy/{slug}/ resolves to its own routed page with its own title, meta description, canonical, and Open Graph image suffix. Search engines treat each as a distinct URL because the response body and head tags differ per row.

The sleekRankRelatedEntries helper returns up to six rows from the same page group, deterministic per slug, so each page links to a stable cluster of siblings. You wire it into the template once and every page in the group gets a related strip.

The base page is a regular WordPress page, so any block or shortcode you can use there is available. Field mappings can target image tags or chart container IDs, so a chart URL or data file path from the source row plugs into the layout.

URL patterns are part of the page-group config. Change the urlPattern field in the JSON config, flush WordPress rewrites once, and every row in that group resolves at the new path. Old paths can be redirected with a standard redirect plugin.

Customers run page groups with thousands of routed pages on shared and managed hosting. The plugin caches resolved rows, only the requested page hits the source on a cold load, and most production sites serve generated pages from the WordPress page cache layer.