B2B SaaS SEO: the pages your website needs to win buyers from search

The short answer

B2B SaaS SEO works when the marketing site has a page for each search a buyer makes on the way to choosing you: the problem, the job to be done, the tools they connect, the competitors they compare and your pricing. Each page answers that search with first-hand knowledge of the product, the claims about competitors are fair and checkable, and the pages are plain HTML that search engines can read quickly.

On this page

What B2B SaaS SEO really is

B2B buyers search for their problem long before they search for your brand. An operations manager doesn't type your product name; they type the job that is eating their week, then the kind of software that does it, then "alternatives" to the tool they already pay for, then your pricing.

B2B SaaS SEO is the work of having a good page waiting at each of those searches, and making each one lead to a trial, a demo or a signup. It is less about publishing a lot and more about publishing the right pages, which is why I plan SaaS sites as a growth site: a page for each search worth winning, linked together, with guides that answer what buyers ask.

I have done this from the product side too. I built DueStamp, my own invoicing app, and its marketing site: 22 indexable pages, each planned around one search, with a features hub, a page per feature and a set of guides.

Start with a page plan, not a blog calendar

Before anything is written, list the searches your buyers make and give each one a home. A typical plan for a B2B product looks like this:

PageThe search it is built to winWhere the buyer is
Home[category] softwareKnows the kind of tool they need
Use case pages[job] softwareKnows the problem, not the tool
Integration pages[tool] integrationNeeds it to work with what they use
Comparison and alternatives pages[competitor] alternativeReady to switch
Pricing[product] pricingClose to a decision
Docs and guideshow to [problem]Learning, or already a user

One search per page keeps your own pages from competing with each other, and it tells you which pages to build first: usually the ones closest to a decision. My SaaS website design page shows the same plan with the structured data each page uses.

Use case pages: the job your buyer needs done

A features page lists what the product does. A use case page starts from the buyer's problem and shows how the product solves it, in their words. "Dispatch software for HVAC companies" and "how to schedule technicians across two branches" are use case searches; "drag-and-drop scheduling board" is a feature.

A good use case page names the problem, shows the product doing that job (real screens, not stock photos), answers the objections that buyer has, and links to the features that make it work. For Daywright, a concept site I built for fictional dispatch software, the product itself is on the page as screens built in HTML and CSS, and every page leads to the demo.

Integration pages that say something real

Buyers search for "[your product] [tool they use] integration" because they need to know it fits their stack. Each integration worth mentioning deserves a page that says what syncs, in which direction, how setup works, and what it can't do.

Be careful with templates here. It is tempting to generate a hundred pages that differ only by the tool's name. Google's spam policies list "creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy" as a form of doorway abuse. Ten integration pages with real detail beat a hundred with a logo swapped.

Comparison and alternatives pages, done fairly

"[Competitor] alternative" and "[you] vs [competitor]" searches reach buyers who are ready to switch, which makes them some of the most valuable pages a SaaS site can have. They are also the pages most likely to go wrong, because they make claims about someone else's product.

In the US, the FTC's Statement of Policy Regarding Comparative Advertising "encourages the naming of, or reference to competitors," as long as the comparison is truthful and non-deceptive, and it has supported comparisons "where the bases of comparison are clearly identified." In the UK, the CAP Code's rules on comparisons with identifiable competitors say a comparison "must objectively compare one or more material, relevant, verifiable and representative feature" of the products, and must not mislead about either one.

In practice, that means a fair comparison page:

  • compares features and prices you can show, with the date you checked them;
  • says plainly where the other product is the better fit;
  • links to the source for every claim about the competitor;
  • gets updated when either product changes.

That honesty is also what makes the page convincing. A buyer who is comparing will check, and a page that admits its trade-offs earns more trust than one that wins every row.

A SaaS pricing page that answers the questions

"[Product] pricing" is one of the few searches that include your name, and the people making it are close to a decision. A pricing page that says "contact sales" and nothing else sends them back to the comparison sites.

Write down what each plan costs and includes, and answer the questions buyers usually have to ask: what counts as a user or a seat, setup fees, contract length, what happens at the end of a trial, and how to cancel. On the Daywright concept, the pricing page shows prices per technician with a monthly and yearly switch, and its FAQ covers who counts as a technician, setup fees, contracts and the trial.

