How to Optimize a Service Page for "SaaS Onboarding Video Production": My Full Checklist

I want to tell you about the service page that sat on page four for eight months.

It was a good page. It described what we did, who we did it for, and why it worked. It had testimonials, a portfolio, a pricing section, and a contact form. By any reasonable standard, it was a professional service page. It was also invisible.

The problem wasn't the content. The problem was the optimization. I had built the page for humans and forgotten that humans have to find it first. No keyword research. No title optimization. No schema. No internal links pointing to it. No video. No CTA above the fold. Just a page, sitting on our site, waiting for traffic that never came.

Then I rebuilt it. Not the design—the structure. The same content, reorganized around a single query: "saas onboarding video production." Three weeks later, the page entered the top three. It's now the highest-converting page on our entire site, producing qualified leads every week from people who searched for exactly what we do.

This article is the full rebuild. The keyword research, the title tag, the H1, the meta description, the schema, the CTA, the internal links, and the technical layer. It's the checklist I now run on every service page we publish, and it's the checklist I wish I'd had before I wasted eight months.

We produce the videos that the page sells with LeoStudio, whose approach to clarity you can explore at leostudiohq.com. They were the ones who told me, after I complained about the traffic, that a service page is not a brochure. It's a search result. It has to earn the click the same way a video has to earn the play. That reframe is the reason this page works, and it's the reason this article exists.

Why Service Pages Fail at SEO

Before the checklist, the diagnosis. Because if you don't understand why service pages fail, you'll rebuild yours and watch it fail again.

A service page has two jobs. The first is to convert the visitor. The second is to be found by the visitor. Most teams obsess over the first and ignore the second. They write beautiful copy, add testimonials, design a conversion flow—and then wonder why the page gets forty visits a month.

The reason is that service pages are usually written for people who already know the company. A referral clicks the link, lands on the page, and decides whether to reach out. That's the referral flow. But referrals are not a search strategy. A search strategy requires the page to rank for the queries your prospects are typing. And ranking requires the page to be built for the query, not just for the conversion.

The second reason service pages fail is that they're written for the company, not the searcher. A page titled "Our Services" targets no query. A page titled "SaaS Onboarding Video Production" targets exactly the query the buyer is typing. The difference is not cosmetic. It's the difference between being found and being invisible.

The third reason is technical. Service pages rarely have schema, rarely have video, rarely have internal links pointing to them from supporting content. They exist in isolation, on a site that has no topical authority around the service. Google has no reason to rank them, because Google can't tell what they're about or why they matter.

The fix is not complicated. It's just specific. Here's the checklist.

Step 1: Keyword Research Before Anything Else

The first thing I did—after eight months of failure—was keyword research. Not the vague kind. The specific kind.

I wanted to know three things. What is the primary query? What are the supporting queries? What is the intent behind each one?

The primary query: "SaaS onboarding video production." It has moderate volume and very high intent. Someone searching this phrase is looking for a vendor. They're not researching the concept. They're not comparing approaches. They're looking for someone who does this, and they're close to buying.

The supporting queries: "Onboarding video for SaaS." "SaaS product video production." "Onboarding video agency." "SaaS video production company." "Onboarding video cost." "Onboarding video script." Each of these is a related query with its own intent. Some are informational. Some are commercial. Some are transactional.

The intent mapping: The primary query is transactional. The searcher wants a vendor. The supporting queries are a mix. "Onboarding video cost" is commercial investigation—the searcher is evaluating whether to buy. "Onboarding video script" is informational—the searcher is trying to understand how to build one.

The mapping determines the page structure. The primary query gets the page. The commercial queries get sections within the page. The informational queries get supporting articles that link to the page. That's the architecture.

I spent two hours on this research. It changed the entire rebuild.

Step 2: The Title Tag

The title tag is the single most important on-page element for ranking. It's the first thing Google reads. It's the first thing the searcher sees in the results.

What I did: "SaaS Onboarding Video Production | Cut Time-to-Value" — 56 characters. The primary keyword is front-loaded. The value proposition is appended. The pipe separates the keyword from the benefit.

Why this works: The primary keyword is in the first three words. Google can immediately tell what the page is about. The value proposition—"Cut Time-to-Value"—is specific. It promises an outcome, not a service. It's the same principle we use in video titles, and it's the same principle LeoStudio applies to every opening frame. The promise earns the click. The keyword earns the ranking. You need both.

