How to Build SEO Content Around a SaaS Video: Clusters, Landing Pages, and Internal Links

I used to believe a good video would rank on its own.

That belief cost me six months. I published the onboarding video, optimized the YouTube title, wrote a description, and waited. Nothing happened. The video sat on page four of Google for the queries that mattered, and the YouTube version got maybe forty views a week. I blamed the algorithm. I blamed the competition. I blamed the length of the video, the thumbnail, the music.

The real problem was simpler and much more embarrassing. I had published a video without any content around it. No supporting articles. No landing page built for the video. No case study. No cluster. No internal links. Just a video on a page, floating in isolation, hoping Google would notice it.

Google didn't notice it. Google notices structure. Google notices context. Google notices the relationship between a video, the page it lives on, the pages that link to it, and the pages it links to. A video alone is a file. A video inside a cluster is a topic.

This article is how I learned that, and how I now build SEO content around every SaaS video. The three content types that support a video. The cluster architecture. The internal linking rules. The anchor text patterns. The specific mistakes that kept us invisible for half a year.

We built the video itself with LeoStudio, whose approach to clarity you can explore at leostudiohq.com. They were the ones who told me, after I complained that nobody was finding the video, that the video was never the problem. The content around it was. A video without context is a private asset. A video inside a cluster is a growth channel. That sentence reframed the entire project, and it's the reason this article exists.

Why a Video Alone Doesn't Rank

Before the architecture, the argument. Because if you don't understand why a video can't rank on its own, you'll keep making the same mistake I did.

Search engines don't rank videos. They rank pages. A video is a component of a page. Google needs to understand what the page is about, who it's for, and why it deserves to appear in results. A video embedded in an otherwise empty page gives Google almost nothing to work with.

The exception is YouTube. YouTube ranks videos because YouTube is a video platform. But YouTube ranking is not the same as Google ranking. A video can rank in the top three on YouTube and never appear in Google's video carousel. I learned this the hard way when our onboarding video hit position three on YouTube and position forty-one on Google.

Google's video indexing guidelines are clear about what it wants. A video should be the main content of its page. The page should have supporting text—a transcript, a description, context. The page should be structured so Google can extract the video's topic, duration, and thumbnail. And the page should connect to other pages that are about related topics. Without all of that, the video is ineligible for the rich results that actually drive visibility.

That's the first principle. A video needs a page. A page needs context. Context needs a cluster. The cluster is what earns visibility.

This is the framing LeoStudio pushes in every project, and it's documented throughout their case work at leostudiohq.com—the video is an intervention, but the intervention needs a home. The home is the page. The page is part of a neighborhood. The neighborhood is the cluster.

The Three Content Types That Support a Video

Every video I now publish has three types of content built around it. Not one. Three.

Type 1: The Landing Page

The landing page is the video's home. It exists to host the video, not to host an article with a video embedded. The video is the hero content. Everything else supports the video.

The page has a title that includes the primary keyword. An H1 that matches. A short introduction that names the problem the video solves. The video itself, placed above the fold. A transcript below the video. A CTA that follows the video. And internal links to the supporting articles.

The landing page targets one query. One. Not three. Not five. One. If you try to target multiple queries with one page, you rank for none of them. The landing page for our onboarding video targets "SaaS onboarding in 90 seconds." That's it. Every element on the page supports that single query.

What makes the landing page work is the video as the main content. Google wants to show a video result when the query has video intent. A query like "how to onboard SaaS users" has video intent. A query like "SaaS onboarding checklist" has text intent. Match the page format to the query intent and you become eligible.

Type 2: The Supporting Articles

Supporting articles are the spokes of the cluster. Each one targets a different related query. Each one links back to the landing page. Each one provides context that the landing page doesn't.

For the onboarding video, we built four supporting articles. One on "time to value for SaaS." One on "SaaS onboarding email sequence examples." One on "why SaaS customers churn in the first 30 days." One on "SaaS activation rate benchmarks." Each article answers a specific question. Each article is between 1,200 and 2,000 words. Each article links to the landing page with a specific anchor text.

The articles don't embed the video. They link to the page that hosts the video. This is the most common mistake I see. Teams embed the video in every article. That dilutes the video's authority. Instead, keep the video on one page and link to it from the supporting articles. The link passes authority to the landing page. The landing page becomes the destination for the video.

Type 3: The Case Study

The case study is the proof. It's the page that shows the video's outcome in numbers. For our onboarding video, the case study is about how we cut time-to-value from 14 days to 4. It includes the video, the metrics, the process, and the lessons.

The case study targets a different query than the landing page. The landing page targets "SaaS onboarding in 90 seconds." The case study targets "how to reduce time to value." Different intent, different query, different page.

