Emit one row per transition, not one row per company. A company that changed names in 2008 and again in 2021 gets two distinct rows with two slugs and two routed pages. The base page can link a company's rebrands together using a brand-lineage field that drives a cross-link strip.

Yes. Add a reversed-on field to each row when a rebrand is undone. The base page renders the reversal alongside the original change, so the page tells the full arc from old name to new name and back. Readers searching for what happened to the new name reach a complete narrative on one URL.

Each rebrand page is keyed by the transition slug. The slug stays stable, so the URL and canonical do not change. You add a colloquial-name field to the row, and the base page surfaces it under the official new name as context for readers looking for the older terminology.

Yes. Long-form fields like leadText and press-release-url live on the row, so each rebrand carries its own narrative and primary source link. The base page renders those fields in fixed slots, and you never touch the template HTML to add a new rationale section.

Add old-ticker and new-ticker fields to each row. The base page renders both in the rebrand fact table, so the ticker change appears next to the name change for the same effective date. Investors searching for the new ticker reach the same page as readers searching for the new brand.

Yes. Each /rebrands/{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 in the rebrand ledger.

The sleekRankRelatedEntries helper filters by category, so when you tag rebrands with a sector field like tech or food-and-beverage, each page links to a stable cluster of peer rebrands. 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 rebrand hits the source on a cold load, and most production sites serve rebrand pages from the WordPress page cache layer on warm hits.