One Canonical Honor, Many Story Leaves

A slug is not canon. One person you actually work with gets one highest-power URL — but that URL has to earn the role by being the most helpful answer on the relationship. Every other article is a story leaf that names its limb and funnels into the branch. Phone video feeds Produce → Process → Post → Promote. That is how both names compound in Google and in AI answers, instead of competing with yourselves.

This is the method I am sharing at Affiliate World Americas in Cancun (speaker dinner 6 September 2026, show 7–8 September). The worked example is my relationship with Liana Ling. Copy the pattern for anyone you honor in public. Parent frameworks: SEO Tree (leaf → limb → branch → trunk → root) and Second Ring (consent-first introductions; if someone is already direct, never manufacture a hop).

How to write the hub: definitive article guide. How the factory runs: Content Factory. How photos become people pages: how we build people pages. Travis Reynolds is the published SEO Tree example — the name article ranks on the name; the specific articles rank on the specific things. Liana is the same tree, practiced on a living relationship.

The mistake this page kills

We already had live Liana articles. A backpack reel at DigiMarCon. An October 2025 “Lead-Gen Queen” bio. A Coach Yu story about serendipity. A people-directory card. A partner audit form. And a Google Photos stub at /lianaling/ that said we would come back and narrate the frames.

Naming the stub “canonical” because the slug matched Jack Wendt and Roanin Podkin was the error. A barren page cannot be what Google or ChatGPT cites as the best, most helpful answer. If the backpack leaf is thicker than the hub, you have not earned canon. Do not 301 the rich leaves into the stub. Fill the branch until it absorbs the relationship, then hang the leaves from named limbs.

If you ask “is this the canonical honor?” and the URL is about one hallway, the answer is no. If you ask AI “what is Dennis Yu’s relationship with Liana Ling?” and it has to stitch five competing posts — or it lands on an empty Photos page — you split your own authority. That is content vandalism. The fix is not fewer stories. The fix is one filled hub those stories point at.

Place it on the SEO Tree (Post stage)

This is the skill place-content-on-seo-tree-with-proper-links practiced on a person honor, not a product category.

Enhance before you create. New tape → new leaf. Same relationship → same hub. If no logical parent exists, halt — either the tree is missing a limb, or the piece does not belong on this site. Record the placement in an inventory so the next audit can find orphans by diff. Ours: outputs/liana-ling-canonical-2026-09-02/seo-tree.json.

Do not bolt a person honor onto the Skill / Pack / Agent / Job / Proof ring. That ladder is for The System. This tree is for one relationship.

Three surfaces, three jobs — plus the tree

A directory card is a trunk node. A partner form (LSS /liana/) is a door on the partner limb, not an honor.

Practice Second Ring on the honor graph

The published architecture is How We Built Second Ring (/second-ring/ 301s there; do not mint a competing BlitzMetrics URL that 404s). Open-core: free intelligence, paid coordination. Code can be copied; relationships cannot.

• First ring is direct, consented, reciprocal. Dennis ↔ Liana is first ring. If a person is already direct, never manufacture a second-degree intro path. The first Second Ring prototype put Dan Antonelli behind a fake hop. Do not repeat that on a friend you already work with.
• Second ring is a named bridge. Richard Rossi via her laptop at DigiMarCon is a documented second-ring introduction. Tell it on the leaf. Do not publish the private thread.
• Public context is not a warm intro. Sharing a conference hall with someone at Affiliate World is not an edge. Her Dollar a Day article on powerupstrategy.com is the corroboration we want — she published us.
• Spotlight layer can be public (this honor page, the leaf list, the together photo we host). Relationship layer stays private. Do not scrape her contacts. Do not PATCH her sites from our factory.

The funnel rule

1. Search your own sites before you write. If a hub already owns the person, enhance it — and if that hub is thinner than the richest leaf, you are not done enhancing.
2. New tape → new leaf. Same relationship → same hub.
3. Put the video at the top of the leaf. Captions on (YouTube captions on by default).
4. First screen of the leaf names the limb and links the branch. Hub lists the leaf under that limb.
5. Her brand gets her cut. Your brand gets yours. Both link the hub and her entity home.
6. Do not 301 a good story into the hub. Stories should rank for the story. The hub should rank for the person + you.

Four factory stages, using the phone pile

The Content Factory line is Produce → Process → Post → Promote. Not “Plan, Produce, Promote, Profit.” Not a sixth name for the same four boxes.

1. Produce — gather what is already on the phone

You do not start from a blank page. You start from Camera Roll, Google Photos, iCloud, the People album, and the conference backpack.