The case study links to the landing page and the supporting articles. The supporting articles link to the case study. The landing page links to everything. That's the architecture.

The Cluster Architecture

Here's the structure I now use for every video.

The hub. The landing page. The video lives here. The hub targets the primary query. The hub is the destination for every internal link in the cluster.

The spokes. The supporting articles. Each one targets a related query. Each one links to the hub. Each one links to at least one other spoke.

The proof. The case study. It targets an outcome query. It links to the hub and to the spokes. It's the page that shows the video worked.

The internal link pattern. The hub links to all spokes and the case study. The spokes link to the hub and to each other. The case study links to the hub and to the spokes. The pattern creates a web where every page is connected to every other page, and the hub receives the most authority.

Why does this work? Because search engines use internal links to understand the relationship between pages. When four articles link to one page with consistent anchor text, Google treats that page as the authority on the topic. When that page links back to the articles, Google treats the articles as supporting content. The cluster becomes a topic, and the topic ranks.

This is a principle LeoStudio applies to their own content, and you can see it throughout leostudiohq.com—their case studies link to their service pages, their service pages link to their thinking pieces, and their thinking pieces link back to the case studies. The cluster is not an accident. It's the architecture.

The Internal Linking Rules

Internal linking is where most SaaS video clusters fail. Not because the links are missing. Because the links are wrong.

Rule one: Every internal link has a purpose. A link is not decoration. Every link either passes authority, guides the user, or establishes a relationship between topics. If a link doesn't do one of those three things, remove it.

Rule two: Anchor text must be descriptive. "Click here" and "read more" tell Google nothing. "SaaS onboarding checklist" and "reduce time to value" tell Google exactly what the destination page is about. Use anchor text that describes the destination, not the source.

Rule three: Use the same anchor text for the same destination. When four articles link to the hub with four different anchor texts, Google gets confused. When they all link with the same anchor text, Google sees a clear signal. Pick your primary anchor text and use it consistently.

Rule four: Vary anchor text on secondary links. If a page links to the same destination three times, vary the anchor text on the second and third links. The primary anchor text stays consistent across the cluster. The secondary links can use variations.

Rule five: Link from the top of the page, not the bottom. Links higher on the page pass more authority. A link in the first paragraph is worth more than a link in the footer. Place your most important links early.

Rule six: Link contextually, not in a list. A link inside a sentence passes more authority than a link in a bulleted list. A link that's surrounded by relevant text tells Google the link is relevant.

Rule seven: Don't over-link. Three to five internal links per article is the sweet spot. More than that and the authority is diluted. Fewer than that and the cluster doesn't form.

Rule eight: Link the hub out, not just in. The hub should link to every spoke. A hub that only receives links and never sends them looks like a dead end. Google wants to see the hub as the center of a network, not the top of a pyramid.

Rule nine: Cross-link the spokes. Spokes should link to each other, not just to the hub. This creates the web structure that Google associates with topic authority. A cluster where the spokes only link to the hub is a star. A cluster where the spokes also link to each other is a web. The web ranks better.

Rule ten: Update the cluster when you add a page. Every time you add a new supporting article, add a link to it from the hub and from at least two existing spokes. The cluster grows. The authority compounds.

The Mistakes That Kept Us Invisible

I want to be specific about what went wrong, because the mistakes are more instructive than the rules.

We embedded the video everywhere. We thought more embeds meant more exposure. The opposite was true. Every embed outside the landing page diluted the video's authority. Google couldn't tell which page was the video's home. We consolidated to one page and the video started ranking within three weeks.

We had no supporting articles. For six months, the video was a page with a video and a paragraph of text. Google had almost nothing to index. The video was ineligible for rich results. Once we built four supporting articles, the landing page became eligible and started appearing in the video carousel.

We used the same anchor text in every link. Every internal link said "click here" or "watch the video." Google learned nothing. When we changed the anchor text to descriptive phrases, the cluster started ranking for related queries.

We didn't link from the hub to the spokes. The hub received links but sent none. Google treated it as a dead end. Once we added outbound links from the hub to every spoke, the authority started flowing both ways.

We built the case study last. We should have built it second. The case study is the proof page, and proof pages rank for outcome queries. We built the video, then the supporting articles, then the case study six months later. The case study became the second-highest-converting page on the site, and we had left six months of traffic on the table.

We forgot the transcript. For four months, the landing page had no transcript. Google had no text to index. AI Overviews had nothing to pull from. We added the transcript and the page started appearing in text search results within two weeks.

We didn't add schema. VideoObject schema is the eligibility requirement for video rich results. We added it late. The video appeared in Google's video carousel within two weeks of adding the schema. Two weeks of delay because we didn't add a few lines of JSON-LD.