What I avoided: "Our Services | [Company Name]." No keyword. No promise. No reason to click. A page titled after the company is a page that only ranks for the company name, which means it only gets found by people who already know you.

The variation I tested: "Onboarding Video Production for SaaS Companies | [Company]." It performed worse than the keyword-first version. The keyword-first title won because it matched the query exactly.

Step 3: The H1

The H1 is the second most important on-page element. It should match the title tag closely, but not identically. Google uses both as signals, and consistency matters.

What I did: H1: "SaaS Onboarding Video Production That Cuts Time-to-Value." It includes the primary keyword. It includes the value proposition. It's the first thing the visitor sees on the page, and it tells them exactly what this page is about and why it matters.

Why this works: The H1 confirms the title tag's promise. It's also the anchor for the page's content. Every section below the H1 supports the claim in the H1—that our onboarding video production cuts time-to-value. The page becomes a proof of its own headline.

What I avoided: "Welcome to Our Services." A headline that says nothing tells Google nothing. The H1 is not a greeting. It's a statement of what the page is about.

Step 4: The Meta Description

The meta description doesn't directly affect rankings. It affects click-through rate, and click-through rate affects rankings indirectly.

What I did: "SaaS onboarding video production that cut time-to-value from 14 days to 4. See our process, our numbers, and what we got wrong. Book a call." — 155 characters. It includes the primary keyword. It includes the proof point. It includes the CTA.

Why this works: The description promises three things the searcher cares about. The process. The numbers. The honesty about failure. That third one is unusual. Most service pages promise perfection. Promising to show what went wrong signals credibility, and credibility is what converts a commercial query.

What I avoided: "We provide high-quality onboarding video production services for SaaS companies." Generic. No proof. No differentiation. Every competitor says the same thing.

Step 5: The On-Page Content Structure

The content has to rank for the primary query and support the commercial queries. Here's how I structured it.

The opening section. It names the problem the searcher has. Not the service. The problem. "Your users sign up, get confused, and churn in the first two weeks. Onboarding video is the fastest way to fix it—if the video is built for the moment, not for the features." That opening establishes relevance before it sells anything.

The mechanism section. It explains how onboarding video production actually reduces churn. Not "video works." The specific mechanism—video shortens time-to-value, which lifts activation, which reduces churn. This section targets the commercial queries. It's also the section that earns trust, because it demonstrates that we understand the problem, not just the service.

The process section. It walks through our production process—diagnosis, brief, script, storyboard, production, measurement. This section targets "SaaS video production process" and "onboarding video production process." It's the section that answers the question "what will it be like to work with you."

The proof section. It includes the case study—the onboarding video that cut time-to-value from 14 days to 4. Real numbers. Real before-and-after. This is the section that converts. It's also the section that ranks for "onboarding video results" and "onboarding video case study."

The cost section. It addresses the pricing question directly. Not a price list—a range and the factors that move it. This section targets "SaaS onboarding video cost," which is one of the highest-intent supporting queries.

The failure section. It acknowledges what onboarding video can't do. It can't fix a product that's too complex. It can't create a use case that doesn't exist. This section builds credibility and targets "onboarding video mistakes" and "onboarding video problems."

The FAQ section. It answers the questions that appear in People Also Ask—"How long does onboarding video production take?" "What makes a good onboarding video?" "How much does onboarding video cost?" Each answer targets a query and adds FAQ schema eligibility.

The structure is not linear. It's layered. Each section targets a query. Each section supports the primary keyword. Each section builds toward the CTA.

Step 6: Schema Markup

Schema is the technical layer that makes the page eligible for rich results. I added three types.

Service schema. It describes the service—name, description, provider, areaServed, serviceType. It tells Google exactly what the page sells. Without it, Google has to infer the service from the content. With it, Google knows.

VideoObject schema. The page includes the onboarding video, embedded above the fold. The schema includes the name, thumbnailUrl, uploadDate, contentUrl, description, and duration. It makes the video eligible for the video carousel, which is a separate SERP feature that most service pages never reach.

FAQ schema. The FAQ section includes ten questions, each marked up with Question and Answer schema. This makes the page eligible for the FAQ rich result, which expands the page's real estate in the search results and increases click-through rate.

