The Branches & The Orchard Ecosystem Framework™

What is up, everyone? Welcome back to The Canopy, the view from above where we talk generative engine optimization, small business, and what's changing in the world of AI search. I'm your host, Jen Shannon, and founder of Clemelopy. And if you are listening to this, I want to say thank you so much for sharing your time with me and being here, and just giving you a big shout out.

I feel like I'm finally coming into my own in terms of my voice here on the podcast. I've tried to keep it fairly neutral and that sort of thing, but I feel like in the last couple of episodes, I've really started to be more myself and develop that voice. So I'm hoping that you all are enjoying it.

This is episode five of our ten part series on the Orchard Ecosystem Framework, and we're officially halfway through. Can you believe it? So far, we've covered roots, soil, and trunk. Today, we're staying above ground and talking about what extends from your trunk. Did anybody guess branches? Because if you did, that would be correct.

And here's the simplest way I can explain branches. Branches are the supporting topics that help a page do its job more thoroughly. Your trunk gives the page its primary direction, while your branches are the related questions, ideas, concerns, explanations, and subtopics that give the page depth without pulling it away from the central purpose.

That distinction matters because a good page usually needs more than one paragraph about one idea. People have follow-up questions. They need context, and they have concerns and objections, and they may need practical details before something fully makes sense — kind of like this, kind of like the Orchard Ecosystem Framework and generative engine optimization. Branches allow you to answer those needs while still keeping the page focused.

By the end of this episode, you'll understand what branches mean inside the Orchard Ecosystem Framework, why supporting topical coverage matters for AI visibility and user experience, how to identify the right branches for a page, and how to tell when something should remain a branch versus when it deserves to become its own page.

Now before I get into it, let's quickly do a recap of the framework we've already talked about. We started underground with the roots, which represent the major topics your business wants to establish expertise around. If you haven't listened to that episode, go ahead and listen to episode nine where we talk about the roots. Then we talked about the soil in episode ten, which is the terminology and vocabulary surrounding those topics. In the last episode, which was episode eleven, we moved above ground to the trunk, which represents the primary purpose of an individual page.

And now we're moving outward from the trunk and into the branches. But they all grow from that central structure. They allow the tree to expand and create more surface area. They support leaves. They eventually hold fruit. You've seen trees before. Even though they move outward, you can still trace each healthy branch back to the same tree, and your content should work the same way.

A page may explore several related ideas, but those ideas should still clearly connect back to the page's purpose. The branches give the page enough depth to actually be useful. They help you anticipate what someone may want to know next, answer related questions, address concerns, and explain the parts of the subject that actually matter. But that doesn't mean it replaces the trunk, and that's important. If the trunk answers what is this page supposed to be doing, then the branches answer what supporting information will help this page do that job well.

So what are the branches? Let's make that a little more concrete.

Imagine you're a wedding photographer, and you have an informational page called what to expect from your wedding day photography. In the trunk episode, we might define the purpose of that page as helping couples understand the photography experience so they feel prepared for the day. That would be the trunk.

Now think about the questions that naturally grow from that purpose. Couples may want to know how to build photography into their wedding timeline. They may want tips for getting ready photos. They may wonder what happens if it rains. They may be worried about getting thirty family members together for formal photos without absolute chaos breaking loose. And hey, just in case you didn't know, I was a professional photographer for ten years and I shot a lot of weddings. And yeah, it can be absolute chaos during that time. They may want to know when golden hour happens and how portraits fit around dinner or the ceremony or maybe even a first look.

Those would be the branches. Each one explores a specific aspect of the larger subject, but every one still serves the same purpose — helping the couple understand and prepare for their wedding day photography experience. They make the content more useful and more complete without changing what the page is fundamentally there to accomplish.

And there are a few things branches are not. A branch is not a completely different subject that you happen to find interesting. If you're halfway through a wedding photography guide and suddenly there's an eight paragraph section on choosing wedding flowers because technically flowers appear in photographs, it's probably not a branch. That is a tangent that wandered into the orchard and got lost.

