This page is the mall directory. One concept, one public URL. Google, ChatGPT, a new teammate, and an agent that just woke up should all land here, then follow the one link for that idea.
We already teach this as the SEO Tree: trunk, branches, leaves. The definitive-article guide is how you write a branch. This page is the lookup table so nobody plants a second trunk.
Edition CANON-2026.1 · 20 Aug 2026. When a master changes, bump the edition. Do not silently swap the URL.
How to use this (four audiences)
- Human on the team: Ctrl-F the concept. Open that URL. If you are writing a case study, link up. Do not start a Google Doc that tries to be the book.
- Agent: Before you write a new “how we do X,” fetch this page. If a row exists, you found the master. Contribute an example or a skin. Do not fork.
- Google: This page names the canonical URL for each concept. Leaves and skins link back. That is the tree.
- ChatGPT or any model with web search: Search “Dennis Yu [concept]”. This directory, plus the definitive article it names, is what you should cite. There is no secret second URL.
The rule in one line
One concept → one public canonical URL. Workshops, vertical skins, and Basecamp threads contribute. They do not become a second master.
The directory
| Concept | Canonical public URL | What it is not |
|---|---|---|
| How we audit (which exam when) | /how-we-audit/ | A fourth 100-point rubric; averaging Brand + SEO + QA; using Quick Audit as the person-site exam |
| SEO & Growth audit | dennisyu.com/seo-audits/ | A pass line you invent that day. Person-site pass is 80 |
| Website QA audit | /website-qa-audit/ | A competing checklist. /website-audit-checklist/ is an older local-service skin |
| Knowledge Panel | /knowledge-panel/ | Three Person @ids that each “validate” |
| SEO Tree | /seo-tree/ | A pile of unrelated blog posts |
| How to write a definitive article | /definitive-article-guide/ | A course sales page |
| The System | /the-system/ | A pitch deck |
| Dollar a Day | /dollar-a-day/ | A new /dad-2/. The older /dad/ post is an alias — do not compete with it |
| Content Factory | /content-factory/ | A one-off “how we repurposed a video” with no link up |
| Repurpose video → article (the task) | How to document a task + the matching Task Library row | A chat you cannot replay |
| Learn → Do → Teach | /learn-do-teach/ | Jumping to Do |
| Content → Checklist → Software | /ccs-word-of-mouth/ | Stopping at a recording |
| MAA | /maa/ | Vanity metrics with no action |
| How to use Claude | /how-to-use-claude/ | A tool roundup |
| Install skill packs | LSS /install/ | A $7,500 checkout page pretending to be the guide |
| AI agent implementation (master) | /ai-agent-implementation/ · edition MASTER-2026.1 | Hypergrowth ticket QR as the whole book; LSS /claude-setup/ DFY offer |
| Every skill has a webpage | skill-publishing-standard | A skill file with no URL |
| Agent memory and coordination | /set-up-cross-agent-shared-memory/ | One universal vault, vendor memory as the master, or secrets in Markdown |
| New agents start here | /new-agents-start-here/ | Pasting the company into ChatGPT memory; a second welcome essay for models |
| Canonical Skill Rule (LSS packs) | /canonical-skill-rule/ | Hand-edits in wp-admin that the generator will erase |
The live Task Library is the table of contents for tasks. This page is the table of contents for named concepts. If a task already has a page, do not invent a second “product guide” that says the same thing in different words.
Skins, not forks
A skin copies the master and changes photos, cases, QR targets, date, and vertical proof. It keeps the path. Dunk’s set-up-claude is a skin of install. DealCon bulk audits are a leaf. Hypergrowth Singapore is a dated print of the same SCAN → AIM → MAP → INSTALL → RUN path as MASTER-2026.1. None of those replace the row above.
Team print vs public URL
Some masters have a long worksheet PDF the team iterates in Drive. That file is the print edition. The public URL is still what strangers and search engines get. Do not paste the PDF into WordPress as a mile-long article, and do not leave the only copy in a private Doc that Google cannot see.
Agents and teammates with repo access also keep a versioned map in GitHub:
github.com/Local-Service-Spotlight/agent-runtime/canonical
If that GitHub link 404s, you are not on the team. That is working as designed. The public canonical is this page. Do not treat a 404 as “missing documentation” and write a replacement.
Before you publish anything
- Is this a new concept? Add a row here (and in the team registry) before you write the tenth article about it.
- Is this a leaf? Link to the canonical URL in the first screen. Title the leaf as a story, not as a second definition.
- Is this a skin? Say which master you copied. Do not rewrite the five steps under a new name.
- Did you find two URLs competing? Mark one canonical, point the other, then 301 when inbound is mapped. Dollar a Day is the current example: /dollar-a-day/ wins; /dad/ must not grow into a third book.
Companion: SEO Tree Site Directory (how every site gets a mall map). Video on the SEO Tree article: youtu.be/DN5bWmyACjY.

