How to Build an SEO Tree: The Definitive Guide to Mapping Your Brand’s Content Architecture

The SEO Tree visualization above makes an abstract concept tangible. Your brand is a living organism. The trunk is your core identity. The branches are your major frameworks and services. The leaves are the proof — case studies, client stories, and meta-articles that demonstrate you actually do what you say you do. And beneath the ground, invisible but essential, are the roots: citations, entity verification, structured data, and every external signal that tells Google and AI systems this tree is real and rooted in the earth.

Most people think of their website as a collection of pages. The SEO Tree reframes it as a hierarchy where every page has one job: strengthen the pages around it.

But here is what the SEO Tree framework article does not address, and what this guide will fix: How do you actually build this map? What inputs do you need? Where do you get them? And what happens when the existing website was built by someone who was winging it — creating whatever felt good without any structural logic?

This is the step-by-step process for building the SEO Tree mapping from scratch, and then using it to drive the Content Factory process going forward.

Phase 1: Gathering Public Inputs — What AI and Anyone Can Find

Before you ever talk to the business owner, you can build roughly 60 to 70 percent of the SEO Tree from publicly available information. Here is what to collect and where to find it.

Brand Entity Signals (Trunk Data)

Start by searching the business name and the owner’s name. You are looking for what Google already associates with this entity. Pull the Google Knowledge Panel if one exists. Check Wikidata for an entity record. Search Google News, YouTube, LinkedIn, and industry publications. The goal is to understand what the world already thinks the trunk of this tree looks like — because that is the starting point, whether it is accurate or not.

For BlitzMetrics, the trunk entity includes: Dennis Yu, digital marketing, local service businesses, Facebook advertising, Dollar a Day strategy, and the Content Factory methodology. Those associations exist across hundreds of external sources. For a local plumbing company, the trunk might be the company name, the owner, the city, the license number, and the core service category.

Website Crawl (Current Branch and Leaf Inventory)

Crawl the entire website using Screaming Frog, Sitebulb, or even a simple sitemap review. Map every URL and categorize each page: is it trying to be a branch (a comprehensive topic page)? A leaf (a specific example, case study, or blog post)? Or is it an orphan floating in space with no clear purpose?

Build a spreadsheet. Column A: URL. Column B: Intended role (trunk, branch, leaf, unknown). Column C: What branch does this page link to? Column D: Does it actually link there? This audit reveals the damage immediately. You will find blog posts covering three topics at once linking to none of the hub pages. You will find service pages with zero supporting content pointing to them. You will find duplicate pages cannibalizing each other.

Social Media Entity Scan

Check every social platform: Facebook business page, LinkedIn company page, YouTube channel, Instagram, TikTok, X/Twitter. Are the profiles consistent with the trunk identity? Do they reference the same core topics? Are the bios aligned or do they tell different stories? For a personal brand, this also includes podcast appearances, speaking engagements listed on event sites, and any bio pages on third-party platforms.

Review and Reputation Signals

Google Business Profile reviews, Yelp, BBB, industry-specific review platforms — these are leaf-level proof signals. Every five-star review from a customer describing a specific service is a leaf that could (and should) be connected back to the branch for that service. Collect them. Categorize them by which branch they naturally support.

Citation and Structured Data Check (Root Data)

Check NAP (Name, Address, Phone) consistency across citation sources using Moz Local, BrightLocal, or manual searches. Check whether the site has Schema markup implemented. Check whether a Wikidata entry exists. Check whether there is consistency between what the Google Knowledge Panel says, what the homepage says, and what the About page says. These are the roots. If they are tangled, broken, or inconsistent, the tree cannot absorb nutrients no matter how good the branches and leaves are.

Phase 2: Owner-Guided Inputs — What Only Humans Can Provide

This is where most SEO mapping falls apart. The public data gives you what currently exists, but the business owner needs to tell you what should exist. The current website might have been built by a previous agency, a freelancer, or an internal team member who created pages based on what felt right rather than what was strategically correct.

The Trunk Validation Conversation

Ask the business owner: “If someone Googles your name or your company name and reads only the first three sentences that appear, what should those sentences say?” If the answer does not match what Google currently shows, the trunk needs to be rebuilt. The existing website might position the company as a general contractor when the owner wants to be known specifically as an emergency plumber in Phoenix. That misalignment means every branch and leaf built on top of the wrong trunk is structurally unsound.

The Branch Definition Session

Sit with the owner and list every major service or topic they want to be the authority on. Most businesses have between three and ten branches. A local service business might have: drain cleaning, water heater installation, emergency plumbing, sewer line repair, and commercial plumbing. A marketing agency might have: Dollar a Day, Content Factory, Digital Plumbing, MAA, Nine Triangles, and Social Amplification Engine.

The critical question for each branch: “Do you have one comprehensive page on your website that is THE definitive resource for this topic?” If not, that branch does not exist yet — no matter how many blog posts reference the topic.

The “What’s Wrong” Audit

This is where the owner tells you what the previous person got wrong. Maybe the old agency created fifteen blog posts about topics the business does not even offer. Maybe there are service pages for cities they no longer serve. Maybe the About page describes a mission statement from five years ago. This is content vandalism — not malicious, but structurally damaging. It needs to be identified so you know what to prune, redirect, or reorganize.

The Proof Inventory