A branch is also not a second competing trunk. If a supporting section starts requiring its own audience, purpose, structure, call to action, or several subtopics of its own, you may no longer be looking at a branch. You may be looking at another tree.

And branches are definitely not an excuse to cram related keywords into a page because somebody told you that mentioning more phrases will make Google or ChatGPT love you. That is not what we're doing. We're building useful topical depth, because at the end of the day, that is what Google and ChatGPT love.

So let's talk about what it means to have depth versus breadth. There's an important distinction between them. Breadth is how many different things you talk about. Depth is how thoroughly you help someone understand the thing they actually came for. And they're not the same thing.

A page can be extremely long and still be shallow if it spends two sentences on twenty unrelated ideas. On the other hand, a page can be much shorter but demonstrate far greater depth because it anticipates the right questions, explains the important details, and gives someone enough context to actually understand the subject.

So when I talk about branches adding depth, I don't mean make every page longer. I mean cover the supporting information that genuinely belongs there. This matters because there's a tendency in content marketing to equate word count with quality. Someone decides that the competitor ranking above them has a two thousand word article, so clearly they need a twenty five hundred word article. That's not a strategy. If twelve hundred words answer the question thoroughly, use twelve hundred words. If the subject genuinely requires three thousand, fine. The goal is not to reach a magic number. It's to satisfy the intent of the page, and branches help you decide what deserves space.

So now let's talk about why that matters for AI visibility. When someone asks an AI system a question, the system is trying to generate a response that meaningfully addresses that request. Content that clearly explains a subject, covers relevant supporting information, answers natural follow-up questions, and provides useful context gives the system more material for understanding what that page actually knows and where it may be useful.

And that doesn't mean AI systems simply count the number of subtopics on a page and declare you an authority — because wouldn't that be wonderfully easy? But no. The point is that genuine topical coverage creates that context.

So imagine someone asks, how should I prepare for wedding day photography? And a page containing three sentences saying hire a photographer you trust, relax and have fun, your photographer will tell you what to do — that technically addresses the topic, but it leaves an enormous number of questions unanswered.

Compare that with a page that explains how photography affects the timeline, what to consider when choosing a getting ready space, how to organize family photo combinations, what happens if weather changes — all of these things give the page a much fuller answer. The supporting topics that help establish what the page covers are now thoroughly addressed, and AI is much more likely to surface that article than the three sentence one.

So if someone lands on your page with five questions and you answer four of them before they even have to ask, that page has massive value to them. It may keep them on your website longer. It may increase trust. It may encourage them to explore another page. It may make them think, okay, this person has clearly thought through the things I'm worried about. And do you know what that does? It also shows your expertise. It says I've been doing this long enough to not only think through these things, but to think through them enough to give you that information in advance.

Now those same contextual relationships can also make the content easier for search and AI systems to interpret. I wouldn't think of branches as secondary keywords, so to speak. There may be some keyword overlap because the questions and subtopics people care about are naturally reflected in search language, but branches are conceptually bigger than that. They're supporting concepts. So while your trunk defines the job, your branches supply the substance that helps accomplish it.

This is also where I want to be careful with the word comprehensive, because I use that word a lot. What I want to say is comprehensive does not mean everything. It does not mean exhaustive. You do not need to answer every question anyone has ever asked about wedding photography on one page. Don't do that.

The goal is to be comprehensive relative to the intent of the page. If the page is about preparing for a bridal makeup trial, you probably need to address what to bring, how to prepare your skin, how inspiration photos work, how long the appointment typically takes, and what decisions are usually made during the trial. You probably don't need a twelve hundred word history of cosmetics. You also probably do not need to explain how to choose lipstick for your honeymoon, because while that may be related to makeup, it doesn't really serve the purpose of that particular page.

