Yes. RepeaterBook exposes a JSON export per state and per call-area. Configure that endpoint as a REST source, set a daily cache, and SleekRank refreshes the whole roster automatically. For wider international coverage, the IRLP, EchoLink, and Brandmeister rosters are also JSON-friendly. Most clubs combine RepeaterBook data with their own controlled-vocabulary edits (preferred call labels, accurate net schedules, custom coverage notes) in a sheet layered on top.

Store rule citations (97.301, 97.305) as a column on each frequency row, then use a tag mapping to render the citation inline. Some sites also keep a separate page group for rule text itself, linking from frequency pages into the rule reference. That keeps citations consistent and lets rule edits propagate without touching every frequency page.

Yes, but two page groups is usually cleaner. /frequencies/{slug}/ for bandplan entries (simplex, calling frequencies, segment limits) and /repeaters/{slug}/ for operating repeaters. They can share most of the base template but differ on offset, tone, and operator fields. Splitting them also lets each group answer different intents.

FCC Part 97 changes propagate slowly, but ARRL band plan updates and regional coordination changes happen yearly. Keeping rules in the row data means an editor changes one cell and the page rerenders on the next cache refresh. Some clubs maintain a date-effective column so historical band plans stay viewable.

Yes. Add columns for DMR-specific fields (color code, time slot, talkgroup ID) and selectively render them when the mode column indicates DMR. A meta mapping can also distinguish 'DMR repeater' pages with their own schema metadata, useful for the Brandmeister and TGIF directories.

Add a status column (active, retired, off-air) and use a meta mapping to set robots=noindex when the value is retired. Retired-but-historical pages still earn back-links worth preserving, so most clubs noindex rather than delete. A pinned 'off-air since' notice keeps the URL useful for visitors arriving from old documentation.

Either store the mode list as an array (FM, D-STAR, DMR) and render via list mapping, or split the same physical site into separate rows per mode. The array approach keeps one page per site; the split approach gives each mode its own SEO surface for queries like 'D-STAR repeater Denver'. Pick based on traffic intent.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page. New frequencies or repeaters added to the roster appear on the next cache refresh. For high-stakes deployments (large club rosters), pair the refresh with a wp rewrite flush so URL coverage propagates within minutes.