SaaS SEO: a playbook for B2B startups (2026)

Searches to plan around

Query patterns and the intent behind them. We don’t quote search volumes: check your own Search Console for the ones you already appear for.

• “[problem] software”, “tool to [job]”

  Category discovery

  The buyer knows the pain, not the vendors. Use-case pages that describe the job in their words win here, not feature pages.

• “best [category] for [team size or industry]”

  Shortlisting

  Results are usually listicles and review sites. You want to be on those lists, and to publish an honest one of your own.

• “[competitor] alternatives”, “[A] vs [B]”

  Switching

  Often typed by someone unhappy with an incumbent. High intent, and the page has to be fair or it won't convert.

• “[your product] [other tool] integration”, “connect [A] to [B]”

  Evaluation

  Buyers check that the tool fits their stack before trialling it. One page per real integration answers it.

• “[your product] pricing”, “… SSO”, “… SOC 2”

  Vendor due diligence

  Brand queries from procurement. If the answer isn't on your site, assistants and search results will quote a third party's guess.

• “how to [job] in [your product]”, “[job] template”, “[metric] calculator”

  Doing the job

  Customers and prospects who want the task done now. Docs and free tools answer these, and both can earn links and be quoted.

Page families that work

• Use-case and feature pages

  /use-cases/approval-workflows

  One page per job your product does, in the words buyers use: the problem, the steps in your product, a real screenshot and the limits. These answer the category-discovery searches. Skip a page if the only change from another one is the noun.

• Integration pages

  /integrations/hubspot

  One page per integration you actually support: what syncs, in which direction, setup steps and limits. Each page has facts no other page has, which is what keeps it indexable.

• Alternatives and X vs Y

  /compare/you-vs-incumbent

  Tables with real limits, prices and integration counts, plus a plain section on who should pick the competitor. A fair page is easier for a switcher to believe than an attack page. Our own alternatives and comparison pages show the format.

• Docs and help articles

  /docs/export-to-csv

  People search “how to [job] in [product]”, and the answer should be on your domain. One question per page, a plain title, numbered steps and a link to the feature page it belongs to. Make every navigation link a real link: Google only discovers links that are anchor elements with an href.

• Templates, calculators and free tools

  /templates/quarterly-okr-sheet

  Things a buyer can use before signing up. They earn links and bookmarks, and they rank for “[job] template” queries your product pages can't.

• Programmatic pages, done safely

  /integrations/[app]

  Pages generated from data you hold: one per real integration, template or role. Each needs facts of its own and a minimum bar; below it, don't publish, or noindex. That is what separates a page family from the scaled content abuse Google describes. The method is here.

Risky page types

• Industry × feature × city grids

  Pages like “CRM for dentists in Ohio” with the same body text are the pattern Google's doorway abuse policy describes: many pages built to rank for similar queries.

• Integration pages for integrations you don't own

  Hundreds of “[App] integration” pages that all say “connect via Zapier” add no facts. Google's scaled content abuse policy targets exactly this.

• AI-written posts at volume

  Google's guidance on generative AI content says using AI tools to generate many pages without adding value for users may violate its scaled content abuse policy, and asks you to fact-check AI output before it's published. A hundred generic “what is [term]” posts is that pattern.

Technical pitfalls

1. 1

   App routes indexed alongside marketing pages

   Login screens, empty dashboards and share links on the same host get crawled and dilute the site. Serve the app on its own subdomain or path, keep it out of the sitemap, and noindex shells that render nothing without a session.

2. 2

   Marketing pages rendered only in the browser

   Site builders and SPA frameworks sometimes ship an empty HTML shell. Google can render JavaScript, but its own docs still recommend server-side rendering or pre-rendering because it's faster and not every crawler runs JavaScript.

3. 3

   Docs and galleries built from click handlers

   A docs sidebar, an integration gallery or a “load more” button that works only through JavaScript click handlers can hide pages from crawlers. Google says it can only discover links that are anchor elements with an href attribute, so render real links and give every docs page its own URL.

4. 4

   A help center on a third-party subdomain

   Help platforms often ship default titles like “Article – Help Center” and duplicate articles per language. Fix titles, set canonicals, and link from help articles back to the product pages they describe.

5. 5

   Pricing that exists only in sales decks

   Even “from $X per seat” or a description of the pricing model gives search engines and assistants something true to quote. Without it, they quote a review site or a competitor's comparison.

6. 6

   Software markup you can't back up

   Google's software app markup needs a name, a price and either a rating or a review to be eligible for a rich result. Add it only with real ones, and don't mark up testimonials you collected yourself as independent reviews: Google's review snippet guidelines restrict self-serving reviews.

How AI assistants answer questions in this category

