FREEFirst project with us? Your landing page design is on the house.See the offer

Pricing

How to structure a SaaS pricing page

A SaaS pricing page in six sections: plans, who each is for, a comparison table, FAQ, proof and a CTA per plan. Plus prices in the HTML and honest schema.

By Abdul QuadirUpdated 2026-11-108 min read
TL;DR
  • Use six sections in this order: plans, who each plan is for, a comparison table, an FAQ, proof, and a CTA for each plan.
  • Show a price for every plan a buyer can start alone. For quoted plans, say what drives the price.
  • A monthly and yearly toggle should only switch what is visible. Both prices belong in the page.
  • Keep prices, the table and the FAQ in the HTML the server sends, because not every crawler or AI tool runs JavaScript.
  • Add Offer schema only for prices shown on the page, and keep plans in a CMS so one edit updates the card, the table and the schema.

The short answer

A SaaS pricing page works best in six sections, in this order: the plans with prices, who each plan is for, a comparison table, an FAQ, proof, and a next step for each plan. Show a price wherever a buyer can start alone, and say what drives the quote where they cannot. Keep every price in the HTML the server sends, so search engines and AI tools can read it. Build the plans in a CMS, so marketing can change a price without a developer.

The rest of this post takes each part in turn.

The six sections, in order

A buyer on a pricing page asks the same questions in roughly the same order. The page should answer them in that order.

  1. Plans. Three or four cards, each with a name, a price, the billing period and one line on what you get. The price is the largest thing on the card.
  2. Who each plan is for. One sentence per plan in the buyer's words: "For a team of up to 10 sending its first campaigns." This does more than a feature list, because buyers pick by situation, not by feature count.
  3. Comparison table. Every feature and limit, plan by plan, for the people who want the detail.
  4. FAQ. The billing and contract questions sales hears every week.
  5. Proof. Real customer logos, quotes or reviews, close to the decision.
  6. A CTA per plan. Each plan gets its own next step, repeated under the table.

Our own pricing page follows the same idea for services: cards with prices first, then a plan comparison, a section on which option fits, and the questions at the end.

Plans and who each is for

Keep the cards easy to compare. Same order of information on each one, same length of feature list, the same unit after every price (per user per month, per month, per year).

  • Name plans by who they suit, or add the line that says so. "Starter" tells a buyer little. "Starter, for one team" tells them where they belong.
  • List what changes. On each card, lead with "Everything in the plan before, plus" and then the three to five things that are new.
  • Mark one plan as the usual choice only if it is true for most of your customers.
  • Put limits on the card. Seats, projects, usage. Limits are what push a buyer from one plan to the next, so hiding them in the table costs you questions later.

If the price depends on seats, a small calculator helps. Our guide to a seat-based pricing calculator covers the rules and the build.

Show a price or say contact sales

Both, in most cases. We looked at this in our study of pricing pages on the Forbes Cloud 100 (checked 10 November 2026). Of the pricing pages we could read, 68% show at least one price, 78% point bigger buyers to sales, and 66% have an FAQ on the page. Self-serve plans with a quoted tier on top is the common shape.

A simple rule:

  • Show a price for any plan a buyer can start without talking to you.
  • Use contact sales for plans that really are quoted. Then say what drives the quote: seats, usage, support level, security reviews. A buyer, and an AI tool describing you, can still explain how you charge.
  • Do not hide a price you have. If the plan costs the same for everyone, a "Talk to us" button only adds a step.

If you have a free plan or a trial, say which it is and what happens at the end of it.

The monthly and yearly toggle

A toggle is a small thing that often goes wrong. A short checklist:

  • Pick one default and state it. If the default is yearly, the card must say "billed yearly" next to the price.
  • Show the price per month in both views, so the two are easy to compare.
  • Say the saving in plain words, such as "2 months free", and make sure the sum is right.
  • Put both prices in the page. The toggle should only change which one is visible, not fetch or work out a number.
  • Use a real button or switch that works with a keyboard, and keep the choice when the visitor scrolls to the table.

Selling in more than one currency adds one more switch. Our post on local currency pricing shows how to pick a default and let the visitor change it.

Table, FAQ, proof and a CTA per plan

The table. Group rows under short headings (core features, limits, security, support). Keep the plan names and prices visible while the visitor scrolls. On phones, show one or two plans at a time with a switch, not a table that scrolls sideways. Build it as a real HTML table with header cells, so screen readers and crawlers can read which value belongs to which plan.

