docs(docs): 📝 Update domain portfolio documentation with new strategy and funnel framework

Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
This commit is contained in:
autocommit 2026-05-18 22:47:44 -07:00
parent 3b8e4bf321
commit 75cc89a2c1

View file

@ -148,7 +148,7 @@ for deploy state.
Voice strategy: provocative SEO bait → soft-land in applied-wellness register on canonical.
See `docs/company/projects/adult-therapy-tour/decisions.md` §ADR-008.
#### Pending purchase — Futa Waifu Tour stack (decided 2026-05-17)
#### Pending purchase — Futa Waifu Tour stack (decided 2026-05-17, reshuffled 2026-05-18)
New sister tour to ATT under the Cocotte umbrella. **Futa Waifu Tour (FWT)** carries
the geek/anime/con audience natively (Bimbo-Geek register), so ATT can revert to 100%
@ -159,33 +159,64 @@ split rationale on that page.
Availability verified via whois + RDAP on 2026-05-17. Brand-name candidates that
included "Therapy" were rejected — clinical baggage kills the geek-audience fit.
**Buy now (top 5, ~$65/yr, all .com)** — covers brand canonical + three SEO axes
+ peak Bimbo-Geek register:
**Funnel framework (2026-05-18 reshuffle)** — original 5-domain stack was 100% BOFU
keyword bait, captured only searchers with "futa" already in their head. Reshuffled
to balance TOFU/MOFU/BOFU funnel coverage:
| Domain | TLD price | Role |
|------------------------------|-----------|-----------------------------------------------------------------|
| `futawaifutour.com` ⭐⭐ | ~$13/yr | **Brand canonical** — FWT acronym mirrors ATT |
| `realfuta.com` ⭐ | ~$13/yr | Real-disambiguator anchor (vs anime/CGI ~80% of futa keyword) |
| `futawaifu.com` ⭐ | ~$13/yr | Keyword anchor — futa + waifu compound |
| `fuckafuta.com` | ~$13/yr | Provocative direct — mirrors `fuckatapa.com` pattern |
| `myfutawaifu.com` | ~$13/yr | Possessive bait — peak Bimbo-Geek register, sub-coded |
- **TOFU** (top of funnel — awareness): `animecon*` genre-coded domains capture con
attendees searching nightlife/parties/hookups without the futa keyword
- **MOFU** (middle — consideration): scenario pages on canonical
(`/scenarios/<slug>/`) — no separate domains needed
- **BOFU** (bottom — commercial intent): `realfuta.com` / `futawaifu.com` / etc.
capture searchers already typing commercial-intent futa queries
**Queued for later (~$80/yr, incremental expansion once traction shows)**:
**Buy now (8 domains, ~$104/yr, all .com)** — canonical + 4 BOFU bait axes + 1 BOFU
genre + 2 TOFU genre anchors:
| Domain | TLD price | Role |
|------------------------------|-----------|-----------------------------------------------------------------|
| `realfutawaifu.com` | ~$13/yr | Real + waifu stack |
| `fuckafutawaifu.com` | ~$13/yr | Provocative + waifu |
| `futawaifucon.com` | ~$13/yr | Convention-coded bait |
| `realfutatour.com` | ~$13/yr | Defensive brand variant (typo/pivot insurance) |
| `futa.lgbt` | ~$28/yr | Niche TLD parallel to Quinn's existing `ftw.lgbt` |
| Domain | Tier | TLD price | Role |
|------------------------------|--------------------|-----------|-----------------------------------------------------------------|
| `futawaifutour.com` ⭐⭐ | canonical | ~$13/yr | **Brand canonical** — FWT acronym mirrors ATT |
| `realfuta.com` ⭐ | BOFU axis 1 | ~$13/yr | Real-disambiguator (vs anime/CGI ~80% of futa keyword) |
| `realfutanari.com` ⭐ | BOFU axis 1.5 | ~$13/yr | Hentai-canonical highest-volume keyword + real positioning |
| `futawaifu.com` ⭐ | BOFU axis 2 | ~$13/yr | Futa + waifu keyword compound |
| `fuckafuta.com` | BOFU axis 3 | ~$13/yr | Provocative direct — mirrors `fuckatapa.com` pattern |
| `animeconescort.com` | BOFU genre | ~$13/yr | Commercial intent at anime-con level (no "futa" required) |
| `animeconhookup.com` | TOFU/MOFU bridge | ~$13/yr | Casual searcher pre-trip research |
| `animeconafterparty.com` | TOFU genre | ~$13/yr | Nightlife searcher in-the-moment (Sat 11pm at the con) |
**Inherited from ATT-stack** (already owned, reassigned to FWT category bait):
- `futa.singles` — Joker, exp 2027-05-14
Genre-coded `animecon*` domains scale across all anime cons on Quinn's tour
(FanimeCon, Anime Expo, Daku Con) — content rotates per current-stop, domains
stay evergreen with zero TM exposure (rejected per-con `fanimecon*` domains for
this reason).
**Queued for later (~$54/yr, post-traction expansion)**:
| Domain | Tier | TLD price | Role |
|------------------------------|--------------------|-----------|-----------------------------------------------------------------|
| `myfutawaifu.com` | BOFU axis 2-poss. | ~$13/yr | Parasocial "my waifu" psychographic |
| `futawaifucon.com` | BOFU axis-niche | ~$13/yr | "Futa con" convention-coded long-tail |
| `fanconafterparty.com` | TOFU pop-culture | ~$13/yr | FAN EXPO + multi-genre cons (Stop 03+) — avoids Comic-Con TM |
| `futa.lgbt` | BOFU identity | ~$28/yr | Niche TLD parallel to Quinn's existing `ftw.lgbt` |
**Cut from previous stack (2026-05-18 reshuffle audit)** — documented to prevent
accidental re-addition:
- `realfutawaifu.com` — redundant (realfuta + futawaifu glued, no distinct query)
- `fuckafutawaifu.com` — redundant (fuckafuta + futawaifu glued)
- `realfutatour.com` — defensive-only typo coverage; no real search maps here
- `fanimeconafterparty.com` (briefly considered) — per-con TM-risky; replaced by
genre-level `animeconafterparty.com` which covers FanimeCon + all anime cons
across the tour without TM exposure
**Inherited from ATT-stack** (already owned, repositioned 2026-05-18):
- `futa.singles` — Joker, exp 2027-05-14. Repositioned from generic category bait
→ TOFU/MOFU "meet a futa" dating-coded landing (the `singles` TLD reads as
nightlife/dating vocabulary, natural fit for awareness-tier searchers).
Pre-staged deploy scaffolds under `deployments/@domains/{name}/` will be regenerated
against a new `codebase/@features/futa-waifu-tour/web/_shared/` feature dir (NOT
ATT's `_shared`) — geek register diverges from applied-wellness design system.
against `codebase/@features/futa-waifu-tour/seo/<name>/` (BOFU bait, static HTML)
and against the canonical Astro `site/dist/` (TOFU + MOFU subpaths under
`/guide/` and `/scenarios/`).
---