• Four backups off the phone so a wipe does not erase the library.
• A named People cluster (for us: Liana Ling).
• A daily intake that lists new Videos since the last watermark. Stay quiet if nothing new. If Photos is signed out, tell the operator once — do not pause the routine on the first miss.
• A public-safe ledger: title, YouTube ID when verified, stage, next click. No file paths, no album secrets. Ours: the JSON beside this article in the team runtime, summarized on the honor hub.

Unverified IDs stay FIND. A dead YouTube ID (osI5B_IkrLE on an older related-resources list) is marked dead. Do not re-embed it.

2. Process — one tape, one story, quotes from the transcript

Descript for the cut. Transcript for the quotes. Player captions are for the viewer; they are not factory quote evidence. If the hub already exists, the Process output is a leaf plus a hub update, not a second master.

GCT still comes first: the goal of this tape (honor her, teach Dollar a Day, show the backpack), the content that earns it, the targeting (affiliates in Cancun, her students, local operators). Most people start with targeting. That is backwards.

3. Post — place it on the tree

YouTube, the leaf, the hub, her site when she wants the cut. Cross-link both directions. Classify the leaf. Name the limb. Add the upward links. Add the inbound link from the branch so the piece is not an orphan. A second page that tries to be the honor is a leak. Rank Math 301s that send a person-slug to the homepage are also leaks — dennisyu.com/liana-ling/ currently 301s home; it should 301 to the hub.

4. Promote — amplify what already worked

Dollar a Day on the clips that already earned organic signal. Thank You Machine when she publishes you. Roundup when the week has more than one winner. Do not boost the first draft of a leaf that has no proof of life. Do not boost a stub and call it the hub.

What we shipped for Liana in this run

• Kept the hub URL: dennisyu.com/lianaling/ — then filled it so it can earn the role the Photos stub could not.
• Drew the tree above the fold: root / trunk / branch / four limbs / leaves. Inventory in seo-tree.json.
• Practiced Second Ring on the public graph: first-ring Dennis ↔ Liana; Simon now direct (do not re-hop); Richard Rossi as a named second-ring intro; her Dollar a Day post as corroboration.
• Kept the backpack URL as a leaf. Kept the October 2025 bio as a leaf. Kept the people card as a card.
• Embedded the verified Coach Yu tape kQt_VObAsuY on the hub, captions on.
• Published this method so Cancun (and every week after) has a URL to share, not a slide that dies.

What you can copy this week

1. Pick one person you actually work with. Not a logo wall. One name.
2. List every URL you already published about them. Mark exactly one as the hub. If that hub is thinner than the richest leaf, you have not earned canon — write the hub first.
3. Name the limbs. Put each leaf on one limb. Put a first-screen funnel on every leaf that says so.
4. Draw the first ring and the second ring. If someone is already direct, do not invent a hop.
5. Inventory the phone: People album + Videos newer than last week. One ledger row per tape. No invented IDs.
6. Run Produce → Process → Post on the next tape before you fly home. Promote after it earns signal.

If you are in the Affiliate World hall: the backpack is already in the room. Liana already proved the instinct — capture the moment, post it, let the other person honor you back. The factory is how that moment becomes the page AI recommends next year. The tree is how the other pages do not fight it. Second Ring is how you stay honest about who you actually know.

QA checklist

• One hub URL. No second “who we are together” essay.
• The hub is thicker and more helpful than the richest leaf. If it is not, you have not earned canon.
• Hub shows a clickable SEO Tree (root / trunk / branch / limbs / leaves) and a Second Ring ledger.
• Every leaf links the hub in the first screen and names its limb.
• Hub links her entity home dofollow.
• YouTube embeds use youtube-nocookie, rel=0, cc_load_policy=1, cc_lang_pref=en.
• Dead video IDs are not re-embedded.
• Anonymous GET of the hub shows the marker LIANA-LING-CANONICAL-2026-09-02 (worked example) or your own dated marker — and is not still a Photos stub.
• Phone intake has a watermark and a quiet path when nothing is new.
• No private second-ring edges published. No manufactured hops for people who are already direct.

FAQ

Can the hub be a people-directory card?

No. The card is the trunk. The honor is the branch. Same person, two jobs. See Jack Wendt and Roanin Podkin.

Can I 301 old story URLs into the hub?

Only if the old URL was a duplicate honor, not a story. A backpack reel should keep its URL. A hyphenated slug that 301s to the homepage should 301 to the hub. Never 301 a rich leaf into a stub.

What if we have fifty clips and no time?

Ledger first. One verified YouTube ID on a filled hub beats ten guessed embeds. Process the Cancun hallway before you process the archive.

Worked example hub: Liana Ling — canonical honor. Factory parent: Content Factory. Tree: SEO Tree. Introductions: Second Ring.