Original research ยท October 2026

Where B2B SaaS publishes comparison pages - and who never does

A study of 479 YC-backed B2B software companies: every homepage and sitemap crawled for competitor-comparison pages, 8,717 candidate URLs fetched and classified by title, 1,683 vendor-vs-vendor comparisons identified. Three in ten companies publish one. The decisions that separate publishers from non-publishers are size, category and commitment - in that order.

479
companies studied
30.9%
publish comparisons
95% CI 26.9-35.2%
51.2%
publish at 200+ staff
vs 24.0% at 1-10
20
pages: 90th percentile
median 3, max 264

Crawled October 2026 across 479 companies. Every count on this page is computed from the saved crawl; method, accuracy and limits are documented below.

Executive summary

Comparison pages - the "X vs Y" and "X alternatives" pages that catch buyers mid-shortlist - are not a standard part of B2B SaaS publishing. In a study of 479 YC-backed B2B software companies, 148 (30.9%, 95% CI 26.9-35.2%) published at least one page comparing themselves to a named rival. The majority, 331 companies, published none at all.

Three patterns organize the result. First, publishing is a scale decision. The rate climbs monotonically across company size: 24.0% of companies with 1-10 employees, 27.4% with 11-50, 36.9% with 51-200, and 51.2% with 200+ - a 2.1x spread. Category effects exist but are flatter: sector rates run from 0.0% (Supply Chain and Logistics) to 48.3% (Analytics). Second, publishers treat comparison content as a library, not a page. The median publisher maintains 3 pages; the 90th percentile maintains 20, and the top ten companies produce 57.3% of every comparison page in the sample. Third, most apparent comparison pages are not comparisons. 77.0% of candidate URLs were concept articles ("lead vs prospect"); only 19.3% were vendor-vs-vendor pages, which is why URL counting alone mis-measures this entire category.

For buyers and sales teams, comparison libraries are a minority signal concentrated among larger, more established vendors. For content teams, the data says to plan comparison pages as a structured, maintained asset set - 74.3% of real comparison pages live on permanent paths - rather than as individual blog posts.

The six findings

01

Bigger companies publish; small ones rarely do

51.2% of companies with 200+ employees publish a comparison page against 24.0% with 1-10 employees (31/129). The ladder climbs monotonically across all four bands. Competitive pages follow size.

02

Category matters less than size

0.0% in Supply Chain and Logistics (0/18) to 48.3% in Analytics (14/29), against 30.9% overall. The extremes separate from each other (permutation p=0.001); the spread is narrower than the size ladder.

03

It is a library decision, not a page

Median 3 pages per publisher, but the top 3 companies write 31.8% of all comparison pages and the top 10 write 57.3%. 4 companies publish more than 100 each.

04

Most "-vs-" URLs are not comparisons

77.0% of candidate URLs are concept articles ("lead vs prospect"). Only 19.3% are vendor-vs-vendor. Any study counting URL patterns measures blog strategy, not competitive positioning.

05

The rivalry spreads across a long tail

213 distinct vendors are named across 1,854 target mentions. The top 10 absorb just 29.5%, and 216 of 496 vendor pairs - 43.5% - are contested by two or more companies.

06

Comparisons live on structured pages

74.3% sit on /compare/, /alternatives/ or /vs/ paths rather than 432 blog posts (25.7%). 1103 of 1683 pages (65.5%) put the publisher's own product in the frame.

The strategic read: comparing yourself against rivals is something companies start doing as they scale into a category fight - and they treat it as an asset library, not a one-off argument.

Three archetypes, five tiers

Every company in the sample falls into one of six tiers. The tiers are defined by page count, benchmarked against the publishers' own distribution.

ArchetypeCompaniesShareBenchmarkProfile
Non-publishers33169.1%-No page we could classify. The default state, at every size.
The One-Pager479.8%1 pageExactly one comparison page - usually against the nearest rival.
The Occasional5110.6%2-5 pagesTwo to five pages. Compete selectively, at the terms the buyer already searches.
The Committed377.7%6-20 pagesSix to twenty pages. A maintained set covering the shortlist buyers actually type.
The Programmatic91.9%21-100 pagesTwenty-one to a hundred pages. Comparison content as an acquisition program.
The Library40.8%100+ pagesMore than a hundred pages - a page for every tool a prospect might name.