Structured data helps search engines read the details. Google's guide to SoftwareApplication structured data says it helps "to better display your app details in Google Search results," and that you "must include" either an aggregateRating or a review property for that rich result. If you don't have genuine ratings yet, describe the product and its offers accurately anyway, and don't invent a rating to qualify. My guide to what schema markup is explains the types in plain English.

Docs and guides that earn their place

Your help docs answer the questions your users search for every day, and a clean, fast docs section gives those searches a home on your own site. Treat it as part of the marketing site's page plan, not an afterthought on a separate tool nobody maintains.

For blog posts and guides, Google's guide to creating helpful, reliable, people-first content is the best filter I know. It asks whether your content "clearly demonstrate[s] first-hand expertise and a depth of knowledge" and whether it provides "original information, reporting, research, or analysis." It also lists a warning sign: "Are you producing lots of content on many different topics in hopes that some of it might perform well in search results?"

A software company has an advantage here. You know how your customers do the job, you see the problems in support tickets, and you can show the product solving them. Write the guides only you could write, about the problems your product solves, and link each one to the use case page that fits.

Technical basics for a SaaS marketing site

Many SaaS teams build the marketing site with the same JavaScript framework as the app. That can work, but it adds steps before search engines see the content. Google's JavaScript SEO basics explain that Google processes JavaScript sites in three phases (crawling, rendering and indexing) and say "server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers."

The same guide gives two rules worth checking on any SaaS site:

  • Real links: "Google can only discover your links if they are <a> HTML elements with an href attribute." Navigation built only from buttons and scripts gives Google no links to follow.
  • Real addresses: use the History API instead of fragments, so each page has its own address rather than a part after a # sign.

The simplest answer is a marketing site of plain, pre-built HTML pages that link to the app, which is how I build them. The DueStamp marketing site scored 100 on mobile speed in a Lighthouse lab test before launch. If your current site is slow or has pages missing from Google, the speed and technical SEO sprint finds and fixes those first.

A SaaS SEO strategy in five steps

  1. Research the searches. List the problems, jobs, tools and competitors your buyers search for, with search volumes, and mark which ones are close to a decision.
  2. Plan the pages. Give each search worth winning one page, and decide how they link: use cases to features, comparisons to pricing, guides to use cases.
  3. Build the decision pages first. Pricing, the main use cases and the comparisons buyers already search for usually bring in leads soonest.
  4. Get the foundations right. Pre-built HTML, real links, a sitemap, structured data that matches the page and fast pages on a phone.
  5. Add guides and docs steadily. A few pages a month, each one written from real product knowledge, each one linked to the page that sells.

SEO for a new product takes months, not weeks, so start with the pages closest to a decision and measure from day one. My guide on how long it takes a new website to rank sets realistic expectations.

More questions

Is it legal to name competitors on comparison pages?

In the US and the UK, generally yes, when the comparison is fair. The FTC encourages naming competitors when comparisons are truthful and non-deceptive, and the UK CAP Code asks for objective comparisons of material, relevant, verifiable and representative features. Check the rules where you sell, and keep every claim sourced and dated.

Do we need SoftwareApplication structured data?

It helps Google read your product details, and it is quick to add to the home and pricing pages. For Google's software app rich result you must include a rating or review property, so only add those if they come from genuine reviews.

Can our marketing site use the same framework as our app?

It can, as long as search engines get real HTML pages with real links and their own addresses. Google says server-side or pre-rendering is still a great idea because it makes sites faster for users and crawlers. Plain, pre-built pages that link into the app are the simplest way to get there.

Should we hire an SEO agency or a web designer for SaaS SEO?

Whoever you hire, the page plan and the build have to be done together, because the pages that rank are the pages that get built. I plan and build both, from the keyword research to the launch checks, on a growth site or a redesign that keeps your rankings.

Sources

  1. Creating helpful, reliable, people-first content, Google Search Central
  2. Understand the JavaScript SEO basics, Google Search Central
  3. Software app (SoftwareApplication) structured data, Google Search Central
  4. Spam policies for Google web search, Google Search Central
  5. Statement of Policy Regarding Comparative Advertising, Federal Trade Commission
  6. Comparisons with identifiable competitors, Advertising Standards Authority (CAP Code)

Keep reading

Tell me about your website

A 20-minute video call, no slides and no pressure. Bring your current site or your plan, and you'll leave with the three changes I'd make first, whether or not we work together.

Chat