This is where your trunk becomes your filter. Whenever you're unsure about whether something belongs, just go back to your purpose statement from your trunk — which is from the last episode, by the way. Does this help the page do its primary job? If yes, you have a branch. If no, you may have another page idea.

So what makes a good branch? We keep talking about weddings and bridal makeup, so we're going to continue on with those examples because I think it helps as you listen to this over the course of these ten episodes to get a good idea of what this will eventually look like as a whole.

Imagine you're a makeup artist and you have a bridal makeup services page. The trunk of that page might be: help brides understand our bridal makeup service so they can decide whether we're the right fit and feel confident taking the next step.

Now think about what someone evaluating that service would naturally want to know. She may want to understand what happens during a bridal trial. She may need to know how to prepare her skin. She may wonder whether the makeup will last in heat and humidity or through tears. She may be concerned about whether it will photograph naturally. She may want to know how your work fits into the wedding morning timeline.

Those are all excellent branches because each one helps answer a question involved in making the decision. You could have a section about bridal trials, another about skin prep, another about longevity and touch ups, another about photography, and another about timing. But notice that none of those sections is random. Every one of them helps the prospective client better understand the service she's evaluating, and that's a good, strong branch structure.

Now imagine a house cleaning company with a deep cleaning services page. The primary purpose is to help someone understand what the service includes and decide whether they need to book it. What questions naturally grow from that? The visitor may want to know the difference between a regular clean and a deep cleaning. They may want to know which areas of the house receive the extra attention. They may wonder how long the service takes, or if there's going to be extra people helping the cleaner, whether they need to prepare anything beforehand, and how often a deep clean is typically useful.

Again, those become branches. And it's important to note that they're not there because how often should I deep clean happens to be a keyword somebody found in a tool. They're there because it is a completely reasonable question someone considering a deep cleaning service might have. So when you think about branches from the consumer perspective instead of the algorithm's perspective, you'll tend to end up with better content anyway.

Alright, so let's get a little more practical. How do you actually identify the right branches for each page?

The first thing is you start with your trunk. Before you can identify your branches, you need a clear trunk — and again, go back to the last episode that talks about the trunk for more information on that. What is the single job this page is meant to do? Once you know that, you can ask, what supporting topics would help accomplish that job more thoroughly?

Next would be to ask, what would someone naturally want to know next? Put yourself in the consumer's shoes. If they're on a page about bridal makeup services, what questions would they have? What concerns? What adjacent topics would normally come up?

Next, look at what you're already explaining. If you have existing content, look at what you naturally cover, or even go through your emails and see if you're getting a lot of the same questions. Sometimes your branches are already there, you just haven't structured them clearly. Look for sections that could be broken out with their own headings that explore a specific aspect of that main topic.

Next, I would research what people actually ask. Look at questions from clients. Look at the people also ask boxes in Google. Look at related searches. Look at comments and questions on social media, or FAQ patterns in your industry. These reveal the branches people actually care about.

Check that each branch connects back. For each potential branch, ask: does this support the trunk, or does this distract from it? If a branch is interesting but doesn't really serve the page's main purpose, save it for a different page. Not every related idea belongs on the page.

And then prioritize four to six strong branches. You don't need to cover everything, but aim for four to six. That's typically what I recommend. Too many branches and the page becomes kind of unwieldy. Too few and the content feels thin.

So a framework for thinking about the branches, in my opinion, would be: for any page, ask yourself, what does someone need to understand before they can act on the main idea? What concerns or objections might they have? What related topics would make this more useful? What practical details would help them implement this? And what questions do people ask me about this all the time? The answers to these questions are definitely going to be your branches.

Now let's talk a little bit about branches versus separate pages. One of the trickiest things about branches is knowing when something should be a branch versus when it should be its own page. And here's my general rule. If a topic needs more than a few paragraphs to cover properly, it deserves its own page.