Ask: “What are your best results? What clients can we reference? What projects have documentation — photos, videos, testimonials, before-and-afters?” These are the leaves the tree needs. Many business owners have incredible proof sitting in their phone’s camera roll, in email threads, in text messages from happy clients — none of it published, none of it connected to the tree. The Content Factory process exists to turn this raw material into leaves and attach them to their branches.

Phase 3: Where Citations Fit — The Roots That Make the Tree Real

The SEO Tree framework article explains trunk, branches, and leaves — but does not explicitly address citations. They belong in this picture as the roots. Here is why the root metaphor is precise.

A tree’s roots do two things: they anchor the tree in the ground so it does not topple, and they absorb water and nutrients from the soil so the tree can grow. Citations do exactly the same thing for an SEO entity.

Anchoring (Entity Verification)

When your NAP is consistent across fifty citation sources, and your Wikidata entry links to your official website, and your Google Knowledge Panel shows the same information as your LinkedIn, your homepage, and your BBB listing — that is anchoring. You are telling every system that evaluates your entity: this is real, this is verified, this is not fabricated. For a local service business, this anchoring is what makes the phone ring. Google’s local pack algorithm weighs citation consistency heavily. A plumber in Phoenix with clean, consistent citations across forty directories will outrank a plumber with better content but messy NAP data.

Nutrient Absorption (Authority Transfer)

External links from authoritative sites flow authority into your tree the same way roots absorb water from soil. A mention in a local news article, a link from an industry association, a feature in a podcast directory — these are nutrients entering through the roots and flowing up through the trunk into the branches.

More Roots = More Trust, More Leaves = More Proof

The E-E-A-T mapping on the SEO Tree visualization shows this directly. Trustworthiness maps to roots. The more citation sources that verify your entity, the more structured data that confirms your identity, the more external signals that corroborate your trunk story — the more trust the tree has. Trust is the foundation that everything else sits on.

Similarly, Experience maps to leaves. Every case study, every client testimonial page, every before-and-after project documentation is a leaf that proves you actually do what your branches claim you know how to do. A plumbing company with a beautiful definitive article about water heater installation (branch) but zero case studies showing actual installations (leaves) has expertise without experience. Google and AI systems can see the difference.

Phase 4: Using the Map to Drive the Content Factory

Once the SEO Tree is mapped, it becomes the operating system for all content production. The Content Factory stops being a random content machine and starts being a tree-growing machine.

Every piece of content gets assigned before it is created. The first question is always: which branch does this belong to? The second question is: does the definitive article for that branch exist yet? If not, build the branch before you grow leaves on it.

The enhance-before-create rule applies. When the Content Factory produces a new video testimonial from a client, the first move is to check whether an existing leaf page already covers that client or that service. If it does, enhance that page — add the video, add the transcript, add the new results. Only create a new page if the content is genuinely distinct enough to be its own leaf.

Internal links follow the tree. Every leaf links back to its branch. Every branch links to the trunk where appropriate. Cross-branch links happen only when there is a genuine topical connection — the Dollar a Day article links to the Content Factory article because they work together, not because someone thought it would be nice to add a link.

The MAA framework measures tree health. At the trunk level: is brand search volume growing? Is the Knowledge Panel complete? Do AI systems like ChatGPT and Perplexity accurately describe the entity? At the branch level: is each definitive article ranking for its target keyword cluster? At the leaf level: are case studies driving traffic and linking back to their branches? When a branch is weak, the Content Factory prioritizes creating more leaves for it. When a leaf is orphaned, someone connects it.

How the SEO Tree Visualization Was Generated

The SEO Tree image at the top of this article was built as an SVG diagram using HTML and CSS. Here is exactly what went into it and what inputs were required.

The trunk was identified from the BlitzMetrics homepage and brand entity. The six branches were pulled directly from the existing article’s framework list: Dollar a Day, Content Factory, MAA, SEO Tree, Digital Plumbing, and Nine Triangles. The leaves were populated from case studies and examples mentioned across the site: roofing case study, plumber dollar-a-day results, HVAC campaigns, Murphy Door build, GSC dashboards, KPI tracking, Plumbing Pros mapping, and David Meerman Scott’s tree. The roots were derived from standard entity verification sources: Wikidata, Google Knowledge Panel, NAP citations, Schema markup, and social profiles.

What this reveals: even an AI system can build approximately 70 percent of the tree from public inputs alone. The remaining 30 percent — whether branches are correct, whether the trunk identity needs to shift, whether there are hidden proof assets the business owner has not published — requires human guidance. That is why Phase 2 of this process exists.

The content vandalism callout (the red disconnected box on the left of the visualization) shows what happens when pages exist outside the tree. They have no links to any branch, they contribute zero authority, and they actively confuse Google about what the site is about.

Next Steps

This mapping process is repeatable. The next phase is to generate SEO Trees for Dennis Yu’s personal brand and for each client using the same two-phase approach: gather everything public, then validate and correct with the owner. Each tree becomes the permanent blueprint for what the Content Factory produces and how it is organized.

The tree is alive. It grows as you publish more leaves. It strengthens as you add more roots. And it only works if every page earns its place — linked up, down, and across — so authority flows naturally from proof to expertise to brand.

Read the companion article: The SEO Tree: How to Organize All Your Content So Every Page Strengthens Every Other Page — which explains the full trunk, branches, and leaves framework in detail.

Download the Skill File

This article has a companion Claude skill file that automates the process described above. Download it below, rename from .zip to .skill, and install it in Claude to get step-by-step guidance.