SaaS landing page website content checklist
A SaaS landing page has to say who the product is for, show it working and give a price or a clear next step. Real screenshots, customer permission to use names and a pricing page that is still changing cause most of the delay.
Where to start
- Pricing. Pricing is the most argued section and shapes the layout, so settle the plan structure before design.
- Hero and positioning. The headline and the primary call to action set the page, and the founder can answer in one meeting.
- Brand and legal. Logo files and tracking choices are quick to send and need to be known before the first design.
- Proof and customers. Permissions from customers take the longest to gather, so start the requests early.
- Integrations and security. Security claims need documents, so ask for them while the design is in progress.
The checklist
Hero and positioning
The top of the page decides whether a visitor stays, and it fails when the headline describes a category instead of a customer and a job.
- Product name as written Short text, requiredSpell it with the exact capitalisation and spacing you want, such as 'Ledgerly' or 'LEDGERLY'. Say if there is a tagline that always travels with the name.
- One-sentence value proposition Short text, requiredName the customer and the job in plain words, for example 'Invoicing for freelance designers who bill in more than one currency.' Skip 'all-in-one platform'.
- Who the product is for Long text, requiredDescribe the buyer and the user, their job title, company size and the problem that makes them search. Write what you hear on sales calls, in their words.
- Hero product screenshot Image upload, requiredA real screen from the app with demo data and no customer names or emails visible. At least 2400 pixels wide, light and dark versions if you ship both.
- Primary call to action Single choice, requiredPick the one button most visitors should press. Every section of the page repeats it.Start free trialBook a demoSign up freeGet early accessTalk to sales
- Signup or demo booking link Link, requiredThe address of the signup page or the calendar that books demos. Test it in a private window, because redirects often break there.
Features
Visitors skim for the one feature that solves their problem, so features need names that match the app and a screenshot each.
- Top three features with names Long text, requiredUse the exact names that appear in the app. For each, write one sentence on the problem it removes, with a number only if you can show where it came from.
- Feature screenshots Image upload, requiredThree to six screens, each showing one feature at work, with demo data. Capture them at the same browser width so they sit together on the page.
- Full feature list for comparison File uploadA spreadsheet or document listing every feature by plan. The designer builds a comparison table from it, so mark which features are in beta.
- Product demo video LinkA YouTube, Vimeo or Loom link to a walkthrough of under two minutes. Check the video is public and has captions.
- Known limits to state Long textWhat the product does not do yet, such as missing integrations or a region it does not support. Visitors who find out after signing up are the ones who cancel.
- Roadmap items to mention Long textOnly features with a date the team will stand behind. Anything vaguer stays off the page.
Pricing
Visitors scroll to price early, and a pricing section that is still being argued about internally is the most common reason a launch slips.
- Plans, prices and limits File upload, requiredA table with each plan's name, price, billing period, currency and limits, such as seats or projects. Mark which plan you want to highlight.
- Billing options offered Multiple choice, requiredTick the ways a customer can pay today. The page shows only these.MonthlyAnnual with discountPer seatUsage-basedCustom enterprise quote
- Free plan or trial terms Long text, requiredLength of the trial, whether a card is needed and what happens at the end. Visitors check this before they click.
- Enterprise price shown Yes or no, requiredIf no, say what the page shows instead, such as 'Contact sales', and who answers that form.
- Cancellation and refund policy Long text, requiredHow a customer cancels, when access ends and when refunds apply. Check the wording matches your terms of service.
- Checkout or billing page link LinkThe address of the checkout from Stripe, Paddle or your own system. Say who owns the account so the designer can ask for test access.
Proof and customers
Customer names and quotes persuade more than any copy, and they go missing because nobody asked the customers.
- Customer logos File uploadVector logos (SVG or PDF) of customers who agreed in writing to be shown. Send each customer's brand page link if their logo rules are strict.
- Written permission to show customer names Yes or no, requiredConfirm each customer shown has agreed in writing. An email thread counts, so keep it where the team can find it.
- Customer quotes Long textTwo to four quotes with name, job title and company, each approved by the person quoted. Short, specific quotes beat long praise.
- Case study documents File uploadFinished case studies as PDF or Word. If they do not exist, name the customers you would ask for one.
- Numbers and claims with sources Long textAny figure on the page, such as users, time saved or uptime, with the date and where it came from. A figure without a source stays off.
- Review site profiles LinkYour G2, Capterra or Product Hunt page, if the rating is public and recent. Skip a profile with fewer than a few real reviews.
Integrations and security
Buyers and their IT teams check integrations and security before a trial turns into a purchase, so the page needs facts they can verify.
- Integrations list Long text, requiredEach integration's name, whether it is native or through Zapier, and one line on what it does. Mark any still in beta.
- Integration logos or brand pages LinkLinks to each partner's brand or press page, so the designer uses their approved logo files.
- Security certifications held Multiple choice, requiredTick only what you hold today with a report or certificate you could show a buyer. Check the rules where you operate before using any badge.SOC 2 Type IIISO 27001Data processing agreement availableHIPAA supportSingle sign-onNone yet
- Security or trust page link LinkThe page that describes encryption, backups and access control, if one exists. If not, say who writes it.
- Where customer data is hosted Short text, requiredThe cloud provider and region, such as 'AWS in Frankfurt'. Buyers in regulated industries ask this first.
- Status page address LinkThe public page showing uptime and incidents. Link it from the footer so a buyer can see your record.
Support and FAQ
A short, honest FAQ removes the questions that sales calls keep repeating, and it needs to come from the people who answer them.
- Top questions from sales and support Long text, requiredThe eight questions you hear most, each with the answer you give. Use the real questions from email, not a list the team imagined.
- Support channels and hours Multiple choice, requiredTick every channel customers can use today and note the hours in the next field if they differ by plan.EmailLive chatPhoneCommunity forumHelp centre articlesDedicated account manager
- Help centre or docs link LinkThe address of the help site. Link to the home page of the docs and not to a single article.
- What happens after signup Long textThe first week for a new customer: onboarding email, setup steps and who helps. Visitors want to know how fast they get value.
Brand and legal
Logo files, fonts and the legal footer are asked for last and needed first, so they hold up the final review.
- Logo files File upload, requiredSVG files of the full logo, the icon alone and a version for dark backgrounds. A PNG export from a slide deck will look soft on large screens.
- Brand colours Colour, requiredThe primary and accent colours as hex codes from your design system or app. If the app and the marketing site use different blues, say which wins.
- Brand fonts FontThe typefaces in the app and slide deck, and whether you hold a web licence. If you use a free font, name the foundry.
- Terms of service and privacy policy links Link, requiredThe live addresses of both documents. If they are still being written, say who is drafting them and the target date.
- Analytics and tracking tools in use Multiple choice, requiredTick every tool that will run on the site, so the designer can set up a consent banner that matches.Google AnalyticsPostHogPlausibleSegmentHotjarMeta pixelLinkedIn Insight tagNone yet
- Company legal name and address Short text, requiredThe registered company name, number and address as they appear on your incorporation papers. Check the rules where you operate for what the footer must show.
What clients get stuck on
Screenshots with real customer data
Founders send screenshots from production, with customer names visible. Ask for a demo account filled with plausible data and capture every screen from it at the same width.
Customer logos without permission
A logo wall is common and often unapproved. Ask for the email that granted permission for each customer, and remove any that cannot be shown.
Pricing that is still moving
Ask who decides price and when it is final. If the answer is 'after launch', design the section with placeholders and keep the plan names separate from the numbers.
Security claims with no document
Badges and 'bank-grade' lines appear without a report behind them. Ask for the certificate or audit summary for every claim before it is written on the page.
Metrics with no source
Figures on users or time saved come from a slide the team remembers. Ask for the dashboard or the study, with the date, and leave out any number that cannot be traced.
Copy the checklist
Plain Markdown you can paste into a doc or an email.
# SaaS landing page website content checklist
## Hero and positioning
- [ ] Product name as written (Short text, required)
- [ ] One-sentence value proposition (Short text, required)
- [ ] Who the product is for (Long text, required)
- [ ] Hero product screenshot (Image upload, required)
- [ ] Primary call to action (Single choice, required)
- [ ] Signup or demo booking link (Link, required)
## Features
- [ ] Top three features with names (Long text, required)
- [ ] Feature screenshots (Image upload, required)
- [ ] Full feature list for comparison (File upload)
- [ ] Product demo video (Link)
- [ ] Known limits to state (Long text)
- [ ] Roadmap items to mention (Long text)
## Pricing
- [ ] Plans, prices and limits (File upload, required)
- [ ] Billing options offered (Multiple choice, required)
- [ ] Free plan or trial terms (Long text, required)
- [ ] Enterprise price shown (Yes or no, required)
- [ ] Cancellation and refund policy (Long text, required)
- [ ] Checkout or billing page link (Link)
## Proof and customers
- [ ] Customer logos (File upload)
- [ ] Written permission to show customer names (Yes or no, required)
- [ ] Customer quotes (Long text)
- [ ] Case study documents (File upload)
- [ ] Numbers and claims with sources (Long text)
- [ ] Review site profiles (Link)
## Integrations and security
- [ ] Integrations list (Long text, required)
- [ ] Integration logos or brand pages (Link)
- [ ] Security certifications held (Multiple choice, required)
- [ ] Security or trust page link (Link)
- [ ] Where customer data is hosted (Short text, required)
- [ ] Status page address (Link)
## Support and FAQ
- [ ] Top questions from sales and support (Long text, required)
- [ ] Support channels and hours (Multiple choice, required)
- [ ] Help centre or docs link (Link)
- [ ] What happens after signup (Long text)
## Brand and legal
- [ ] Logo files (File upload, required)
- [ ] Brand colours (Colour, required)
- [ ] Brand fonts (Font)
- [ ] Terms of service and privacy policy links (Link, required)
- [ ] Analytics and tracking tools in use (Multiple choice, required)
- [ ] Company legal name and address (Short text, required)
Questions about this checklist
How long should a SaaS landing page be?
As long as it takes to answer the buyer's questions, usually six to eight sections. A product that needs a security review before purchase needs more detail than a self-serve tool a visitor tries in minutes.
Should a SaaS landing page show prices?
Yes for self-serve products, because visitors leave pages that hide the number. For enterprise-only products, show a starting point or the plan structure, and say who answers the sales form.
Can we use mock-ups instead of screenshots?
Use a mock-up only if the real screen is not ready, and label the section as an example. Buyers compare the page with the trial, and a mismatch costs more trust than a plain screenshot.
Related checklists
Mobile app
A mobile app site has to show the app on a phone, link to the right store and answer privacy and support questions before the stores ask. The usual delays are store listing assets, a privacy policy address and the real pricing.
Developer tools
A developer tool site has to get an engineer from the home page to a working install in minutes, with code that runs as written. The delays come from sample code nobody tested, benchmark claims and docs owned by another team.
API product
An API product site has to show a working request and response, explain how to get a key and state limits, prices and uptime in plain terms. Most delays come from docs owned by engineering, SLA figures and unclear rate limits.