I'll give you an example. Say you're writing that what to expect on your wedding day page for your wedding photography. Tips for getting ready photos could be a branch — a section with a few helpful tips. But if you find yourself wanting to write fifteen hundred words about getting ready photos, that's not a branch anymore. That's a separate page. And that's okay. You can have a branch that introduces the topic and then links to a dedicated page for people who want to go deeper.

So think of it this way. A branch is kind of like a mention and exploration. You cover it in the context of the main topic. But a separate page is a deep dive. It deserves its own trunk, its own branches, and its own full treatment.

Signs that something should be a branch: it could be covered in a few paragraphs, it only makes sense in the context of the main topic, readers would expect to find it on only that page, or it doesn't need its own structure or subtopics.

Signs that it should be its own page: it needs substantial coverage to be useful, people search for it independently, it has its own subtopics and complexities, and it could serve as a hub for other content.

When you move a topic to its own page, the branch on the original page becomes a link. For more detailed tips on getting ready photos, see our complete guide. That's how branches connect to your larger ecosystem anyway. They can point to other pages where topics are explored more fully. This is how the underground network we'll talk about in a future episode starts to form. Branches on one page link to trunks on other pages. Everything connects, because it's an ecosystem — and that's why I called it the Orchard Ecosystem Framework.

So let's talk about how branches connect to the rest of the Orchard Ecosystem Framework.

Branches extend from the trunk. We already talked about how the trunk is the main purpose of the page. Your branches are the supporting topics that help accomplish that purpose. Every branch should serve the trunk. If it doesn't, it's either a distraction or it belongs on a different page.

Branches are rooted in roots. We covered roots in episode nine, so feel free to check that out. Your branches should connect back to your canonical pillars. If your root is wedding photography, your branches on any wedding photography page should be related to wedding photography. They're extending your expertise within your pillar areas.

Next is how branches use soil. We talked about the soil in episode ten. The language inside those sections should remain consistent with the vocabulary you've established around your business. If your photography style is consistently described as documentary wedding photography, that language should naturally continue appearing when relevant throughout supporting sections. You don't suddenly rename your approach in every branch because you're trying to sound creative. Your soil keeps the language recognizable while the branches allow the ideas to expand.

And then branches grow from the trunk — that was episode eleven. The relationship between the trunk and branches is probably the easiest part of the metaphor, because the trunk is the central purpose and the branches are the supporting topics helping the page accomplish that purpose. If you ever become unsure about a branch, go backwards. What's the trunk? What is the page here to do? Does the section help? If it does, keep going. If it doesn't, you just found something that belongs somewhere else. That question alone can clean up a surprising amount of messy website content.

Then there's how branches connect to the leaves. We haven't gotten there yet, but we will. Leaves are the clarity signals that help expose the structure of the content. In practical terms, your individual branches often become the major sections of a page, and headings help identify those sections. So the branch may be preparing your skin for your bridal makeup trial, but the heading that makes that branch visible is part of the leaves layer. The ideas exist first, but then the structure — the leaves — helps humans and machines see them.

And then we have the fruit. The fruit represents proof, and proof often belongs naturally inside your branches. If you have a section explaining how your makeup lasts through a long Florida wedding day, perhaps you have a testimonial from a bride specifically talking about how her makeup survived heat, tears, dancing, sweat, and humidity. That proof supports the specific branch while also supporting the larger trunk of the page. The fruit doesn't have to sit in one giant testimonial section at the bottom of the page. Sometimes the strongest place for proof is directly beside the claim it supports.

Then we head underground to the underground network, and how branches feed it. Branches are one of the most natural places to discover internal linking opportunities. A supporting idea may deserve a short explanation on the current page, but also have a deeper resource somewhere else. You can link the two. The branch becomes the contextual bridge to another tree. That helps people continue learning based on what they care about, and it helps establish relationships between pages inside the ecosystem.