Reading down the tiers: 20.5% of the whole sample sits in the light-touch tiers (one to five pages), while 2.7% has moved to program depth (13 companies). The middle - 37 companies at six to twenty pages - is where a maintained comparison set starts looking like strategy rather than opportunism.

Benchmarks: pages per publisher

Percentile distribution across the 148 publishing companies, for teams that need to know what "normal" looks like.

PercentilePages maintained
P251
P50 (median)3
P758
P9020
P99147
Maximum264
Pages per publishing company
1 page47 companies2-5 pages51 companies6-20 pages37 companies21-100 pages9 companiesMore than 1004 companies
Median 3, mean 11.4, maximum 264: the mean is nearly 3.8x the median. 15.7% of all comparison pages come from a single company; the top three together produce 31.8%, the top ten 57.3%.

The top 25 comparison publishers in the sample

Every company in the 479-company frame that maintains 13 or more vendor-comparison pages, showing the split between direct 1-on-1 self-comparisons and third-party comparison pages.

Company (domain)ArchetypeTotal pages1-on-1 / 3rd-partyRivals namedPrimary path
Bird (bird.com)The Library264231 / 3312/de-de/
Courier (courier.com)The Library1474 / 14315/integrations/
Basedash (basedash.com)The Library12528 / 979/vs/
Deepnote (deepnote.com)The Library1136 / 1075/compare/
Rootly (rootly.com)The Programmatic6967 / 24/sre/
Rippling (rippling.com)The Programmatic6551 / 1416/blog/
Taskade (taskade.com)The Programmatic5754 / 325/compare/
Airbyte (airbyte.com)The Programmatic4638 / 814/data-engineering-resources/
Polytomic (polytomic.com)The Programmatic4036 / 44/versus/
Deel (deel.com)The Programmatic3936 / 35/blog/
OpenReplay (openreplay.com)The Programmatic3829 / 94/compare/
SigNoz (signoz.io)The Programmatic3838 / 05/comparisons/
PostHog (posthog.com)The Programmatic3525 / 1020/compare/
Hightouch (hightouch.com)The Committed2020 / 05/compare-cdps/
Jet Admin (jetadmin.io)The Committed201 / 199/blog/
SuperTokens (supertokens.com)The Committed195 / 143/blog/
LiveFlow (liveflow.com)The Committed1917 / 24/blog/
Miniloop (miniloop.ai)The Committed190 / 1915/blog/
HackerRank (hackerrank.com)The Committed1818 / 05/writing/
Cosmic (cosmicjs.com)The Committed1812 / 69/blog/
Mixpanel (mixpanel.com)The Committed1515 / 04/compare/
Motion (usemotion.com)The Committed1515 / 07/blog/
Webflow (webflow.com)The Committed1414 / 08/vs/
AssemblyAI (assemblyai.com)The Committed1414 / 08/blog/
Algolia (algolia.com)The Committed1313 / 05/competitors/

Two distinct playbooks appear inside the top 25. Direct-siege publishers (rootly.com, taskade.com, signoz.io, hightouch.com, hackerrank.com, mixpanel.com, algolia.com) put their own product in nearly every title. Third-party matrix publishers (courier.com at 143 of 147 pages, deepnote.com at 107 of 113, basedash.com at 97 of 125, polytomic.com, jetadmin.io, miniloop.ai) publish head-to-head and alternatives pages for rival pairs to intercept category search before the buyer knows the publisher's name. Several library leaders (bird.com, basedash.com, openreplay.com) also multiply page counts by localising comparison slugs across German, Spanish, French, Arabic and Japanese.

Who publishes

By company size - the strongest pattern

