Search-first coverage updated for March 2026

Cluster hub

The platform hub should gather every high-intent support and storefront question in one place

This cluster is where root-level utility pages and nested platform-status routes meet. It should make platform intent easy to navigate without collapsing everything into one vague FAQ page.

Cluster

Platform

Public routes

7

Root-level utility

2

Review class

Critical status

Why the platform hub matters

Platform intent is rarely just one query. A user who lands on Mac support may also care about Steam Deck, Switch, mobile, or whether the game is likely to reach another storefront later. That is why the platform cluster needs a real hub instead of a loose pile of status pages.

The job of this hub is simple:

  • gather the highest-intent platform questions in one place
  • make the current level of confirmation obvious
  • route users into the most relevant child page without duplicating every answer

What this hub should do better than a generic FAQ page

A generic FAQ page would blur everything together. A proper platform hub should separate:

That structure helps both searchers and future content production.

Why the hub should stay conservative

Platform pages get stale fast when they drift into implication instead of confirmation. This hub should stay useful even when the answer on several child pages is still Not confirmed. A clean negative or unknown answer is still better than wishful filler.

The cluster becomes more valuable over time because new platform announcements can slot into existing routes without changing the overall structure.

Priority child pages

Start with the clearest platform and utility routes

The hub should surface the most useful public routes first, then let the long-tail status pages absorb narrower platform intent.

Cluster shortcuts

The two most useful support checks after the hub

Users usually move from platform discovery into launch status or buying checks.

FAQ

Cluster questions worth answering fast

A hub should answer the broad questions while routing users into the right child page.

Why does the platform hub exist if some platform pages also live at root level?

Because searchers still need one cluster-level page that organizes Mac, Switch, mobile, Steam Deck, and Game Pass intent into a clear structure.

Should the hub hide pages that are still unconfirmed?

No. Unconfirmed pages can still be useful if they are clearly labeled and supported by the right source context.

What makes this hub different from a generic FAQ page?

A real hub groups related platform routes, separates utility pages from status pages, and routes users into the exact child page that matches their next question.