Emit one row per role tenure, not one row per person. A leader who was CFO and then CEO gets two rows with two distinct slugs and two routed pages. The base page can link a person's tenures together with a name field that drives a cross-link strip.

Yes. The end date field can be a real date for past tenures or the string present for sitting executives. The base page renders the value verbatim, so you keep full control over how present tenures versus past tenures appear in the table.

Each tenure is its own routed page keyed by the executive slug. The retiring CEO's URL stays stable, you flip the end date on that row, and you add a new row for the successor. The predecessor and successor fields keep the lineage cross-links accurate.

Yes. Long-form fields like leadText and whyMatters live on the row, so each tenure carries its own bio and citation list. The base page renders those fields in fixed slots, and you never have to touch the template HTML to add a new biography section.

Interim and acting roles get their own row with a short tenure window. The fact table surfaces the role as Acting CEO or Interim CFO, and the duration calculation in the template handles spans measured in weeks just as cleanly as spans measured in decades.

Yes. Each /leadership/{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 filters by category, so when you tag tenures with a role-lineage field like apple-ceo or microsoft-ceo, each page links to a stable cluster of peers. You wire the helper in once and every page in the group inherits the cross-links.

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