Article schema. Even though it's a service page, the content includes long-form sections that function like an article. Article schema signals that the page contains substantial content, which supports ranking.

I verified all four schemas with the Rich Results Test before publishing. Three of them appeared in the search results within a month.

Step 7: The CTA Placement

Most service pages put the CTA at the bottom. That's a mistake. By the time the visitor reaches the bottom, they've either already decided to contact you or they've already left.

What I did: Three CTAs. One above the fold, in the hero section, next to the video. One mid-page, after the proof section. One at the bottom, after the FAQ.

Why three: Different visitors decide at different points. Some decide immediately—they see the video, they see the promise, they're ready. Some need the proof—they read the case study and then decide. Some need the FAQ answered—they read the questions and then decide. Three CTAs catch all three.

What the CTA says: Not "Contact Us." "Book a 15-minute call." It's specific. It's low-commitment. It tells the visitor exactly what happens next. Specific CTAs outperform generic ones by a wide margin.

What I avoided: A single CTA at the bottom. A form with seven fields. A "Submit" button. Every one of those adds friction at the moment of decision.

Step 8: Internal Linking

Internal links are how authority flows through a site. A service page with no internal links is a page that Google sees as an orphan.

What I did: Every supporting article on our site now links to the service page with descriptive anchor text. The onboarding video case study links to it. The welcome email article links to it. The analytics setup guide links to it. The localization piece links to it. Nine internal links with consistent anchor text variations.

Why this works: The internal links tell Google that the service page is the authority on the topic. The supporting articles become context. The service page becomes the destination. The cluster forms.

The anchor text: "SaaS onboarding video production" is the primary anchor. Variations include "onboarding video production," "SaaS onboarding video," and "onboarding video for SaaS." The variation avoids over-optimization while keeping the signal consistent.

What I avoided: "Click here." "Read more." "Learn more." Generic anchor text tells Google nothing about the destination. Descriptive anchor text tells Google exactly what the page is about.

Step 9: The Technical Layer

The content and structure were done. The technical layer determined whether Google could actually see it.

Page speed. I compressed every image. I lazy-loaded the video. The page loads in under two seconds on mobile. Service pages with heavy media assets often load in four to six seconds. That's a ranking problem.

Mobile experience. I tested on an actual phone. The hero section, the video, and the CTA all worked on a small screen. The video was readable. The text was legible. The form was tappable. More than half of the traffic comes from mobile. If the page doesn't work on a phone, it doesn't work.

Video on mute. The embedded video autoplays muted with captions. Never with sound. Autoplay with sound is the fastest way to lose a visitor and hurt the page's engagement signals.

The URL. /services/saas-onboarding-video-production. Short. Keyword-rich. No dates. No parameters.

The canonical tag. Self-referencing. No duplicates. No ambiguity.

The sitemap. The service page is in the main sitemap. The video is in a video sitemap. Both are submitted to Google Search Console.

The robots meta. Index, follow. No noindex. No nofollow on internal links.

Step 10: Measurement

The page launched. Then I measured.

Rankings. I tracked the primary query and eleven supporting queries weekly. The page entered the top ten for the primary query in three weeks. It entered the top three in eight weeks.

Click-through rate. I tracked the CTR in Search Console. The title tag and meta description that I'd tested outperformed the previous version by 41% on CTR.

Conversion rate. I tracked the percentage of visitors who booked a call. The page converts at 4.2%—the highest on the site.

Assisted conversions. I tracked the pages that visitors viewed before booking. The service page is the most common last page before conversion, but it's also the most common second-to-last page. That means the page is both a closer and a connector.

The one metric I wish I'd tracked from the start: the source of the visitor. Which queries brought visitors who converted. The answer surprised me. The highest-converting query was not the primary keyword. It was "SaaS onboarding video cost." The searcher was further down the funnel than I'd assumed. That finding changed how I wrote the pricing section, and it's the reason that section is now the longest on the page.

The Mistakes That Kept the Page Invisible for Eight Months

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

We had no keyword research. The page targeted no query. It was titled "Our Services." Google had nothing to rank it for.

We had no video on a video production page. This is the mistake that still embarrasses me. We sell onboarding video production, and our service page had no video. Adding the onboarding video to the hero section increased time-on-page by 68% and made the page eligible for the video carousel.

We had no schema. No Service schema. No VideoObject schema. No FAQ schema. The page was ineligible for every rich result. Adding the schemas brought the page into the video carousel and the FAQ rich result within a month.

