seo: root `/` serves the Coming Soon page — the real homepage is stranded at /home

Problem

The domain root — the URL with all the link equity — serves a Coming Soon placeholder, while the real homepage lives at /home with no internal links pointing to it.

Findings

• resources/views/index.stx:1-7 extends layouts/soon; /home is an orphan.
• app/Actions/SitemapAction.ts:33 lists / at priority 1.0 — advertising the placeholder to crawlers.
• No launch flag, redirect, or noindex exists to manage the transition.

Acceptance criteria

• At launch, / serves the real homepage; /home 301s to /
• Until launch, the coming-soon page is noindexed and excluded from both sitemaps

Split out from the SEO bundle of the 2026-06-10 production-readiness audit.

Still open, and it now costs more than SEO: / is the native app's launch screen.

The iOS app (#79) loads the site's root, so the first thing anyone sees after tapping the icon is the Coming Soon placeholder — confirmed on an iPhone 17 Pro simulator running the bundled build. dist-offline/index.html contains the "Coming soon" pill; the real homepage is still stranded at /home.

For the web this is a crawler and first-impression problem. For the app it is worse: there is no address bar to type /home into, so the placeholder is the only thing an app user can reach at the root. Every mobile session starts there.

Worth fixing before any TestFlight or App Store build, independently of the SEO argument in the original description.

Still true, and I've left it alone deliberately — this looks like a launch switch rather than a bug.

resources/views/index.stx is four lines: @extends('layouts/soon') wrapping Bench/BenchComingSoon. The real homepage at /home is complete and carries its own title, description, OG set and JSON-LD. Swapping them is a one-line change to that view.

So this is a "go live" decision, not an engineering one, and it's the only reason / and /coming-soon share a title (the last duplicate pair on the site — see #59).

Worth noting what else it gates: the sitemap lists / at priority 1.0, so right now the highest-priority URL advertised to crawlers is the placeholder. If launch is not imminent, that entry is arguably worth pointing at /home in the meantime; if it is, this issue closes with the view swap.