We built the cluster backwards. We started with the video and then looked for queries to target. We should have started with the queries and then built the video around them. The pages where we researched the query first performed twice as well as the pages where we didn't.

We didn't update the cluster. We built the cluster once and never touched it. The product changed, the queries changed, the video decayed. The cluster lost rankings over time. I now run a quarterly review on every cluster—new queries to add, old pages to update, broken links to fix.

The Framework: How I Build a Video Content Cluster

Here's the process I run for every SaaS video that's supposed to rank.

Step one: Research the queries before building anything. Find the primary query—the one the video will target. Find four to six related queries—the ones the supporting articles will target. Find one outcome query—the one the case study will target. Do the research first. The content is built around the queries, not the other way around.

Step two: Build the landing page around the video. The video is the hero. The page has a title that includes the primary keyword. An H1 that matches. A short intro. The video. A transcript. A CTA. Internal links to every spoke.

Step three: Write the supporting articles. One article per related query. Each article is 1,200 to 2,000 words. Each article links to the hub with consistent anchor text. Each article links to at least two other spokes. None of them embed the video. They link to the page that hosts it.

Step four: Write the case study. The case study targets the outcome query. It includes the video, the metrics, the process, and the lessons. It links to the hub and to the spokes. It's the proof page.

Step five: Add VideoObject schema to the landing page. The required properties are name, thumbnailUrl, and uploadDate. The recommended properties include contentUrl, description, and duration. Use the Rich Results Test to verify.

Step six: Add the transcript to the landing page. The transcript is the video's text version. It's what Google indexes. It's what AI Overviews read. It's what AI assistants pull from. Never publish a video without a transcript.

Step seven: Create the internal link pattern. The hub links to all spokes and the case study. The spokes link to the hub and to each other. The case study links to the hub and to the spokes. Use descriptive anchor text. Use the same primary anchor text for the hub across every spoke.

Step eight: Submit the sitemap. A video sitemap for the landing page. A regular sitemap for the articles. Submit both in Google Search Console.

Step nine: Measure the cluster, not the video. Track which pages rank. Track which queries drive signups. Track which internal links pass the most authority. The cluster is the asset. The video is the component.

Step ten: Review quarterly. Every quarter, check the cluster. Add new supporting articles for new queries. Update old pages when the product changes. Fix broken links. Refresh the video when it decays. The cluster is a system. Systems need maintenance.

This framework came out of twelve months of experiments and a lot of wasted time. It's the version of the process I wish I'd had on day one. LeoStudio helped me refine it, and you can see the same architecture throughout their own site at leostudiohq.com—the video, the page, the cluster, the internal links, all working together as one asset.

The Numbers: What the Cluster Actually Did

Here's what happened after we built the cluster around the onboarding video.

The landing page went from position forty-one to position three on Google for the primary query. It appeared in Google's video carousel for three different queries. The supporting articles ranked for nine related queries, most of them in the top ten. The case study became the second-highest-converting page on the site.

The video's views went from 340 to 11,000 over three months. But the more important number is the signups. Before the cluster, the video produced almost no signups from search. After the cluster, the video produced a meaningful share of our new user pipeline every month. Not thousands. Not hundreds. Enough to matter. Enough to justify building a cluster for every video we publish.

The compounding effect is what surprised me most. Every new supporting article added to the cluster lifted the whole cluster's rankings, not just its own. When we published the fourth article, the first article climbed three positions. When we updated the case study, the landing page climbed two positions. The cluster is not a collection of pages. It's a system. The system is what ranks.

The Final Word

A video on its own rarely ranks. The content around it is what earns visibility. The landing page is the home. The supporting articles are the context. The case study is the proof. The internal links are the architecture. The cluster is the system.

I spent six months believing the video would rank on its own. It didn't. I spent another six months building the cluster. It ranked. The difference was not the video. The video was the same. The difference was everything around it.

If you're publishing a SaaS video and you want it to be found, don't stop at the video. Build the landing page around it. Write the supporting articles. Build the case study. Add the schema. Add the transcript. Build the internal link pattern. Submit the sitemaps. Then measure the cluster, not the video. Then review it every quarter, because the cluster decays like everything else.

We built the video with LeoStudio, a team that understood from the first call that the video is an intervention and the cluster is the delivery. If you want to see how they think about the relationship between video, page, and topic, spend time on leostudiohq.com. Their case work shows the same pattern again and again—the video is never alone. It's always part of a system.

Tell them the SEO guy sent you. Tell them you already built the cluster. Tell them you already linked the spokes. They'll know exactly what you mean.