Publishing rate by team size, with 95% confidence intervals
0%20%40%60%80%100%1-10 employees24.0%n=12911-50 employees27.4%n=19051-200 employees36.9%n=111200+ employees51.2%n=41
The 200+ interval (36.5-65.7%) sits clear of the 1-10 interval (17.5-32.1%), so the top and bottom bands separate even on 41 large companies. The two middle bands overlap each other.
Team sizePublishers / totalRate95% CI
1-10 employees31 / 12924.0%17.5-32.1%
11-50 employees52 / 19027.4%21.5-34.1%
51-200 employees41 / 11136.9%28.5-46.2%
200+ employees21 / 4151.2%36.5-65.7%

By sector

SectorPublishers / totalRate95% CI
Analytics14 / 2948.3%31.4-65.6%
Infrastructure20 / 4544.4%30.9-58.8%
Security9 / 2536.0%20.2-55.5%
Finance and Accounting11 / 3135.5%21.1-53.1%
Marketing12 / 3435.3%21.5-52.1%
Productivity12 / 3435.3%21.5-52.1%
Engineering, Product and Design31 / 9034.4%25.4-44.7%
Sales6 / 2227.3%13.2-48.2%
B2B15 / 6124.6%15.5-36.7%
Recruiting and Talent3 / 1323.1%8.2-50.3%
Operations6 / 2722.2%10.6-40.8%
Human Resources4 / 2119.0%7.7-40.0%
Retail2 / 238.7%2.4-26.8%
Supply Chain and Logistics0 / 180.0%0.0-17.6%

Analytics leads at 48.3% (n=29); Supply Chain and Logistics trails at 0.0% (n=18), with no publisher in the sample. The extremes separate from each other (permutation p=0.001) but most sector intervals overlap the overall 30.9% - size explains more of the variance than category does.

Cross-cut, read cautiously. Inside the generic "B2B" sector, publishing rises from 12% (n=16) at 1-10 employees to 40% (n=20) at 51-200 - the same size ladder, within one sector. Cells this small are indicative only; they are shown because the direction is consistent with the full-sample pattern, not because they are significant on their own.

Anatomy of a comparison page

How the 1,683 real comparison pages are built.

Where comparison pages live
1251432
  • Structured path (/compare/, /alternatives/, /vs/)125174.3%
  • Blog, learn or resources path43225.7%
74.3% sit on permanent structured URLs - pages meant to be maintained and linked from navigation, not published once.
Target vendors named per page
1 vendor1519 pages90.3% of pages2 vendors158 pages9.4% of pages3 vendors5 pages0.3% of pages4 vendors1 pages0.1% of pages
1519 of 1683 pages (90.3%) name a single rival; 164 name two or more. Roundups that compare several vendors are a minority format.
Page framingPagesShare
Publisher's own product in the frame110365.5%
Two other vendors compared58034.5%

34.5% of comparison pages compare two vendors neither of which is the publisher - editorial comparisons that capture buyers researching alternatives. Those pages are competitive as content, not as positioning.

The competitive landscape

The 1,683 comparison pages name 213 distinct vendors over 1,854 target mentions.

Concentration of target mentions
Top 5 targets18.7%18.7% of mentionsTop 10 targets29.5%29.5%Top 25 targets50.9%50.9%Top 50 targets70.6%70.6%
Concentration is moderate: the ten most-targeted vendors absorb 29.5% of mentions. 216 of 496 vendor pairs - 43.5% - are attacked by two or more different companies, so comparison effort spreads across a long tail rather than piling on one incumbent.
Top 15 competitive anchors by number of distinct attacking publishers
Google (Cloud / BigQuery / Workspace)32 pubs119 pages (55 1-on-1, 64 3rd-party)Microsoft (Azure / Teams / BI)15 pubs43 pages (20 1-on-1, 23 3rd-party)Salesforce13 pubs29 pages (20 1-on-1, 9 3rd-party)HubSpot10 pubs15 pages (7 1-on-1, 8 3rd-party)Firebase8 pubs20 pages (6 1-on-1, 14 3rd-party)Amazon Redshift8 pubs13 pages (9 1-on-1, 4 3rd-party)Google BigQuery8 pubs11 pages (9 1-on-1, 2 3rd-party)Databricks7 pubs45 pages (7 1-on-1, 38 3rd-party)Zapier7 pubs14 pages (11 1-on-1, 3 3rd-party)Datadog6 pubs24 pages (23 1-on-1, 1 3rd-party)Elasticsearch6 pubs23 pages (19 1-on-1, 4 3rd-party)ZoomInfo6 pubs15 pages (7 1-on-1, 8 3rd-party)Cloudflare6 pubs7 pages (5 1-on-1, 2 3rd-party)FlutterFlow6 pubs7 pages (5 1-on-1, 2 3rd-party)LinkedIn Sales Navigator6 pubs7 pages (5 1-on-1, 2 3rd-party)
Ranked by how many distinct companies in the 479-company frame publish at least one comparison page naming the vendor. Page counts differ sharply from publisher counts where a single library builder publishes dozens of localized or pairwise pages.

