Staff directories carry real operational weight: prospects email staff through them, partners pull contact details, and journalists track who runs what at the organisation. Hand-built staff pages mean the public directory drifts from the HR source the moment someone changes role, joins, or leaves, and the editor running updates is rarely in the loop on every personnel change.

SleekRank reads the staff directory from a Google Sheet, CSV, or JSON file pulled from the HRIS with one row per staff member. Columns carry slug, name, title, department, office, contact_email, contact_phone, headshot_url, bio_short, manager_slug, and a consent column for public visibility.

Each consented row drives /staff/{slug}/ on one shared template, with tag mappings handling name and title, selector mapping injecting headshot and contact block, list mapping rendering focus areas. Per-department hubs run as a second page group with urlPattern /staff/{department}/. The base page stays auto-noindexed; the consent filter ensures only opted-in staff appear publicly.

Staff directories are one of the highest-traffic operational surfaces on most company sites and one of the worst-maintained. Personnel changes happen weekly: hires, promotions, transfers, departures, parental leave returns, role changes, office moves. Hand-built staff pages mean the editor running updates is operating one or two changes behind HR, and the directory either lags or fills with stale entries that prospects and partners use anyway because the URLs still resolve.

SleekRank reframes the directory as a render of the HR source. A JSON proxy pulls from BambooHR, Rippling, HiBob, or whatever HRIS the organisation already runs, strips sensitive columns to keep compensation and home addresses out of the public feed, and exposes the consented public-safe rows to SleekRank. The page group filter renders rows where consent equals true, so non-consented staff never generate a URL and revocation is a one-cell flip.

Per-department hubs run as a second page group filtered by the same source. The directory becomes a live read of HR rather than a parallel database the marketing team has to maintain, and the structural separation between source and surface means every personnel change flows through normal HR workflow rather than a CMS ticket. Search engines pick up Person JSON-LD per row with worksFor pointing to the organisation, which compounds the discoverability of senior staff over time.