B2B questions put to an assistant tend to be shortlist questions: “what's a good [category] tool for a 20-person team that works with Salesforce?”. Assistants that search answer them by pulling listicles, review profiles, comparison pages and vendor pages, then summarising a shortlist. Google describes the same mechanism for AI Overviews and AI Mode as query fan-out: one question is split into related searches (pricing, integrations, alternatives) and supporting pages are picked from those. Google also says there is no special schema or AI file needed, only that pages are indexed and eligible for a snippet.

What tends to earn a citation

• A crawlable page that says plainly who the product is for, what it costs and what it integrates with, in text rather than images.
• Comparison tables with specific, dated facts (plan limits, integrations, hosting regions) that an assistant can lift without guessing.
• Listings and profiles on the third-party sites that get retrieved for shortlist questions, with the same one-line description you use on your own site.
• Help-center answers to the exact “can it do X?” questions buyers ask, one question per heading.

Check whether the AI crawlers you want can reach your site with our AI crawler checker.

Where links come from

• Partner marketplaces

  Most platforms you integrate with have an app or integration directory. A listing there is a relevant link and a referral channel from people already using that platform.

• SaaS directories and review sites

  Pick maintained, reviewed ones from the SaaS directories and software review sites lists. On review sites the listing matters less than honest reviews from real customers over time.

• Aggregated data from your own product

  If your product sees patterns across accounts (anonymised and with permission), a yearly report on them is the kind of original source other writers link to. Only publish numbers you can back up.

• A free tool next to your product

  A small calculator or checker for the job your product does earns links from people who will never read a feature page.

A 90-day plan

1. Days 1–30

   Foundations and inventory

   • –Verify the domain in Search Console and note your top 20 queries, brand and non-brand.
   • –Noindex app shells and remove them from the sitemap.
   • –Publish or fix the pricing, security and integrations index pages.
   • –List every real integration, your five most-compared competitors and the ten questions support answers most.

2. Days 31–60

   First page families

   • –Ship integration pages for the ten integrations customers use most, each with setup steps and limits.
   • –Publish three to five alternatives or X vs Y pages with dated fact tables.
   • –Write use-case pages for the two or three jobs customers name most, in their words.
   • –Submit to a handful of maintained SaaS directories and partner marketplaces.

3. Days 61–90

   Docs, a free tool and the Search Console loop

   • –Turn the most-asked support questions into docs pages, each linked to its feature page.
   • –Ship one free tool or template for the job your product does.
   • –Rewrite titles and descriptions on pages sitting at positions 5–20 with impressions but few clicks.
   • –Link help-center articles to the matching product and integration pages.

What to watch in Search Console

The Performance report gives clicks, impressions, CTR and average position by query, page, country, device and date. Clicks from Google's AI features are counted there too, under the Web search type (Google), and since August 31, 2026 the Generative AI performance report shows which pages get impressions in AI Overviews and AI Mode.

Non-branded impressions

Use the branded queries filter where Search Console offers it: Google says it is for top-level properties with enough query volume, so a young site may not see it yet. Brand clicks rise with sales activity; non-brand impressions tell you whether new pages are being found.

Integration and comparison pages in the Page indexing report

Filter the Page indexing report by sitemap or URL pattern. A family with many “Crawled – currently not indexed” pages is telling you the pages look too alike.

Pages at positions 5–20 with impressions

These are the cheapest wins: a better title often moves clicks more than a new article.

CTR on the pricing page for brand queries

If it's low, the search result is probably showing a stale or confusing snippet. Rewrite the title and description around what buyers want to know.

Trial or demo starts by organic landing page

Tag signups by the page they started on. A page with traffic and no signups needs a clearer next step, not more traffic.

Frequently asked questions

Launching one of these?

The launch guides for products in this playbook: where users find them, what to prepare and a 4-week timeline.

• Launch guideHow to launch a SaaS productA SaaS launch plan: where buyers find new software, what to prepare, a 4-week timeline, launch-day checklist and the…
• Launch guideHow to launch B2B SaaS for enterprise buyersLaunching SaaS to enterprise buyers: security review, cloud marketplaces, review sites and a 4-week plan built around…

Sources

Checked on October 8, 2026. Search patterns and page advice are our own judgement from running this playbook; we don’t quote search volumes or third-party statistics.

1. Google Search Central: JavaScript SEO basics
2. Google Search Central: Spam policies for Google web search
3. Google Search Central: Guidance on using generative AI content
4. Google Search Central: Software app structured data
5. Google Search Central: Review snippet structured data
6. Google Search Central: AI features and your website
7. Google Search Central blog: Introducing the branded queries filter in Search Console
8. Search Console Help: Page indexing report
9. Search Console Help: Performance report