The 30 broad competitive anchors (targeted by 4+ SaaS publishers)

Incumbents and category leaders that four or more separate companies in the sample position against directly.

Target vendorCategoryAttacking publishersTotal pages1-on-1 / 3rd-partySample publishers in frame
Google (Cloud / BigQuery / Workspace)Cloud, Data & Workspace3211955 / 64airbyte.com, algolia.com, assemblyai.com +29
Microsoft (Azure / Teams / BI)Cloud, Productivity & BI154320 / 23basedash.com, deepgram.com, deepnote.com +12
SalesforceCRM & Revenue132920 / 9algolia.com, chatwoot.com, close.com +10
HubSpotCRM & Marketing10157 / 8chatwoot.com, close.com, dyspatch.io +7
FirebaseApp Backend & Messaging8206 / 14airbyte.com, courier.com, growthbook.io +5
Amazon RedshiftCloud Data Warehouse8139 / 4airbyte.com, basedash.com, hightouch.com +5
Google BigQueryCloud Data Warehouse8119 / 2airbyte.com, basedash.com, evidence.dev +5
DatabricksData & AI Lakehouse7457 / 38airbyte.com, deepnote.com, evidence.dev +4
ZapierWorkflow Automation71411 / 3assemblyai.com, hotglue.com, jetadmin.io +4
DatadogObservability & APM62423 / 1feroot.com, growthbook.io, posthog.com +3
ElasticsearchSearch & Analytics Engine62319 / 4airbyte.com, algolia.com, influxdata.com +3
ZoomInfoB2B Sales Intelligence6157 / 8apollo.io, miniloop.ai, popl.co +3
CloudflareEdge, CDN & Security675 / 2assemblyai.com, cosmicjs.com, feroot.com +3
FlutterFlowNo-Code / App Builder675 / 2draftbit.com, glideapps.com, jetadmin.io +3
LinkedIn Sales NavigatorSales Prospecting675 / 2miniloop.ai, plai.io, trellus.ai +3
TwilioCommunications APIs (CPaaS)58561 / 24bird.com, courier.com, plivo.com +2
ADPPayroll & HCM52923 / 6checkr.com, deel.com, getontop.com +2
AirtableConnected Apps & Database52010 / 10glideapps.com, jetadmin.io, noloco.io +2
ReplitCloud IDE & AI App Builder598 / 1draftbit.com, glideapps.com, retool.com +2
WebflowVisual CMS & Web Platform587 / 1cosmicjs.com, taskade.com, webiny.com +2
VantaCompliance & Trust Center565 / 1feroot.com, rippling.com, skypher.co +2
VercelFrontend Cloud & AI Gateway554 / 1assemblyai.com, fly.io, jetadmin.io +2
Zoho CRMCRM & Office Suite555 / 0chatwoot.com, close.com, getswipe.in +2
QuickBooksSMB Accounting & Payroll42925 / 4finlens.app, hotglue.com, liveflow.com +1
VonageCommunications APIs (CPaaS)42512 / 13bird.com, courier.com, plivo.com +1
MongoDBDocument Database41714 / 3airbyte.com, influxdata.com, secoda.co +1
ClickHouseAnalytical Database41515 / 0airbyte.com, posthog.com, questdb.com +1
WordPressCMS41210 / 2cosmicjs.com, miniloop.ai, taskade.com +1
Oracle NetSuiteERP & Financial Management4104 / 6blixo.com, hypotenuse.ai, liveflow.com +1
ZendeskCustomer Support & Ticketing465 / 1assembly.com, chatwoot.com, fivetran.com +1

