Emit one row per discrete SKU, not one row per family. The Wii and Wii U get two rows with two distinct slugs and two routed pages. The base page can link sibling SKUs together using a product-family field that drives the related entries cluster.

Yes. Add fields for general-availability EOL date, security update end date, and extended-support end date. The base page renders all three in the fact table, so customers understand exactly which window applies to their specific use case for that SKU.

Each SKU has its own routed page. When a successor itself reaches end of life, you add a new row for that successor and leave the original legacy page intact. The successor field on the older page still points at the same URL, which stays valid in the archive.

Yes. Long-form fields like leadText and migration-link live on the row, so each legacy product carries its own migration narrative. The base page renders those fields in fixed slots, and you never have to touch the template HTML to add a new migration block.

Either emit one row per region with region in the slug, or add a region-EOL-dates field to a single row that the base page renders as a small per-region table. Both approaches are common, and the choice depends on whether each regional EOL deserves its own URL.

Yes. Each /discontinued/{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 successor-slug field on each row maps to a link in the base page. If the successor is also in the SleekRank cluster, the link resolves to its routed page. If the successor lives elsewhere on the site, you point at that page URL directly in the field value.

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