The FAQ. Answer what stops a purchase:

  • Can I change plan or cancel, and what happens to my data?
  • What counts as a seat or a unit of usage?
  • What happens if I go over a limit?
  • Do you offer refunds, invoices, or discounts for charities and startups?
  • Which taxes apply?

Write each answer in two or three sentences, and keep the answers in the page, not loaded on click. Google no longer shows FAQ rich results, so the reason to do this is the buyer and the AI tools that read the page, not a search feature.

Proof. Put proof where the doubt is. A row of customer logos under the plans, one or two short quotes near the table, and review scores if you have them on a public review site. Use only real names and real numbers, with permission. Our glossary entry on social proof lists the forms that work.

A CTA per plan. Give each plan its own button, with a label that says what happens next:

  • Free plan: "Start free".
  • Paid self-serve plan: "Start trial" or "Buy now", whichever is true.
  • Quoted plan: "Talk to sales", with a line on how long a reply takes.

Repeat the buttons under the comparison table, so a visitor who read every row does not have to scroll back up.

Keep prices in the raw HTML

Many pricing pages draw their numbers with JavaScript after the page loads. Google can run JavaScript, but its own guide says rendering happens in a later step and a page can wait in the queue. The same guide says server-side or pre-rendering is still a great idea, because it is faster for users and crawlers and because not all bots can run JavaScript.

So the safe pattern is:

  • The default plan names, prices, currency and billing period are in the HTML the server sends.
  • Scripts only switch what is shown: monthly or yearly, one currency or another.
  • The comparison table and the FAQ answers are in the HTML too.

To check, open the page source in your browser (not the inspector) and search for one of your prices. If it is not there, a tool that does not run scripts cannot see it. Our study above also records, site by site, whether the price is in the raw HTML. For a wider check, run the page through our free AEO checker.

Product and Offer schema, only where accurate

Schema markup can describe your plans to search engines, but only add what is true and visible. Three points from Google's own documentation:

  • Mark up what the reader can see. Google's structured data guidelines say not to mark up content that is not visible on the page, and to keep the information up to date. A price in the schema that differs from the price on the card breaks both rules.
  • Product markup is for single products. Google's product snippet guide says product rich results only support pages that focus on a single product, or variants of the same product. A product needs a name plus a review, a rating or an offer, and an offer needs a price. Google recommends adding the currency as well.
  • Software app markup needs real ratings. Google's software app guide requires a name and either a rating or a review, and says to set the price to 0 if the app is free. Do not add ratings you cannot show on the page.

In practice: one Offer per plan that has a public price, with the price and currency exactly as shown. No Offer with a made-up number for a quoted plan. Google also says it does not guarantee that structured data will appear in results, so treat schema as a clear description, not a promise. You can draft the markup with our schema generator.

Build it in a CMS so marketing can change prices

Prices change more often than page designs. If each number is typed into the layout in three places, one of them will be missed. Keep each plan as one item in the CMS instead.

A plan item usually needs these fields:

FieldExampleUsed by
NameTeamCard, table, schema
Who it is forFor teams of up to 10Card
Monthly priceA number, no symbolCard, table, schema
Yearly priceA number, no symbolCard, table
Quoted planOn or offSwaps the price for "Contact sales"
Feature listShort linesCard
Button label and linkStart freeCard, table
Order1, 2, 3Card, table

The cards, the table header and the schema all read the same item, so one edit updates every place the price appears. Store prices as numbers and add the symbol in the layout, so a second currency is a new field, not a rewrite. On Webflow that is a plans collection in the Webflow CMS. On Astro and Sanity it is a plan document the page reads at build time. After any price change, publish, then check the card, the table and the page source.

What to do next

Open your pricing page and check it against the six sections. Then view the source and search for a price. Those two checks find most of the problems. If the page needs a rebuild, see Webflow development or send us your pricing page and we will tell you what we would change.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Pricing page, Core Web Vitals

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Six, in this order: the plans with prices, who each plan is for, a comparison table, an FAQ, proof, and a clear next step for each plan.

Show a price for every plan a buyer can start alone. Use contact sales for plans that really are quoted, and say what drives the quote, such as seats, usage or support level.

Pick one default and put both prices in the page. The toggle only changes which one is visible. Show the per-month price, the billing period and the saving in plain words.

Not every crawler or AI tool runs JavaScript. A price that is in the HTML the server sends can be read by all of them. A price drawn later by a script can be missed.

Only where it is accurate. Mark up prices that are visible on the page, keep them up to date, and do not invent a price for a quoted plan. Schema does not guarantee a rich result.

Keep each plan as an item in the CMS with fields for name, prices, features and button. The page, the table and the schema all read those fields, so one edit updates everything.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.