Programmatic and single-publisher siege targets (20+ pages from 1-3 publishers)

Why raw page counts and publisher breadth diverge: 16 vendors appear on 20 to 52 comparison pages each despite being targeted by only one to three companies in the frame.

Target vendorCategoryAttacking publishersTotal pages1-on-1 / 3rd-partyPublishing domains in frame
PagerDutyIncident Management15251 / 1rootly.com
InfobipCommunications APIs (CPaaS)24533 / 12bird.com, courier.com
SinchCommunications APIs (CPaaS)24522 / 23bird.com, courier.com
Google ColabData Science Notebooks1392 / 37deepnote.com
QlikBusiness Intelligence2393 / 36airbyte.com, deepnote.com
MailgunTransactional Email API23511 / 24bird.com, courier.com
BandwidthCommunications APIs (CPaaS)23422 / 12bird.com, courier.com
PlivoCommunications APIs (CPaaS)23422 / 12bird.com, courier.com
MetabaseBusiness Intelligence3268 / 18basedash.com, explo.co, whaly.io
Twilio SendGridTransactional Email API32613 / 13bird.com, courier.com, usewaypoint.com
OmniBusiness Intelligence2245 / 19basedash.com, getdot.ai
OneSignalPush & Customer Messaging1241 / 23courier.com
ThoughtSpotSearch & AI Analytics3245 / 19basedash.com, explo.co, getdot.ai
Lightdashdbt-Native BI2234 / 19basedash.com, getdot.ai
ExploEmbedded Analytics1224 / 18basedash.com
Atlassian OpsgenieIncident Alerting12120 / 1rootly.com
Verification note on named targets. Matched titles for every named vendor above were audited against classified.json. Eleven single-word dictionary tokens that collided with ordinary English or technical terms in page titles (runtime, vibe, books, signals, panels, async, expectations, sharpe, replicas, traces, computing) were removed from the named tables.

What it means, by audience

FOR VENDORS

The band you are in sets the expectation

At 51-200 or 200+ employees, 36.9% and 51.2% of your peers publish comparisons, so a buyer's shortlist increasingly contains rivals who do. Below 50 employees, publishing is a minority position (24.0-27.4%) and an option rather than a norm.

FOR CONTENT TEAMS

Plan a library on structured URLs

The benchmark for a serious program is 20 pages (P90 of publishers), and 74.3% of real comparison pages sit on permanent paths. Write to 3-page depth first (3 = median, 8 = P75), then extend toward the shortlist terms buyers actually type.

FOR SALES AND BUYERS

Absence is the normal signal

331 of 479 companies (69.1%) publish no comparison page at all, at every size. Treat a vendor's comparison library as a sign of category maturity, not as evidence that other vendors without one are hiding - and 34.5% of pages compare vendors that are both third parties, so read them as editorial too.

FOR RESEARCHERS

Do not count URLs; classify titles

77.0% of candidates were concept articles. Any method built on "-vs-" URL patterns would report numbers several times too high. Read the methodology before replicating the design.

How to act on it

  1. Size your ambition against the benchmark, not against competitor noise. If you are under 50 employees, 24.0-27.4% of peers publish comparison pages: a focused set beats a full library. At 51+, 36.9%+ do, and the buyer's shortlist increasingly assumes rival names exist.
  2. Build on structured paths. 74.3% of real comparison pages live on /compare/, /alternatives/ or /vs/ URLs. Put comparison content behind navigable, permanent URLs rather than dated blog slugs - it is how publishers keep them maintained.
  3. Commit to depth or don't start. Among publishers, P75 is 8 pages and P90 is 20. 13 of 479 companies went past twenty pages. Single-page efforts cluster at the bottom of the publisher distribution; plan the set of terms you will cover before publishing the first one.

Methodology

Pipeline

