Carry term_start and term_end columns per juror. The page group filter compares the current date against both, so jurors whose term has not started yet are hidden, jurors mid-term render in the live hub, and jurors past term_end automatically move to the archive without an editor touching them.

A recusals_json column on each row carries entries like {decision_id, entity, reason, declared_at}. List mapping renders the recusals block on the public profile and the same data feeds the internal scoring tool so a recused juror cannot be assigned to that decision.

Yes. Set status to past-term rather than deleting the row, and the URL stays resolvable. A status badge on the page indicates the term has ended. For panels reformed annually, run a per-year page group with urlPattern like /jury/2026/{slug}/ to preserve each cycle independently.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new jurors start getting crawled after the next rewrite flush, and past-term jurors either stay listed (recommended for archive) or drop based on your filter.

Yes. Add the JSON-LD block to the base template and inject row-specific values like name, affiliation, alumniOf, and hasOccupation through selector or meta mappings. Each /jury/{slug}/ renders its own valid Person schema, which improves the chances of a knowledge panel for established jurors.

Set status to stepped_down and update term_end to the actual departure date. The page group filter moves the juror to archived state on the next cache cycle. Run wp db query "DELETE FROM wp_319_sleek_rank_items" plus wp rewrite flush --hard to propagate immediately.

Not if you keep one slug per juror across cycles, since the page accumulates appearance history rather than duplicating content. If you run per-year page groups, ensure each cycle's juror page carries unique cycle-specific text in the statement column to differentiate them, and use canonical tags pointing to the most recent term.

Yes. Add a decisions_json column listing the decisions the juror participated in, with public-safe metadata like cycle, category, and outcome. List mapping renders the block on the public profile. Keep individual vote records private; the public surface shows only that the juror served on the panel for that decision.