We had no internal links. The page was an orphan. Nothing linked to it. Google saw it as a dead end. Adding nine internal links from supporting articles moved it from page four to page one.

We put the CTA at the bottom only. Visitors who decided early had nowhere to go. Adding the above-the-fold CTA doubled the conversion rate.

We wrote for the company, not the searcher. The page said "we are a video production company." The searcher wanted to know whether we understood their problem. The rewrite opened with the user's problem—churn in the first two weeks—before mentioning the service.

We ignored mobile. The first version of the page had a hero video that was unreadable on a phone. We re-exported everything. Mobile is not an afterthought. It's the majority.

We didn't measure assisted conversions. We only looked at last-click. The page was doing more work than we knew, because it was a connector for visitors who converted elsewhere. Once we measured assisted conversions, we understood the page's real value.

The Framework: How I Optimize Every Service Page Now

Here's the process I run before publishing any service page.

Step one: Keyword research. Identify the primary query and the supporting queries. Map the intent of each one. The primary query gets the page. The commercial queries get sections. The informational queries get supporting articles.

Step two: Title tag. Primary keyword front-loaded. Value proposition appended. Under 60 characters. No company name unless the company is the keyword.

Step three: H1. Match the title tag closely. Include the primary keyword. State what the page is about in one sentence.

Step four: Meta description. Include the primary keyword. Include a proof point. Include a CTA. Under 160 characters.

Step five: Content structure. Open with the problem. Explain the mechanism. Walk through the process. Show the proof. Address the cost. Acknowledge the failures. Answer the FAQs. Each section targets a query.

Step six: Schema. Service schema. VideoObject schema. FAQ schema. Article schema. Verify with the Rich Results Test.

Step seven: CTA placement. Above the fold. Mid-page. Bottom. Three CTAs. Specific language. Low-commitment offer.

Step eight: Internal links. Every supporting article links to the service page with descriptive anchor text. Nine links minimum. Consistent anchor text variations.

Step nine: Technical layer. Page speed under two seconds. Mobile tested on an actual phone. Video autoplay muted. Short URL. Self-referencing canonical. Sitemap submitted.

Step ten: Measurement. Track rankings, CTR, conversion rate, and assisted conversions. Review monthly. Iterate on the sections that underperform.

This framework came out of eight months of failure and one rebuild. It's the version of the process I wish I'd had on day one. LeoStudio helped me refine it—their approach to the first five seconds, the promise, and the moment before the play is the same discipline applied to a service page. The title is the hook. The H1 is the promise. The CTA is the play. You can see that thinking throughout their work at leostudiohq.com.

The Results

Here's what happened after the rebuild.

The page entered the top ten for "saas onboarding video production" in three weeks. It entered the top three in eight weeks. It now ranks for eleven supporting queries. It appears in the video carousel. It appears in the FAQ rich result.

The conversion rate is 4.2%—the highest on the site. The page is the most common last page before a booked call and the most common second-to-last page. It's both a closer and a connector.

The traffic is good. The rankings are good. But the number that matters most is the one that doesn't show up in an SEO tool. The page produces qualified leads every week from people who searched for exactly what we do. That's the outcome the query was asking for. The page delivers it.

The Final Word

A service page is not a brochure. It's a search result. It has to earn the click the same way a video has to earn the play. The title is the hook. The H1 is the promise. The content is the proof. The schema is the eligibility. The internal links are the authority. The CTA is the conversion. Every element has a job.

Our service page sat on page four for eight months because I built it for humans and forgot that humans have to find it first. The rebuild took two weeks. The results took three months. The page is now the highest-converting page on our site.

If you're building or rebuilding a service page for "saas onboarding video production," start with the keyword research. Then the title. Then the H1. Then the structure. Then the schema. Then the internal links. Then the technical layer. Then measure. The order matters. The keyword determines everything downstream.

We produce the videos that the page sells with LeoStudio, a team that understood from the first call that a service page is a search result, not a brochure. If you want to see how they think about the promise, the hook, and the moment before the click, spend time on leostudiohq.com. Their approach to clarity is the reason the videos work. The service page optimization is the reason people find them.

Tell them the SEO guy sent you. Tell them you already ran the keyword research. Tell them you already added the schema. They'll know exactly what you mean.