Crawl sitemaps + links479 frame domainsFilter comparison slugs8,717 candidate URLsFetch each pagetitle and h1 storedClassifybrand-dictionary matchon titlesHand-check a sample52-URL labelled pilot
Discovery ran across all 479 domains; classification matched page titles against the curated vendor dictionary, excluding the publisher's own brand and common English words.

Candidate classification

What the 8,717 candidate URLs turned out to be
16836711
  • Vendor-vs-vendor comparison168319.3%
  • Concept article or other671177.0%
  • Generic "vs competitors"1071.2%
  • Not a comparison candidate2162.5%
77.0% of candidates are concept articles ("ERP vs CRM"). Reading titles is the difference between measuring competitive positioning and measuring editorial themes - and the reason URL counting would overstate this category several times over.

Design

Cross-sectional crawl of 479 B2B software companies, October 2026. Candidate URLs discovered from every company's homepage links and sitemap, filtered by comparison pattern (/-vs-/, /compare/, /alternatives/, /versus/, -alternative-to). Every candidate was fetched and its page title classified against a curated vendor dictionary (1948 entries, built from the frame, the YC pool and a disclosed manual list). Classification requires a comparison marker AND a named vendor that is not the publisher's own brand and not an ordinary English word.

Definitions

Candidate URL
A URL matching a comparison pattern, discovered from homepage links or sitemaps. 8,717 fetched; 49 fetch failures excluded from classification.
Vendor comparison
A candidate whose title names a known vendor other than the publisher: the page compares actual products.
Publisher
A company from the frame with at least one vendor comparison. 148 companies.
Target
A vendor named in a comparison page. 213 distinct across 1,854 mentions.
Contested pair
A vendor pair compared by two or more different publishers. 216 of 496 pairs.

Accuracy

CheckSampleResultMeaning
Precision520.889 (16 of 18)One of the two false positives was itself a label error; effective precision is higher
Recall520.727Bounded by the curated vendor dictionary; misses are vendors not on the list
Independent double-code0not runOpen - single reviewer so far

Uncertainty

Confidence intervals are Wilson intervals on sample proportions; segment gaps tested with two-sided permutation tests (5,000 shuffles). These cover sampling error within this frame only - not classification error, and not the frame's selection bias.

Reproduce

Downloadable tables: publishers.csv (aggregate metrics), named-targets.csv (verified target vendors), and top-publishers.csv (all 148 publishing companies).

Disclosure and corrections

DataDab sells AI-visibility work and paid inclusion in its research pages. A research mention costs $400-$1,200. Payment does not change a figure in this study. DataDab is not part of the measured set. Corrections are published on the page; send factual corrections with the URL to amit@datadab.com.

python3 scripts/research/s3_discover_all.py # discover candidate URLs across the frame python3 scripts/research/s3_fetch_parallel.py # fetch titles for every candidate python3 scripts/research/s3_graph.py # classify and aggregate python3 scripts/research/build_s3_page.py # rebuild this page
Cite this study

Covering this research? Please link the primary source so readers can verify the data and methodology:

Markdown: [B2B SaaS Comparison Page Map 2026 by DataDab](https://www.datadab.com/research/saas-comparison-page-map/)

Disclosure: DataDab sells AI-visibility work and paid inclusion in its research pages. A research mention costs $400-$1,200. Payment does not change a figure in this study. DataDab is not part of the measured set. Corrections are published on the page (amit@datadab.com).

What this study does not show

  • Full target coverage. Recall 0.727 on the pilot; vendors outside the curated dictionary are invisible as targets.
  • Unlinked pages. Discovery reads homepage links and sitemaps; JavaScript-only navigation is missed. 49 fetch failures are excluded, not classified.
  • Quality or effect. Pages are counted, not read for accuracy; no traffic, ranking or revenue effect is claimed.
  • Market-wide claims. YC-backed companies only; single reviewer; no independent double-coding yet.
About this study. Crawled October 2026 across 479 YC-backed B2B software companies; 8,717 candidate pages fetched, 1,683 classified as vendor comparisons across 148 publishing companies and 213 target vendors. Method, accuracy, disclosure and limitations are documented above.