SaaS comparison page template

Most SaaS comparison pages fail in the first 80 words. They open with a paragraph about how choosing the right tool is a big decision, bury the verdict below a 24 row feature table, and win every single row. Nobody believes that page, including the buyer who already uses the competitor and came to see if switching is worth the pain.

Below is the structure we use, block by block, with example copy at two honesty levels so you can see the difference in tone. Copy the blocks, fill them, and keep the claims log.

The block order, and why the verdict goes above the table

Eight blocks. The order is not negotiable, because it maps to how both buyers and answer engines read the page.

The verdict goes above the table because that is the block an AI answer engine lifts. A model summarising “Product A vs Product B” pulls a self contained paragraph that names both products and states a conclusion. A feature table gives it nothing quotable. This is the same logic driving every other bottom of funnel page you ship.

Block 1 and 2: the H1 pattern and the verdict

The H1 takes one of three patterns and nothing else: {Us} vs {Them}, {Us} vs {Them}: Which {Category} Fits {Segment}, or {Them} vs {Us} ({Year} Comparison). Do not get creative. The query is the query.

Then the verdict, written to stand alone if someone reads only that paragraph.

Level two names a segment, concedes onboarding speed and free tier, gives a numeric threshold and still closes. It is also the only version that survives a competitor reading it with a lawyer.

Block 3: who each product is best for

Two short columns, four bullets each, written in the buyer’s language rather than yours. This block does most of the qualification work on the page.

Pick real differentiators. Team size, deployment model, compliance requirements, technical skill of the admin, budget band, integration dependencies. Avoid anything that reads as a slur dressed as a fit statement, because buyers notice and it undermines the concession you just made.

Block 4: the feature table with a date column

This is the block that keeps you out of trouble. Four columns minimum, and the fourth one is what almost nobody ships.

The date column does three jobs. It signals maintenance to readers, it gives you a defensible position if the competitor changed something after your check, and it forces your own team to actually look before publishing. Keep the rows to eight or twelve. A 30 row table is where credibility goes to die, and it is also where the reader stops scrolling.

Block 5: pricing, handled carefully

State published list prices only, name the plan tier, and add the date. Never publish a competitor’s negotiated or rumoured pricing, and never publish a number a customer told you in a sales call.

Add one sentence naming what is not included in the headline price on each side, because that is the comparison buyers actually want and almost nobody provides. Seat minimums, annual commitment discounts, overage charges, the cost of the SSO tier. If your own pricing looks worse in that light, say so and explain what the extra buys. A page that hides your weakness on price gets caught in the first sales call anyway.

Block 6: switching and migration

On a vs page the reader is frequently a current customer of the competitor. Feature parity is not their objection. Losing three years of history is.

The comparison pages playbook covers how to staff and route those migration requests once they start arriving.

Block 7 and 8: third party proof, FAQ and CTA

Pull two or three verbatim review quotes from G2 or Capterra, one of which should be mildly critical of you. Include the reviewer role and the review date. Never edit a review quote beyond trimming, and never quote a review that names a competitor unfavourably without linking the original.

The FAQ block carries the long tail queries the main body does not answer: migration timelines, contract length, data residency, what happens to your data if you cancel. Five to seven questions, 40 to 70 word answers, each one written to work as a standalone snippet. Real examples of all of this working live are collected in the comparison page examples library.

The JSON-LD to attach

Keep it narrow. FAQPage on the FAQ block, Organization and WebPage on the document, BreadcrumbList for the path.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Can I migrate my Beta data to Acme?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. Projects, comments, attachments and custom fields import through the native importer. Attachment version history does not transfer."
    }
  }]
}

What to avoid: Review or AggregateRating schema describing a competitor. You are an interested party, the ratings are not user generated, and Google’s structured data guidelines treat self serving review markup as a violation. Product schema stays on your own product page with your own real prices.

The claims log

One row per competitor statement anywhere on the page. This lives in a sheet next to the page, not in someone’s head.

Superlative claims (best, fastest, most secure) need either a named third party source or removal. Comparative claims (faster than, cheaper than) need a measurement method stated somewhere on the page. Factual claims (supports SAML on the Business plan) need the source URL and nothing more.

Legal wording that keeps the page defensible

This is general practitioner guidance, not legal advice, and your counsel gets the final read.

In the United States, nominative fair use permits naming a competitor’s trademark to refer to that competitor, provided you use no more of the mark than necessary, avoid their logo and styling, and do nothing suggesting sponsorship or endorsement. False or misleading comparative claims create Lanham Act exposure, so truth and substantiation are the whole defence. In the EU, Directive 2006/114/EC permits comparative advertising where it compares goods meeting the same needs, compares verifiable and material features objectively, and does not discredit the competitor’s marks.

Three wording habits that reduce risk: attribute every comparative statement to a dated source in the visible copy, use “as of” phrasing on anything time sensitive, and add a standing line near the table reading “All competitor information sourced from publicly available documentation on the dates shown. Trademarks are the property of their respective owners.”

Keep a takedown response ready. If a competitor emails, the reply is a link to your claims log entry with the source URL and screenshot, plus a correction within five business days if they are right. Teams with a claims log resolve these in one exchange. Teams without one usually pull the page.

What to do next

Build one page with this structure against your single highest intent competitor query, then measure it for 60 days before templating the rest. Once the structure proves out, the same block order carries into your alternatives pages and your integration pages, and if you are generating dozens of comparison URLs from a data source, the field mapping belongs in a programmatic page brief instead of this template.

To decide which competitor to build first, check where you already appear against them using the share of voice calculator, and read the strategy behind page selection in the SaaS comparison pages guide and the wider SaaS SEO pillar.