Use a deal-structure field on each row that distinguishes a merger of equals from an asset purchase or stock-for-stock combination. The base page renders the structure verbatim in the fact table, so the same /mergers/{slug}/ archetype handles both with full transparency to readers.

Yes. Add an unwind-date and unwind-reason field to each row. The base page renders the unwind alongside the original close date, so the page tells the full arc from combination to split. Readers searching for what happened to AOL Time Warner reach a complete narrative on one URL.

Each merger page is keyed by the original deal slug. The slug and URL stay stable even after a rebrand. You add a rebranded-to field to the row, and the base page surfaces it in the fact table so readers see both the original and current entity name.

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

Each row stores the headline deal value and a deal-mix field with the cash, stock, and earnout breakdown. The base page renders the breakdown in the fact table, so the headline value and the mix appear together and search engines pick up the structured detail.

Yes. Each /mergers/{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 merger ledger.

The sleekRankRelatedEntries helper filters by category, so when you tag mergers with a sector field like media or consumer-packaged-goods, 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 merger hits the source on a cold load, and most production sites serve merger pages from the WordPress page cache layer on warm hits.