Then we move on to the pollinators. Pollinators represent the outside sources carrying signals into and around your ecosystem. Useful, well developed content has a greater chance of becoming something other people want to cite, reference, share, discuss, and link to. That doesn't mean writing more branches automatically produces more backlinks, but useful information with depth gives people something worth referencing. A page that says exactly what every other page says in a slightly different order is not remarkable. But a page that anticipates the real questions people have, explains them clearly, and offers genuine expertise is way more valuable — and that value gives the content a better reason to travel.

I want to cover some common branch mistakes that I think are going to be helpful for you going forward.

The first one is branches that compete with the trunk. Sometimes people add quote unquote branches that are really competing purposes. If you're supposed to be educating someone but one of your branches is a hard sales pitch, that's not a branch. That's a conflicting trunk. Keep your branches in service of the main purpose.

The second mistake is too many branches. Some pages try to cover everything — fifteen different subtopics crammed into one page. The result is overwhelming and unfocused. Again, as I mentioned earlier, aim for four to six strong branches.

Mistake number three is disconnected branches. These are branches that don't clearly connect to the trunk, which confuses the reader and AI. Every section should obviously relate to the main topic. If someone has to wonder why is this here, cut it out or move it.

Mistake number four is branches without headings. If you have good branches but they're buried in walls of text, no one can find them. Use clear headings to make each branch visible. This helps both readers scanning the page and AI understanding your structure.

Mistake number five is thin branches. Sometimes people mention a subtopic in one sentence and move on. That's not really a branch. If it's worth including, you need to give it enough substance to make it worth being on that page. A few sentences or a paragraph at minimum.

And then mistake number six, branches that could be pages. If you're trying to cram five hundred words about a subtopic into what should be a branch, give it its own page. Link to it. Let the branch be an introduction and the page be the deep dive.

Now let's talk about some practical exercises to help you identify your branches, because you know homework's coming. It always does.

Step one, pick a page on your website. As I've said in all my other episodes, I like to start with my homepage.

Step two, write down your trunk — the single job that page is meant to do. If you did your homework last week, that should already be done.

Step three, brainstorm eight to ten potential branches. What supporting topics could add depth to this page? What questions would readers naturally have? What related aspects could you explore? I like to think of this like one of those brainstorming bubbles from back in school, where you write the main topic in the center of the page and circle it, then draw a line out from it and write something. And you go all the way around. So what I would do is literally write that down just like that, and come up with eight to ten potential branches.

Step four, evaluate each potential branch. Does it support the trunk? Is it substantial enough to include, but not so big it needs its own page? Would a reader expect to find this here?

Step five, narrow down to four to six strong branches. Cut anything that doesn't clearly serve the main purpose.

And step six, check your existing content. Do you already cover these branches? If so, do they have clear headings? If not, what do you need to add?

And as always, I made a workie sheetie for you guys. If you want a structured place to do this work, I have created a free worksheet for this episode. It walks you through identifying branches for your key pages, evaluating whether each branch serves your trunk, and deciding what should be a branch versus a separate page. I also included an AI prompt where you just plug in your website URL and a specific page, and it'll help you identify what subtopics you're already covering and what gaps might exist. You can download it for free at clemelopy.com/branches.

Is your brain fried a little bit today, just like last week and the week before and the week before?

Alright. Let's talk about what's next. In the next episode, we're talking all about the leaves. And to be honest, that's probably going to be the most brain frying episode, because this is where things go from concept into very technical. But we've got you, boo.

The leaves are the clarity signals that make your content scannable and understandable. You have a strong trunk and great branches, but if your content isn't structured clearly, people and AI can't see it. Leaves are the headings, the formatting, the schema, the structure that makes your content easy to parse. It's like the bones — the bones that sometimes people see, sometimes people don't see, but AI sees. We'll talk about how to structure your pages for both humans and AI, what schema markup is and why it matters, and how to make your expertise visible at a glance. I'd say it's gonna be a good one, but it's gonna be a great one.

So that being said, this episode is brought to you by Clemelopy. If you want to start optimizing your website for AI search, head to clemelopy.com to see how you can get started. Thanks for spending this time with me, and until next time, keep growing forward.