# TailMux search-intent and query ownership map

**Status:** pre-implementation content map
**Principle:** one canonical page owns one primary user intent. Supporting pages
link to it instead of publishing a near-duplicate keyword variant.

## Intent clusters

| Cluster | Canonical owner | Supporting pages | Boundary |
|---|---|---|---|
| Product entity | / | /download, /pricing, /docs/getting-started | Home explains the category; it does not replace setup guidance. |
| Broad simultaneous-access solution | new /guides/connect-to-multiple-tailscale-tailnets | macOS, Linux, fast-switching, VM, and daemon guides | The new guide answers the cross-platform question and links to specialized decisions. |
| macOS setup | /guides/multiple-tailscale-tailnets-macos | /docs/installation, /docs/use-cases/browser-routing | Owns macOS installation, menu bar, PAC, and macOS workflow. |
| Linux setup | /guides/multiple-tailnets-linux | /docs/installation, /docs/commands | Owns Linux alternatives and the CLI-only path. |
| Two identities on one machine | /guides/two-tailscale-accounts-one-machine | /docs/use-cases/work-and-personal | Owns the account/state explanation; use case owns exact work-and-home setup. |
| Fast user switching decision | /guides/tailmux-vs-fast-user-switching | broad guide, FAQ | Comparison only; it must not become another generic setup guide. |
| VM decision | /guides/tailmux-vs-orbstack-vm | broad guide, macOS guide | Comparison only; it must say when a VM is the correct choice. |
| Daemon/userspace decision | /guides/tailscale-multiple-tailnets-without-vm-or-daemons | Linux guide, limits reference | Owns architecture and trade-offs, not all installation detail. |
| Routing/security limits | new /docs/limitations | /docs/configuration, /docs/tunnels, /docs/ssh | Owns no-TUN, raw-IP, TCP, PAC, DNS, and no-fallback constraints. |
| Concrete workflows | existing /docs/use-cases/* | reference docs | Each page owns one client/workflow, not a generic product pitch. |

## Branded query map

| Query | Intent | Ideal landing page | Current landing / gap | Priority | Cannibalization control |
|---|---|---|---|---|---|
| TailMux | identify the product | / | homepage has brand but weak exact category in its H1 | P0 | Homepage is the only entity root. |
| TailMux app | find the desktop product | /download or /docs/app | /docs/app is accurate; download needs an explicit product entity link | P1 | Do not create a second “app” landing page. |
| tailmux.app | verify official domain | / | production title and canonical already help; add repository sameAs and organization identity | P0 | Homepage only. |
| TailMux Tailscale | disambiguate name and relation | / | non-affiliation exists in footer and LLM files; add explicit disambiguation in FAQ/LLM/product data | P0 | Keep the explanation short; avoid a defensive homepage block. |
| TailMux multiple tailnets | understand capability | /guides/connect-to-multiple-tailscale-tailnets | no cross-platform direct page today | P0 | New broad guide owns the query; homepage links to it. |
| TailMux macOS | platform fit | /guides/multiple-tailscale-tailnets-macos | existing strong route | P1 | macOS guide remains platform-specific. |
| TailMux Linux | platform fit | /guides/multiple-tailnets-linux | existing strong route | P1 | Linux guide remains platform-specific. |
| TailMux documentation | reference setup | /docs/getting-started | current docs redirect is correct; docs need article schema and alternate discovery | P1 | Avoid an indexable /docs duplicate; retain redirect. |

## Non-branded query map

| Query | Intent | Ideal landing page | Current landing / missing work | Priority | Cannibalization risk and control |
|---|---|---|---|---|---|
| connect to multiple Tailscale tailnets simultaneously | broad how-to and architectural decision | new /guides/connect-to-multiple-tailscale-tailnets | macOS guide is close but platform-constrained | P0 | New page must be cross-platform and link out; do not repeat macOS steps in full. |
| use two Tailscale accounts at once | account/state question | /guides/two-tailscale-accounts-one-machine | existing page | P0 | Keep the work-and-personal use-case page task-oriented. |
| multiple Tailscale networks macOS | macOS implementation | /guides/multiple-tailscale-tailnets-macos | existing page | P0 | Page owns macOS, menu bar, PAC and supported paths. |
| multiple tailnets macOS | macOS product discovery | /guides/multiple-tailscale-tailnets-macos | existing page | P0 | Use homepage as a supporting entity link only. |
| multiple tailnets Linux | Linux implementation | /guides/multiple-tailnets-linux | existing page | P0 | Keep the broad guide conceptual; Linux guide owns commands/trade-offs. |
| Tailscale home and work at the same time | concrete workflow | /docs/use-cases/work-and-personal | existing precise use case | P0 | Do not duplicate into the account guide; reciprocal links are enough. |
| alternative to Tailscale fast user switching | compare approaches | /guides/tailmux-vs-fast-user-switching | existing comparison | P0 | Avoid repeating “fast switching” in every guide title. |
| access multiple tailnets without switching | broad solution | new /guides/connect-to-multiple-tailscale-tailnets | no broad owner today | P0 | New guide uses this as secondary phrasing, not a separate page. |
| multiple Tailscale profiles simultaneously | conceptual/product question | new broad guide | profile terminology exists but has no direct cross-platform answer-first page | P1 | Explain that TailMux profiles are not native OS VPN profiles. |
| multi-tailnet client | category discovery | / | homepage needs literal category wording in its title/H1/answer block | P1 | Homepage owns category/entity; do not make a thin category page. |
| access overlapping Tailscale networks | overlapping address/DNS concern | new broad guide + /docs/limitations | existing docs explain suffix conflict, not the user-facing raw-IP limitation | P1 | Explain FQDN selection and do not claim automatic raw-IP disambiguation. |
| two Tailscale VPN connections at once | architecture/comparison | new broad guide | current pages can answer but are fragmented | P1 | Use precise “app-layer access”, not “two native VPN interfaces”. |
| run multiple Tailscale connections simultaneously | generic solution | new broad guide | current macOS/Linus pages split the intent | P1 | Broad guide links to platforms; no duplicate platform steps. |
| multiple independent Tailscale organizations from one computer | independent tailnets/control planes | new broad guide + Headscale guide | Headscale page covers mixed control plane; broad guide needs a factual caveat | P1 | Do not imply TailMux is an admin/organization-management product. |

## Required page changes by priority

### P0

1. Make the homepage answer the category question literally in its H1 and first
   explanatory paragraph: TailMux provides simultaneous, app-layer access to
   multiple independent Tailscale tailnets on macOS and Linux.
2. Add the cross-platform guide at
   /guides/connect-to-multiple-tailscale-tailnets. It must answer the core
   question before introducing TailMux, explain official-client/session
   switching carefully, compare the realistic alternatives fairly, and state
   the routing limitations.
3. Add a concise security-and-limitations reference route and link it from the
   homepage, new broad guide, existing platform guides, and LLM files.
4. Ensure product entity, LLM files, schemas, and footer use the same
   disambiguation: TailMux at tailmux.app is unrelated to tmux terminal
   projects with a similar name.

### P1

1. Make guide related links intentional: current first-two registry selection
   is not an intent graph.
2. Add visible Markdown alternate links and machine-readable relationship
   headers to strengthen citation/ingestion without search duplication.
3. Add TechArticle schema to documentation pages and improve product
   structured-data consistency.
4. Add a direct internal link from homepage to the new broad guide,
   /docs/limitations, /docs/getting-started, /download, and relevant security
   facts.

### Explicitly not creating

- Separate pages for every wording variation of “two accounts”, “two
  connections”, “multiple profiles”, and “without switching”.
- A generic “multi-tailnet client” page with no distinct user job.
- A comparison that claims TailMux is superior to shared nodes, VMs,
  subnet routers, or manual proxy setups in every environment.
- A page that presents TailMux as a native multi-interface/system-wide VPN.
